rm-config should handle SOURCE_DATE_EPOCH
While preparing 4.19~rc1 I messed up: I set the wrong SOURCE_DATE_EPOCH
when building the IUKs on Jenkins, so they didn't match what I built, and I thought we had something like #17976 (closed) all over again, spending quite some time before I understood my mistake.
Specifically, what happened was this: I had started building the IUKs locally, and that was the terminal where I had set SOURCE_DATE_EPOCH
. In parallel I wanted to start the IUK building on Jenkins (which the release notes suggest), so I started another terminal, ran the expected command to recover the required env:
. $(./bin/rm-config generate-environment --stage reproduced-images)
except that I also had to run
export SOURCE_DATE_EPOCH=$(date --utc --date="$(dpkg-parsechangelog --show-field=Date)" '+%s')
to get SOURCE_DATE_EPOCH
.
However, the only problem was that I had checked out WEBSITE_RELEASE_BRANCH
(as a result of following the release instructions), in which the last release in debian/changelog
is 4.18, and not 4.19~rc1, so I got the SOURCE_DATE_EPOCH
for 4.18. So I've wasted a lot of time on this, which would be prevented if rm-config
also handled SOURCE_DATE_EPOCH
.