Re: Re: Bug#920127: Removed package(s) from unstable
Hi, po 9. 9. 2019 v 5:37 odesílatel Sandro Tosi napsal: > Nope. This package did not see an upload since Aug 2013. it was > orphaned since Jan 2019. Nobody stepped up. It ended up removed. > > If the upstream author or a debian packager wants it in debian, it's > easy enough to re-introduce it. > +1 -- Best regards Ondřej Nový
Re: Re: Bug#920127: Removed package(s) from unstable
On September 9, 2019 3:25:43 AM UTC, Paul Wise wrote: >On Mon, Sep 9, 2019 at 4:11 AM Scott Kitterman wrote: > >> This was sent to the FTP Team, but it seems like someone with some >bandwidth >> to assist from DPMT/PAPT would be a better audience. Note that the >removal's >> already been done, but if someone wants to sponsor a python3 update >to the >> package, they can ping me for a quick trip through New to bring it >back. > >It seems like a little bit more due diligence is needed before filing >removals. In theory yes, but in practice because this is a multi-thousand package transition we're trying to get through, I think it's better to move fast even if we break a few things than to be super careful and slow. Things like this can be fixed. It's better to push hard early in the development cycle so there's time to recover. Scott K
Re: Re: Bug#920127: Removed package(s) from unstable
On Sun, Sep 8, 2019 at 11:26 PM Paul Wise wrote: > > On Mon, Sep 9, 2019 at 4:11 AM Scott Kitterman wrote: > > > This was sent to the FTP Team, but it seems like someone with some bandwidth > > to assist from DPMT/PAPT would be a better audience. Note that the > > removal's > > already been done, but if someone wants to sponsor a python3 update to the > > package, they can ping me for a quick trip through New to bring it back. > > It seems like a little bit more due diligence is needed before filing > removals. Nope. This package did not see an upload since Aug 2013. it was orphaned since Jan 2019. Nobody stepped up. It ended up removed. If the upstream author or a debian packager wants it in debian, it's easy enough to re-introduce it. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Re: Re: Bug#920127: Removed package(s) from unstable
On Mon, Sep 9, 2019 at 4:11 AM Scott Kitterman wrote: > This was sent to the FTP Team, but it seems like someone with some bandwidth > to assist from DPMT/PAPT would be a better audience. Note that the removal's > already been done, but if someone wants to sponsor a python3 update to the > package, they can ping me for a quick trip through New to bring it back. It seems like a little bit more due diligence is needed before filing removals. -- bye, pabs https://wiki.debian.org/PaulWise
Fwd: Re: Bug#920127: Removed package(s) from unstable
This was sent to the FTP Team, but it seems like someone with some bandwidth to assist from DPMT/PAPT would be a better audience. Note that the removal's already been done, but if someone wants to sponsor a python3 update to the package, they can ping me for a quick trip through New to bring it back. Scott K - Forwarded Message -- Subject: Re: Bug#920127: Removed package(s) from unstable Date: Sunday, September 8, 2019, 3:05:59 PM EDT From: John Eikenberry To: Debian FTP Masters Hello, I am up upstream maintainer for colortest-python and wanted to communicate that it is not dead and it fully supports running with python3. I responded with the same message to the ticket about this (#936320). I'd be happy to help maintain it the package if necessary. Thanks. Debian FTP Masters wrote: > We believe that the bug you reported is now fixed; the following > package(s) have been removed from unstable: > > colortest-python | 2.2-1 | source, all > > --- Reason --- > python2-only; orphaned; dead upstream; low popcon > -- > > 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 920...@bugs.debian.org. > > The full log for this bug can be viewed at https://bugs.debian.org/920127 > > 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) > -- John Eikenberry [ j...@zhar.net - http://zhar.net ] "Perfection is attained, not when no more can be added, but when no more can be removed." -- Antoine de Saint-Exupery -
