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

Couldn't get package details for package Bender #1387

Closed
dcorriveau-omniscient opened this Issue Jan 14, 2016 · 18 comments

Comments

Projects
None yet
4 participants
@dcorriveau-omniscient
Contributor

dcorriveau-omniscient commented Jan 14, 2016

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

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jan 14, 2016

Member

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

Member

forki commented Jan 14, 2016

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

@dcorriveau-omniscient

This comment has been minimized.

Show comment
Hide comment
@dcorriveau-omniscient

dcorriveau-omniscient Jan 14, 2016

Contributor

paket.dependencies.txt

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

Contributor

dcorriveau-omniscient commented Jan 14, 2016

paket.dependencies.txt

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

@isaacabraham

This comment has been minimized.

Show comment
Hide comment
@isaacabraham

isaacabraham Jan 14, 2016

Contributor

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

Contributor

isaacabraham commented Jan 14, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@dcorriveau-omniscient

dcorriveau-omniscient Jan 14, 2016

Contributor

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).

Contributor

dcorriveau-omniscient commented Jan 14, 2016

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

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jan 14, 2016

Member

yes resolution is slow here. already analysing.

Member

forki commented Jan 14, 2016

yes resolution is slow here. already analysing.

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jan 14, 2016

Member

ok. already found the perf issue.

now I can reproduce (blazing fast):

image

Member

forki commented Jan 14, 2016

ok. already found the perf issue.

now I can reproduce (blazing fast):

image

@forki forki added the bug label Jan 14, 2016

@dcorriveau-omniscient

This comment has been minimized.

Show comment
Hide comment
@dcorriveau-omniscient

dcorriveau-omniscient Jan 14, 2016

Contributor

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

  • 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.

Contributor

dcorriveau-omniscient commented Jan 14, 2016

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

  • 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

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jan 14, 2016

Member

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?

Member

forki commented Jan 14, 2016

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

This comment has been minimized.

Show comment
Hide comment
@maartenba

maartenba Jan 14, 2016

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

maartenba commented Jan 14, 2016

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

@dcorriveau-omniscient

This comment has been minimized.

Show comment
Hide comment
@dcorriveau-omniscient

dcorriveau-omniscient Jan 14, 2016

Contributor

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

Contributor

dcorriveau-omniscient commented Jan 14, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jan 14, 2016

Member

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

Member

forki commented Jan 14, 2016

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

This comment has been minimized.

Show comment
Hide comment
@dcorriveau-omniscient

dcorriveau-omniscient Jan 14, 2016

Contributor

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.

Contributor

dcorriveau-omniscient commented Jan 14, 2016

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

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jan 14, 2016

Member

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

Member

forki commented Jan 14, 2016

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

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jan 14, 2016

Member

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

Member

forki commented Jan 14, 2016

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

@maartenba

This comment has been minimized.

Show comment
Hide comment
@maartenba

maartenba commented Jan 14, 2016

Yup

@forki forki closed this in 3e0bab5 Jan 14, 2016

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jan 14, 2016

Member

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

Member

forki commented Jan 14, 2016

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

@dcorriveau-omniscient

This comment has been minimized.

Show comment
Hide comment
@dcorriveau-omniscient

dcorriveau-omniscient Jan 14, 2016

Contributor

Yep, it does work. Thanks !

Contributor

dcorriveau-omniscient commented Jan 14, 2016

Yep, it does work. Thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment