unrecognized option '--insert-timestamp=1686475264'

[Shengjing Zhu]

Imported from Debian bug http://bugs.debian.org/1052219:

Package: binutils-mingw-w64-i686
Version: 2.41-4+11+nmu1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: <email address hidden>, <email address hidden>

The NMU binutils-mingw-w64/11+nmu1 drops specify-timestamp.patch.
It causes libgcrypt20, gcc-mingw-w64 FTBFS.

These packages use options like --insert-timestamp=1686475264,
which is not supported in upstream implementation.

I find such option is mentioned on
https://wiki.debian.org/ReproducibleBuilds/TimestampsInPEBinaries
It looks like Debian specific behaviour.

[Matthias Klose (doko)]

that information from the wiki page is from 2015, maybe not accurate anymore

[Launchpad Janitor (janitor)]

This bug was fixed in the package libgcrypt20 - 1.10.2-3ubuntu1

---------------
libgcrypt20 (1.10.2-3ubuntu1) mantic; urgency=medium

  * Merge with Debian unstable. Remaining changes:
    - d/p/disable_fips_enabled_read.patch
      Disable the library reading /proc/sys/crypto/fips_enabled file
      and going into FIPS mode.
      libgcrypt is not a FIPS certified library.
  * Dropped changes, not needed:
    - d/p/12_lessdeps_libgcrypt-config.diff: refresh patch offsets
  * For Ubuntu, this fixes an FTBFS by following Debian 1.10.2-3 in
    dropping the use of --insert-timestamp (LP: #2036527).

libgcrypt20 (1.10.2-3) unstable; urgency=medium

  [ Simon Josefsson ]
  * Update Homepage: URL.

  [ Andreas Metzler ]
  * Drop --insert-timestamp linker option on mingw*, binutils 2.41 should use
    SOURCE_DATE_EPOCH automatically and the Debian package has dropped the
    patch to add the --insert-timestamp option. Closes: #1052219

 -- Shengjing Zhu <email address hidden> Thu, 28 Sep 2023 09:51:31 +0000