Bug 2558244

Summary:	Review Request: shim-unsigned-riscv64 - First-stage UEFI bootloader
Product:	[Fedora] Fedora	Reporter:	Andrea Bolognani <abologna>
Component:	Package Review	Assignee:	Richard W.M. Jones <rjones>
Status:	RELEASE_PENDING ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	package-review, rjones
Target Milestone:	---	Flags:	rjones: fedora-review+
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	177841

Description Andrea Bolognani 2026-10-21 12:08:23 UTC

Spec URL: https://abologna.fedorapeople.org/shim/shim-unsigned-riscv64.spec
SRPM URL: https://abologna.fedorapeople.org/shim/shim-unsigned-riscv64-16.1-1.src.rpm
Description: Unsigned build of shim for the riscv64 architecture 
Fedora Account System Username: abologna

This package serves the same purpose as the existing shim-unsigned-x64 and shim-unsigned-aarch64 packages: it produces the unsigned shim binary for the matching architecture. The binary can then optionally be sent out for signing, and later imported into the main shim binary which is what ends up installed on users' systems.

In fact, the spec file and the rest of the package are basically 1:1 identical to the shim-unsigned-aarch64 package, minus the obvious changes needed to adapt to the new architecture.

Having separate source packages for each architecture, instead of a single shim-unsigned package that covers all of them at once, is an intentional design choice. According to the shim maintainers, this approach makes their lives easier when it comes to ongoing maintenance which is why, in agreement with them, I'm sticking with it.

One final thing that is worth mentioning is that, as of the 16.1 release (which is the most recent upstream one), shim does not actually build on riscv64. Support for the architecture has however already been merged upstream[1] and is going to be part of the upcoming 17.0 upstream release, expected roughly a month from now. I am submitting the package for review early in the hope that, by the time upstream tags the new release, everything on the Fedora side is already prepared and all three architectures (x86_64, aarch64, riscv64) can be updated at once.

Thank you for the consideration.


[1] https://github.com/rhboot/shim/pull/778

Comment 1 Richard W.M. Jones 2026-10-21 13:29:42 UTC

I have sponsored Andrea into the packagers group.

Comment 2 Richard W.M. Jones 2026-10-26 13:09:57 UTC

The differences between this package and current shim-unsigned-aarch64 are simply:

-%global efiarch aa64
+%global efiarch riscv64

-Name:          shim-unsigned-aarch64
+Name:          shim-unsigned-riscv64

-ExclusiveArch: aarch64
+ExclusiveArch: riscv64

-Summary:       Debug information for shim-unsigned-aarch64
+Summary:       Debug information for shim-unsigned-riscv64

(and the %changelog is obviously completely different).

Since the package doesn't compile on riscv64, as we are waiting for
upstream 17.0 release to include riscv64 support, I can't use
fedora-review.  Nevertheless the spec file is sane, and obviously
it's substantially identical to the package that is already in Fedora.

I checked the upstream PR (https://github.com/rhboot/shim/pull/778)
which is complete and merged, and compiles from source, so it appears
like we just need to wait and things will proceed smoothly.

I see no reason not to merge this now, even though we don't have
riscv64 support in Fedora yet, and we're waiting briefly for an
upstream release.

Comment 3 Fedora Admin user for bugzilla script actions 2026-10-26 13:37:17 UTC

The Pagure repository was created at https://src.fedoraproject.org/rpms/shim-unsigned-riscv64
Monitoring:
Wasn't able to create project in Anitya. You can create it manually on: `https://release-monitoring.org`