Hi, On 15 Oct 2006, Pierre Habouzit wrote: > Le dim 15 octobre 2006 21:25, Jochen Striepe a écrit : > > Releasing the hold of course instantly solved the problem. I'm under > > the strong impression that apt-listchanges should require an apt > > version where libapt-pkg-libc6.3-6.so.3.11 is already available, and > > that seems to be an apt version > 0.5.14 (instead of the current > > dependency on apt >= 0.5.3). > > Can I ask you why ? apt-listchanges does almost not rely on apt directly > at all, but on python-apt instead.
I must admit I just looked where /usr/lib/libapt-pkg-libc6.3-6.so.3.11 comes from, and what dependencies apt-listchanges has. Please try simply renaming /usr/lib/libapt-pkg-libc6.3-6.so.3.11 to something else: ------------SNIPP------------ $ apt-listchanges Traceback (most recent call last): File "/usr/bin/apt-listchanges", line 27, in ? import apt_pkg ImportError: libapt-pkg-libc6.3-6.so.3.11: cannot open shared object file: No such file or directory ------------SNIPP------------ This looks quite similar to the message I got on commands like "apt-get -u install ...". However, this may not be the *exact* message -- since apt itself no longer is v0.5.14 on my system, I cannot reproduce the exact situation. > so maybe the problem is with python-apt having too loosy depends ? Hmm, sounds plausible. I don't have any clue of apt internals, I am just a dumb user. :) > So I need more informations than your "thoughts". I don't say you're not > correct, but I cannot see what's going on exactly either. I am sorry I cannot be of much help here. Since upgrading from apt-0.5.14 to current apt last week nothing similar has happened (as should be expected, since the above lib missing in old apt-0.5.14 is installed by now), and the old error messages are lost in time. Greetings, Jochen. -- "This is Linux Country. On a quiet night, you can hear Windows reboot." -- .sig in <[EMAIL PROTECTED]>
pgpmU0mknTRn0.pgp
Description: PGP signature