Re: libc4 upgrade -- Ouch!
Mark Eichin writes ("libc4 upgrade -- Ouch!"):
> So the mirror updated, I decided to update my unstable system. Well,
> aout-gcc needs the new libc first, so rather than iterate, I was
> clever and thought I'd just upgradge the libc4 package directly. Well,
> that *obliterated* my existing libc4 (-11) installation. This is
> bad... because the dpkg I'm running is a 1.1.5 a.out :-)
>
> Perhaps this should have a corresponding conflict (I assume the postrm
> failure has to do with the linux link in /usr/include? but I'm
> guessing here...) but just thought I'd give a heads up to others like
> me who are using unstable...
The problem here is that the libc4 maintainer scripts are buggy.
Ian.
> maneki-neko+% sudo dpkg -i /lump/deb/unbin/devel/libc4-4.6.27-13.deb
> (Reading database ... 25814 files and directories currently installed.)
> Preparing to replace libc4 (using /lump/deb/unbin/devel/libc4-4.6.27-13.deb) ...
> Unpacking replacement libc4 ...
> rm: linux: is a directory
> dpkg: warning - old post-removal script returned error exit status 1
> dpkg - trying script from the new package instead ...
> dpkg: error processing /lump/deb/unbin/devel/libc4-4.6.27-13.deb (--install):
> there is no script in the new version of the package - giving up
> mv: libc.so.4.6.27.new: No such file or directory
> mv: libm.so.4.6.27.new: No such file or directory
> mv: libcurses.so.0.1.2.new: No such file or directory
> mv: libdb.so.1.85.1.new: No such file or directory
> ln: ./linux: cannot overwrite directory
> dpkg: error while cleaning up:
> subprocess post-installation script returned error exit status 1
> Errors were encountered while processing:
> /lump/deb/unbin/devel/libc4-4.6.27-13.deb
> Exit 1
> maneki-neko+% sudo dpkg -i /lump/deb/unbin/devel/libc4-4.6.27-12.deb
> dpkg: can't find library 'libc.so.4'
> Exit -128
>
> (Yes, I can recover by grabbing the library off of another
> system... but a second attempt just nukes it again...)
>
> Part of the problem is that the libc4 postrm ends with:
> cd /usr/i486-linuxaout/include ; rm -f asm linux
>
> yet asm and linux are actual directories. Moving them out of the way
> got the dpkg --remove libc4 to work; having done that, I could *then*
> install -13. Ahh well, such is progress :-)
>
Reply to: