On 2026-10-18, Santiago Vila wrote: > On Tue, Sep 22, 2026 at 01:51:13PM -0700, Vagrant Cascadian wrote: >> On 2026-01-15, Chris Lamb wrote: >> > Whilst working on the Reproducible Builds effort [0], we noticed that >> > tea-cli could not be built reproducibly. >> > >> > This is because the generation of BUILD_DATE in debian/rules (which ends >> > up in a manpage) took into account the surrounding timezone which, of >> > course, can vary. >> > >> > Patch attached that ensures that BUILD_DATE is always generated in the >> > "UTC" timezone. >> >> I just confirmed that this patch is still needed. >> >> I would like to perform an Non-Maintainer Upload (NMU) applying the >> patch to fix the issue in the coming weeks. >> >> Please let me know if there are outstanding concerns! > > Sorry for taking so long to process this. > > I've finally done a team upload with the proposed change.
You are much faster than many, thanks for getting to it! > Note mainly for Vagrant, who took the time to do a MR: My personal > preference for MRs, which is also my recommendation, is that they do > not update debian/changelog, this way I can still use gbp-dch, which > collects all the commits included in the release. > > Rationale: When I see a MR I often have to face this dilemma: Either I > accept it "as is" and then change what I don't like (for example, a > changelog entry saying it's a NMU), or I just take the pieces which I > want and do the merge "by hand", but then the merge request has to be > closed in red, which is not nice... (well, there is still a third way, > which is to force-push to the external branch before accepting the MR > when the person doing MR allows that, which is quite often). That would normally be my preference as well for all the same reasons, although since I actually submitted the NMU to DELAYED/10, I figured it was best to submit with the exact changes (including the signed tag). Happy to see the fixes included! live well, vagrant
signature.asc
Description: PGP signature
