Nuget restore issue with v0.7.0 #177

Closed
calloncampbell opened this Issue Jul 6, 2016 · 7 comments

Comments

Projects
None yet
4 participants
@calloncampbell

We get the following nuget restore issue in TeamCity with the latest v0.7.0 build. We downgraded to v0.6.8 and issue goes away.

[11:38:11][Step 2/4] restore: Restoring NuGet packages for Plato.NET.sln (1s)
[11:38:11][restore] NuGet command: C:\BuildAgent\plugins\nuget-agent\bin\JetBrains.TeamCity.NuGetRunner.exe C:\BuildAgent\tools\NuGet.CommandLine.DEFAULT\tools\NuGet.exe restore C:\BuildAgent\work\cfb932647685dff1\Plato.NET.sln
[11:38:11][restore] Starting: C:\BuildAgent\temp\agentTmp\custom_script6315179492532981544.cmd
[11:38:11][restore] in directory: C:\BuildAgent\work\cfb932647685dff1
[11:38:11][restore] JetBrains TeamCity NuGet Runner 8.0.37573.9
[11:38:11][restore] Registered additional extensions from paths: C:\BuildAgent\plugins\nuget-agent\bin\plugins-2.8
[11:38:11][restore] Starting NuGet.exe 2.8.60717.93 from C:\BuildAgent\tools\NuGet.CommandLine.DEFAULT\tools\NuGet.exe
[11:38:12][restore] WARNING: 'MsgPack.Cli' already has a dependency defined for 'System.Collections'.
[11:38:12][restore] Installing 'MsgPack.Cli 0.7.0'.
[11:38:13][restore] 'MsgPack.Cli' already has a dependency defined for 'System.Collections'.
[11:38:13][restore] Process exited with code 1

Oddly enough NuGet restore seems fine with Visual Studio and Command line.

@kryptt

This comment has been minimized.

Show comment
Hide comment
@kryptt

kryptt Jul 13, 2016

I have a similar issue myself.

It seems dependencies have come in that make the project incompatible with Xamarin ?

kryptt commented Jul 13, 2016

I have a similar issue myself.

It seems dependencies have come in that make the project incompatible with Xamarin ?

@yfakariya

This comment has been minimized.

Show comment
Hide comment
@yfakariya

yfakariya Jul 17, 2016

Member

It looks package dependency resolution problem. Could you give packages.config and/or project.config used? I might fix it if this issue is not TeamCity implementation specific.

Member

yfakariya commented Jul 17, 2016

It looks package dependency resolution problem. Could you give packages.config and/or project.config used? I might fix it if this issue is not TeamCity implementation specific.

@rfcdejong

This comment has been minimized.

Show comment
Hide comment
@rfcdejong

rfcdejong Aug 24, 2016

I get this error in the commandline in visual studio 2013 using the Package Manager Console. .NET 4.6.1

PM> Install-Package MsgPack.Cli
Install-Package : 'MsgPack.Cli' already has a dependency defined for 'System.Collections'.
At line:1 char:1

  • Install-Package MsgPack.Cli
  • - CategoryInfo          : NotSpecified: (:) [Install-Package], InvalidOperationException
    - FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
    

I get this error in the commandline in visual studio 2013 using the Package Manager Console. .NET 4.6.1

PM> Install-Package MsgPack.Cli
Install-Package : 'MsgPack.Cli' already has a dependency defined for 'System.Collections'.
At line:1 char:1

  • Install-Package MsgPack.Cli
  • - CategoryInfo          : NotSpecified: (:) [Install-Package], InvalidOperationException
    - FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
    

@yfakariya yfakariya added this to the 0.9 milestone Sep 22, 2016

@yfakariya yfakariya added bug and removed need-more-info labels Sep 22, 2016

@yfakariya

This comment has been minimized.

Show comment
Hide comment
@yfakariya

yfakariya Sep 22, 2016

Member

Thank you @rfcdejong! I will investigate it with your information.

Member

yfakariya commented Sep 22, 2016

Thank you @rfcdejong! I will investigate it with your information.

yfakariya added a commit that referenced this issue Sep 24, 2016

Set minClientVersion to nuspec. #177
NuGet 2.x does not support .NET Standard, so they fail to parse msgpack.nuspec file as 0.7.0.
This commit set minimum version restriction which just prevents confusing error. This fix actually does not solve the problem, it still says the client should update nuget to 2.12 or 3.x, but it gives hint to the solution.
Note: this solution is also used in corefx packages.
@yfakariya

This comment has been minimized.

Show comment
Hide comment
@yfakariya

yfakariya Sep 24, 2016

Member

I reproduced this issue and I found that this is caused by nuget version. Indeed, NuGet 2.x does not support .NET Standard, which is added in 0.7.0 package, so they cannot handle package correctly. When I update nuget in VS2013 to 2.12, In fact, I could install msgpack package correctly.

So, these are solution:

  • If you use VS2013(or before), please update your NuGet 2.12 or later.
  • If you use TeamCity, please update your TeamCity or contact to support to use latest NuGet (2.12 or 3.x) compatible feature.
  • To prevent confusing error message, I've added minClientVersion to .nuspec file (it is nuspec bug -- I missed it).

Thanks.

Member

yfakariya commented Sep 24, 2016

I reproduced this issue and I found that this is caused by nuget version. Indeed, NuGet 2.x does not support .NET Standard, which is added in 0.7.0 package, so they cannot handle package correctly. When I update nuget in VS2013 to 2.12, In fact, I could install msgpack package correctly.

So, these are solution:

  • If you use VS2013(or before), please update your NuGet 2.12 or later.
  • If you use TeamCity, please update your TeamCity or contact to support to use latest NuGet (2.12 or 3.x) compatible feature.
  • To prevent confusing error message, I've added minClientVersion to .nuspec file (it is nuspec bug -- I missed it).

Thanks.

@yfakariya

This comment has been minimized.

Show comment
Hide comment
@yfakariya

yfakariya Sep 24, 2016

Member

I've released modified version as 0.9.0-beta1. Would you try it in Team City environment?

Member

yfakariya commented Sep 24, 2016

I've released modified version as 0.9.0-beta1. Would you try it in Team City environment?

yfakariya added a commit that referenced this issue Feb 2, 2017

Set minClientVersion to nuspec. #177
NuGet 2.x does not support .NET Standard, so they fail to parse msgpack.nuspec file as 0.7.0.
This commit set minimum version restriction which just prevents confusing error. This fix actually does not solve the problem, it still says the client should update nuget to 2.12 or 3.x, but it gives hint to the solution.
Note: this solution is also used in corefx packages.
@yfakariya

This comment has been minimized.

Show comment
Hide comment
@yfakariya

yfakariya May 4, 2017

Member

Close because it looks nupkg issue and solved.

Member

yfakariya commented May 4, 2017

Close because it looks nupkg issue and solved.

@yfakariya yfakariya closed this May 4, 2017

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