GNU Astronomy Utilities - Bugs: bug #59074, Tarball contains creation date,...
You are not allowed to post comments on this tracker with your current authentication level.
bug #59074: Tarball contains creation date, making it non-reproducible
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Mon 07 Sep 2020 03:01:34 AM UTC | ||
Category: | Installation | Severity: | 3 - Normal |
Item Group: | Output not reasonable | Status: | Postponed |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-09-07 | makhlaghi | Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-d3ae.
Corresponding source code
After the release of Gnuastro 0.13, it was reported that the checksums don't match (while the GPG signature was valid!).
After looking into the difference (in P.S.), I just noticed what happened: First I made the tarballs, gpg-signed them and uploaded them to gnu.org. Then something came up and I had to go do other things. In the process, I (unintentionally!) deleted the old tarballs (they were in a temporary directory!). Also, in this period, the hour passed midnight in my timezone!
So in the newly created tarball, the date in the automatically generated file ('doc/version.texi') was changed, causing this problem!
Having the date hard-coded in the tarball thus makes it non-reproducible, which is not good! We should remove this and just get the date at run-time, not hard-code it in the source.
P.S.