Bug#1052219: unrecognized option '--insert-timestamp=1686475264'
Andreas Metzler
ametzler at bebt.de
Tue Sep 19 12:51:01 BST 2023
On 2023-09-19 Shengjing Zhu <zhsj at debian.org> wrote:
> On Tue, Sep 19, 2023 at 5:08 PM Andreas Metzler <ametzler at bebt.de> wrote:
[...]
> > Looking at the changelog entry
> > * Drop specify-timestamp.patch, applied upstream in binutils 2.41
> > (Closes: #1042734)
> > changing the rdeps does not make any sense at all, since the
> > --insert-timestamp support is now supposed to be available upstream?
> > Since binutils-mingw-w64-i686 is reported to be 2.41 the support should
> > be available. So is binutils-mingw-w64-i686 actually 2.41 and if yes,
> > why does "applied upstream" not hold?
> Upstream implements it in a different way, it doesn't take argument in
> --insert-timestamp option, it just looks SOURCE_DATE_EPOCH implicitly.
> Ref https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=6badd1020f5bebd3f60a780b8e41a1b581046087
Thanks for the explanation.
cu Andreas
More information about the Pkg-gnutls-maint
mailing list