Package: python-apt
Version: 0.5.5.1
Severity: grave
Okay, look at the following:
python-apt (0.5.5.1), in sarge, depends on the following:
* libapt-inst-libc6.3-5-1.0
* libapt-pkg-libc6.3-5-3.3
The packages providing the libapt-(inst|pkg) stuff are apt-utils and
apt, respectively.
Both of these packages are available as of version 0.5.4 in sarge.
BUT -- the package versions in sarge in question only provide:
apt-utils, 0.5.4 - libapt-inst-libc6.2-3-2-1.0
apt, 0.5.4 - libapt-pkg-libc6.2-3-2-3.2
Wheres the _sid_ versions, i.e. 0.5.8, provide:
apt-utils, 0.5.8 - libapt-pkg-libc6.3-5-3.3
apt, 0.5.8 - libapt-inst-libc6.3-5-1.0
Seems like the sid dependencies got mixed into sarge, for whatever
reason.
This, of course, leads to the following nicety:
$ sudo apt-get install python-apt
[...]
Sorry, but the following packages have unmet dependencies:
python-apt: Depends: libapt-inst-libc6.3-5-1.0 but it is not installable
Depends: libapt-pkg-libc6.3-5-3.3 but it is not installable
E: Sorry, broken packages
Et cetera, rendering packages like apt-listchanges unusable, too.
I'd advise someone to fix this.
-towoAttachment:
pgpETv4ieV2OQ.pgp
Description: PGP signature