Debian Bug report logs - #991020
gcc-mingw-w64: embeds path to sed which differs with usrmerge

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@reproducible-builds.org>

To: submit@bugs.debian.org

Subject: gcc-mingw-w64: embeds path to sed which differs with usrmerge

Date: Mon, 12 Jul 2021 22:56:33 -0700

[Message part 1 (text/plain, inline)]

Source: gcc-mingw-w64
Severity: normal
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: usrmerge
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

The path to sed is embedded in various binaries, which differs on a
usrmerge vs. non-usrmerge system.

  https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/diffoscope-results/gcc-mingw-w64.html

  ./usr/lib/gcc/i686-w64-mingw32/10-posix/install-tools/fixincl

  /bin/sed
  vs.
  /usr/bin/sed

Patch attached which passes the SED variable to configure to use the
non-usrmerge location, as usrmerge installations typically have
compatibility symlinks, but not vice-versa.


This should make gcc-mingw-w64 reproducible in the testing suite on
tests.reproducible-builds.org, but does not resolve all tested
variations (e.g. build paths) in the unstable and experimental suites.


live well,
  vagrant

[0001-debian-rules-Pass-explicit-path-for-sed.patch (text/x-diff, inline)]

From 1186fd00803ff053eb5dac817bd72e994ba0f506 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@reproducible-builds.org>
Date: Tue, 13 Jul 2021 05:48:59 +0000
Subject: [PATCH] debian/rules: Pass explicit path for sed.

Use the non-usrmerge path for sed binary, which works on both usrmerge
and non-usrmerge systems.

https://tests.reproducible-builds.org/debian/issues/paths_vary_due_to_usrmerge_issue.html
---
 debian/rules | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/debian/rules b/debian/rules
index b71f935..ba60795 100755
--- a/debian/rules
+++ b/debian/rules
@@ -256,6 +256,10 @@ CONFFLAGS += \
 CONFFLAGS += \
 	--enable-dependency-tracking
 
+# Use the most compatible path for sed (e.g. non-usrmerge).
+CONFFLAGS += \
+	SED=/bin/sed
+
 spelling = grep -rl "$(1)" $(upstream_dir) | xargs -r sed -i "s/$(1)/$(2)/g"
 
 # Patches applied or unapplied after the upstream sources have been
-- 
2.20.1

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 991020-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 991020-close@bugs.debian.org

Subject: Bug#991020: fixed in gcc-mingw-w64 24.3

Date: Fri, 11 Feb 2022 16:48:50 +0000

Source: gcc-mingw-w64
Source-Version: 24.3
Done: Stephen Kitt <skitt@debian.org>

We believe that the bug you reported is fixed in the latest version of
gcc-mingw-w64, 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 991020@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt <skitt@debian.org> (supplier of updated gcc-mingw-w64 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: SHA512

Format: 1.8
Date: Fri, 11 Feb 2022 17:25:46 +0100
Source: gcc-mingw-w64
Architecture: source
Version: 24.3
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt <skitt@debian.org>
Changed-By: Stephen Kitt <skitt@debian.org>
Closes: 932969 986615 991020
Changes:
 gcc-mingw-w64 (24.3) unstable; urgency=medium
 .
   * Add gnatgcc links, attached to the gnat links; this allows gprbuild to
     find the appropriate gcc. Closes: #932969.
   * Drop the asterisk from NEWS, to follow best practices as documented
     in <https://www.debian.org/doc/manuals/developers-reference/best-
     pkging-practices.html#supplementing-changelogs-with-news-debian-
     files>.
   * Make 4.3 broke the space construction in debian/rules, use a space
     directly instead.
   * Mark gcc-mingw-w64-base as “Multi-Arch: same”. Closes: #986615.
   * Enforce the use of /bin/sed to ensure reproducibility across
     usrmerge; thanks to Vagrant Cascadian for the patch. Closes:
     #991020.
   * Drop the obsolete patch-file-present-but-not-mentioned-in-series
     Lintian override.
   * Override the non-standard-file-perm Lintian warning for ALI files.
   * Fix the spelling of “shouldn’t”.
   * Standards-Version 4.6.0, no change required.
Checksums-Sha1:
 09ae747ca79ede0813d1fcdef45e7f5be495c50e 6777 gcc-mingw-w64_24.3.dsc
 dbfda68ae131d7a8d8404e90ac930a730df60abe 34680 gcc-mingw-w64_24.3.tar.xz
 3978c3bd69a200f30a032429e1201438d0b34a06 7519 gcc-mingw-w64_24.3_source.buildinfo
Checksums-Sha256:
 8636b07eddf17b5a870901bfdf6fa6c70ca35de4c0285bac7d70d9380a0ad1a2 6777 gcc-mingw-w64_24.3.dsc
 fedd36a7a285f2a396ae5e001664c3188b91b45d704d5505914e8a11f05f2909 34680 gcc-mingw-w64_24.3.tar.xz
 f5faec70208a659ebe27990254aca10d8ab9a87299cbb01d2b30e01ff3426dc2 7519 gcc-mingw-w64_24.3_source.buildinfo
Files:
 7ed2c8c68aa27ba8afedd7772fd79854 6777 devel optional gcc-mingw-w64_24.3.dsc
 2283cd01db3956e32ec62e9cf424cba1 34680 devel optional gcc-mingw-w64_24.3.tar.xz
 fb9500a2292a79ff86600e92c1cdfa57 7519 devel optional gcc-mingw-w64_24.3_source.buildinfo

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

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmIGjhkACgkQgNMC9Yht
g5zhkQ//a6dl/cnhZX6vYqO8+Fc6wYvt7CiMCI0LMPnoVCzJc27mXxKSZEBBSLAJ
m0eI1VBRusTpvDP1OBP0QJnxKFkFgz1AQfepoi4aDalDoGrPwWWwCVDyIUKYfqiA
kgTMsm5y/C+u8aEVz/R73B6q3BIJ5jx/2lla2Uw0UWA/Peg1dNHTKAzVXZnsDq9D
boD2VE49GGdJJqg8ACmjw3ncmxGyYEoVsNUM/bGPNlTDEIIWfrF81bvZEyQUHScu
ILNTzcscBZ5jUEsKDn32XbANQAmECNwVMN7XreHrTLnSBtQ1WRVfozux37Pj4e3x
A52mgHtMHze2ypaDKQNDyvgjJ2atuRzlgLHyaYklIF4JUVGWd8zq+bF0uEzzzi96
5ppDWiumsJRCpL+Rtcav7xYr8G+oCEABVRO4fs9+sOz0cgEm8YJujX0dyNo6r/93
+DohEwG0/qrV+gVHw4kzFhW8KhRb3GFF0JeidrgKDiIrJ2d+3ftkb4+/v5NSKK3p
+X4z5eLY8g8EFrYzqiv6vvsksU/8/kwYgx65VAVNiQ5yvBdvFw7c+7vf/1/fMJ5r
AhwrdZXrxxengHPmRNWrhZ6OwwtoYUrpv2a53+MnOIYCNUUUKSy8iJ3FS2whF1ql
N5VVjWaQuEDFIwj8hgVoAHessB7M7M8kH4vnzXsnggb3CryPFr4=
=JwSY
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.