Package: libgpiod3
Version: 2.1-1~exp2
Severity: important

Hi,

I'm filing this as important, but this might warrant the serious bug
severity instead…

Your libgpiod3 package declares Breaks and Replaces against libgpiod2
and libgpiod2t64, but that doesn't make any sense to me: those packages
have different contents, so there's no actual conflict in there. Worse,
when SONAMEs get changed, library packages get their names changed to
*ensure* both the old and the new libraries can co-exist.

For reference, on amd64:

 - libgpiod2:
    /usr/lib/x86_64-linux-gnu/libgpiod.so.2.2.2
    /usr/lib/x86_64-linux-gnu/libgpiodcxx.so.1.1.2
    /usr/lib/x86_64-linux-gnu/libgpiod.so.2 -> libgpiod.so.2.2.2
    /usr/lib/x86_64-linux-gnu/libgpiodcxx.so.1 -> libgpiodcxx.so.1.1.2

 - libgpiod3:
    /usr/lib/x86_64-linux-gnu/libgpiod.so.3.1.1
    /usr/lib/x86_64-linux-gnu/libgpiodcxx.so.2.1.0
    /usr/lib/x86_64-linux-gnu/libgpiod.so.3 -> libgpiod.so.3.1.1
    /usr/lib/x86_64-linux-gnu/libgpiodcxx.so.2 -> libgpiodcxx.so.2.1.0


The current state of things make it impossible to deploy libgpiod3
(found in trixie) alongside libgpiod2 (found in bookworm), making it
harder than it should be to upgrade from bookworm to trixie.


Cheers,
-- 
Cyril Brulebois ([email protected])            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Reply via email to