-
Notifications
You must be signed in to change notification settings - Fork 21
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
Bad version number in 2.1.0 #10
Comments
hannesm
added a commit
to hannesm/ocaml-base64
that referenced
this issue
Oct 14, 2016
I fixed the META issue in #11. The 2.1.1 vs 2.1.0 -- maybe we should rename the thing in opam-repository (the url of 2.1.0 there points to v2.1.1.tbz)? |
this issue is not fixed, only a future release (or a local patch in opam-repository) will fix the META issue... |
samoht
added a commit
to samoht/opam-repository
that referenced
this issue
Oct 18, 2016
Which explains why the URL was wrong. Fixes mirage/ocaml-base64#10
dsheets
pushed a commit
to ocaml/opam-repository
that referenced
this issue
Oct 18, 2016
Which explains why the URL was wrong. Fixes mirage/ocaml-base64#10
fdopen
added a commit
to fdopen/opam-repository-mingw
that referenced
this issue
Oct 18, 2016
Which explains why the URL was wrong. Fixes mirage/ocaml-base64#10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After installing base64 with opam:
The version number is not the same (2.1.1 instead of 2.1.0) and having 'v' at the beginning of the version number is not standard.
The text was updated successfully, but these errors were encountered: