Ubuntu
binutils-mingw-w64 package

unrecognized option '--insert-timestamp=1686475264'

Bug #2036527 reported by Shengjing Zhu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
binutils-mingw-w64 (Debian)
Fix Released
Unknown
binutils-mingw-w64 (Ubuntu)
Invalid
Undecided
Unassigned
gcc-mingw-w64 (Ubuntu)
Fix Released
Undecided
Unassigned
libgcrypt20 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

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.

Tags: ftbfs

Related branches

~zhsj/ubuntu/+source/libgcrypt20:bug2036527
Robie Basak: Approve
Shengjing Zhu: Pending requested
Brian Murray: Pending requested
Diff: 354 lines (+229/-1)
4 files modified
debian/changelog (+192/-0)
debian/control (+2/-1)
debian/patches/disable_fips_enabled_read.patch (+32/-0)
debian/patches/series (+3/-0)
~zhsj/ubuntu/+source/gcc-mingw-w64:bug2036527
Brian Murray (community): Disapprove
Shengjing Zhu (community): Disapprove
Diff: 39 lines (+9/-2)
3 files modified
debian/changelog (+7/-0)
debian/control (+2/-1)
debian/rules (+0/-1)
Shengjing Zhu (zhsj)
tags: added: ftbfs
Bug Watch Updater (bug-watch-updater)
Changed in binutils-mingw-w64 (Debian):
importance: Undecided → Unknown
status: New → Incomplete
Bug Watch Updater (bug-watch-updater)
Changed in binutils-mingw-w64 (Debian):
status: Incomplete → Fix Released
Shengjing Zhu (zhsj)
Changed in binutils-mingw-w64 (Ubuntu):
status: New → Invalid
Revision history for this message
Matthias Klose (doko) wrote :

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

Shengjing Zhu (zhsj)
Changed in gcc-mingw-w64 (Ubuntu):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in libgcrypt20 (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.