TeamCity NuGet Package Restore Failing After Upgrade to 10.x - teamcity

Been getting the old NuGet Installer Failed error after upgrading to TeamCity 10.x.
The Build Server is on a local VM and the NuGet Server is on another VM on RackSpace. I can authenticate using the feed and the credentials, and the package is created and exists. I can update the package manually in VS using the same credentials. Just no joy in TeamCity build.
[restore] Unable to find version '1.1.0.16' of package 'Velociraptor'.
[23:00:39][restore] Process exited with code 1
[23:00:39][Step 1/4] Step NuGet Installer failed
This was working prior to the upgrade from 9.1.7 to 10.x
I've looked at the other answers but none have worked so far.
What am I missing?

I haven't moved up to 10.x yet, but expect that maybe the default version of NuGet.exe has changed.
If your NuGet server supports a pinned version of the NuGet.exe client then it might be worth trying with an earlier versions of the client. This can be changed in the Administration section.
Hope this helps.

Related

when I try to run my existing flutter project in windows version, I am getting this error

I have an flutter project which I created long back when Flutter windows became stable version I want to use same project for windows version but it says this error.
You should be able to fix this error by downloading the Nuget.exe and adding it to your Windows' path manually.
The root problem may be related to your installation of Visual Studio as described here

Unable to install NuGet Packages due to Incompatibility

I can't seem to install the Windows Azure Storage NuGet Package because the version clashes with another package that probably depends on it. I can't seem to install anything related Azure because the same error pops up every time.
Install failed. Rolling back... Updating 'Microsoft.Data.OData 5.6.2'
to 'Microsoft.Data.OData 5.6.4' failed. Unable to find versions of
'WindowsAzure.MobileServices.Backend.Tables,
WindowsAzure.MobileServices.Backend.Entity' that are compatible with
'Microsoft.Data.OData 5.6.4'.
Why do I get this and how can I get around to having all compatible versions?

Sonar Qube plugin Failed to install on Mule Studio

I tried to install sonar qube plugin from http://downloads.sonarsource.com/eclipse/eclipse/ in Mule Studio Version (3.5.0) with Mule runtime (3.4.0). For my requirement I cannot got with the latest version of studio.
The following is the error message I am getting when trying to install the plugin in Mule studio
The operation cannot be completed. See the details.
Details:
Cannot complete the install because one or more required items could not be found.
Software being installed: SonarQube Integration for Eclipse 3.5.0.20150804-1512-RELEASE (org.sonar.ide.eclipse.feature.feature.group 3.5.0.20150804-1512-RELEASE)
I tried installing the Sonar Qube plugin from the Eclipse marketplace, SonarQube 3.5.0 was listed there, but it was also mentioned that it has been deprecated and SonarLint 1.1.0 should be used instead.
I went ahead with the installation but as you reported it couldn't be completed as there seems to be a problem with the SonarQube Integration for Eclipse component.
However, can you try creating an offline copy of the update site and then try installing the plugin in studio?
http://mcuoneclipse.com/2014/07/03/replicating-an-eclipse-update-site-for-offline-usage/
EDIT
I continued with the same SonarQube installation, it took a lot of time and eclipse had to look for various alternate solutions (15 in total), but it finally came up with this dialog.
So, while installing the plugin, unselect the 2 components (if you don't need it) and move ahead with installation, I was able to successfully complete it, eclipse restarted and it was all done.
-Shanky G.

Cannot install NuGet package Microsoft.Bcl.Build 1.0.14

I am making a multi-platform app in VS 2013 (iOS, WinPhone and Android). I want to add into the iOS reference folder a Nuget Packages named Microsoft Http Clients Libraries and I cannot do it because I get the following error:
Could not install package 'Microsoft.Bcl.Build 1.0.14'. You are trying
to install this package into a project that targets
'Xamarin.iOS,Version=v1.0', but the package does not contain any
assembly references or content files that are compatible with that
framework. For more information, contact the package author.
Can anybody help me with that?
I faced the same problem and apparently the Bcl.Build 1.0.14 can not be installed, but you probably you don't need that old version.
I faced this issue when I tried adding WindowsAzure.MobileService to the iOS Xamarin project. And it failed, because the minimal supported Bcl.Build is required to be 1.0.14, but if you have a newer version, which installs quite fine, you will be able to add other packages that depend on it.
So
1. Install Microsoft.Bcl.Build package separately (the latest)
2. Install your package that depends on it.
Go to -> Solution -> Manage Packages For Solution -> In the tab "Browse" -> Select the two options follow below:
First:
Install package "Microsoft.Bcl.Build" your version more latest 1.0.21
Second:
After this step, now install package "Microsoft.Net.Http" your version mor latest 2.2.29
Result:
For me was solved!
Microsoft.Bcl.Build 1.0.14 can be installed into Xamarin.iOS projects.
It may fail if:
Your NuGet Package manager is not up to date.
You do not have the Xamarin Portable Class Library profiles for Xamarin.iOS installed.
If you have the latest Xamarin version installed it is probably the NuGet Package Manager not being up to date. You can update it from Tools - Extensions and Updates - Updates - Visual Studio Gallery.
In Visual Studio 2017 I encountered above error, and I solved the issue by installing Microsoft.Bcl.Build first on the Xamarin.Android, then installed Microsoft.Net.Http and System.Net.Http, but Xamarin.IOS and Xamarin.UWP there were no issues.
I found the solution and put it here in case some one may face the same problem.
Install "Microsoft.Bcl.Build.1.0.21" first for all your projects.
Now you can install "PortableRest", all dependency that depends on Microsoft.Bcl.Build will be installed correctly.
I was trying to install Microsoft.Net.Http in my Xamarin.Forms project when i faced this issue. Here is what you must try to get rid of this error:
1- Update Xamarin.Forms to latest version in each project of solution.
2- As my primary intention was to install Microsoft.Net.Http, and this package had dependencies on Microsoft.BCL and Microsoft.BCL.Build. I tried installing these packages (Microsoft.Bcl and Microsoft.Bcl.Build) individually and it worked for me. First install latest version of Microsoft.Bcl.Build 1.0.21 (If 1.0.14 did not install, try latest version). Then, install Microsoft.Bcl which should be installed successfully and this solution worked for me and I hope would work for you too. After installing these packages indivisually, I was able to install Microsoft.Net.Http successfully.
NOTE: While installing Packages (Microsoft.Bcl and Microsoft.Bcl.Build) into your projects, check which version you are installing. Try installing another version, if one does not work and let me know If problem does not solve.
Have a great day :)

SVN version in Maven tasks with SVNKit on MacOS

I am getting this error in a Maven build (mvn clean install) on a Mac with Mountain Lion
org.tmatesoft.svn.core.SVNException: svn: The path 'XYZ' appears to be part of Subversion 1.7 (SVNKit 1.4) or greater
working copy rooted at '/Users/XYZ/workspace/XYZ'.
Please upgrade your Subversion (SVNKit) client to use this working copy.
I had SVN installed as part of the Apple Command Line tools package and that gets installed at /usr/bin. I have installed the latest SVN as well but that got installed at /usr/local/bin.
When the maven build runs, it does not pick up the latest SVN, it picks the older one and fails.
Has anyone faced this kind of problem before?
I think there are 2 options -
1) Somehow force maven to use the new installed SVN.
2) Upgrade the SVN installed as part of Apple' Command Line tools to the latest SVN. I have reinstalled Command Line tools with the latest version but it still sticks to the older version.
I dont control the pom.xml so modifying it is not a viable option.
Any pointers in resolving this would be much appreciated.
Thanks!
This means your svn client is version 1.7 but the working copy(your project workspace) was checkout with the older version.
It's simple by execute the following command at your project root directory, where the pom.xml is there.
svn upgrade
please note, the maven use the svn client which is in your OS path.
After upgrade you should configure your IDE to use the version 1.7 as well. In my case I use the Eclipes Juno sr1 with Svnkit.
Anyhow if you would not like to change the working copy or IDE configuration. There is an alternative by install the svn clinet 1.4/1.5/1.6 and set it active via OS path instead.
I hope this may help.
Regards,
Charlee Ch.

Resources