Your message dated Fri, 01 Dec 2023 18:55:09 +0000
with message-id <[email protected]>
and subject line Bug#1057213: Removed package(s) from unstable
has caused the Debian Bug report #1057213,
regarding RM: haskell-diagrams-gtk -- ROM; obsolete
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 [email protected]
immediately.)
--
1057213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057213
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: haskell-diagrams-gtk
Severity: normal
User: [email protected]
Usertags: gtk2 oldlibs
Control: block 947713 by -1
This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.
GTK 2 was superseded by GTK 3 in 2011 (see
<https://bugs.debian.org/947713>). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.
GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.
A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html
Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.
A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.
Regards,
smcv
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
haskell-diagrams-gtk | 1.4-8 | source
libghc-diagrams-gtk-dev | 1.4-8+b2 | mips64el, s390x
libghc-diagrams-gtk-dev | 1.4-8+b3 | armhf, ppc64el
libghc-diagrams-gtk-dev | 1.4-8+b4 | arm64, armel, i386
libghc-diagrams-gtk-dev | 1.4-8+b5 | amd64
libghc-diagrams-gtk-doc | 1.4-8 | all
libghc-diagrams-gtk-prof | 1.4-8+b2 | mips64el, s390x
libghc-diagrams-gtk-prof | 1.4-8+b3 | armhf, ppc64el
libghc-diagrams-gtk-prof | 1.4-8+b4 | arm64, armel, i386
libghc-diagrams-gtk-prof | 1.4-8+b5 | amd64
------------------- Reason -------------------
ROM; obsolete
----------------------------------------------
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.
Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.
We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected].
The full log for this bug can be viewed at https://bugs.debian.org/1057213
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
