Bug#939766: [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.

2020-01-30 Thread Guilhem Moulin
On Tue, 14 Jan 2020 at 03:22:20 +0100, Guilhem Moulin wrote: > If there is a need for a complex logic I guess this could be done once > and for all in /usr/share/initramfs-tools/hook-functions. Quick follow up about this: asked Ben for feedback and he agreed that it would make sense to do it in

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

2020-01-13 Thread Guilhem Moulin
Hi Guillem! On Tue, 14 Jan 2020 at 02:01:09 +0100, Guillem Jover wrote: > The problem I've got is that I upgraded to gcc-10 from experimental, > which pulled in libgcc1-s1 and libgcc1 (that I later removed), neither > of which install libgcc_s.so.1 under /lib/$MULTIARCH anymore. The first >

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

2020-01-13 Thread Guillem Jover
Control: tags -1 - moreinfo Hi! On Mon, 2019-09-09 at 00:53:44 +0200, Alexander Brock wrote: > I searched for clues why that libgcc_s.so.1 is not added and found the > script: > /usr/share/initramfs-tools/hooks/cryptroot > > it contains the line: > > LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr

Bug#939766: [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.

2019-09-09 Thread Guilhem Moulin
Control: retitle -1 cryptsetup-initramfs: Missing libgcc_s on linux-image-5.2.0-2-amd64 On Mon, 09 Sep 2019 at 02:55:06 +0200, Guilhem Moulin wrote: > This on a sid system upgraded from buster with a ‘usrmerge’ layout: > > root@kvm-10487:~# ldd /sbin/cryptsetup | grep -F libc.so >

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

2019-09-08 Thread 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

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

2019-09-08 Thread Alexander Brock
I searched for clues why that libgcc_s.so.1 is not added and found the script: /usr/share/initramfs-tools/hooks/cryptroot it contains the line: LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" but on my machine there is no

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

2019-09-08 Thread Alexander
Package: cryptsetup-initramfs Version: 2:2.2.0-3 Severity: important Dear Maintainer, * What led up to the situation? I ran apt upgrade and restarted the system since I noticed that some drivers were upgraded (firmware-linux-* stuff). I have an encrypted / partition, this is the output of