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.

Sign up for GitHub

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

Jump to bottom

Forced update resets gist dependency #499

Closed
tpluscode opened this issue Jan 1, 2015 · 5 comments
Closed

Forced update resets gist dependency #499

tpluscode opened this issue Jan 1, 2015 · 5 comments
Labels
bug

Comments

@tpluscode
Copy link
Contributor

When there is a gist dependency locked to some commit other than the initial running paket.exe update --force downloads the gist's first commit and updates paket.lock accordingly. Can be reproduced in this repo
@forki
Copy link
Member

forki commented Jan 2, 2015

strange I get the following expected diff:

image

@tpluscode
Copy link
Contributor Author

That's it precisely what I meany though it seem that I wrongly assumed 5d9 was the initial commit. It's even worse because it's the gist id only. I though they were the same thing. And 77ad6 is the latest revision, which should appear in paket.lock after running update, forced or otherwise.

@forki
Copy link
Member

forki commented Jan 2, 2015

Look into your dependencies file. You pinned the commit to 5d9 - I think it's all correct now.

@tpluscode
Copy link
Contributor Author

Why do say I pinned the commit? Looks fine to me

@forki
Copy link
Member

forki commented Jan 2, 2015

sorry my bad. that hash is not the version but the gist identifier.

will try to fix asap.

@forki forki added the bug label Jan 2, 2015
@forki forki closed this as completed in 58953ef Jan 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@forki @tpluscode