search

fsprojects / Paket

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

Couldn't get package details for package Bender #1387

Closed dcorriveau-omniscient closed 8 years ago

dcorriveau-omniscient commented 8 years ago

Hi, I'm trying to convert a solution from Nuget to Paket using convert-from-nuget, but I get this:

It fails every time, if I'm using --force, it restarts the convert process and also breaks with the same error.

I'm guessing it has to do with something specific about that package, but for the sake of completeness: I'm on Windows 10, and my solution folder contains multiple projects and even other solutions (could this cause problems?).

Thanks.

forki commented 8 years ago

can you give us the paket.dependencies file that was generated?

dcorriveau-omniscient commented 8 years ago

paket.dependencies.txt

Some packages are custom nuget packages from a private nuget serv as you can see.

isaacabraham commented 8 years ago

@dcorriveau-omniscient it won't be solutions or projects - the resolution / download phase doesn't use them (which is where the error is occurring).

dcorriveau-omniscient commented 8 years ago

If I remove Bender, it does the same error for

(the resolution / download is quite slow, I don't know if it's normal but it takes about 2 seconds for each package).

forki commented 8 years ago

yes resolution is slow here. already analysing.

forki commented 8 years ago

ok. already found the perf issue.

now I can reproduce (blazing fast):

image

dcorriveau-omniscient commented 8 years ago

You are probably looking at this as we speak, but in case somebody else has the issue and lands on this page, I also get the same error with:

And

And

Edit: Didn't think there would be so many, so I'll stop listing them from now on since they probably all have something in common and you will most likely be able to fix this in one shot.

forki commented 8 years ago

ok in order to get you a bit further. please use Paket 2.42.7 and replace the NuGet v3 souce line with:

source https://www.nuget.org/api/v2

I'm still trying to figure out what's wrong with the v3. @maartenba is there an issue with Bender on NuGet v3 feed?

maartenba commented 8 years ago

Not that I know of. What is the URL that you are requesting that would throw the above error?

dcorriveau-omniscient commented 8 years ago

@forki The package resolution is now working after changing to the v2 source and it's indeed "blazing fast". I've fixed a few version dependencies errors that I had (my mistake when creating custom packages) and it seems to complete the nuget conversion.

Danke !

forki commented 8 years ago

you should now try to remove as many versions pins as possible from the dependencies file. Also running paket simplify will help you to clean the deps file.

In the end you only want to have top-level deps in it with as few as possible version restrictions

dcorriveau-omniscient commented 8 years ago

And I also had a few subfolders with "unused" projects in them which may have made the whole dependency tree worse than it should be, I'll have some cleanup to do, we'll see how awesome paket simplify is.

forki commented 8 years ago

it can do a lot, but it's only a heuristic...

forki commented 8 years ago

@maartenba it's https://api.nuget.org/v3/registration1/bender/3.0.29.0.json

forki commented 8 years ago

I guess we have to normalize that one https://api.nuget.org/v3/registration1/bender/3.0.29.json works

maartenba commented 8 years ago

Yup

forki commented 8 years ago

@dcorriveau-omniscient with latest paket version you can back to the v3 url if you want.

dcorriveau-omniscient commented 8 years ago

Yep, it does work. Thanks !