On Dec 11, Aurelien Jarno <aurel...@aurel32.net> wrote:

> On 2019-12-11 17:54, Marco d'Itri wrote:
> > On Dec 11, Thorsten Glaser <t...@mirbsd.de> wrote:
> > 
> > > Thankfully, I had a root session in a chroot open and used
> > > the program, statically linked, from http://koltsoff.com/pub/getroot/
> > > to recover access outside the chroot, by using dpkg -i --force-all
> > > first on libc6_*.deb, then libcrypt1_*.deb. Afterwards, normal recovery
> > > mechanisms apply.
> > I suspect that ldconfig would have been enough to fix this.
> > 
> > Theory A: maybe after all we really need some Pre-Depends in libc6?
> 
> A Depends should be enough, we don't need the package fully configured,
> just unpacked. In the machines that I have upgraded, libcrypt1 is
> unpacked before libc6, so it works.
> 
> I am not sure we can use a Pre-Depends given we have a dependency loop,
> libcrypt1 depends on libc6 and libc6 depends on libcrypt1. In addition
> we also have a Breaks + Replaces...
> 
> > Theory B: did we miss something related to x32?
> 
> On 2019-12-11 17:57, Thorsten Glaser wrote:
> > Given it worked in the amd64-only chroot and on another machine,
> > this most likely only fails if one has more than one architecture
> > enabled in Multi-Arch, perhaps also needs the -dev packages installed
> > to trigger.

> I thing that's the issue. Multi-Arch forces some order for all the
> versions of libc6, and also all the versions of libcrypt1.

So far I have not been able to reproduce this. My attempt:

debootstrap --arch=amd64 --variant=buildd buster mabuster 
http://ftp.it.debian.org/debian/
chroot mabuster/
dpkg --add-architecture i386
apt update
apt install whois:i386
perl -i -pe s/buster/unstable/ /etc/apt/sources.list
apt update
apt install libc6

Filtered output from apt:

Preparing to unpack .../archives/libc6_2.29-6_i386.deb ...
De-configuring libc6:amd64 (2.28-10) ...
Unpacking libc6:i386 (2.29-6) over (2.28-10) ...
Preparing to unpack .../libc6_2.29-6_amd64.deb ...
Unpacking libc6:amd64 (2.29-6) over (2.28-10) ...
Setting up libc6:amd64 (2.29-6) ...
Setting up libc6:i386 (2.29-6) ...
Preparing to unpack .../libc6-dev_2.29-6_amd64.deb ...
Unpacking libc6-dev:amd64 (2.29-6) over (2.28-10) ...
Setting up libc6-dev:amd64 (2.29-6) ...

-- 
ciao,
Marco

Attachment: signature.asc
Description: PGP signature

Reply via email to