Bug#193566: python-apt: depends on python (>= 2.1), python (<< 2.2), should depend on python2.1
retitle 193566 Uninstallable in testing
thanks
On Fri, May 16, 2003 at 05:47:13PM +0100, Randy Orrison wrote:
> I just did apt-get dist-upgrade on a mostly testing (slightly unstable)
> system, and apt-listchanges and python-apt were removed. Trying to
> reinstall, I've found that python-apt won't install:
> [...]
> python-apt: Depends: python (< 2.2) but 2.2.2-6 is to be installed
> [...]
> $ dpkg -l | grep python2\\..\
> ii python2.1 2.1.3-18 An interactive object-oriented scripting lan
> ii python2.2 2.2.2-6 An interactive object-oriented scripting lan
The dependency is referring to the 'python' package, not python2.1 or
python2.2. 'python' represents the default version of python, which is what
python-apt supports.
> Checking the dependancies for python-apt I see:
>
> $ apt-cache show python-apt
> Package: python-apt [ unstable ]
> Priority: optional
> Section: python
> Installed-Size: 164
> Maintainer: APT Development Team <deity@lists.debian.org>
> Architecture: i386
> Version: 0.5.5
> Depends: python (>= 2.2), python (<< 2.3), libapt-inst-libc6.3-5-1.0, libapt-pkg-libc6.3-5-3.3, libc6 (>= 2.3.1-1)
This is the version you want if you are using python 2.2.
> Since I do have unstable sources, I can fix this by installing the
> unstable python-apt, but shouldn't it work with the testing version?
It should, and it used to. This is listed as a problem on:
http://ftp-master.debian.org/testing/testing_probs.html
along with a bunch of other python module packages. I assume this means
that python 2.2 was forced into testing despite this breakage, and that it
won't be fixed until the new apt gets into testing (which may be quite some
time).
--
- mdz
Reply to: