-
Notifications
You must be signed in to change notification settings - Fork 524
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 has trouble resolving .NET Core dependency lists #1610
Comments
I think that in case you had defined a framework version in your paket.dependency it would work faster |
Thanks for reporting. If the resolver needs that longer it usually means there is no valid |
mhm. even with strategy:min (which is NuGet's default) it doesn't find a valid resolution in a short timespan.
I assume there is in fact no valid resolution (looks like one of packages needs System.Compression and there is only a RC3 version of it and that's incompatible to other stuff). If we open the version restrictions like the following then paket has no issues to find a valid resolution:
|
OK, thanks. I'll close for now. I somehow suspect these might indicate recurring problems, where people take an existing project.json and try to use Paket over the same dependencies. |
@forki Just to mention that although the resolution did go through, it resolved to a bunch of packages using the So a big 👍 to adding support for the netstandard monikers :) |
Yeah we will add that. And next week they will make that obsolete again Just kidding. ;-) |
@forki I think netstandard is going to stick. |
Description
I've been trying to use Paket to resolve the kind of dependency listings we're seeing in project.json files for compiling F# .NET Core components. I'm finding that Paket rarely succeeds in resolving these dependency lists.
Repro steps
Create a
paket.dependencies
for this dependency listing, taken straight from this project.jsonExpected: the dependency list resolves OK in reasonable time
Actual: I aborted the operation after about 8 minutes, with this log
The text was updated successfully, but these errors were encountered: