[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



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. Reinstalling libgcc-s1
fixes the problem.

- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (101, 'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgcc1 depends on:
ii  gcc-10-base  10-20200202-1
ii  libc6        2.29-9
ii  libgcc-s1    10-20200202-1

libgcc1 recommends no packages.

libgcc1 suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl45Bb4SHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5MDkP/AoeAopCOY4NEL8+GG5qC/4xiQk4SKWY
tBqFKmEhrex/46+idUV9AmY5G7BGJQad1i0L551vcuyNye2utz6dP/2XIgSJk3Ai
HVSjApSGDdo8MDVW6w2C0GucGSQAX55XPGtC6BU7I5C5ukny+MZx6Z0R/5cOYjy9
BWL8KejRawltzKIZpPIT7DuA+OG1tAQ6njdfbQxn5ihNGIHXoEcgEShEVlBhx48I
lIadw5jKJkhK6LDYWmzfvigVo9NIC/IIgepvzapNrMirjjsQE6Q/OpsxMjakfk+t
+dI4kiBbPqXNqDyaSMgUG3nKYZcIjgMU14fMC2JbRKIOOvXMHzgn5I/oj3zxau50
qZ5l1Yk1Rkds0u9mGVxmrGefxEd5IWet2HVwsqhDXNz+xyHH0yZE59UbXcdO+mfq
JVn2vbbXUBpYaAVmKyaocinDlgUYMg987j+HCNQYtmbyXfgD0GobVc3yDJykHiRj
T3Isk2ZbwLZhT5yb2p4KTbodZO1AWbGW2wabODjgAfeCtOM3tJjUioVYvXlHCnVm
hxReC7+c81CvzkNA95hT23TL4GKu21KXUpD60TWUv3i6VFp2dvDs4YV2JGzPjXbB
zIlSk04AhOlzLP8N3gRRW0J+vLQdLB+7USeyDlNgbf7HPhuNlvekPsAwh/BxDxdf
bClIfmr3peYd
=lto4
-----END PGP SIGNATURE-----


Reply to: