Bug#950551: marked as done (libgcc1 should add a Breaks on cryptsetup-initramfs)
Your message dated Tue, 11 Feb 2020 07:19:22 +0000
with message-id <E1j1PpK-000BID-G6@fasolo.debian.org>
and subject line Bug#950551: fixed in gcc-10 10-20200211-1
has caused the Debian Bug report #950551,
regarding libgcc1 should add a Breaks on cryptsetup-initramfs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
950551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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"
so i think it's libgcc1 related.
had to chroot to disk from liveusb, downgrade some packages & finally use a
different kernel to boot.
noticed that update-initramfs with libgcc1 1:9.2.1-25 adds file : "Adding
binary /lib/x86_64-linux-gnu/libgcc_s.so.1" , while libgcc1 version
1:10-20200202-1 doesn't add any libgcc_s.so.1.
also, version from testing includes file /lib/x86_64-linux-gnu/libgcc_s.so.1,
while sid version uses /lib/libgcc_s.so.1 . libgcc-s1 also includes this file :
/usr/lib/x86_64-linux-gnu/libgcc_s.so.1
let me know if you need anymore info.
thanks,
d.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages libgcc1 depends on:
ii gcc-9-base 9.2.1-25
ii libc6 2.29-9
libgcc1 recommends no packages.
libgcc1 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gcc-10
Source-Version: 10-20200211-1
We believe that the bug you reported is fixed in the latest version of
gcc-10, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 950551@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated gcc-10 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 11 Feb 2020 07:20:23 +0100
Source: gcc-10
Architecture: source
Version: 10-20200211-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers <debian-gcc@lists.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Closes: 950551 950624
Changes:
gcc-10 (10-20200211-1) unstable; urgency=medium
.
* GCC snapshot, taken from the trunk (20200211, a6ee556c765).
.
[ Matthias Klose ]
* Let the libgcc-sN multilib cross packages provide libgccN.
* libgcc-sN: Move library back to /lib from /usr/lib, and add
a replaces to libgccN. Closes: #950624.
* libgcc-sN: Add break on cryptsetup-initramfs. Closes: #950551.
.
[ Aurelien Jarno ]
* debian/libgcc-s.symbols: add mipsn32el to the list of architectures
with GCC_3.3.4, GCC_4.4.0 and CC_4.5.0 symbols.
* debian/rules.conf: libgcc-s1 and corresponding multilib packages are
epochless. Adjust DEB_LIBGCC_VERSION accordingly.
Checksums-Sha1:
36580735d9b9a7f4a667430a9c90605d4aa0d9e3 27973 gcc-10_10-20200211-1.dsc
6ab38d965dfe029ee2980c39660c1478e4b9b4ad 75763549 gcc-10_10-20200211.orig.tar.gz
3fbffa4f5d76197f73081cdf8b08e4ebc42d72c4 556424 gcc-10_10-20200211-1.debian.tar.xz
dbd92b145a4e1e52d736811d02a3715398b70e08 10605 gcc-10_10-20200211-1_source.buildinfo
Checksums-Sha256:
0040f2ffc9ddf1ab383c0734e49af6d00707b1e03b90e15e85ad739d05a76845 27973 gcc-10_10-20200211-1.dsc
17319478396aaacf8ad20612326df9cccd240e330bc5085136d4d9ec895c0294 75763549 gcc-10_10-20200211.orig.tar.gz
f69d2978310e960c9fa3249cb6cb66ab755eb4eece7ff1b92d91dec27c2866d6 556424 gcc-10_10-20200211-1.debian.tar.xz
e26a7b59cfe6e40795cbb0d4f29f3b54186c7efaf5ccd89182e97841951c731d 10605 gcc-10_10-20200211-1_source.buildinfo
Files:
b2f73cac4253e64cf5e46bb4b15cfecd 27973 devel optional gcc-10_10-20200211-1.dsc
b16aac84d7b1e6810ccc66aea17b14d2 75763549 devel optional gcc-10_10-20200211.orig.tar.gz
5f9e88351b5784ae13140f92cf944e32 556424 devel optional gcc-10_10-20200211-1.debian.tar.xz
ee3c790c6c448b20cd4d4c27366a83f0 10605 devel optional gcc-10_10-20200211-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl5CSpsQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9dfcD/sGibgeTNps+d7KByOrU36d21WspfMc/Ufn
GbmRIbwEY5nV8hpgnaK0VFy3lllH7LOcdKrNGvIqUNFn5OibN8gagWZA2MciLwU7
iGz57sa31r74f4IsUrxqWwRwwUpnOQmFRmwdiYHnDG6StDkKVNROIxY+F7s+OJOk
K85BNj1hb4Gbfhmde/8Bqu2Bw2NgdiFtflzzTpjAJHi7r+c/84hAfMG5BzddVX7J
Ds8sPQZmTnF3onDM6hK53ciKbQnc467EQW/b3TtfW+/cBMPJ1hFo97tMzusz8JHC
GvDMCjtVO7VW1ntVvGhFjWj0757I7KsoSr/eC04qti2lDa4DM9LC+C417wrDilve
2nn5Nim5V53bma+zJ9VcUqCj48122lNS0N4zFHMo0vQ3HYbK47suFyxTXJA3lZJX
2m8FuL1Sb1RBV3XoBNetxlq8tP/jeA7WQ8ciJz4i7Rgt8WD7oXHmYd467zj/sFvo
NlxapYjBUXtMmr0UmHT0o4hGGSZFGSjCHiqI//cJe/wyy0fqBpGb1o1T6cLIzKA4
r7k/2jeZrRMzb7QRetbKO9Wr7YwhEGJUk+wL0kFib0OD3HuDWk3z2/fJWqPP9a5l
oPz7WwbBhepT/uxDRc/yIGKWzS1FLMfMQtpuW5gNVaknMq+bCpMJxrCGKOufFRA9
4inrvJGo1w==
=vu4k
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: