@Ali Caglayan : since yesterday I get in the Coq Platform CI "bacd checksum" errors on HoTT packages (various versions and only HoTT). I had this in the past for another project and the root cause was some change in GIT server settings, so that different files are included in the tar ball - which changes the checksum (stuff like .gitignore afair).
You should either change back the GIT server settings or update the checksums in all opam packages.
I double checked
OPAM: sha512=3a8e3c51f1802f21b26a8279babdcd38c61d87010f4dc9d4c823c77f746af981817cab17ef231507196ee1ef87b59fdbf6d26e046f5780f3faf0ce17f5ee10d6 openssl: SHA2-512(V8.16.tar.gz)= 7190e416abca853b4d84a57f9dc97b158bc80fb1b85f14a8fde0549401768b7b31ac04569f64ce003d69eedf3ae8f2ae9920584e0aaee11f9512a1482de0fe0e
@Karl Palmskog : FYI.
We have renamed the Hott repo to Coq-HoTT
The fact that this changes the checksum is a bit unfortunate.
Will we have a redo all of the checksums?
yes, a change in repo name will mean all tarballs are regenerated and checksums changed
@Ali Caglayan can you submit an opam archive PR with the updated checksums?
I am not quite sure I understand this - if the repo name changed, shouldn't also the tar ball URL in the opam files change?
GitHub sets up forwarding for those URLs
so ideally Ali changes the URLs as well so we don't have the forwarding
This would definitely add to clarity. I usually consult opam on whereabouts of Coq projects.
And I guess things like issue URLs should also be changed while doing this.
I've changed the URLs and the checksums: https://github.com/coq/opam-coq-archive/pull/2376
I used opam lint for the first time for the checksums
Much smoother than manually making the checksums as I was doing before
I wish opam lint had an update feature for the checksums tho
Last updated: Jan 30 2023 at 11:03 UTC