Skip to content
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

Appveyor CI failing due to nuget restore #556

Closed
mikkelbu opened this issue Feb 22, 2019 · 3 comments
Closed

Appveyor CI failing due to nuget restore #556

mikkelbu opened this issue Feb 22, 2019 · 3 comments
Assignees
Milestone

Comments

@mikkelbu
Copy link
Member

mikkelbu commented Feb 22, 2019

Builds are failing on AppVeyor in nuget restore, see e.g. #549 (comment).

...
Installing NUnit 3.11.0.
  OK https://ci.appveyor.com/nuget/nunit/FindPackagesById()?id='System.Reflection.TypeExtensions'&semVerLevel=2.0.0 472ms
NU3005: Package 'Microsoft.NETCore.Platforms 2.0.0' from source 'C:\Program Files\dotnet\sdk\NuGetFallbackFolder': The package signature file entry is invalid. The central directory header field 'compression method' has an invalid value (8).
  GET https://www.myget.org/F/nunit-analyzers/api/v3/flatcontainer/nunit/index.json
  NotFound https://www.myget.org/F/nunit-analyzers/api/v3/flatcontainer/nunit/index.json 194ms
...

The problem with nuget is the same as in #515 which should be solved by #525, but it seems like the solution is not enough.

AppVeyor had new images uploaded 11 February (see e.g. AppVeyor Windows images update. There was no changes to msbuild, but nuget was bumped, so nuget now probably calls to the same msbuild version that was failing in #515.

@rprouse
Copy link
Member

rprouse commented Mar 1, 2019

I missed this before my comments on Charlie's PR. I see that your PR attempt hasn't worked @mikkelbu. Since an older version of NuGet.exe worked, could we include that older version and do the restore using that?

@mikkelbu
Copy link
Member Author

mikkelbu commented Mar 1, 2019

@rprouse That would probably work, but I've found another solution which is even simpler (but it took a lot of attempts 😄).

@CharliePoole
Copy link
Member

Nice!

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

No branches or pull requests

3 participants