Bug#746741: release.debian.org: dh-python2 transition
On 13/12/15 14:45, Mattia Rizzolo wrote:
> On Tue, May 27, 2014 at 10:59:56PM +0200, Emilio Pozuelo Monfort wrote:
>> On 05/05/14 15:46, Julien Cristau wrote:
>>> On Sat, May 3, 2014 at 07:48:03 +0100, Dimitri John Ledkov wrote:
>>>> Debian python teams would find useful to evaluate on continuous basis
>>>> removal of python-support from the archive and thus migrating to
>>>> dh-python2. We are uncertain of the scope, and the pace at which this
>>>> transition can be completed. But it would be extremely useful to have a
>>>> transition tracker setup (permanent-type ?!).
>>>>
>>> I don't think that makes much sense as a transition / tracker, as it's
>>> not something rebuilds would fix or where it's hard to find the set of
>>> affected packages.
>>
>> FWIW, you may get a lot of things switched by emailing debian-devel@ with a
>> dd-list. And also by adding a lintian check.
>
> I'm currently undergoing a sprint to push this to an end, I'm down to
> ~80 packages still affected, a handful already in deferred, and if I
> continue with this pace I'm going to NMU/team upload all of them by the
> end of the next week or so.
>
> We came to a point where I think the number of affected packages is not
> going down by itself, since most of the packages have either the
> maintianer that is de-facto MIA or the package is de-facto orphaned.
>
> So I ask for permission to bump all those bugs to severity:serious, and
> move on; that way I'll have the excuse to ask for RM: RoQA for a couple
> of packages without feeling too guilty...
That's too many. Maybe when the ones you plan to fix are done and there are only
a handful left that'll be fine.
> PS: let me guess, should this bug be reassigned to ftp-master for RM?
> since you already stated -release is not the right place for this, and a
> transition tracker is not really needed in this case.
Yes, feel free to reassign this and make it a removal bug.
Thanks for the work on this!
Emilio
Reply to: