-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Usage of pin-depends
in opam-repository released packages
#14978
Comments
However, about |
The |
@hannesm could you open an issue on Camelus? I'm going to close this one as soon as it is fixed in opam-repository |
Dear valued maintainers,
opam packages released to opam-repository contain checksums of tarballs to ensure that the same tarball is used for installation as intended by the person doing a release. opam packages which point to a branch / tag are generally not accepted AFAICT.
opam 2.0 introduced a
pin-depends
stanza to specify dependencies of certain off-trunk dependencies (i.e. a custom version of yyy). I just discovered that the opam-repository contains few packages withpin-depends
, which I assume should not be there, applying the same rule above.//cc @kit-ty-kate @AltGr @camelus maybe camelus should discover and warn the usage thereof? (it could as well warn/error if there's no checksum)
//cc @dinosaure (who's the maintainer of most packages above)
(see #14977 for a fix of mirage-block-xen)
The text was updated successfully, but these errors were encountered: