Your message dated Mon, 14 Oct 2019 05:01:52 +0000
with message-id <e1ijsus-0009rt...@fasolo.debian.org>
and subject line Bug#935745: Removed package(s) from unstable
has caused the Debian Bug report #935745,
regarding RM: python-pushy -- RoQA; python2 only; dead upstream; low popcon;
last upload in 2015
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.)
--
935745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935745
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pushy
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: py2removal
Hello,
i'm looking at python-pushy as it depends on python-paramiko; one of bullseye
goals is to remove python2 and python-pushy
* is dead upstream
* last upload was in 2015, and NMU (one of the only 2 uploads)
* python2-only
* low popcon
If i dont hear anything back in 10 days, I'll file a RM bug for this package.
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 python-pushy depends on:
ii python 2.7.16-1
ii python-paramiko 2.6.0-1
python-pushy recommends no packages.
python-pushy suggests no packages.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
python-pushy | 0.5.1-1.1 | source
python-pushy | 0.5.1-1.1+b1 | amd64, arm64, armel, armhf, i386, mips64el,
mipsel, ppc64el, s390x
------------------- Reason -------------------
RoQA; python2 only; dead upstream; low popcon; last upload in 2015
----------------------------------------------
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 935...@bugs.debian.org.
The full log for this bug can be viewed at https://bugs.debian.org/935745
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 ---
