Hi,

On 22-12-2024 17:45, p...@debian.org wrote:
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?

Nothing really, this occasionally happens during transitions and we don't have an appropriate solution for this yet. It's similar to a smooth transition where not all binNMU's have migrated and some binaries link to the old and new library at the same time (e.g. via different dependencies).

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.

Unless somebody else has a better idea, let's just ignore for now.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to