Couldn't get package details for package Bender

[dcorriveau-omniscient]

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

• Bender is pinned to 3.0.29.0
  Paket failed with:
  Couldn't get package details for package Bender 3.0.29.0 on http://api.nuget.org/v3/index.json.

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]

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

[dcorriveau-omniscient]

paket.dependencies.txt

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

[isaacabraham]

@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]

If I remove Bender, it does the same error for

• Topshelf.Owin is pinned to 1.3.12.0
  Paket failed with:
  Couldn't get package details for package Topshelf.Owin 1.3.12.0 on http://api.nuget.org/v3/index.json.

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

[forki]

yes resolution is slow here. already analysing.

[forki]

ok. already found the perf issue.

now I can reproduce (blazing fast):

[dcorriveau-omniscient]

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:

• SimpleConfig is pinned to 1.0.37.0
  Paket failed with:
  Couldn't get package details for package SimpleConfig 1.0.37.0 on http://api.nuget.org/v3/index.json.

And

• flexo is pinned to 1.0.22.0
  Paket failed with:
  Couldn't get package details for package flexo 1.0.22.0 on http://api.nuget.org/v3/index.json.

And

• Microsoft.Web.Infrastructure is pinned to 1.0.0.0
  Paket failed with:
  Couldn't get package details for package Microsoft.Web.Infrastructure 1.0.0.0 on http://api.nuget.org/v3/index.json.

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]

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]

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

[dcorriveau-omniscient]

@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]

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]

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]

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

[forki]

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

[forki]

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

[maartenba]

Yup

[forki]

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

[dcorriveau-omniscient]

Yep, it does work. Thanks !