Hi, On 21-10-2024 06:57, Alastair McKinstry wrote:
I'll prepare this now for debian/experimental. Is there an example of good practice with breaks/replaces/provides when doing two transitions in one release, ie libopenmpi3->libopenmpi3t64->libopenmpi40 ?
You can't add a provides, otherwise you wouldn't need the rename.Normally library packages as co-installable (that's why we want new binary packages with SONAME matching names) and you don't need any breaks/replaces.
Having said that, I think you can just add a Breaks/Replaces on libopenmpi3t64 in same way you already have it for libopenmpi3.
And looking at the content of libopenmpi3t64, I'm wondering if you're not violating Policy 8.1 [1] (the names of the files suggest the libraries don't have the same SONAME):
"""If you have several shared libraries built from the same source tree, you may lump them all together into a single shared library package provided that all of their SONAMEs will always change together.
""" Paul[1] https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#run-time-shared-libraries
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature