[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Python 2.1/2.2 removal; Python 2.4 as default



Hi all,

It's been quite a while, but 2.1 and to a slightly lesser extend, 2.2
are really obsolete now. One of the issues with 2.1 and 2.2 are that
they don't build on amd64, and are holding up a whole chain of packages
also.

Therefore, I'd like to remove python 2.1 and 2.2 as soon as possible,
like, before the weekend for example. As far as I can see, nothing
really important depends on it any more, and whatever it is, can be NMUd
or removed. Most if not all depending packages already have a bug filed
for at least 2 months, which should've been plenty of warning.

For reference, please find below the full list of packages that will be
broken, only listing the first reason (often it's both
build-dependencies and dependencies on all archs). If you want to help,
and are not the maintainer of any python package needing changes
yourself, you can do so right now, by starting to:

1) File bugs where there are no bugs filed yet, at serious
2) Upgrade any bugs that are already filed to 'serious'
3) Usertag such bugs, with debian-python@lists.debian.org as user, and
   'python2.1', 'python2.2' respectively, for easier tracking. You can
   view these usertags by going to
   http://bugs.debian.org/usertag:debian-python@lists.debian.org
4) These packages are candidates for delayed NMUs immediately, and once
   python2.1/2.2 are removed they fall under the regular release team's
   0-day NMU policy for RC bugs -- note that this policy includes that
   bugs need to be at least one week old, so there is not direct 0-day
   NMUing of previously non-RC-buggy packages. This shouldn't stop
   anyone from filing patches though, and assisting the maintainer where
   possible.
5) Or, as an alternative to (4), suggest removal of a package if that is
   appropriate. Do this by filing a bug on the package in question, and
   ask the maintainer to reassign to ftp.debian.org if he/she agrees.

Now, for the list:

carpaltunnel has an unsatisfied build-dependency: python2.2-dev
decompyle2.2 has an unsatisfied build-dependency: python2.2-dev
htmlgen has an unsatisfied build-dependency: python2.1-dev
jabber.py has an unsatisfied build-dependency: python2.1
jython has an unsatisfied build-dependency: python2.1
libapache-mod-python has an unsatisfied build-dependency: python2.1-dev (>= 2.1.3-11)
libapache-mod-python2.1 has an unsatisfied dependency on alpha: python2.1
libapache-mod-python2.2 has an unsatisfied dependency on alpha: python2.2
libapache2-mod-python has an unsatisfied build-dependency: python2.2-dev (>= 2.2.3)
libapache2-mod-python2.2 has an unsatisfied dependency on alpha: python2.2 (>= 2.2.2)
pexpect has an unsatisfied build-dependency: python2.2-dev
pygdchart2 has an unsatisfied build-dependency: python2.1-dev
pyopenssl has an unsatisfied build-dependency: python2.2-dev (>= 2.2)
python-adns has an unsatisfied build-dependency: python2.1
python-cjkcodecs has an unsatisfied build-dependency: python2.1-dev
python-crack has an unsatisfied build-dependency: python2.2-dev
python-dhm has an unsatisfied build-dependency: python2.2-dev
python-iconvcodec has an unsatisfied build-dependency: python2.1-dev
python-japanese-codecs has an unsatisfied build-dependency: python2.2-dev
python-korean-codecs has an unsatisfied build-dependency: python2.1-dev
python-medusa has an unsatisfied build-dependency: python2.1-dev
python-omniorb2 has an unsatisfied build-dependency: python2.1-dev
python-orbit has an unsatisfied build-dependency: python2.1-dev
python-oss has an unsatisfied build-dependency: python2.1-dev
python-pam has an unsatisfied build-dependency: python2.1-dev
python-pylibacl has an unsatisfied build-dependency: python2.2-dev
python-pyxattr has an unsatisfied build-dependency: python2.2-dev
python-weblib has an unsatisfied build-dependency: python2.1-dev
python2.1-adns has an unsatisfied dependency on alpha: python2.1
python2.1-cjkcodecs has an unsatisfied dependency on alpha: python2.1
python2.1-gdchart2 has an unsatisfied dependency on alpha: python2.1
python2.1-htmlgen has an unsatisfied dependency on alpha: python2.1
python2.1-iconvcodec has an unsatisfied dependency on alpha: python2.1
python2.1-jabber has an unsatisfied dependency on alpha: python2.1
python2.1-korean-codecs has an unsatisfied dependency on alpha: python2.1
python2.1-medusa has an unsatisfied dependency on alpha: python2.1
python2.1-omniorb2 has an unsatisfied dependency on alpha: python2.1
python2.1-orbit has an unsatisfied dependency on alpha: python2.1
python2.1-oss has an unsatisfied dependency on alpha: python2.1
python2.1-pam has an unsatisfied dependency on alpha: python2.1
python2.1-tclink has an unsatisfied dependency on alpha: python2.1
python2.1-weblib has an unsatisfied dependency on alpha: python2.1
python2.2-adns has an unsatisfied dependency on alpha: python2.2
python2.2-cjkcodecs has an unsatisfied dependency on alpha: python2.2
python2.2-crack has an unsatisfied dependency on alpha: python2.2
python2.2-dhm has an unsatisfied dependency on alpha: python2.2
python2.2-gdchart2 has an unsatisfied dependency on alpha: python2.2
python2.2-htmlgen has an unsatisfied dependency on alpha: python2.2
python2.2-iconvcodec has an unsatisfied dependency on alpha: python2.2
python2.2-jabber has an unsatisfied dependency on alpha: python2.2
python2.2-japanese-codecs has an unsatisfied dependency on alpha: python2.2
python2.2-korean-codecs has an unsatisfied dependency on alpha: python2.2
python2.2-medusa has an unsatisfied dependency on alpha: python2.2
python2.2-omniorb2 has an unsatisfied dependency on alpha: python2.2
python2.2-omniorb2-omg has an unsatisfied dependency on alpha: python2.2
python2.2-orbit has an unsatisfied dependency on alpha: python2.2
python2.2-oss has an unsatisfied dependency on alpha: python2.2
python2.2-pam has an unsatisfied dependency on alpha: python2.2
python2.2-pexpect has an unsatisfied dependency on alpha: python2.2
python2.2-pylibacl has an unsatisfied dependency on alpha: python2.2
python2.2-pyopenssl has an unsatisfied dependency on alpha: python2.2
python2.2-pyxattr has an unsatisfied dependency on alpha: python2.2
python2.2-tclink has an unsatisfied dependency on alpha: python2.2
python2.2-weblib has an unsatisfied dependency on alpha: python2.2
python2.2-xmms has an unsatisfied dependency on alpha: python2.2
python2.2-zopeinterface has an unsatisfied dependency on alpha: python2.2
pyxmms has an unsatisfied build-dependency: python2.2 (>= 2.2-1)
syslog-summary has an unsatisfied dependency on alpha: python2.2
vegastrike has an unsatisfied dependency on arm: python2.2 (>= 2.2.2)
zope-zshell has an unsatisfied dependency on alpha: python2.2
zopeinterface has an unsatisfied build-dependency: python2.2-dev


Furthermore, python 2.4 is out for quite a while now, it entered
unstable in 2004. The first freezes are already closing in fast, and
python is an important language. I'm aware of the python policy and
packaging infrastructure changes, but they are largely orthogonal to
actually moving packages' default version from 2.3 to 2.4. I especially
expect the infrastructure changes to take a bit to get right, because
they are reaching out to everything python, while the default python
version change is a tried change, it's been done before, and our current
tools all across the board support it. Also, most upstream packages will
already be 2.4 ready, because 2.4 has been out for so long. If there are
any bugs potentially blocking 2.3 -> 2.4 migration, please usertag them
as above, with 'python2.4' as tag.

So, I'd like to suggest changing python-defaults next week, and
consequently getting a mini-BSP to get all packages in Debian working
fine with python2.4, and all libraries that didn't move yet to
python2.4, and also NMU the remainder of packages that still have 2.1
or 2.2 support. Any comments?

--Jeroen

-- 
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl



Reply to: