-
Notifications
You must be signed in to change notification settings - Fork 27
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
failure with a pinned opam package #326
Comments
Hmm, that's strange. It should be able to find a HEAD ref, given that you specifically pinned it to |
Can you help me by passing ways to reproduce? I checked out |
so. in a clean opam switch
If you run into issues ("it fails with a log of error messages"), please report the step and the failure you encounter. |
Any chance you could post your "lot of error messages", or expose where you're stuck? I suspect opam-monorepo fails if you |
Ah I guess my problem was that I tried running
I'll try your steps. |
When using a pinned dependency the refs might not have a prefix (e.g. `HEAD` is a plain ref) thus they wouldn't have been found when attempting to resolve the refs. Closes tarides#326
Created #332 to fix the problem. I am not entirely sure why the code is like that, but let's see what the code review will say. |
When using a pinned dependency the refs might not have a prefix (e.g. `HEAD` is a plain ref) thus they wouldn't have been found when attempting to resolve the refs. Closes tarides#326
Even with the latest release, 0.3.4, this issue persists. Are there any plans to fix and release this issue? It is pretty annoying. |
CHANGES: ### Changed - Treat packages with no build commands as if they can be built with dune (tarides/opam-monorepo#355, @gridbugs) ### Fixed - Fix resolving refs of locally pinned repositories (tarides/opam-monorepo#326, tarides/opam-monorepo#332, @hannesm, @Leonidas-from-XIV) - Read the `compiler` flag from OPAM metadata thus classifying more packages correctly as base packages (tarides/opam-monorepo#328, @Leonidas-from-XIV) - Fix bug where dev repo urls ending with a "/" would result in `opam monorepo pull` placing package source code directly inside the duniverse directory instead of in a subdirectory of the duniverse directory (tarides/opam-monorepo#359, @gridbugs)
@hannesm I've created a 0.3.5 release which includes the fix: ocaml/opam-repository#22765 |
I try to use opam monorepo 0.3.3 with the following pins:
gmp.6.2.1-2 (uninstalled) git git+file:///usr/home/hannes/devel/mirage/ocaml-gmp#HEAD
And receive a failure during
opam monorepo lock
:It would be pretty nice to support pins to git repositories the same as opam does, or are there any blockers?
The text was updated successfully, but these errors were encountered: