[Bug 2036527] Re: unrecognized option '--insert-timestamp=1686475264'

[Bug Watch Updater]

** Changed in: binutils-mingw-w64 (Debian)
       Status: New => Incomplete

** Changed in: binutils-mingw-w64 (Debian)
   Importance: Undecided => Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libgcrypt20 in Ubuntu.
https://bugs.launchpad.net/bugs/2036527

Title:
  unrecognized option '--insert-timestamp=1686475264'

Status in binutils-mingw-w64 package in Ubuntu:
  New
Status in gcc-mingw-w64 package in Ubuntu:
  New
Status in libgcrypt20 package in Ubuntu:
  New
Status in binutils-mingw-w64 package in Debian:
  Incomplete

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: olasd at debian.org, zhsj at debian.org

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils-mingw-w64/+bug/2036527/+subscriptions