-
Notifications
You must be signed in to change notification settings - Fork 365
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
Silently mark packages requiring an unsupported version of opam as unavailable #5665
Conversation
50bbdf2
to
85f6ebe
Compare
692465f
to
b88b9a4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this PR is an excellent idea - it concludes groundwork I laid in ocaml/opam-file-format#44 in opam 2.1.
9a675df
to
b7a875f
Compare
b7a875f
to
82fab22
Compare
Updated the PR |
6fe9a90
to
f34f3b7
Compare
rebased |
f34f3b7
to
62d8e8e
Compare
62d8e8e
to
da3d901
Compare
Once rebased on top of 6199, good to go! |
73a0cfa
to
60039ce
Compare
…sitories containing opam files with an unsupported version
60039ce
to
03296d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
03296d2
to
537d216
Compare
Fixes #5631
This makes it possible to have a smoother upgrade path for the opam repository when opam adds a new syntax for example.
In the future it would be nice to have a specific error message to tell the user why this package is not available, but I feel like we can do this later (TODO: open a ticket for it if this is merged first)