Eugene V. Lyubimkin wrote:
> On 2011-05-20 13:16, Jonathan Nieder wrote:
>> unpack libc6
>> unpack libc-bin
>> configure libc-bin
>> configure libc6
>
> Emm, the whole #558151 was about the order above does not work unless
> you specify --force-bad-path which Guillem was much against.
Ah, I see --- the upgraded libc6 removed ldconfig.
This looks like a case of missing pre-depends (Depends don't constrain
unpacking order!). With a pre-depends, the best upgrade path would be
deconfigure libc6
unpack libc-bin
unpack libc6
configure libc-bin
configure libc6
which is relevant to this bug, indeed. It is also a good example for
how the "breaks+replaces to steal files" idiom does not capture the
desired semantics perfectly. :/ In an ideal world, the upgrade path
would be
unpack libc-bin
unpack libc6
configure libc-bin
configure libc6
with no deconfigure step (essential packages are not supposed to ever
need to be deconfigured). Sorry for a tangent.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
