Hi, Cyril Brulebois <[email protected]> wrote (Fri, 15 May 2026 21:48:40 +0200): > 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.
I see. > 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) I'm absolutely clueless about all this. I don't remember anything special with that upload ... And I always use 'dch -i' when preparing my uploads. > ((The git repo also features a 1.248 tag that probably doesn't belong > there.)) Yes, that's my fault. That tag should have go to console-setup. I fixed that. Thanks! Holger -- Holger Wansing <[email protected]> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
