-
Notifications
You must be signed in to change notification settings - Fork 519
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
Dependency resolution does not work for VSTS feed #1798
Comments
|
ok this sounds very very strange. @isaacabraham do you have seen this? |
|
I'm also reproducing this problem, even with packages from the same source. paket.dependencies with nuget.org source paket intall the same paket.dependencies but with a custom source paket install with custom source |
|
Paket calls v2 API for VSTS even when v3 source specified (as in my example above). To retrieve a Nuget package details (including a list of dependencies) For pkgs.visualstudio.com source (v2 API) Response: For nuget.org source (v2 API) Response: As result, I have two JSON files in my C:\Users\user1\AppData\Local\NuGet\Cache: |
|
This commit doesn't solve the problem. Why does Paket always stick to v2 API? I tried to debug with |
|
Because c3 is faster in nearly all situations. Is there a way for me to reproduce? Am 04.10.2016 21:13 schrieb "Sergey Kostrukov" notifications@github.com:
|
|
I will create an account in VSTS with a private NuGet feed for reproduction. |
Description
I have a private package
Ain my VSTS feed that depends on a packageBfrom the nuget.org feed. When Ipaket install,Ais resolved and downloaded, butA's dependency onBis not resolved (andBis not downloaded). By comparision, when I source a local folder feed containingA,Bis successfully resolved and downloaded.Repro steps
Adepending on nuget.org packageB, pushAto the VSTS feed.Atopaket.dependencies, e.g.:c:\path\to\project\paket.dependencies:paket installExpected behavior
Actual behavior
Known workarounds
None.
Related information
The text was updated successfully, but these errors were encountered: