D. Richard Hipp <d...@hwaci.com> schrieb: > > The mingw_cross_env verifies all downloads via their SHA-1 checksum. > > However, the SQLite source package changes every few hours. [...] > > The amalgamations packages changed once after the release announcement > because the first package we put up was a defective build. This was > brought to our attention and we reran the build and put up new and > corrected amalgamation packages.
Thanks for your quick reply. That information helps me a lot. > If you have seen the amalgamation SHA1 sums change more than one time, > that is an indication of unauthorized hacking of the SQLite website. > Please let us know. But if you saw just this one change, then please > discard the first amalgamation and use only the second one. I did notice at least three different checksums, i.e. at least two changes. However, maybe I just downloaded the package while the regeneration or upload was in progress? Anyway, the current download has exactly the checksum you were providing to me: > 950855d9eed9b8bd6fad406cece5a24b640c3e3f sqlite- > amalgamation-3.6.13.tar.gz So I think the problem is solved now. I'll update the checksum in mingw_cross_env and hope there won't be any sudden changes in the future. In case of last corrections I strongly recommend to use a different version number, something like "3.6.13a" or "3.6.14". That simple trick prevents a lot of confusion. Greets, Volker -- Volker Grabsch ---<<(())>>--- Administrator NotJustHosting GbR _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users