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 #862113,
regarding gcc-6: Generate reproducible output independently of the build path
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.)
--
862113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862113
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gcc-6
Version: 6.3.0-16
Severity: wishlist
Tags: patch upstream
User: [email protected]
Usertags: build-path
Dear Maintainer,
I've been asked to file this bug report so that others working on the
Reproducible Builds project can better track the ongoing issue of
build-path-independent reproducibility in various tools and compilers. I don't
mean to imply to rush this process nor pressure you, this report is only for
informational purposes.
As you know, I've already contacted upstream with a proposed patch:
- https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00513.html
These (backported to GCC-6) may be browsed as git commits here:
-
https://anonscm.debian.org/cgit/reproducible/gcc-6.git/log/?h=pu/reproducible_builds
The built packages may be downloaded here:
- https://reproducible.alioth.debian.org/debian/
- https://tests.reproducible-builds.org/debian/index_repositories.html
(overview)
The reproducibility status of dependent packages is being tracked on these
pages:
-
https://tests.reproducible-builds.org/debian/issues/unstable/captures_build_path_issue.html
We're currently waiting to hear back from upstream to see what they think.
However, I don't think the patch is missing any functionality and is unlikely
to negatively affect any other packages.
Ximin
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (300, 'unstable'), (200, 'experimental'), (1,
'experimental-debug')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gcc-6 depends on:
ii binutils 2.28-4
ii cpp-6 6.3.0-16
ii gcc-6-base 6.3.0-16
ii libc6 2.24-10
ii libcc1-0 6.3.0-16
ii libgcc-6-dev 6.3.0-16
ii libgcc1 1:6.3.0-16
ii libgmp10 2:6.1.2+dfsg-1
ii libisl15 0.18-1
ii libmpc3 1.0.3-1+b2
ii libmpfr4 3.1.5-1
ii libstdc++6 6.3.0-16
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages gcc-6 recommends:
ii libc6-dev 2.24-10
Versions of packages gcc-6 suggests:
ii gcc-6-doc 6.3.0-1
pn gcc-6-locales <none>
ii gcc-6-multilib 6.3.0-16
pn libasan3-dbg <none>
pn libatomic1-dbg <none>
pn libcilkrts5-dbg <none>
pn libgcc1-dbg <none>
pn libgomp1-dbg <none>
pn libitm1-dbg <none>
pn liblsan0-dbg <none>
pn libmpx2-dbg <none>
pn libquadmath0-dbg <none>
pn libtsan0-dbg <none>
pn libubsan0-dbg <none>
-- no debconf information
--- 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 ---
