Re: freezing python packages until python-2.3 becomes the default in testing

[Ron <ron@debian.org>]

Howdy,

Forgive my apparent ignorance here, but I'm a little confused if I read
Matthias' message correctly.  I don't understand how uploading a new
libwxgtk2.4-python package (which build-deps on python2.3) might hold
up python from entering testing.  Python doesn't depend on the wx
package (or presumably any of the wx deps either), so how does wx being
too new for testing hold up Python from entering it?

I ask because there is a new wx release which fixes some outstanding
issues and there are a bunch of apps waiting for wx to hit testing,
so the sooner I get this in, the sooner they all go too.

OTOH if doing this will skrew the python transition, I'm happy to wait
and let them all enter together with the older version first, but I just
don't see which nuance of testing makes this a problem.

If someone can shed some more light on this for me I'd be grateful.
(and less likely to mess things up for you guys in the future :)

thanks,
Ron

  (please CC on any replies, I'm not on the deb-python list)


On Sat, Oct 04, 2003 at 01:45:13PM -0600, Matthias Klose wrote:

...

> To help python2.3 to enter the testing (sarge) release as the default
> python version, we need a whole bunch of packages to enter the testing
> release at the same time.
> 
> To minimize the number of packages with the "Too young" states, please
> consider the following packages be frozen (no new uploads to unstable):
> 
>   - packages, whose source have a dependency on a binary package built
>     from the python2.3 or python2.3 source, which is not yet in the
>     testing release.
> 
>   - the pythonX.Y packages itself.
> 
>   - generally: all packages you see in update-excuses, which have
>     a dependency on the python2.3 source. See
>     http://ftp-master.debian.org/testing/update_excuses.html.gz
> 
> Exceptions are:
> 
>   - Uploads, which fix release critical bugs
> 
>   - Uploads of packages, which are needed for other transitions
>     from unstable to testing.
> 
>   - Uploads of python related packages, which do not touch the
>     python transition (i.e. packages depending on python2.1 or
>     python2.2 only, like the zope packages).
>     Those uploads must not introduce on the python2.3 source
>     currently only in unstable.
> 
>   - Uploads of source packages, which are not yet part of testing.

...