Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
The library package libgdk-pixbuf2.0-0 was recently (in early December)
split into libgdk-pixbuf-2.0-0 and the deprecated libgdk-pixbuf-xlib-2.0-0,
with a transitional libgdk-pixbuf2.0-0 that depends on both. Newly built
packages will depend on libgdk-pixbuf-2.0-0 and/or libgdk-pixbuf-xlib-2.0-0,
but binary packages that were built before December still depend on
what is now a transitional package.
This is a "soft" transition and does not need a flag-day or coordination:
if bullseye releases with this transition incomplete, the only practical
impact is that the deprecated libgdk-pixbuf-xlib-2.0-0 stays installed
on more systems.
If you're still willing to trigger binNMUs at this stage of the freeze,
reverse dependencies of libgdk-pixbuf2.0-0 could be rebuilt to drop the
dependency on the transitional package. Most of them will lose their
unnecessary indirect dependency on the deprecated library as a result.
A few packages that were most recently built shortly after the transition
might show as both "good" and "bad", because they depend on
"libgdk-pixbuf-2.0-0 | libgdk-pixbuf2.0-0". This is harmless and I don't
mind whether they get rebuilt or not.
Ben file:
title = "gdk-pixbuf";
is_affected = .depends ~ "libgdk-pixbuf2.0-0" | .depends ~
"libgdk-pixbuf-2.0-0" | .depends ~ "libgdk-pixbuf-xlib-2.0-0";
is_good = .depends ~ "libgdk-pixbuf-2.0-0" | .depends ~
"libgdk-pixbuf-xlib-2.0-0";
is_bad = .depends ~ "libgdk-pixbuf2.0-0";
Thanks,
smcv
