Bug#801071: Should this package be removed?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#801071: Should this package be removed?

Moritz Muehlenhoff
Package: minirok
Severity: serious

Should minirok be removed? It hasn't seen an upload
since 2009, it's dead upstream (Debian maintainer is also
upstream), popcon usage is marginal and it relies on
obsolete gstreamer 0.10. Plus, there's plenty of alternatives
in the archive.

Please address the outstanding bugs or reassign this to
ftp.debian.org for removal.

Cheers,
        Moritz

Reply | Threaded
Open this post in threaded view
|

Bug#801071: Should this package be removed?

Adeodato Simó-4

retitle 801071 Please remove minirok from the archive reassign 801071 ftp.debian.org stop

Hello—

I agree with Moritz: let’s remove minirok from the archive.

I’m maintainer and upstream. I don’t have intentions to work on it any further.

Thanks,

Moritz Muehlenhoff [hidden email] writes:

Package: minirok Severity: serious

Should minirok be removed? It hasn't seen an upload since 2009, it's dead upstream (Debian maintainer is also upstream), popcon usage is marginal and it relies on obsolete gstreamer 0.10. Plus, there's plenty of alternatives in the archive.

Please address the outstanding bugs or reassign this to ftp.debian.org for removal.

Cheers, Moritz

Reply | Threaded
Open this post in threaded view
|

Processed: Re: Bug#801071: Should this package be removed?

Debian Bug Tracking System
Processing commands for [hidden email]:

> retitle 801071 Please remove minirok from the archive
Bug #801071 [minirok] Should this package be removed?
Changed Bug title to 'Please remove minirok from the archive' from 'Should this package be removed?'
> reassign 801071 ftp.debian.org
Bug #801071 [minirok] Please remove minirok from the archive
Bug reassigned from package 'minirok' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #801071 to the same values previously set
Ignoring request to alter fixed versions of bug #801071 to the same values previously set
> stop
Stopping processing here.

Please contact me if you need assistance.
--
801071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801071
Debian Bug Tracking System
Contact [hidden email] with problems

Reply | Threaded
Open this post in threaded view
|

Bug#801071: marked as done (RM: minirok -- ROM; dead upstream; low popcpn; alternatives available)

Debian Bug Tracking System
In reply to this post by Moritz Muehlenhoff
Your message dated Mon, 12 Oct 2015 12:25:26 +0000
with message-id <[hidden email]>
and subject line Bug#801071: Removed package(s) from unstable
has caused the Debian Bug report #801071,
regarding RM: minirok -- ROM; dead upstream; low popcpn; alternatives available
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 [hidden email]
immediately.)


--
801071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801071
Debian Bug Tracking System
Contact [hidden email] with problems

Package: minirok
Severity: serious

Should minirok be removed? It hasn't seen an upload
since 2009, it's dead upstream (Debian maintainer is also
upstream), popcon usage is marginal and it relies on
obsolete gstreamer 0.10. Plus, there's plenty of alternatives
in the archive.

Please address the outstanding bugs or reassign this to
ftp.debian.org for removal.

Cheers,
        Moritz

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

   minirok |      2.1-1 | source, all

------------------- Reason -------------------
ROM; dead upstream; low popcpn; alternatives available
----------------------------------------------

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 [hidden email].

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

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[hidden email].

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