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.dependency with version ranges fails when package has pinned dependency and that version is unlisted #1579

Closed
Rcomian opened this issue Apr 7, 2016 · 5 comments
Closed

Paket.dependency with version ranges fails when package has pinned dependency and that version is unlisted #1579

Rcomian opened this issue Apr 7, 2016 · 5 comments
Labels
bug

Comments

@Rcomian
Copy link

Rcomian commented Apr 7, 2016

Description

We can't use version ranges in the paket.dependency file when a nuget package has a pinned dependency which has been unlisted and we require that dependency as well as that package.

Repro steps

NugetPackageA: Depends on NugetPackageB pinned to 1.1.5

NugetPackageB 1.1.5 has been unlisted, but is still available.

paket.dependencies brings in both packages, but tries to allow itself to use an unpinned version of the dependency:

nuget NugetPackageA
nuget NugetPackageB ~> 1.1

When running paket update we get the error message:

Could not resolve package NugetPackageB:
 - Dependencies file requested package NugetPackageB: >= 1.1 < 2.0
 - NugetPackageA 1.0.0 requested package NugetPackageB: 1.1.5

For testing, the specific unlisted package we're having trouble with is Mvvmlight 4.2.30.0.

Expected behavior

I would expect paket to bring in version 1.1.5 of NugetPackageB since it satisfies the requirements of both the package.dependencies and NugetPackageA.

Actual behavior

The actual behaviour is to claim that no version matches both criteria, which is wrong as the required version exists, it's just unlisted.

Known workarounds

If you pin the dependency to the same version as NugetPackageA or remove all version constraints, everything works ok. Version constraints are useful tho.

nuget NugetPackageA
nuget NugetPackageB 1.1.5

Related information

  • Windows 7
  • Standard release
  • .NET Runtime 4.5
@isaacabraham
Copy link
Contributor

Hmmm. Do unlisted versions of packages show up on the nuget feed?

@Rcomian
Copy link
Author

Rcomian commented Apr 7, 2016

No, unlisted means that they're not on the nuget feed, but they are available for download since projects get built against specific versions.

I can see what's happening in that paket is saying "What versions are available and match the constraints", getting a shortlist, then seeing that 1.1.5 is not in that shortlist.

But it's still a valid setup as you can still find and install version 1.1.5. If you can convince paket to allow the configuration, it will print a nice warning about it being unlisted, and everything works fine.

@isaacabraham
Copy link
Contributor

So essentially what Paket should theoretically do is during the resolution phase check if the pinned versions are actually available even if not listed and add them to the versions available from the feed as part of the resolution phase?

@forki forki added the bug label Apr 7, 2016
@forki
Copy link
Member

forki commented Apr 7, 2016

this is a bug. I'm tring to reproduce.

@Rcomian
Copy link
Author

Rcomian commented Apr 7, 2016

isaacbraham, something like that might work.

I'm not sure what the best resolution actually is, but the situation is a valid (if ill-advised) configuration.

@forki forki closed this as completed in e79f45c Apr 7, 2016
@forki forki mentioned this issue Dec 4, 2016
Merged
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
3 participants
@forki @Rcomian @isaacabraham