On Fri, 2009-11-27 at 21:09:57 +0200, Eugene V. Lyubimkin wrote:
Guillem Jover wrote:
Something like this could do (on a clean lenny chroot):
r...@gaara:~# export LC_ALL=C
r...@gaara:~# dpkg --auto-deconfigure --unpack libc-bin_2.10.2-2_amd64.deb
This:
a) may break the planned
Guillem Jover wrote:
On Fri, 2009-11-27 at 21:09:57 +0200, Eugene V. Lyubimkin wrote:
Guillem Jover wrote:
Something like this could do (on a clean lenny chroot):
r...@gaara:~# export LC_ALL=C
r...@gaara:~# dpkg --auto-deconfigure --unpack libc-bin_2.10.2-2_amd64.deb
This:
a) may break
reopen 558151
thanks
Guillem Jover wrote:
Hi!
That seems to me to be an obvious enough indication that order is not
the correct one. There's a small window of time were the stuff previously
in libc6 and now in libc-bin is not going to be present on the file
system. And one of the point of
Guillem Jover wrote:
So, what's the correct order then?
Something like this could do (on a clean lenny chroot):
r...@gaara:~# export LC_ALL=C
r...@gaara:~# dpkg --auto-deconfigure --unpack libc-bin_2.10.2-2_amd64.deb
This:
a) may break the planned changeset by allowing dpkg to do
Package: dpkg
Version: 1.15.4
Severity: normal
Hello,
-8-
Preparing to replace libc6 2.9-7 (using .../libc6_2.10.2-2_i386.deb) ...
Removing obsolete conffile /etc/init.d/glibc.sh ...
Checking for services that may need to be restarted...
Checking init scripts...
Unpacking replacement libc6 ...
5 matches
Mail list logo
