Your message dated Mon, 29 Nov 2021 18:27:43 +0000
with message-id <e1mrlnp-0005ev...@fasolo.debian.org>
and subject line Bug#992319: Removed package(s) from unstable
has caused the Debian Bug report #992319,
regarding RM: nekobee -- RoQA, unmaintained, RC-buggy, dead-upstream, python2
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.)


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

nekobee is currently RC buggy with 2 RC bugs, (one being a gcc 10 and one being
a python-removal-bug;  upstream seems dead as well with only a minor commit last
year.
The Debian package has seen the last upload 5 years ago, and missed bullseye,
so it looks unmaintained from here.

I guess this software is EOL and should probably be removed from the archives.

Dear maintainer,

If you disagree, just close this bug.
If you agree, please reassign this bug to ftp.d.o to make the RM happening.
I will do the latter in exactly 3 months from now if there is no answer on this 
bug.

--  
tobi

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

   nekobee | 0.1.8~repack1-1 | source, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
   nekobee | 0.1.8~repack1-1+b1 | amd64

------------------- Reason -------------------
RoQA, unmaintained, RC-buggy, dead-upstream, python2
----------------------------------------------

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

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

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