Skip to content
Discussion options

You must be logged in to vote

Heya!

It turned out the issue was in fact downstream with argon2 itself. It has to do with argon2 v.1.0.2 not being published (ocaml/opam-repository#24314). It fixes the issue

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by MarcCoquand
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant