Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1225245

Bug#1088632: transition: hdf5

From pini@debian.org
Newsgroups linux.debian.bugs.dist, linux.debian.devel.release
Subject Bug#1088632: transition: hdf5
Date 2024-12-22 18:00 +0100
Message-ID <JWxtb-1BUV-53@gated-at.bofh.it> (permalink)
References (9 earlier) <JWheF-1r7F-3@gated-at.bofh.it> <JWsWt-1zgT-3@gated-at.bofh.it> <JWsWt-1zgT-1@gated-at.bofh.it> <JNTCx-cigm-3@gated-at.bofh.it> <JWsWt-1zgT-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Le 2024-12-22 12:59, pini@debian.org a écrit :
> Le 2024-12-22 09:07, Paul Gevers a écrit :
>> On 22-12-2024 00:36, pini@debian.org wrote:
>>>> There are a few autopkgtest regressions. I briefly looked at fast5 
>>>> and it looks like its examples need changes for the new API. I 
>>>> haven't looked at the others. Can you take a look and file bugs as 
>>>> appropriate?
>> 
>>> * fclib: autopkgtest is successful on my box
>> 
>> I assume you test in a pure unstable/sid environment. Indeed on ci.d.n 
>> fclib also passes on unstable. Most of the times that means we're 
>> missing a *versioned* (test-) Depends or Breaks somewhere. The test 
>> infrastructure tries to test in a testing/trixie environment with as 
>> little as possible from unstable. Do you have any idea what that could 
>> be?
>> 
>>> * fenics-dolfinx: autopkgtest is successful on my box
>> 
>> Same.
>> 
>>> * gatb-core: autopkgtest is successful on my box
>> 
>> Same.
>> 
>>> * petsc: autopkgtest is successful on my box
>> 
>> Same.
> 
> Should I upload a new HDF5 revision with versioned `Breaks:` against 
> these packages?

As I understand it the failing test for fclib depends on libfclib-dev 
which brings the transitioning libhdf5-dev. This leads to an executable 
linked to both libhdf5_serial_hl.so.100 and libhdf5_serial_hl.so.310, 
causing the failure.

What is the best practice to prevent this?

I thought about adding `Breaks: libfclib-dev (<< 3.1.0+dfsg-3+b4)` to 
libhdf5-dev but it seems inappropriable because the binNMU number is not 
the same for all architectures.

Best,
_g.

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

Bug#1088632: transition: hdf5 Gilles Filippini <pini@debian.org> - 2024-11-28 21:50 +0100
  Bug#1088632: transition: hdf5 pini@debian.org - 2024-12-08 15:50 +0100
  Bug#1088632: transition: hdf5 pini@debian.org - 2024-12-10 22:20 +0100
  Bug#1088632: transition: hdf5 pini@debian.org - 2024-12-22 00:40 +0100
  Bug#1088632: transition: hdf5 pini@debian.org - 2024-12-22 13:10 +0100
    Bug#1088632: transition: hdf5 pini@debian.org - 2024-12-22 18:00 +0100

csiph-web