You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see the source for git*.3.10.0 is the opam source even though we pinned git.3.10.0 and git-paf.3.10.0. Meanwhile oneffs.42 is correctly pinned to the git repository.
Since git, git-mirage, git-paf and git-unix all share the same source directory it would not be possible to use both the opam source as well as the git repository, but I would rather expect an error than ignoring the pin.
The text was updated successfully, but these errors were encountered:
This may be an issue with opam-monorepo, but I observe it when using mirage.
When I pin a package in Mirage it is not always reflected in the lock file:
mirage/unipi-unix.opam
:mirage/unipi-unix.opam.locked
:As you can see the source for
git*.3.10.0
is the opam source even though we pinnedgit.3.10.0
andgit-paf.3.10.0
. Meanwhileoneffs.42
is correctly pinned to the git repository.Since git, git-mirage, git-paf and git-unix all share the same source directory it would not be possible to use both the opam source as well as the git repository, but I would rather expect an error than ignoring the pin.
The text was updated successfully, but these errors were encountered: