Hi, Holger Wansing <[email protected]> (2026-05-15): > I don't get what you mean by "the timestamp in the debian/changelog > being set to the future with respect to the time of the upload to the > Debian archive".
Note this issue is about the previous version: https://tracker.debian.org/news/1726921/accepted-finish-install-2125-source-into-unstable/ From the changelog: Date: Sat, 07 Mar 2026 23:33:26 +0100 From the accepted mail: Date: Sat, 07 Mar 2026 20:41:43 +0000 which is earlier than the changelog entry. Packages getting built between both dates don't get their timestamps clamped to the date in the changelog, while builds that happen later do, which breaks reproducibility (later builds are all similar, but they're different than the initial builds). https://reproducible-builds.org/docs/source-date-epoch/ https://reproducible-builds.org/specs/source-date-epoch/ I'm not sure how that happened, but I'd recommend `dch -r` or similar in case some update is needed (as opposed to manually editing dates). (The git commit seems even weirder: - changelog: Sat, 07 Mar 2026 23:33:26 +0100 - git metadata: Sat Mar 7 21:20:18 2026 +0100) ((The git repo also features a 1.248 tag that probably doesn't belong there.)) Cheers, -- Cyril Brulebois ([email protected]) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
