Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

2020-02-09 Thread Paul Gevers
Control: retitle -1 libgcc1 should add a Breaks on cryptsetup-initramfs Hi Matthias, initramfs-tools maintainers, > Am Montag, den 03.02.2020, 18:59 +0100 schrieb Matthias Klose: > > I'm fine to add some breaks if required. cryptsetup-initramfs version 2:2.2.2-3 already worked around the issue a

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

2020-02-03 Thread Felix Zielcke
Am Montag, den 03.02.2020, 18:59 +0100 schrieb Matthias Klose: > $ dpkg -S libgcc_s.so.1 > libgcc-s1:amd64: /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 > libgcc1: /lib/libgcc_s.so.1 > > if you need the library in /lib, make sure that you depend on > libgcc1, else it's > found in /usr/lib/. > > I'm f

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

2020-02-03 Thread Vincent Bernat
Package: libgcc1 Version: 1:10-20200202-1 Followup-For: Bug #950551 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! On both my systems running unstable, libgcc-s1 is installed, but I don't have /usr/lib/x86_64-linux-gnu/libgcc_s.so.1. So, it seems something removes it. I have no clue on why

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

2020-02-03 Thread Nico Alt
I can confirm this bug. After doing an apt full-upgrade, I faced the same issue as OP. However, I was not able to fix it by downgrading packages, but instead used a similar approach to the way described in the btrfs bug #950556 [1]. After chrooting into the system, I changed the following file: $

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

2020-02-03 Thread Matthias Klose
On 2/3/20 3:46 PM, Felix Zielcke wrote: > On Mon, 03 Feb 2020 15:35:21 +0200 dimit...@stinpriza.org wrote: >> Package: libgcc1 >> Version: 1:9.2.1-25 >> Severity: grave >> Justification: renders package unusable >> >> hey, >> >> after upgrading some latest packages on sid, i can no longer unlock >

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

2020-02-03 Thread Felix Zielcke
On Mon, 03 Feb 2020 15:35:21 +0200 dimit...@stinpriza.org wrote: > Package: libgcc1 > Version: 1:9.2.1-25 > Severity: grave > Justification: renders package unusable > > hey, > > after upgrading some latest packages on sid, i can no longer unlock luks > partition and boot. message: > > "Please u

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

2020-02-03 Thread dimitris
Package: libgcc1 Version: 1:9.2.1-25 Severity: grave Justification: renders package unusable hey, after upgrading some latest packages on sid, i can no longer unlock luks partition and boot. message: "Please unlock disk rootfs: libgcc_s.so.1 must be installed for pthread-cancel to work Aborted"