-
Notifications
You must be signed in to change notification settings - Fork 526
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
Cannot consume package from VSTS private Nuget feeds #1496
Comments
Can you mail me a dependencies file with credentials that reproduces this?
|
@blumu Don't know if this'll help. But I'm using a VSTS private feed and am able to get packages by including credentials like this |
@forki I can't share the credentials to this project/feed unfortunately. The source is configured as follows in the paket dependency file:
I tried with both v2 and v3 and got the same error after running the command:
|
Correction: the actual error message I get when running
|
Ok this is a really weird error. It finds the package versions, but not the
|
pretty sure it depends on the url in https://MyProject.pkgs.visualstudio.com/DefaultCollection/_packaging/MyVstsFeed/nuget/v3/index.json but I'd need access to solve that. |
Is there any switch I could use when running paket.exe to collect additional diagnostics for you to debug? |
@forki I can share with you the content of the index.json file if this helps. Let me know. |
no idnex.json doesn't really help. I need access to a similar visualstudio.com server. Can you set up one for testing where this reproduces and give me access? |
I created an account and it looks like I can reproduce |
Awesome. Looking forward to next release with the fix! |
it's already released |
lol |
I confirm that the fix works for me. Thanks for implementing this quick workaround! |
I have the same issue. Has this error been fixed? Is there a work around? |
Paket fails to get nuget packages from private feeds created in Visual Studio Team Service Package Management
It reproes using both v2 and v3 versions of the nuget feed.
The text was updated successfully, but these errors were encountered: