Bug#1049422: transition: dbus-c++

[Bastian Germann]

Package: release.debian.org
Control: affects -1 + src:dbus-c++
X-Debbugs-Cc: [e-mail]
User: ***@packages.debian.org
Usertags: transition
Severity: normal

libdbus-c++-1-0v5 has been split in the experimental version 0.9.0-13 into
three packages containing each of the shared object files which were previously
all in libdbus-c++-1-0v5. libdbus-c++-1-0v5 did not gain dependencies on the
two other packages, so in my opinion, a transition is needed. The ABIs have
not changed, however.

I have just uploaded experimental version 0.9.0-14, which is the one that the
transition testing should target.

[Sebastian Ramacher]

Control: tags -1 moreinfo

Post by Bastian Germann
Package: release.debian.org
Control: affects -1 + src:dbus-c++
Usertags: transition
Severity: normal
libdbus-c++-1-0v5 has been split in the experimental version 0.9.0-13 into
three packages containing each of the shared object files which were previously
all in libdbus-c++-1-0v5. libdbus-c++-1-0v5 did not gain dependencies on the
two other packages, so in my opinion, a transition is needed. The ABIs have
not changed, however.

In that case libdbus-c++1-0v5 needs to gain dependencies for proper
upgrades from bookworm to trixie. please let us know once that is
fixed.

Cheers

[Thomas Uhle]

Dear maintainers,

unless a certain strict Debian rule formally enforces a transition, I
don't think that a transition is really necessary because still the only
packages depending on libdbus-c++-1-0v5 are ffado-dbus-server and
jami-daemon (cf. #1018772 [1]). I have double-checked both to be sure
that they only have a dependency on libdbus-c++-1.so.0 but not on
libdbus-c++-glib-1.so.0 or libdbus-c++-ecore-1.so.0. The only other
packages depending on these libraries are libdbus-c++-bin and
libdbus-c++-dev themselves which have updated dependencies in Debian
experimental.

Best regards,

Thomas Uhle


[1] https://bugs.debian.org/1018772#5

Post by Sebastian Ramacher
Control: tags -1 moreinfo

Post by Bastian Germann
Package: release.debian.org
Control: affects -1 + src:dbus-c++
Usertags: transition
Severity: normal
libdbus-c++-1-0v5 has been split in the experimental version 0.9.0-13 into
three packages containing each of the shared object files which were previously
all in libdbus-c++-1-0v5. libdbus-c++-1-0v5 did not gain dependencies on the
two other packages, so in my opinion, a transition is needed. The ABIs have
not changed, however.

In that case libdbus-c++1-0v5 needs to gain dependencies for proper
upgrades from bookworm to trixie. please let us know once that is
fixed.
Cheers
--
Sebastian Ramacher

[Thomas Uhle]

Dear maintainers,

as a brief update: I have just realized that currently jami-daemon is not
in trixie, and the version in experimental has switched from
libdbus-c++-1-0v5 to libsdbus-c++1. So as long as the version in bookworm
does not count, it is only ffado-dbus-server left that is not rebuilt when
building package dbus-c++. I still think that a binNMU is not necessary.

Best regards,

Thomas Uhle

Post by Thomas Uhle
Dear maintainers,
unless a certain strict Debian rule formally enforces a transition, I don't
think that a transition is really necessary because still the only packages
depending on libdbus-c++-1-0v5 are ffado-dbus-server and jami-daemon (cf.
#1018772 [1]). I have double-checked both to be sure that they only have a
dependency on libdbus-c++-1.so.0 but not on libdbus-c++-glib-1.so.0 or
libdbus-c++-ecore-1.so.0. The only other packages depending on these
libraries are libdbus-c++-bin and libdbus-c++-dev themselves which have
updated dependencies in Debian experimental.
Best regards,
Thomas Uhle
[1] https://bugs.debian.org/1018772#5