can't restore packages from AppVeyor feed in 2.38.0 #1326

Closed
ctaggart opened this Issue Dec 22, 2015 · 7 comments

Comments

Projects
None yet
2 participants
@ctaggart
Contributor

ctaggart commented Dec 22, 2015

This is probably related to the fix for #1317. paket restore fails when trying to download any private NuGet package from our AppVeyor feed. To reproduce locally, delete %localappdata%NuGet\Cache first.

Message: Couldn't get package details for package ...
@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Dec 23, 2015

Member

are you on latest? Nuget API changed yesterday and we have a fix around this issue.

Member

forki commented Dec 23, 2015

are you on latest? Nuget API changed yesterday and we have a fix around this issue.

@ctaggart

This comment has been minimized.

Show comment
Hide comment
@ctaggart

ctaggart Dec 23, 2015

Contributor

Yes I am. This also affects 2.39.1. I get a message like this for each of our dependencies hosted on AppVeyor.
image
image
image

Contributor

ctaggart commented Dec 23, 2015

Yes I am. This also affects 2.39.1. I get a message like this for each of our dependencies hosted on AppVeyor.
image
image
image

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Dec 23, 2015

Member

Mhm. Unfortunately I have no idea what happened yet. I will try to reproduce on 27th or 28th

Member

forki commented Dec 23, 2015

Mhm. Unfortunately I have no idea what happened yet. I will try to reproduce on 27th or 28th

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Dec 23, 2015

Member

Just for my understanding is it also happening when you do "paket update -f"?

Member

forki commented Dec 23, 2015

Just for my understanding is it also happening when you do "paket update -f"?

@ctaggart

This comment has been minimized.

Show comment
Hide comment
@ctaggart

ctaggart Dec 24, 2015

Contributor

No, it is not happening with a paket update -f. It is happening with a paket restore -f.

Contributor

ctaggart commented Dec 24, 2015

No, it is not happening with a paket update -f. It is happening with a paket restore -f.

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Dec 24, 2015

Member

Ok thanks. Will try to fix it as first thing after Christmas
On Dec 24, 2015 01:29, "Cameron Taggart" notifications@github.com wrote:

No, it is not happening with a paket update -f. It is happening with a paket
restore -f.


Reply to this email directly or view it on GitHub
#1326 (comment).

Member

forki commented Dec 24, 2015

Ok thanks. Will try to fix it as first thing after Christmas
On Dec 24, 2015 01:29, "Cameron Taggart" notifications@github.com wrote:

No, it is not happening with a paket update -f. It is happening with a paket
restore -f.


Reply to this email directly or view it on GitHub
#1326 (comment).

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Dec 28, 2015

Member

First success: I can reproduce.

Member

forki commented Dec 28, 2015

First success: I can reproduce.

@forki forki added the bug label Dec 28, 2015

@forki forki closed this in 0b0d23c Dec 28, 2015

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