On Fri, Oct 05, 2007 at 06:04:27PM +0000, Josselin Mouette wrote: > Hi, > > I have conducted a thorough analysis of all packages preventing us from > migrating to python 2.5. Thanks a lot for the work ! > Now, for the bad news. The following packages have various kinds of > issues that prevent them from working with python2.5. Some of them are > trivial, some are much more tricky. In all cases, we need to focus on > these bugs if we want to see those packages in lenny: [...] > I request a zero-day NMU policy for these bugs. I second this. > The following packages do not support multiple versions of python at > once. This is where we have the most serious regression compared to the > situation of the python2.4 transition. It is understandable not to > rebuild the gimp or OpenOffice.org packages for several python versions, > but many of these packages are using distutils and are therefore > *trivial* to get to work with several versions. > > Please note that they can all be binNMUed after python2.5 has become the > default, but all of them will have to migrate to testing at once. We > must make this list shorter unless we want this transition to recall bad > memories to the release team. > > Here is the list: [...] > I also request a zero-day NMU policy for these issues, at least for > packages using distutils. This is a tad aggressive as for some of the packages (see wcgi) it make sense to stay like that, and an NMUer that does 10 of those in a round may miss the reasons. I'd rather see a mass bug filling on those packages, and see the maintainers that feel their package should be built for one version only say it loud first. Then maybe we will consider making it RC. -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.org
Attachment:
pgpKqzZuF2NOS.pgp
Description: PGP signature