Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid checksum for package ctypes_stubs_js.0.1 #23587

Closed
mjambon opened this issue Mar 28, 2023 · 3 comments
Closed

Invalid checksum for package ctypes_stubs_js.0.1 #23587

mjambon opened this issue Mar 28, 2023 · 3 comments

Comments

@mjambon
Copy link
Contributor

mjambon commented Mar 28, 2023

The expected checksum is

#=== ERROR while fetching sources for ctypes_stubs_js.0.1 =====================#
OpamSolution.Fetch_fail("https://gitlab.com/nomadic-labs/ctypes_stubs_js/-/archive/0.1/ctypes_stubs_js-0.1.tar.gz (Bad checksum, expected sha256=74ab170e064bff88eaa592efc992d24fa1665c67047fc822276eae52c0f3384d)")

The new checksum I'm getting is

$ wget https://gitlab.com/nomadic-labs/ctypes_stubs_js/-/archive/0.1/ctypes_stubs_js-0.1.tar.gz
$ sha256sum ctypes_stubs_js-0.1.tar.gz 
7c40ffcfda29cb407cb05b7837fe0dc46e18acc8b9a023afb58aa8751ec795e1  ctypes_stubs_js-0.1.tar.gz
@sim642
Copy link
Contributor

sim642 commented Mar 29, 2023

Not the same package, but also a checksum issue with GitLab-generated tag archive.
Over the last few days I've seen similar errors with the json-data-encoding package, e.g.:

#=== ERROR while fetching sources for json-data-encoding.0.12.1 ===============#
OpamSolution.Fetch_fail("https://gitlab.com/nomadic-labs/json-data-encoding/-/archive/0.12.1/json-data-encoding-0.12.1.tar.gz (Bad checksum, expected md5=f70939e5bcaae19f5996e05d3baf5536)")

Also for other versions of it, e.g. 0.8.

Also, some builds seem to not get the error while others do, so maybe there's something broader going on on the GitLab side with different hosts serving differently checksummed archives?

@kit-ty-kate
Copy link
Member

Apparently it's going to be fixed today or tomorrow according to #23589 (comment)

In the meantime if you use

opam repo set-url default https://opam.ocaml.org

instead of the git repository, the opam cache should be used by default, or if you want to keep using a git repository you can use

opam option 'archive-mirrors="https://opam.ocaml.org/cache"'

@hannesm
Copy link
Member

hannesm commented Jan 5, 2025

This specific issue is fixed in the opam-repository. Thanks for your report.

@hannesm hannesm closed this as completed Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants