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 inconsistently adds/removes ‘content: none’ from paket.lock #3257

bacar opened this Issue Jun 18, 2018 · 0 comments


None yet
1 participant

bacar commented Jun 18, 2018


I’m finding that when I run various different commands, Paket makes surprisingly inconsistent decisions to variously add or remove - content: none from my paket.lock files. These decisions appear random to the casual observer.

This is causing a tremendous amount of noise when it affects multiple dependencies, masking the real intent of the change.

Repro steps

Create the following paket.dependencies:

content: none
nuget Angular.UI.Bootstrap.DateTimePicker 0.11.0

If I run paket update it creates a lock file containing:

Angular.UI.Bootstrap (2.5)

But when I run paket update --keep-patch it adds a suffix:

Angular.UI.Bootstrap (2.5) - content: none

Every time I run one or other command it correspondingly adds or removes the content: none bit.

Other commands also remove the suffix, for example doing a paket add....

I tend to run paket update --keep-patch with various other options (clean redirects etc) in order to mop up any inconsistencies added since the last time it ran, but it is frustrating when it makes all these other unrelated changes too.

Note that only the indirect dependency is affected by this problem.

This is just one example; with many indirect dependencies I can get hundreds of such affected lines.

Expected behavior

Paket doesn’t flip between different representations of the lock file.

@bacar bacar changed the title from Paket sometimes adds/removes ‘content: none’ from paket.lock to Paket inconsistently adds/removes ‘content: none’ from paket.lock Jun 18, 2018

@forki forki closed this in 0446b5d Jun 20, 2018

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