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

paket add nuget may resolve inconsistent dependency graph #310

Closed
agross opened this issue Oct 28, 2014 · 1 comment
Closed

paket add nuget may resolve inconsistent dependency graph #310

agross opened this issue Oct 28, 2014 · 1 comment
Labels
bug

Comments

@agross
Copy link
Contributor

agross commented Oct 28, 2014

paket.dependencies:

source http://nuget.org/api/v2

nuget Castle.Core >= 3.2 < 3.3

paket.lock:

NUGET
  remote: http://nuget.org/api/v2
  specs:
    Castle.Core (3.2.2)

$ paket add nuget Castle.Windsor
Paket version 0.10.2.0
Parsing paket.dependencies
Adding Castle.Windsor  to paket.dependencies
Resolving packages:
  - fetching versions for Castle.Core
    - exploring Castle.Core 3.2.2
  - fetching versions for Castle.Windsor
    - exploring Castle.Windsor 3.3.0
Locked version resolutions written to paket.lock
Dependencies files saved to paket.dependencies
03.80s - ready.

After that:

NUGET
  remote: http://nuget.org/api/v2
  specs:
    Castle.Core (3.2.2)      <-- *
    Castle.Windsor (3.3.0)
      Castle.Core (>= 3.3.0) <-- clearly violated by *
@agross
Copy link
Contributor Author

agross commented Oct 28, 2014

This is what you get when you rm paket.lock && paket install, it's consistent:

NUGET
  remote: http://nuget.org/api/v2
  specs:
    Castle.Core (3.2.2)
    Castle.Windsor (3.2.1)
      Castle.Core (>= 3.2.0)

@agross agross added the bug label Oct 28, 2014
@forki forki closed this as completed in 95341a2 Oct 29, 2014
forki added a commit that referenced this issue Oct 30, 2015
@forki
Create regression tests for #310
73a1a26
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
1 participant
@agross