Closed mbarbin closed 1 year ago
Hmm, not a solution to the failing checksums, but I also came across this issue when running opam install bonsai
.
I got around this by sending in --no-checksums
to opam install
. I am unsure if opam monorepo pull
has a similar argument
We are investigating the problem, seems like something broke in our export pipeline. The latest push also has broken checksums.
For now, please use --no-checksums
in opam install
. The actual contents of tarballs are unaffected.
The issue has been fixed, thanks for the report! Please run opam update
to ensure you have the newest commit.
I'm experimenting with a new workflow locally using opam monorepo and pulling from jane-bleeding, and I'm hitting the following error message during a
opam monorepo pull
:I don't have experience yet using opam and this janestreet repo that way, so I currently don't understand the issue. Note that several jane-bleeding packages of this version seem to update just fine, so I don't know why accessor would be special.
Do you know how checksum are computed locally by opam for verification, and how I could trouble shoot ?
Thanks!