Package Details: dotnet-targeting-pack-preview-bin 6.0.0.sdk100+rc.2.21505.57-2

Git Clone URL: (read-only, click to copy)
Package Base: dotnet-core-preview-bin
Description: The .NET Core targeting pack (preview, binary)
Upstream URL:
Licenses: MIT
Conflicts: dotnet-targeting-pack=6.0.0
Provides: dotnet-targeting-pack=6.0.0, dotnet-targeting-pack-6.0
Replaces: dotnet-targeting-pack-preview-bin
Submitter: fmauNeko
Maintainer: fmauNeko
Last Packager: fmauNeko
Votes: 11
Popularity: 0.152109
First Submitted: 2021-10-14 12:24
Last Updated: 2021-10-14 13:27

Latest Comments

1 2 3 4 Next › Last »

fmauNeko commented on 2021-10-14 12:27

@FabioLolix: The package has been renamed, a merge request is pending in order to merge this package in the new one.

FabioLolix commented on 2021-10-12 16:41

Hello Florian, at the moment this is a -bin pkgbuild; not one build from source, you can both correct this and upload a dotnet-sdk-preview-bin

fmauNeko commented on 2021-05-27 09:51

@morealaz I just added completion files for bash, fish and zsh.

@fisch02 That should be fixed too.

fisch02 commented on 2021-05-22 11:45

Package will not build on non-x86_64 platforms, because line 113 "cp -dr --no-preserve='ownership' packs/Microsoft.NETCore.App.{Host.linux-x64,Ref} "${pkgdir}"/usr/share/dotnet/packs/" is specific to x86_64. Package will build, on my RPi4 (aarch64) when "x64" is changed to "arm64". dotnet-core-bin does the following: if [ $CARCH = 'x86_64' ]; then msarch=x64; elif [ $CARCH = 'armv7h' ]; then msarch=arm; elif [ $CARCH = 'aarch64' ]; then msarch=arm64; fi and then replaces x64 with ${msarch}

morealaz commented on 2021-05-10 11:37

@fmauNeko: Could you please add as /usr/share/bash-completion/completions/dotnet for bash completion to dotnet-host package? thanks

xhyinne commented on 2020-10-29 21:09

Interesting, because when I try to build and run a dotnet project (targeting net5.0) with this package it complains about no matching runtime being found; when I use the non-preview dotnet package (project targeting netcoreapp3.1) it works fine as expected. Any idea why?

fmauNeko commented on 2020-10-29 08:31

Your issue cannot come from that, because the binaries are prebuilt, and those version numbers (which are correct, build numbers are almost always mismatched between SDK and Runtime, and I've even seen a mismatched Runtime and Host version once).

You can check the version numbers at .

Plus, those fields are only used for packaging purpose, and are used in patch names in the binary distribution from Microsoft, so if I change them, you'll get empty packages.

xhyinne commented on 2020-10-29 02:04

It looks like the runtime and sdk versions are mismatched:

pkgver=5.0.0+100+rc.2.20479.15 _hostver=5.0.0-rc.2.20475.5 _runtimever=5.0.0-rc.2.20475.5 _sdkver=5.0.100-rc.2.20479.15

This causes the SDK to register as 5.0.0+100+rc.2.20479.15, and the runtime as 5.0.0-rc.2.20475.5, despite using 5.0.100-rc.2.20479.15 for all the source packages. When trying to run an application, dotnet complains about not being able to find a matching runtime, and I traced it down to this mismatch. Could you update the hostver and runtimever to match the pkgver and sdkver, which is also the same as the version in the sources?

fmauNeko commented on 2020-09-23 08:37

@ofrades that's a community repo package (

3.1.8 has been released 10 days ago, sync your repos and retry ;)

ofrades commented on 2020-09-23 08:17

Getting errors retrieving files from mirrors:

:: Retrieving packages... error: failed retrieving file 'netstandard-targeting-pack-3.1.7.sdk107-1-x86_64.pkg.tar.zst' from . . .