[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to tell users that ia32-libs will go away

Jonathan Nieder <jrnieder@gmail.com> writes:

> (replying on -mentors)
> Hi Goswin,
> Goswin von Brederlow wrote:
>> Having multiarch packages and ia32-libs installed will lead to some
>> confusion. The runtime linker will not be able to differentiate between
>> multiarch or ia32-libs libs. One of /usr/lib32/ and
>> /usr/lib/i486-linux-gnu/ will be first in the search path and libs will
>> be taken from there preferably.
> The multiarch dirs come before the biarch dirs.  See glibc-package
> r4683 for details (prefix biarch-compat.conf with zz_ so that is is
> sorted last, 2011-05-24).
> [...]
>> Are there any objections to adding a debconf message to ia32-libs with a
>> short message and reference to a Debian wiki page on how to transition
>> to multiarch?
> Yes, as devref explains, that is debconf abuse.  Please use
> NEWS.Debian.gz and README.Debian instead.
> [..]
>> 4) Should we have some Breaks/Conflicts between multiarch and bi-arch
>> packages?
> No, I don't see why.

Because of the above mentioned problem that the runtime linker will mix
libraries from multiarch and bi-arch. With the multiarch directory being
searched first binaries needing bi-arch libraries will get some
multiarch libraries mixed in and cause random crashes.

    lrwxrwxrwx 1 root root   20 Nov 13  2010 /lib/ld-linux.so.2 -> /lib32/ld-linux.so.2
    lrwxrwxrwx 1 root root   20 Nov 13  2010 /lib/ld-linux.so.2 -> /lib/i486-linux-gnu/ld-linux.so.2

Currently libc6:i386 only Replaces libc6-i386. Which means that
installing libc6:i386 and then removing it again leaves biarch in a
non-functioning state. If the two packages do no Break/Conflict then
diversions or alternatives need to be used. Both of which I don't like
for what is a transtion.

> Thanks for your work and hope that helps,
> Jonathan


Reply to: