I'm getting error - One or more Dlls have change stopping after cloning in git for 1 hour. We have been running cc.net with hg and now trying to migrate to git.
I'm getting this error , not sure how else to proceed.
this is due to the fact that the first integration with git will get all mods :-(
download the latest dev release, it has been fixed.
The 1.8.5 version of CCNet will be out soon.
http://build.nauck-it.de/download/CruiseControl.NET-dev/
Related
I'm getting this error when I try to build a .NET Core solution with Azure DevOps:
error NU1102: Unable to find package NuGet Frameworks with version (>= 4.9.3)
error NU1102: - Found 33 version(s) in http://nuget.bentley.com/nuget/Default [ Nearest version: 4.7.0-preview1-4986 ]
The error occurs in the Cake script when a NuGet restore is being executed by dotnet.exe CLI:
Executing: "d:/vsts/a/_tool/dncs/2.2.100/x64/dotnet.exe" restore "./src/StorageRegistryPortal.sln" --source "http://nuget.bentley.com/nuget/Default"
It tries to restore the NuGet packages from the solution file before throwing the NU1102 error above:
Restoring packages for d:\vsts\a\2921\s\src\StorageRegistryPortal\StorageRegistryPortal.csproj...
Nothing in my solution is referencing this "NuGet.Frameworks" package. So, I wonder if it is the "dotnet.exe" CLI itself that depends on this nuget package before it can restore the rest of the NuGet packages. Also, this only happens in AzureDevops. When I execute the build/cake script on my local PC, it is able to successfully restore all of the nuget packages with no issues.
I've already tried adding a "Use Nuget 4.9.3" task to the build pipeline, but I get the same error.
NOTE: If I remove that "Use Nuget 4.9.3" task, then the error changes to (>= 4.7.0). So, it appears to be looking for the Nuget.Framework that matches the current version of nuget.exe but not finding it.
Here is the screenshot of my build pipeline setup:
TL;DR
This sometimes happens when running dotnet restore on one of my Linux/Ubuntu build servers when pulling from a private Azure DevOps Artifacts/Packages NuGet repo.
The solutions that work for me:
Rebooting the Linux machine, or
Deleting the NuGet cache at ~/.local/share/NuGet/v3-cache/[directory-with-name-of-my-private-nuget-repo]
Background
The error I get is:
error NU1102: Unable to find package [Name-of-my-custom-nuget-package] with version (>= 5.0.116)
I have a nuget.config file that is properly configured to pull down my NuGet packages.
The error is complete nonsense.
The version does exist
Other Linux boxes have no problems running dotnet restore and getting the version of the package
I can run dotnet restore on the same Linux machine for other (older) versions and it's fine
It just seems that dotnet restore decides, for whatever reason, that it's not even going to try to look for the new version of the package.
I've generally found Azure DevOps private NuGet repos secured with AAD to be especially problematic and annoying when dealing with Linux. It really needs some love and attention from the NuGet team.
I was finally able to resolve this issue. It turns out there was a breaking change from the nuget.org folks which caused our internal nuget server to fail to serve the 4.7 and 4.9.3 versions of NuGet.Frameworks. This is an essential nuget library which is required by dotnet.exe to restore nuget packages. For .net core projects, that framework needs to be version 4.7 or higher. Anyway, the resolution was that we had to make adjustments to our internal nuget server to account for the changes from nuget.org.
Could you please have a try to use Nuget 4.9.1 as screenshot then run your build again?
Hope it helps.
Try to download Nuget.Framework of higher version from here https://www.nuget.org/downloads.
In my case it was a problem with version 5.0.0 and I installed 5.0.2 then error disappeared.
I was using git lab (9.5.4) and I took backup and reinstalled complete git lab with latest version. I was trying to restore the data from older version of backup but I am getting error as version mismatch and kindly switch to older version
I went through some of the Git lab doc but I didn't get useful stuff can somebody help me how can I restore the data from older version of git lab backup? Waiting for the reply. Thank you in advance.
Unfortunately GitLab doesn't support that option. You would need to mount a Gitlab with the same version as the one you have, recover the backup there and then update THAT Gitlab, that way you'll have an updated database that you can backup and restore on your installation.
My advice would be to use Docker for the old one (https://hub.docker.com/r/gitlab/gitlab-ce/)
Running a TeamCity build agent to run NUnit tests on Ubuntu 14.04 LTC with the latest build of mono appears to have some dependency issues that I cant for the life of me solve.
I have followed the following installation steps
Mono Installation Steps for 4.0.1
Team City Build Agent
When the TC Build Agent starts the NUnit step, it simply fails, and looking at the logs shows it executes
/usr/bin/mono-sgen /home/ubuntu/buildAgent/plugins/dotnetPlugin/bin/JetBrains.BuildServer.NUnitLauncher.exe
which promptly returns with
Corlib not in sync with this runtime: expected corlib version 117, found 111.
Loaded from: /usr/lib/mono/4.0/mscorlib.dll
Download a newer corlib or a newer runtime at http://www.mono-project.com/download.
Is there any possible way to get this to work? I have tried removing all the pieces and re-installing again and even installing a older version of mono build but to no avail.
The TC connection appears to work and I can manually invoke and call mono on its own and even nunit-console however this .exe build provided by TC seems to have be stumped as linux non-expert.
Please save me from dependency hell!!
Edit: I ended up just solving my problem by installing nunit-console and enabling the XML Report processing build feature rather than play around with the corelib files and break something else.
This is a Mono bug, see https://bugzilla.xamarin.com/show_bug.cgi?id=34675.
The problem is that Mono moved to providing the 4.0 assemblies, including mscorlib.dll, only in form of reference assemblies. They contain only metadata and are intended for the compiler. Normally applications just use the newest version automatically.
The loader code in Mono however wasn't updated to bind forward an explicit runtime version of v4.0.20506 or v4.0.30128 which TeamCity is using in their .exe.config files to the latest version. The runtime instead tries to load mscorlib.dll from the 4.0 directory and bails as the version is too old (it's from the time the reference assemblies were generated).
As a workaround, you can edit <build agent
installdir>/plugins/dotnetPlugin/bin/JetBrains.BuildServer.NUnitLauncher.exe.config (and other .exe.config files)
and remove the following lines:
<supportedRuntime version="v4.0.20506"/>
<supportedRuntime version="v4.0.30128"/>
This might stop working once TeamCity decides to update the plugin though.
Replacing the mscorlib version is only asking for trouble - i.e. TypeLoadException's and friends are waiting around the corner to get you.
What I did was replace the Teamcity build step with a manual invocation of the TC NunitLauncher, but forcing it to use Mono 4.5:
mono --runtime=4.5 /Applications/buildAgent/plugins/dotnetPlugin/bin/JetBrains.BuildServer.NUnitLauncher.exe v4.0 MSIL NUnit-2.6.3 $(find **/bin/Release/*Tests.dll | paste -sd ";" -)
The invocation uses some shell trickery to find all assemblies I'm interested in using a wildcard, but other than that should be straightforward to understand.
It would be nice if Mono fixed their broken 4.0 runtime. Anyone already reported it on https://bugzilla.xamarin.com/ ?
This is how I worked around it : (note my mono is in /opt/mono)
$ cd /opt/mono/lib/mono
$ sudo mv 4.0 __4.0
$ sudo ln -s 4.5 4.0
i.e get rid of the 4.0 folder and symlink the 4.5 to be 4.0
This is something of a hack but it got me up and running until a proper fix surfaces!
Steve
I had this problem on my Raspberry Pi after compiling 4.0.2 but it was loading from /4.5/
This got me going:
sudo mv /usr/lib/mono/4.5/mscorlib.dll /usr/lib/mono/4.5/_old_mscorlib.dll
sudo cp /opt/mono-4.0.2/lib/mono/4.5/mscorlib.dll /usr/lib/mono/4.5
I'm trying to build a Yocto image.
I'm running Ubuntu 12.04. I've installed the packages the link above recommends (and more)
I cloned the poky git repository, and checked out the daisy-11.0.0 tag.
conf/local.conf has MACHINE=qemux86, nearly all other settings are default.
I tweaked # of threads for bitbake and make.
bitbake -k core-image-minimal
I get the following error during the do_configure task of libusb1_1.0.18.bb:
configure: error: "udev support requested but libudev not installed"
libudev-dev is installed.
This seems strange to me because I'm using a plain vanilla no frills setup.
Does anyone know how to resolve this configure error?
I'm not 100% sure this is on-topic for SO. Please direct me to the proper place if so before closing.
You should just do a repo sync, it has been solved and pushed today (20 may 2014)
I got the exact same problem but in a slightly different environment. I’m just sharing this answer in case it helps you solve your problems.
Anyway, I am running Ubuntu 14.04, and I checked out the latest from git://github.com/openembedded/oe-core.git. I started a build but got the exact same problem. Just like you, I get the following error during the do_configure task of libusb1_1.0.18.bb:
configure: error: "udev support requested but libudev not installed"
So I checked the git logs and noticed that that particular recipe was modified on May 15, which was a day before my checkout. I decided to pull out those changes (by checking out the previous commit) and rebuilt the image. It succeeded, which makes me think that update may have broken the build.
Yesterday I've upgraded my Gitlab installation from 5.3 to 6.0 (technically from 5.3 to 5.4 and 5.4 to 6.0), and I can't display Network and other Graphs since then.
On the network page it seems some Javascript is not loaded, as I got a 'Network is not defined' error. Graphs seems to be a different issue, but I can't find anything in the logs.
Is it a bug or I did something wrong?
Both functions were working fine before the upgrade.
Try to precompile your assets:
sudo service gitlab stop
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
sudo service gitlab start
This seems to be a bug in GitLab. It breaks when it encounters a commit that doesn't change any files, such as when creating a branch.
It is in the issue tracker as issue #4867 and has been fixed in master.
Can you try running
bundle exec rake cache:clear RAILS_ENV=production
as per https://github.com/gitlabhq/gitlabhq/issues/4874