fsprojects / Paket

A dependency manager for .NET with support for NuGet packages and Git repositories.
https://fsprojects.github.io/Paket/
MIT License
1.99k stars 520 forks source link

Cannot consume package from VSTS private Nuget feeds #1496

Closed blumu closed 8 years ago

blumu commented 8 years ago

Paket fails to get nuget packages from private feeds created in Visual Studio Team Service Package Management

Error in paket.dependencies line 1
  couldnt load resources from https://<MyVstsProject>.visualstudio.com/DefaultCollection/_packaging/<MyPrivateFeed>/nuget/v3/index.json

It reproes using both v2 and v3 versions of the nuget feed.

forki commented 8 years ago

Can you mail me a dependencies file with credentials that reproduces this? Sforkmann at gmail On Mar 4, 2016 3:45 AM, "William Blum" notifications@github.com wrote:

Paket fails to get nuget packages from private feeds created in Visual Studio Team Service Package Management https://www.visualstudio.com/en-us/get-started/package/overview

Error in paket.dependencies line 1 couldnt load resources from https://.visualstudio.com/DefaultCollection/_packaging//nuget/v3/index.json

— Reply to this email directly or view it on GitHub https://github.com/fsprojects/Paket/issues/1496.

talbottmike commented 8 years ago

@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 Paket.Dependencies.Install """ source https://mysubdomain.pkgs.visualstudio.com/DefaultCollection/_packaging/MyFeedName/nuget/v2 username: "myusername" password: "mypassword" nuget MyPrivatePackage """;;

blumu commented 8 years ago

@forki I can't share the credentials to this project/feed unfortunately. The source is configured as follows in the paket dependency file:

source https://MYPROJECT.pkgs.visualstudio.com/DefaultCollection/_packaging/MYFEED/nuget/v3/index.json username: "***" password: "***"

I tried with both v2 and v3 and got the same error after running the command:

 .\.paket\paket.exe convert-from-nuget
blumu commented 8 years ago

Correction: the actual error message I get when running paket convert-from-nugget is:

Paket version 2.51.4.0
Dependencies files saved to sources/paket.dependencies
Resolving packages for group Main:
 - MyPackage is pinned to 2015.11.26.1
Paket failed with:
        Couldn't get package details for package MyPackage 2015.11.26.1 on any of ["https://www.nuget.org/api/v2";
 "https://MyProject.pkgs.visualstudio.com/DefaultCollection/_packaging/MyVstsFeed/nuget/v3/index.json"].
forki commented 8 years ago

Ok this is a really weird error. It finds the package versions, but not the concrete package. Will be nearly impossible for me to debug without access On Mar 4, 2016 9:31 PM, "William Blum" notifications@github.com wrote:

Correction: the actual error message I get when running paket convert-from-nugget is:

Paket version 2.51.4.0 Dependencies files saved to sources/paket.dependencies Resolving packages for group Main:

— Reply to this email directly or view it on GitHub https://github.com/fsprojects/Paket/issues/1496#issuecomment-192455925.

forki commented 8 years ago

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.

blumu commented 8 years ago

Is there any switch I could use when running paket.exe to collect additional diagnostics for you to debug?

blumu commented 8 years ago

@forki I can share with you the content of the index.json file if this helps. Let me know.

forki commented 8 years ago

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?

forki commented 8 years ago

I created an account and it looks like I can reproduce

blumu commented 8 years ago

Awesome. Looking forward to next release with the fix!

forki commented 8 years ago

it's already released

isaacabraham commented 8 years ago

lol

blumu commented 8 years ago

I confirm that the fix works for me. Thanks for implementing this quick workaround!

stuartjdavies commented 7 years ago

I have the same issue. Has this error been fixed? Is there a work around?