-
Notifications
You must be signed in to change notification settings - Fork 520
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
Paket thinks things have changed #3218
Comments
Another repro: checkout logary at 42aa88966a826a9d640483c3c725a51ccf5c2b0f, run
Also, if you run |
Happens on plain $ paket restore --project src/Logary/Logary.fsproj
Paket version 5.172.0
paket.dependencies and paket.lock are out of sync in /Users/ilja/Projects/logary.
Please run 'paket install' or 'paket update' to recompute the paket.lock file.
Changes were detected for Main/Expecto
- SettingsChanged
Changes were detected for Main/Expecto.FsCheck
- SettingsChanged
Changes were detected for Main/Expecto.Hopac
- SettingsChanged
Starting restore process.
Performance:
- Disk IO: 20 milliseconds
- Runtime: 3 seconds |
Looks like the |
after running "paket update" everything is fine |
can you please check the lock file? the generate_load_script settings should be gone after that |
ok scratch that. need to investigate further |
Restore should behave fine now |
Description
I upgraded a few libs in Logary, 'paket update' and then 'paket install' which got:
Then
./build.sh
yields a lot of output like:But running
paket install does nothing
.I then ran
paket update
which is not what I want (because I don't want to update any nugets), and this delta appeared inpaket.lock
:After letting paket have its way with the lockfile, paket still thinks something is amiss and output the warning while building, so it did not in fact solve anything.
These steps can be done on the parent commit of causiq/logary@d3ce90e
Expected behavior
Following the output's suggestion, paket install, should work.
Also, why paket keeps changing the set of system.* libraries and their constraints I have no idea of, since I haven't changed my compile targets.
Actual behavior
A lot of frequent churn in System.* packages for no apparent reason.
Known workarounds
None
The text was updated successfully, but these errors were encountered: