Upstream tarball keeps changing
(1) By Wouter (sharkwouter) on 2022-02-20 11:22:35 [source]
For the PSPDEV project, a homebrew SDK for the Playstation Portable, we've been packaging SQLite version 3.7.3 from a snapshot tarball and applying a patch to it. We've noticed that the checksum of this tarball has changed for the second time in 2 months now, though. What is up with that? Is this the policy at SQLite or should I be worried?
It's about this tarball: https://www.sqlite.org/src/tarball/26778480/SQLite-26778480.tar.gz
The sha256 hash for this file was: 02703fd07e5050ff627d27e23a0313a4a8288d7a2e6b4678f899b53b16286a50
Then it changed to: bb49ad9c7d0e10f9c0862fdfc57dd6bfe5164b478a464179f3d34ca847a46dc6
And now it changed again...
(2) By Richard Hipp (drh) on 2022-02-20 11:51:13 in reply to 1 [link] [source]
The most recent change was probably due to this check-in to Fossil:
Perhaps the previous hash change was due to this:
The tarballs you are downloading are computed on demand. In particular the "manifest" file contained within the tarball is constructed from repository metadata. The second change above added a harmless comment line at the end of that file. The most recent change took that comment back out again.
(3) By Wouter (sharkwouter) on 2022-02-20 13:03:16 in reply to 2 [link] [source]
Ah, that explains it. Thanks for the reply! We're changing to downloading a tarball from a tag on the github mirror.