Skip to content
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

Migration guide change for paket update #1756

Closed
phatcher opened this issue Jan 6, 2018 · 4 comments
Closed

Migration guide change for paket update #1756

phatcher opened this issue Jan 6, 2018 · 4 comments

Comments

@phatcher
Copy link

phatcher commented Jan 6, 2018

The Migration Guide says to issue

.paket/paket.exe update FAKE

it's more likely that you will have to issue

.paket/paket.exe update FAKE --group Build

@matthid
Copy link
Member

matthid commented Jan 27, 2018

Yes is there any particular reason to change that (as the former includes the later)? I have no objections just trying to figure out if anything special happened here.

@phatcher
Copy link
Author

@matthid It might have been me changing my project to having Fake in the build group rather than the default area, i.e. I was trying to update and move groups at the same time.

How about

.paket/paket.exe update

which seemed to work for me

@matthid
Copy link
Member

matthid commented Jan 27, 2018

Ah I see, the problem is

With Paket: add prerelease after nuget FAKE in paket.dependencies file then .paket/paket.exe update FAKE, check that paket.lock references FAKE version 5

Should probably we written as

With Paket: add prerelease after nuget FAKE in paket.dependencies file then .paket/paket.exe update FAKE, check that paket.lock references FAKE version 5

@phatcher
Copy link
Author

That looks good

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

No branches or pull requests

2 participants