* Johannes Schauer Marin Rodrigues <jo...@debian.org> [250507 17:58]:
On Wed, 7 May 2025 14:01:19 +0200 Chris Hofstaedtler <z...@debian.org> wrote:
Thanks for writing this up.
* Ian Jackson <ijack...@chiark.greenend.org.uk> [250507 13:45]:
> A. Shared files in ma-same packages are not allowed to embed S_D_E.
> For example, no dates in libopts25-dev's manpages. Other
> situations (eg, other docs) will be handled similarly.
I think we are already in this situation, and already varying files
in M-A: same binaries earn the affected packages an rc-bug.
I'll also propose another option, lets call it Holger's Option D:
Set S_D_E to sdate + an offset in seconds of int(binNMU-number).
I have a déjà vu: #843773
That bug was triggered by Ian's mail in 2016 here:
https://lists.debian.org/msgid-search/22562.21637.415611.768...@chiark.greenend.org.uk
Until we get rid of binNMUs, I thought the workaround was that missing binNMUs
get triggered for packages that somehow got out-of-sync before the release to
get them back in sync for the release? wanna-build can send the binNMU
changelog entry including the timestamp to sbuild so that the same timestamp is
used across all architectures. This includes potentially incrementing the
timestamp by a second for each binNMU number so that backups do not break.
Is this timestamp-sending implemented?
I thought we had "fixed" the problem this way a while ago and in cases like
libopts25-dev just some more binNMU scheduling was the answer?
The changelogs look like this:
autogen (1:5.18.16-5+b2) sid; urgency=low, binary-only=yes
* Binary-only non-maintainer upload for amd64; no source changes.
* Rebuild for PAC/BTI support
-- all / amd64 / i386 Build Daemon (x86-grnet-03)
<buildd_amd64-x86-grnet...@buildd.debian.org> Mon, 28 Oct 2024 15:28:42 +0000
autogen (1:5.18.16-5+b2) sid; urgency=low, binary-only=yes
* Binary-only non-maintainer upload for s390x; no source changes.
* Rebuild for PAC/BTI support
-- s390x Build Daemon (zani) <buildd_s390x-z...@buildd.debian.org> Tue, 29
Oct 2024 03:41:50 +0000
So, if the timestamps are sent to sbuild, at least in Oct 2024 it didn't use
them to produce the changelogs?
Chris
