Your message dated Fri, 13 Sep 2019 14:54:27 +0000
with message-id <e1i8mxv-0008eh...@fasolo.debian.org>
and subject line Bug#939529: Removed package(s) from unstable
has caused the Debian Bug report #939529,
regarding RM: gtg -- RoM; python2-only; dead upstream; low popcon; no rdeps
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 ow...@bugs.debian.org
immediately.)


-- 
939529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gtg
Severity: serious

By looking at the status of this package, several points are evidend:

* upstream abandoned its development
* its stack is python2-based, which Debian is trying to remove
* nobody is stepping up to keep this tool up to date

So, should we remove gtg from Debian? I'm opening this bug so people interested
in gtg can voice their opinion; if i dont hear back in a week with a valid
reason to keep it around, i'll convert this bug to RM.

Regards,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gtg depends on:
ii  python            2.7.16-1
ii  python-configobj  5.0.6-3
ii  python-dbus       1.2.8-3
ii  python-glade2     2.24.0-6
ii  python-gtk2       2.24.0-6
pn  python-liblarch   <none>
pn  python-notify     <none>
ii  python-xdg        0.25-5

Versions of packages gtg recommends:
ii  python-simplejson  3.16.0-1
ii  yelp               3.31.90-1

Versions of packages gtg suggests:
pn  bugz                 <none>
pn  python-appindicator  <none>
ii  python-cairo         1.16.2-1+b1
pn  python-cheetah       <none>
ii  python-dateutil      2.7.3-3
pn  python-evolution     <none>
pn  python-geoclue       <none>
pn  python-gnomekeyring  <none>
pn  python-launchpadlib  <none>
pn  python-suds          <none>

--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

       gtg |    0.3.1-4 | source, all

------------------- Reason -------------------
RoM; python2-only; dead upstream; low popcon; no rdeps
----------------------------------------------

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 939...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/939529

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to