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

paket update does not pick latest prerelease version of indirect dependency #866

Closed
dmitryvk opened this issue Jun 10, 2015 · 6 comments
Closed
Labels

Comments

@dmitryvk
Copy link

I have 3 versions of 2 packages:

  1. p1 version 1.0-beta
  2. p1 version 1.1-beta
  3. p2 version 1.0-beta

p2 depends on:

p1 >= 1.0-beta

When I install package p2, paket pick version 1.0-beta of p1.

I expect that version 1.1-beta of p1 would be selected.

@forki
Copy link
Member

forki commented Jun 10, 2015

I'd suspect this too.
Is this somethin I can reproduce with public packages?

@dmitryvk
Copy link
Author

This happened to me with private packages. I'll try to produce small example.

@dmitryvk
Copy link
Author

https://github.com/dmitryvk/paket-866 - here is the reproducing example. Run .paket/paket update inside tst directory.

@forki
Copy link
Member

forki commented Jun 10, 2015

I can confirm the bug with this awesome repro sample. Thanks a lot.

@forki forki closed this as completed in 28112d0 Jun 10, 2015
@forki
Copy link
Member

forki commented Jun 10, 2015

can you confirm that it's fixed in 1.12.1?

@dmitryvk
Copy link
Author

Yes, it works now.

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

No branches or pull requests

2 participants