Bug#801898: marked as done (RM: player -- RoQA; Maintainer MIA; RC-buggy for more than two years; not in stable or testing)

Sun, 15 Nov 2015 02:07:35 -0800 

Your message dated Sun, 15 Nov 2015 10:03:33 +0000
with message-id <[email protected]>
and subject line Bug#801898: Removed package(s) from unstable
has caused the Debian Bug report #801898,
regarding RM: player -- RoQA; Maintainer MIA; RC-buggy for more than two years; 
not in stable or testing
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.)


-- 
801898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801898
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message --- 
Package: ftp.debian.org
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

During Debconf I worked on player for the python-support-removal. Player FTBFS 
at that time
due to the gcc transition which was an addition reason to contacted the 
maintainer.
player has an RC bug for more than 2 years already¹, without any action as far 
as I can see
anywher (except NMU which didn't target that issue). Due to the RC bug, Player 
is
not available in stable or testing. The maintainer didn't respond to my e-mail 
(of two months
ago, cc-ed to the MIA team). The maintainer has a long record in the MIA 
database.

Please remove player from Debian unstable.

Popcon peaks at 166 (there are 29 binary package involved)
Lintian reports 3519 errors and 52 warnings (mostly privacy breach issues)

¹ http://bugs.debian.org/726561

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJWH/uOAAoJEJxcmesFvXUKIZ0H/39NDtyH+zKEVHs245LxiPLN
5rTXWRkQ19l2DXoONHfjz7X2TGc9Lh2QB/M3IaWPDrHjDG4PGk8RBqukV2mBxOoG
j+FkxuPPk/VW/HEEz0MI4+YtVvXmICKA+Gtt6DXW9+bCv/RS/eVhia+zbCu/1IZG
8xNg2gxF435SoT02O/jFC+uB4sS6M21Z1dohygePbZADmF/mmjC3fctg1CRIDCSz
QNth942v1muWaL5EZcnsAKKcoQ43sDvf+rbNZhuWVxGwdIf7hkfMiJVPRaX7L2hm
B0bePOJJpMOtnnJ1/8te+tv1rWNTTy8bxkoQZArqZ7WjaY7i73FjmU95Vjr0s/E=
=QLl7
-----END PGP SIGNATURE-----

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

liblodo3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
liblodo3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
libplayerc++3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
libplayerc++3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, 
mips, mipsel, powerpc, ppc64el, s390x
libplayerc3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
libplayerc3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
libplayercommon3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, 
mips, mipsel, powerpc, ppc64el, s390x
libplayercommon3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, 
mips, mipsel, powerpc, ppc64el, s390x
libplayercore3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
libplayercore3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, 
mips, mipsel, powerpc, ppc64el, s390x
libplayerdrivers3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, 
mips, mipsel, powerpc, ppc64el, s390x
libplayerdrivers3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, 
mips, mipsel, powerpc, ppc64el, s390x
libplayerinterface3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, 
mips, mipsel, powerpc, ppc64el, s390x
libplayerinterface3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, 
i386, mips, mipsel, powerpc, ppc64el, s390x
libplayerjpeg3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
libplayerjpeg3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, 
mips, mipsel, powerpc, ppc64el, s390x
libplayertcp3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
libplayertcp3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, 
mips, mipsel, powerpc, ppc64el, s390x
libplayerwkb3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
libplayerwkb3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, 
mips, mipsel, powerpc, ppc64el, s390x
libpmap3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
libpmap3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
libwavefront-standalone3.0 | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, 
i386, mips, mipsel, powerpc, ppc64el, s390x
libwavefront-standalone3.0-dev | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, 
armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
    player | 3.0.2+dfsg-4.2 | source
python-playerc | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
robot-player | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x
robot-player-dev | 3.0.2+dfsg-4.2 | all
robot-player-doc | 3.0.2+dfsg-4.2 | all
ruby-playerc | 3.0.2+dfsg-4.2+b2 | amd64, arm64, armel, armhf, i386, mips, 
mipsel, powerpc, ppc64el, s390x

------------------- Reason -------------------
RoQA; Maintainer MIA; RC-buggy for more than two years; not in stable or testing
----------------------------------------------

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/801898

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.
Luca Falavigna (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to