Bug#904020: libpetsc-real3.9-dev: dependency on libopenmpi-dev not strict enough

Paul Gevers elbrus at debian.org
Wed Jul 18 12:52:39 BST 2018


Package: libpetsc-real3.9-dev
Version: 3.9.3+dfsg1-2

Dear Drew,

On 17-07-18 13:20, Graham Inggs wrote:
> Hi Drew
> 
>> On Tue, 17 Jul 2018, Drew Parsons wrote:
>>> The configuration of ci.debian.org is not consistent.   A failing test
>>> of deal.ii is marked on
>>> https://ci.debian.net/packages/d/deal.ii/testing/amd64/
>>> as triggered by petsc/3.9.3+dfsg1-2, but the test log shows that in
>>> fact libpetsc-real3.8-dev is used for the test
>>> (i.e. petsc/3.8.4+dfsg1-2+b2).  So unsurprisingly the test fails, which
>>> disrupts migration of the new petsc 3.9 (throwing it out to 10 days
>>> instead of 5). The failure itself occurs since the different petsc were
>>> built against different openmpi.
> 
>>From the times in the logs, it appears that the test was run before
> deal.ii's binNMU happened [1].
> So the delay is only temporary.
> 
> As soon as the test is successful, the migration delay will disappear.
> 
> I've requested a retry for that test, so it should happen soon.

Although Graham was right with his timing regarding binNMU of deal.ii,
there is more going on. I really don't want to offend you, but I wonder
if you read the actual error message carefully? (It took Graham and me
quite some time to figure this out and to understand it).

'''
PETSc was configured with one OpenMPI mpi.h version but now appears to
be compiling using a different OpenMPI mpi.h version
'''

This message comes from petsc, so, whatever header file got installed
was blessed by petsc.

Apart from petsc/3.8.4+dfsg1-2+b2 also petsc/3.9.3+dfsg1-2 packages were
installed (so both of them), so I think the trigger did it's job.

I believe that the current failure is really pointing at a bug in the
dependencies of libpetsc-real3.9-dev which probably need tighter
restrictions on libopenmpi-dev looking at the message. If
libpetsc-real3.9-dev would require libopenmpi-dev from unstable, I
believe everything would be all right. I'll trigger a test like the one
that currently fails, but with libopenmpi-dev from unstable to prove my
hypothesis.

Paul

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20180718/3a0224c3/attachment.sig>


More information about the debian-science-maintainers mailing list