[pkg-cryptsetup-devel] Bug#939766: Bug#939766: cryptsetup-initramfs: Trying to boot linux-image-5.2.0-2-amd64 fails, linux-image-4.19.0-5-amd64 works.

[Guilhem Moulin]

Control: tag -1 moreinfo

Hi,

On Mon, 09 Sep 2019 at 00:53:44 +0200, Alexander Brock wrote:
> but on my machine there is no /bin/libc.so.[0-9.-]+ instead it is in
> /usr/lib/x86_64-linux-gnu.

(I assume you meant ‘/lib.*/libc\.so\.[0-9.-]+’.)  How did you end up
with a system where /lib/*-linux-gnu/libc.so.6 is neither a symlink to a
shared library under /lib nor /usr/lib?  I can't reproduce that with a
clean bullseye nor with an upgrading system from an upgrading system
from a buster netinst.  AFAICT the existing regexp work for these
systems in both normal and ‘usrmerge’ layouts.  This on a sid system
upgraded from buster with a ‘usrmerge’ layout:

    root at kvm-10487:~# ldd /sbin/cryptsetup | grep -F libc.so
            libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f075b205000)
    root at kvm-10487:~# readlink -f /lib/*linux-gnu/libc.so*
    /usr/lib/x86_64-linux-gnu/libc-2.28.so
    root at kvm-10487:~# lsinitramfs /initrd.img | grep libgcc
    usr/lib/x86_64-linux-gnu/libgcc_s.so.1

-- 
Guilhem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20190909/11e64ef9/attachment.sig>