@Gr3q here's the list:
dotnet-sdk-bin 7.0.1.sdk101-1
dotnet-runtime-bin 7.0.1.sdk101-1
dotnet-host-bin 7.0.1.sdk101-1
dotnet-targeting-pack-bin 7.0.1.sdk101-1
aspnet-targeting-pack-bin 7.0.1.sdk101-1
aspnet-runtime-bin 7.0.1.sdk101-1
Git Clone URL: | https://aur.archlinux.org/dotnet-core-bin.git (read-only, click to copy) |
---|---|
Package Base: | dotnet-core-bin |
Description: | The ASP.NET Core targeting pack (binary) |
Upstream URL: | https://www.microsoft.com/net/core |
Keywords: | .net dotnet microsoft |
Licenses: | MIT |
Conflicts: | aspnet-targeting-pack, aspnet-targeting-pack-9.0 |
Provides: | aspnet-targeting-pack, aspnet-targeting-pack-9.0 |
Submitter: | Gr3q |
Maintainer: | Gr3q |
Last Packager: | Gr3q |
Votes: | 47 |
Popularity: | 0.39 |
First Submitted: | 2019-10-02 17:13 (UTC) |
Last Updated: | 2025-04-17 07:37 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 12 Next › Last »
@Gr3q here's the list:
dotnet-sdk-bin 7.0.1.sdk101-1
dotnet-runtime-bin 7.0.1.sdk101-1
dotnet-host-bin 7.0.1.sdk101-1
dotnet-targeting-pack-bin 7.0.1.sdk101-1
aspnet-targeting-pack-bin 7.0.1.sdk101-1
aspnet-runtime-bin 7.0.1.sdk101-1
@Gigas002 can you list all dotnet packages you have installed?
Got error while trying to upgrade dotnet-sdk-bin
to 7.0.1.sdk101-1
:
error: failed to commit transaction (conflicting files)
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.android/WorkloadManifest.json exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.android/WorkloadManifest.targets exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.ios/WorkloadManifest.json exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.ios/WorkloadManifest.targets exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.maccatalyst/WorkloadManifest.json exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.maccatalyst/WorkloadManifest.targets exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.macos/WorkloadManifest.json exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.macos/WorkloadManifest.targets exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.maui/WorkloadManifest.json exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.maui/WorkloadManifest.targets exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.tvos/WorkloadManifest.json exists in filesystem
dotnet-sdk-bin: /usr/share/dotnet/sdk-manifests/7.0.100/microsoft.net.sdk.tvos/WorkloadManifest.targets exists in filesystem
Errors occurred, no packages were upgraded.
What can be done to workaround this?
Unfortunately I probably can't do that because sometimes there are two lts releases, so it would appear too ambiguous.
Would be nice to always be able to install dotnet-*-lts-bin and that it would update with patches and rollover to the next LTS when that gets released.
I keep getting deletion requests, I'll put it back up tomorrow.
What happend to NET6? Don't you think it would be nice to keep the LTS version on AUR?
The dotnet-sdk-bin pkgbuild don't have to provides and conflicts dotnet-sdk-bin
As usual, dotnet-core-bin
follows the latest, and all other versions are provided as other packages, this time dotnet-code-6.0-bin
Hi! This week have 2 separated things changed: .NET 7 has officially been released, but .NET 6 LTS got it's next update to version 6.0.11 as well.
Are you planning to keep this package on the LTS version, or are you going to update it to .NET 7?
I guess probably the best choice would be to start actually maintaining both (or Arch Linux itself should start doing this?).
But I also know that AUR already has another .NET 7 package, but that's still the now obsolete preview version.
Pinned Comments
Gr3q commented on 2019-10-05 07:28 (UTC) (edited on 2021-02-13 09:06 (UTC) by Gr3q)
IMPORTANT INSTALLATION INFO (a reminder for myself as well):
For dotnet to work you need to EXPLICITLY install:
If you keep the install order in mind and you don't rely on pacman to resolve your dependencies you will be fine.
Longer explanation:
Every dotnet-sdk is dependent on a specific version of dotnet-runtime, this is built into dotnet.
Technically you only need the latest dotnet-sdk because it can build to any earlier versions.