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? Theory B: did we miss something related to x32? Is this an x32 perl? > Preparing to unpack .../0-libc6_2.29-6_x32.deb ... > De-configuring libc6:i386 (2.29-3) ... > De-configuring libc6:amd64 (2.29-3) ... > Unpacking libc6:x32 (2.29-6) over (2.29-3) ... > Preparing to unpack .../1-libc6_2.29-6_amd64.deb ... > /usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot > open shared object file: No such file or directory > dpkg: error processing archive > /tmp/apt-dpkg-install-vKsDE7/1-libc6_2.29-6_amd64.deb (--unpack): > new libc6:amd64 package pre-installation script subprocess returned error > exit status 127 -- ciao, Marco
signature.asc
Description: PGP signature
