Request for Updated .NET SDK Packages in AppStream for Rocky Linux 9

Rocky Linux Help & Support
1

Hello,

I’m a .NET developer using Rocky Linux 9 for building applications, etc.

At the runtime level, everything works well and is updated frequently in the AppStream Rocky 9 repo.

However, my issue is that for specific versions of .NET, only outdated SDK versions are available, recent ones are missing.

Here’s a concrete example from the AppStream repo:
dotnet-sdk-6.0-6.0.136
dotnet-sdk-7.0-7.0.119
dotnet-sdk-8.0-8.0.115
dotnet-sdk-9.0-9.0.105

Whereas the latest available versions are:
6.0.428
7.0.410
8.0.408
9.0.203

This gap might not seem significant, but newer SDK versions often include important features that many developers rely on. Without them, we’re forced to perform manual installations outside the dnf package system, which complicates development and deployment workflows.

Please consider updating the .NET SDK packages in the AppStream repository to reflect the latest available versions from Microsoft. This would greatly enhance the development experience and align Rocky Linux 9 more closely with current development standards and tooling.

2

Hey Mattias,

The issue here is that versions of these packages in the Rocky repos don’t diverge from what’s in the upstream Red Hat packages. This is how we maintain our compatibility with RHEL. Currently, Red Hat only packages the N.0.1xx versions of the SDK, so until that changes, that’s what Rocky is going to package.

FWIW, it looks like Microsoft has a repo that would work with Rocky with the N.0.2xx or N.0.4xx SDKs at Index of /rhel/9/prod/ (disclaimer: I haven’t tested this repo).

3

Hi, thanks for the quick response!

Do you know if there’s a place within the Red Hat community where I could submit the same request? It would really help simplify my workflows.

Best regards,
Matthias

4

Further background on this, if I understood it correctly from the Microsoft side currently only the N.0.1xx feature band is considered the LTS for Linux Distributions.
There is a change for this lined up for .NET 10, but I don’t expect this to change for anything below.

5

Hey, I’m not actually sure where the best place to submit a request with Red Hat would be. I suspect a change like this would need to start in Fedora or CentOS Stream, since they are Red Hat’s upstream.

6

That’s actually the main Production repo you can use directly from Microsoft, it has many of their tools in it, so yes this can really be considered be production ready, just no support from RH if you are using it.