On Tuesday 19 Sivan 5771 20:00:29 Aurelien Jarno wrote: > > Do please check over the pre/post/install scripts involved so this mess > > does not recur :-) > > I don't really know what can be done, the preinst script already abort > the installation if a non-dpkg owned version of ld.so is found. After > all why the preinst script should take care about files which have been > placed there by the user?
If they need be replaced, it should be handled. The main thing is that a valid ld ...so needs be around or else. If there are more than one, probably no harm as long as they point to the correct library. Telling the user to get rid of the "non-dpkg" file, naming it, is dangerous. As soon as it is deleted, the system is hosed. Also, packages of different previous major version, i.e. 2.11 upgrading to 2.13 were not handled correctly. Whether I was legitimately upgrading from previous stable or copied them (as can be sometimes necessary for recovery), their existance with the upgrade is catastrophic because somehow, they got symlinked in and the result we saw. The other problem was upgrading from testing to unstable. Since the directory structure changed and the old files were not removed, a combined testing-sid system resulted. Not a catastrophe but strange problems with no obvious fix.
