Package: python2.6-minimal Version: 2.6.4-4 Severity: normal I also bumped into this problem. I then looked what does /usr/lib/python2.6/site-packages directory contain and it was a single library from python-compizconfig. But I don't use compiz, thus I executed the following which fixed the problem: dpkg --purge python-compizconfig compizconfig-settings-manager dpkg -i /var/cache/apt/archives/python2.6-minimal_2.6.4-4_i386.deb
Hope it helps to recover. Now the real question: How did those libraries ended up in testing just after one week? and more importantly where did the older versions go? i.e. I tried to backtrack, but the older version was completely gone: the only option left was to downgrade to stable! Best regards, Marius -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages python2.6-minimal depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libssl0.9.8 0.9.8k-8 SSL shared libraries ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages python2.6-minimal recommends: pn python2.6 <none> (no description available) Versions of packages python2.6-minimal suggests: ii binfmt-support 1.2.15 Support for extra binary formats -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
