Your message dated Thu, 22 Jun 2023 23:31:18 +0000
with message-id <[email protected]>
and subject line Bug#956787: Removed package(s) from unstable
has caused the Debian Bug report #956787,
regarding RM: gtk-sharp-beans -- RoQA; depends on gtk2; abandoned upstream; low
popcon
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.)
--
956787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956787
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gtk-sharp-beans
Version: 2.14.1-4
Severity: wishlist
User: [email protected]
Usertags: proposed-removal
I noticed gtk-sharp-beans while looking at the list of packages that
depend on the superseded library GTK 2.
gtk-sharp-beans appears to be a CLI (.NET) library that is no longer
depended on by anything in Debian >= buster. It depends on GTK 2, which
was superseded by GTK 3 in 2011. The upstream Github repository listed
as its home page appears to have been archived.
Is this library still maintained upstream? Is it sufficiently useful
to justify having it in Debian for use as a dependency of third-party
software, or should it be removed?
smcv
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gtk-sharp-beans | 2.14.1-4.1 | source
libgtk-sharp-beans-cil | 2.14.1-4.1 | all
libgtk-sharp-beans2.0-cil-dev | 2.14.1-4.1 | all
------------------- Reason -------------------
RoQA; depends on gtk2; abandoned upstream; low popcon
----------------------------------------------
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/956787
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.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
