severity 605536 serious thanks On Wed, 2010-12-01 at 10:07:02 +1100, Russell Coker wrote: > Package: dpkg > Version: 1.15.8.5 > Severity: normal
> smtp:/usr/lib# ls -l libz* > lrwxrwxrwx 1 root root 15 Dec 1 09:52 libz.so.1 -> libz.so.1.2.3.4 > -rw-r--r-- 1 root root 81012 Apr 7 2008 libz.so.1.2.3.3 > -rw-r--r-- 1 root root 79980 Dec 29 2009 libz.so.1.2.3.4.dpkg-new > lrwxrwxrwx 1 root root 15 Dec 1 09:52 libz.so.1.dpkg-tmp -> > libz.so.1.2.3.3 > > I aborted an "apt-get install" run with ^C and the above was left in the > /usr/lib directory. After that attempts to install the package aborted with > the following error: > > dpkg-deb: error while loading shared libraries: libz.so.1: cannot open shared > object file: No such file or directory > dpkg: error processing > /var/cache/apt/archives/zlib1g_1%3a1.2.3.4.dfsg-3_i386.deb (--unpack): > subprocess dpkg-deb --control returned error exit status 127 > > I believe that a ^C should be handled in such a way that the sym-links match > up. Ah, nice catch! This should actually be considered an RC bug as it implies dpkg can end up breaking a system like it did with yours on any dpkg interruption, user initiated or not, which it should never do. This is due to the deferred renames, the symlinks should also be deferred or they might end up pointing to nonexistent files. I've a patch queued fixing this. regards, guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
