Your message dated Wed, 26 Apr 2023 08:50:50 +0200
with message-id <[email protected]>
and subject line gcc-6 has been removed from Debian
has caused the Debian Bug report #846148,
regarding 6.2.1 breaks upstream's kernel
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 [email protected]
immediately.)
--
846148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846148
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Package: gcc-6
Version: 6.2.1-5
Upstream's kernel (4.8.11) built with gcc 6.2.1 freezes with the
message "loading initial ramdisk ..." at boot time.
Moving back to 6.2.0-6 fixes the problem. Same config file, of
course.
How comes that Debian suddenly uses the bleeding edge gcc as the
default compiler? Maybe I am too blind to see, but 6.2.1 cannot
even be found on ftp.gnu.org.
A few years ago the default compiler was chosen *very* carefully.
I miss that.
Regards
Harri
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEH2V614LbR/u1O+a1Cp4qnmbTgcsFAlg8arMACgkQCp4qnmbT
gcuZAAf/ZxX2ecd849OVPgIPh4ZuLsRFyrjclJqYUBrzzk9+YwKBwiUGoxFrlmmz
BOwC7EFRWAu71TQ8+ghbwxdOL88ENwdofffLUayzRuBYabeym7uRPmG9KRERQ5S5
MRqWIZm0e4TNDnA1dE+C0YD9FSq0fcarFKg9nOFKATrwe2CX2xYChY2ufrgbYAXy
AdYQTB1oeLcrv5mrVTBGrqdINGXcxtcHl76jUaP/S3npNVtREDmKo2KfI05/vfKl
f4ZcWnKQHhXMJQECeiwRSE2dkrpahiW7BdJVQf7lkpzl7xFiT9oqFqYxwV8RC82V
i10Kq5wWFzhHzkjwqvV6juezv1NQrw==
=MjgG
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 6.5.0-2+rm
src:gcc-6 was last released with Debian 9 (stretch)
in June 2017 and was removed from the Debian archive afterwards.
It has been superseded by newer versions.
See https://bugs.debian.org/920171 for details on the removal.
After regular security support for stretch ended in July 2020 and LTS
support ended in July 2022, I'm closing the remaining bug reports now.
In case the bug is still present in recent releases, please reopen and
reassign it.
Andreas
--- End Message ---
