Package Details: dotnet-cli-git 2.0.0_alpha_005165-1

Git Clone URL: (read-only)
Package Base: dotnet-cli-git
Description: The .NET Core command-line (CLI) tools, used for building .NET Core apps and libraries through your development flow (compiling, NuGet package management, running, testing, ...)
Upstream URL:
Keywords: .net cli core dotnet microsoft
Licenses: MIT
Provides: dotnet
Submitter: lwinch2006
Maintainer: lwinch2006
Last Packager: lwinch2006
Votes: 0
Popularity: 0.000000
First Submitted: 2017-02-12 00:57
Last Updated: 2017-03-03 22:44

Latest Comments

ttshivers commented on 2017-03-20 20:56

The build is failing for me with this error:

lwinch2006 commented on 2017-03-03 22:59

Since copying of is excluded so building of CoreCLR package theoretically not needed. Everyone who interested to spare time can exclude source of CoreCLR from PKGBUILD and try to install without it.
But until it is proven that this library really not needed further (need will not raise during some period of time) building of CoreCLR will still be in PKGBUILD in order to return back this library easily.

lwinch2006 commented on 2017-02-15 21:38

Try again now. It was an issue in pkgver() function when old and new version were the same. I have added 'if condition' for this case.

optlink commented on 2017-02-15 18:28


I had added the library to _corefx_files in my local version of the PKGBUILD and that seemed to solve the issue. However, I'm now having issues with The dotnet-cli package seems to include its own version, I'm currently looking into replacing it with the one from the libuv package.

Synthead commented on 2017-02-15 18:26

This package fails to build with this error:

lwinch2006 commented on 2017-02-15 06:03

* Package has been updated.

* 'SKIP' parameter added to the 'dotnet-cli' source (maybe it would be better not to add this and push users explicitly to turn off checksum checking so that they aware what they are doing)
* Now 'pkgver' parameter is set during the package building execution with the version value received from Github 'dotnet/cli' repository. This time many thanks to @dcelasun with 'visual-studio-code-insiders' package for inspiration :-)
* By running makepkg every day by user it is possible for him to get latest build of dotnet-cli every day without need for me to push new package version to the AUR.

I had the similar problem in the past with the OpenSSL library. The system was complaining about that some library related to cryptography not found. So @abrodersen that time added copying of '' from the newly built CoreFX to the 'dotnet/share/Microsoft.NetCore.App/*' folder and the problem was solved. (see in PKBUILD file)

So there is also such library that ''. You can try to manually copy it to the 'dotnet/share/Microsoft.NetCore.App/*' folders after dotnet-cli-git installation from 'src/corefx/bin/Linux.x64.Release/Native/' folder and see if this helps. There is also some other libraries there that can be copied.

If some library replacement help we can consider to add it to the package description in AUR.

optlink commented on 2017-02-13 22:35

The package has built and installed. dotnet restore fails with this for each package reference in the project:

The type initializer for 'System.Net.Http.CurlHandler' threw an exception.
The type initializer for 'Http' threw an exception.
The type initializer for 'HttpInitializer' threw an exception.
Unable to load DLL 'System.Net.Http.Native': The specified module could not be found.
(Exception from HRESULT: 0x8007007E)

Though I think this is an issue with dotnet itself.

optlink commented on 2017-02-13 21:46

@lwinch2006 I traced the lttng-ust issue back to a GitHub issue here:
From there I created a patch from the commit and I have a build running now. I will let you know if it fails.

Rainmaker commented on 2017-02-13 21:23

Please change the checksum to 'SKIP' (case-sensitive).

That will make makepkg skip the checksum check for the offending file.

lwinch2006 commented on 2017-02-13 20:59


1) Because PKBUILD always downloads latest dotnet-cli from github so checksum is changed every time. So here 2 things that should be taken into account: checksum will not be correct (--skipchecksums flag could be used maybe when building) and actual version of installed package will not be the same as version in PKBUILD. Version will be something different (newer) than 4793 build number.

2) About lttng-ust I'm not sure. I have not found neither in Packages nor in AUR lttng-ust-dev package, just lttng-ust (and lttng-ust-git) packages. Also in dependencies of dotnet there is precise lttng-ust that pointed out. So you can post your exception here so that it becomes more clear what happened during your installation.

All comments