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

To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: debian-mentors@lists.debian.org, Sven Joachim <svenjoac@gmx.de>
Subject: Re: How to tell users that ia32-libs will go away
From: Jonathan Nieder <jrnieder@gmail.com>
Date: Fri, 2 Mar 2012 03:43:30 -0600
Message-id: <[🔎] 20120302094330.GN5248@burratino>
In-reply-to: <87mx89y5kv.fsf@frosties.localnet>
References: <87ehu4oy6o.fsf@frosties.localnet> <20120209152634.GA5575@burratino> <87mx89y5kv.fsf@frosties.localnet>

Goswin von Brederlow wrote:

> Also
>     lrwxrwxrwx 1 root root   20 Nov 13  2010 /lib/ld-linux.so.2 -> /lib32/ld-linux.so.2
> and
>     lrwxrwxrwx 1 root root   20 Nov 13  2010 /lib/ld-linux.so.2 -> /lib/i486-linux-gnu/ld-linux.so.2
> conflict.
>
> 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.

I see.  Is this filed as a bug?

I'm surprised the Replaces is needed.  Symlinks act like directories
in dpkg most of the time, and multiple packages are allowed to share a
directory.

Thanks,
Jonathan

Reply to:

Follow-Ups:
- Re: How to tell users that ia32-libs will go away
  - From: Sven Joachim <svenjoac@gmx.de>

Prev by Date: Re: What happens when an architecture independent package won't build on all architectures?
Next by Date: Re: How to tell users that ia32-libs will go away
Previous by thread: Re: What happens when an architecture independent package won't build on all architectures?
Next by thread: Re: How to tell users that ia32-libs will go away
Index(es):
- Date
- Thread