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

Update / Install behave differently #1867

0x53A opened this Issue Aug 21, 2016 · 1 comment


None yet
2 participants

0x53A commented Aug 21, 2016


Update / install generate different lockfiles.
I would expect that a install after an update is a no-op, but it actually changes the lockfile.

see the last few commits in

Repro steps

Please provide the steps required to reproduce the problem

  1. Open the Paket solution
  2. Run update, it will update a few packages so changes are expected
  3. Run install. I would expect there to be no changes, but this part changes:

n. You can do this in a loop, running update again will revert the change from 3.

Known workarounds

I'm not sure if this is actually relevant, if the different lockfiles cause a different behaviour.
A "workaround" is to just revert the changes before commiting.

Related information

I used the context menu in the VS extension:

@forki forki closed this in ffcef8a Aug 22, 2016


This comment has been minimized.

Show comment
Hide comment

forki Aug 22, 2016


thanks for reporting. should be fixed now


forki commented Aug 22, 2016

thanks for reporting. should be fixed now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment