[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#981141: marked as done (transition: gdk-pixbuf binNMUs to drop transitional package)

Your message dated Tue, 8 Feb 2022 11:19:12 +0000
with message-id <YgJRsFWRZyeTxsI8@momentum.pseudorandom.co.uk>
and subject line Re: Bug#981141: transition: gdk-pixbuf binNMUs to drop transitional package
has caused the Debian Bug report #981141,
regarding transition: gdk-pixbuf binNMUs to drop transitional package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
981141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981141
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@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

--- End Message ---
--- Begin Message --- 
On Tue, 18 Jan 2022 at 20:58:30 +0100, Paul Gevers wrote:
> The tracker only reports some 14 sid only packages of which most have FTBFS
> bugs reported. I think we can close this bug and move the tracker to the
> archive, do you agree?

Yes please, thanks for following up on this.

The transitional libgdk-pixbuf2.0-dev and libgdk-pixbuf2.0-0 are
built by the deprecated src:gdk-pixbuf-xlib, so they will automatically
disappear if it's removed.

    smcv

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: