Inconsistent top level directory name in source tarball vs tarball version
(1) By Bonnietwin (bonnietwin) on 2023-09-12 18:27:13 [link] [source]
I downloaded the sqlite-autoconf-3430101.tar.gz source tarball to do an update in the IPFire firewall distribution currently on 3430000 but the IPFire build failed.
The problem is that the top level directory in the 3430101 source tarball is actually labelled 3430100 and the IPFire build looks for the the top level directory to be the same as the tarball version.
Was this just an error or is it standard that the minor versions will never be used in the source tarball top level directory?
I need to know if I have to modify the build just for this version or if the coding has to be modified in general also for future versions.
(2) By Richard Hipp (drh) on 2023-09-12 20:33:59 in reply to 1 [link] [source]
Please do me this favor: Download (the recently updated)
"sqlite-autoconf-3430100.tar.gz" file and let me know whether or not
the new version of that file works for you. Let me know either way, please.
(3) By Bonnietwin (bonnietwin) on 2023-09-12 21:14:14 in reply to 2 [source]
I can confirm that using the file labelled "sqlite-autoconf-3430100.tar.gz" works as all previous builds of sqlite have and completed build with no problems.
I take it that the filename shouldn't have been 3430101
Thanks very much for the rapid update.
(4) By flavorjones on 2023-09-13 14:55:04 in reply to 2 [link] [source]
I'd like to confirm that the checksum has changed for this file:
- was originally 8c6242fb2abf6a556e849d259134aca9130520b2218f9a7fb1f50eb0528a385a
- is now fd32866c281539eae95cd90b5c2c34337d8808822a988211b9b009c1e788e42d
It seems strange for a checksum to change after a release has been made, so I wanted to check that this was intentional.
(5) By jose isaias cabrera (jicman) on 2023-09-13 15:28:20 in reply to 4 [link] [source]
I believe there was a change after the release for a minor fix. This may have caused the change in checksum.