-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Git --depth 1 breaks orb/dune #6145
Comments
To add a bit more, we use the following API in orb:
Due to the intricate build of a MirageOS unikernel, we use |
I had a go at adding the missing What about we instead introduce a new |
Thinking about this further i think #4442 use-case was for the opam-repository fetch, for regular packages maybe it would make sense to keep |
I've opened #6146 which implements my last comment |
I think it makes sense to default to full fetch for packages. I tried the following on opam 2.2 and opam 2.1.4:
So this change also affects the opam command line utility. |
First of all congratulations on releasing opam 2.2! 🥳
In orb we recently updated to the version 2.2 opam libraries in robur-coop/orb#15 and robur-coop/orb#17. It builds successfully, but when we use the new orb to build itself again we observe an error on Debian: https://builds.robur.coop/job/orb/build/955defa7-9ff5-447b-b67b-4e928d80cda4
The error is that
dune subst
produces a version numberda200fd
instead of the expected0.0.2-25-gda200fd
.After some investigation with @hannesm we believe it may be due to #4442 where a shallow git clone is done now. Dune uses git tags to derive the version number, and with a shallow clone these are no longer available.
From our point of view we didn't find a way to force a deep clone.
The text was updated successfully, but these errors were encountered: