Bug#630608: [bash] Everything Segfaults After lib6 -7 Upgrade
On Tue, Jun 21, 2011 at 08:15:49PM +0300, David Baron wrote:
> 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.
That's what I don't understand, which files did you removed exactly? I
don't understand how your system could use a non-Debian provided
dynamic linker.
> 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.
It's not a problem of upgrade, you told in a previous mail that you
copy the 2.11 files to the /lib directory. Even doing so is not a
problem (except for ld.so, which is taken into account by the preinst
script) given that /lib/i386-linux-gnu has a higher priority. The fact
that in addition you export LD_LIBRARY_PATH=/lib caused all your
problems.
I don't think the preinst script should take care of all these issues.
When you defined LD_LIBRARY_PATH you should assume the consequences.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: