On Wed, 15 Feb 2023, Bastian Germann wrote:
On Wed, 8 Feb 2023 18:58:49 +0100 Thomas Uhle
<thomas.u...@mailbox.tu-dresden.de> wrote:
+ Put libdbus-c++-ecore-1.so.* and libdbus-c++-glib-1.so.* in their own
binary packages libdbus-c++-ecore-1-0 and libdbus-c++-glib-1-0 resp.
to avoid pulling in e.g. Ecore libraries (and their dependencies) on
systems where these libraries are not needed. (Closes: 1018772)
It is too late for bookworm. So please target experimental with the new binary
packages.
If you want the other changes to get into bookworm, you should separate them
into their own unstable revision.
Thanks a lot for your response and having a look into the changes.
After reverting the split of the package libdbus-c++-1v5 into seperate
packages and assuming the other updates make their way into bookworm just
in time, would it then make sense to wait until the release of bookworm to
prepare another revision of dbus-c++ with this remaining change targeted
for unstable or would it then also be required to upload to experimental
at first?
Should I already change "UNRELEASED" into "unstable" in debian/changelog
or shall I leave this as it is?
Best regards,
Thomas Uhle
