-
Notifications
You must be signed in to change notification settings - Fork 359
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
Fix incorrect package installed state written on error #5922
base: master
Are you sure you want to change the base?
Conversation
In the 2.2 project as I haven't yet determined if this is a regression or long-standing. |
### opam update | ||
[NOTE] ongoing.dev has previously been updated with --working-dir, not resetting unless explicitly selected | ||
|
||
<><> Updating package repositories ><><><><><><><><><><><><><><><><><><><><><><> | ||
[second] no changes from file://${BASEDIR}/REPO2 | ||
[default] synchronised from file://${BASEDIR}/REPO | ||
|
||
<><> Synchronising development packages <><><><><><><><><><><><><><><><><><><><> | ||
[quux.dev5] synchronised (no changes) | ||
Now run 'opam upgrade' to apply any package updates. |
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.
Is this opam update
output needed?
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 currently yes but we could remove it if the new version of d-foo.6
was introduced using <pkg:d-foo.6>
instead of <REPO/...>
If a package needs to be rebuilt because of upstream changes, an error in the rebuild causes a cache indicating that it's installed to be written. Something appears to be wrong in
OpamClient.parallel_apply
, but I haven't got to the bottom of exactly what.What I have written is a test! Spotted while debugging #5921 - because errors during fetch also trigger this. Note in the commit history that erasing
.opam-switch/packages/cache
causes opam to do the right thing on the second upgrade.