Bug 2170536
| Summary: | Packaging macro and/or runtime ID update in upstream list | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Cronenworth <mike> |
| Component: | dotnet6.0 | Assignee: | Omair Majid <omajid> |
| Status: | NEW --- | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 39 | CC: | crummel, omajid |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | aarch64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Michael Cronenworth
2023-02-16 16:17:42 UTC
This may be a packaging issue on my side. I'm setting '--runtime fedora.%{fedora}-x64' when building Jellyfin. Should aarch64 be "--runtime fedora.%{fedora}-arm64" ?
(In reply to Michael Cronenworth from comment #1) > This may be a packaging issue on my side. I'm setting '--runtime > fedora.%{fedora}-x64' when building Jellyfin. Should aarch64 be "--runtime > fedora.%{fedora}-arm64" ? Yes, that sounds right. I wonder if we should work on an RPM macro to compute x64/arm64/whatever correctly for any given Fedora architecture. > Please also check dotnet7.0 and if there is an update please publish it for Fedora 36 and higher. I kicked off the builds last night. Updates are now in progress: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d8382f7f24 https://bodhi.fedoraproject.org/updates/FEDORA-2023-8e27c6bfea (In reply to Omair Majid from comment #2) > I wonder if we should work on an RPM macro to compute x64/arm64/whatever > correctly for any given Fedora architecture. Yes, please. > I kicked off the builds last night. Updates are now in progress: > > https://bodhi.fedoraproject.org/updates/FEDORA-2023-d8382f7f24 > https://bodhi.fedoraproject.org/updates/FEDORA-2023-8e27c6bfea Thanks. I was taking a look at the upstream runtime ID list and it looks like it stops at F38. Is it time to add F39, F40, etc.? https://github.com/dotnet/runtime/blob/main/src/libraries/Microsoft.NETCore.Platforms/src/runtime.json > I was taking a look at the upstream runtime ID list and it looks like it stops at F38. Is it time to add F39, F40, etc.? The upstream runtime id list is generally treated as a compatibility matrix. It's effectively append-only and has been growing non-stop, even impacting .NET startup time for certain scenarios. That makes .NET upstream hesitant about adding future/unreleased versions. They only consider future versions when we can show them "this is now in use/active development". That kind of rules out adding F40 right now. Since Fedora 39 branched recently and container images are now available that claim to be Fedora 39, I was able to put out PRs for that: - main: https://github.com/dotnet/runtime/pull/82185 - 7.0: https://github.com/dotnet/runtime/pull/82208 - 6.0: https://github.com/dotnet/runtime/pull/82210 There are also longer term plans to move way from needing to maintain that RID list: https://github.com/dotnet/designs/pull/260 OK, thanks for the update. This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39. |