Bug#368695: possible reason

[Christian Kujau <lists@nerdbynature.de>]

FWIW and for the sake of the archives: I just came across the same issue 
on a current Debian/Etch system. When installing python2.5 and symlink 
/usr/bin/python to the new 2.5 version of Python, apt-listchanges will 
call this new version. Unfortunately, python-apt does not provide modules 
for apt for this nw version like it does for 2.3 and 2.4 
(/usr/lib/python2.[3,4]/site-packages/apt_*.so) and thus fails with the 
error message bdepardon was reporting back in 2006.

Workaround: adjust /usr/bin/apt-listchanges to call python2.4, not just 
python and the error goes away.

Thanks,
Christian.

apt		0.6.46.4-0.1
debconf		1.5.11etch2
debianutils	2.17
python		2.4.4-2
python2.5	2.5-5+etch1
python-apt	0.6.19
ucf		2.0020
--
BOFH excuse #208:

Your mail is being routed through Germany ... and they're censoring us.