Bug#898043: RM: fgo -- RoM; unmaintained and obsolete
Control: reassign -1 ftp.debian.org
On Sun, 2018-05-06 at 15:58 +0200, Markus Wanner wrote:
> Control: user -1 release.debian.org@packages.debian.org
>
> On 05/06/2018 01:51 PM, Adam D. Barratt wrote:
> > Control: tags -1 + moreinfo
> >
> > On Sun, 2018-05-06 at 13:34 +0200, Markus Wanner wrote:
[...]
> > > I figured I should have asked for a removal from testing,
> > > targeting the Release Managers.
> > >
> >
> > If it is indeed unmaintained and obsolete, why shouldn't it be
> > removed from unstable?
>
> Sorry for the confusion. I'd appreciate the package to disappear from
> testing and unstable. It shall not be part of buster.
>
> I was trying to follow instructions here, and considered only
> unstable,
> first:
> https://wiki.debian.org/ftpmaster_Removals
>
> I'm still not quite clear what the best approach is for requesting a
> removal from testing and unstable (which I'll have to repeat for
> fgrun).
>From https://wiki.debian.org/ftpmaster_Removals#Removals_from_testing.2
C_stable_and_oldstable :
<quote>
Note that in most cases it is unnecessary to request removal of your
package from both testing and unstable. Once the package is removed
from unstable, it will automatically be removed from testing once there
are no dependencies keeping it there.
If you do need the package simultaneously removed from both
distributions, you will need to file a removal bug for unstable as
usual, and contact the Release Managers to request removal from
testing.
</quote>
I'm assuming that there's no desperate need for the testing removal to
be expedited, so starting with unstable and letting things take their
natural course is the correct approach; re-reassigning.
Regards,
Adam
Reply to: