On 2025-05-08 Bastian Germann <bage@debian.org> wrote:

Control: tags -1 patch

I am uploading a NMU to fix this. I have based my changes on the last
git commit, so it includes additional changes.

diff -Nru autogen-5.18.16/debian/changelog autogen-5.18.16/debian/changelog --- autogen-5.18.16/debian/changelog 2022-05-24 19:13:45.000000000 +0200
+++ autogen-5.18.16/debian/changelog 2025-05-08 20:03:08.000000000 +0200
@@ -1,3 +1,14 @@
+autogen (1:5.18.16-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop versioned constraint on tar
+ * Record changelog date in manpages (Closes: #1104867)
+
+ [ Andreas Metzler ]
+ * Drop ancient (2014 and pre-2008) Breaks/Conflicts/Replaces.
+
+ -- Bastian Germann <bage@debian.org> Thu, 08 May 2025 20:03:08 +0200
+
autogen (1:5.18.16-5) unstable; urgency=low

* Pull a couple of patches from Suse:

[...]

diff -Nru autogen-5.18.16/debian/rules autogen-5.18.16/debian/rules
--- autogen-5.18.16/debian/rules 2022-05-24 19:09:49.000000000 +0200
+++ autogen-5.18.16/debian/rules 2025-05-08 19:55:20.000000000 +0200
@@ -9,7 +9,7 @@
include /usr/share/dpkg/pkg-info.mk
# Used by 10_libopts_tarball_perms.diff
export MAN_PAGE_DATE = $(shell env LC_ALL=C date -u \
- -d '@$(SOURCE_DATE_EPOCH)' +%Y-%m-%d)
+ -d "$(shell dpkg-parsechangelog -SDate)" +%Y-%m-%d)

ifneq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE))
export libopts_cv_with_libregex=yes

I am going to revert this. It is a no-op, SOURCE_DATE_EPOCH is exactly
the date from debian/changelog and using /usr/share/dpkg/pkg-info.mk is preferred over invoking dpkg-parsechangelog.

cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Andreas,

Am 10.05.25 um 11:31 schrieb Andreas Metzler:

It is a no-op, SOURCE_DATE_EPOCH is exactly
the date from debian/changelog

If that is true, why does SOURCE_DATE_EPOCH change on a binNMU, which was the reason for this bug?

Thanks,
Bastian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2025-05-10 Bastian Germann <bage@debian.org> wrote:

Hi Andreas,

Am 10.05.25 um 11:31 schrieb Andreas Metzler:

It is a no-op, SOURCE_DATE_EPOCH is exactly
the date from debian/changelog

If that is true, why does SOURCE_DATE_EPOCH change on a binNMU, which
was the reason for this bug?

Hello Bastian,

a binNMU essentially does
dch --bin-nmu

which adds a new entry to debian/changelog like this:
autogen (1:5.18.16-6+b1) UNRELEASED; urgency=medium, binary-only=yes

Seeing the binary-only=yes qualifier dpkg-buildpackage (or something
related) takes care off splitting off this entry to a separate file like usr/share/doc/libopts25/changelog.Debian.amd64.gz
in the *binary* package and keeps
usr/share/doc/libopts25/changelog.Debian.gz
unchanged.

I have a googled a little bit and I think SOURCE_DATE_EPOCH used to be binNMU-compatible for autogen's usage because the actual software
triggering the binNMUs added binary-only=yes changelog entries with the
same timestamp as the previous source upload changelog entry. But that
was broken otherwise: https://lists.debian.org/debian-devel/2016/11/msg00329.html

I will use something equivalent the mtime of configure.ac instead.

cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)