Sorry I zero interest in providing compiled modules for fedora, too much
work for no personal gain or benefit.
User will learn their lesson when they don't wait, why should I do more
to fix problems caused gnome-software, discovery or 'dnf offline update'
I don't consider the atomic issue is ours to solve, TBH atomic isn't
fedora, they can solve their own issues.
On 01/07/2026 22:18, gordon.messmer--- via rpmfusion-developers wrote:
I've been working on the infrastructure needed to build and sign modules (and
kernels, for that matter) for Fedora. I think the work is > 90% done, so I
wanted to see if rpmfusion might be interested in deploying similar builds for its
users.
Pre-built modules should help eliminate the relatively common case that users
disrupt a background build of the modules (or they fail for some other reason
like running out of disk space) resulting in a non-functional system after
reboot. They're also a lot easier to layer on Atomic systems.
https://codeberg.org/project-resistor/signed-code-build-stack - Builds run in
an AWS VPC. There are two instances there, one that hosts a runner that
executes builds, with access to a key in an HSM (backed by AWS KMS), and a
second instance that listens to the Fedora messaging bus, which triggers builds
when a new kernel is submitted to the testing repo.
https://codeberg.org/project-resistor-kernel/kmod-build-workflows - This shared
workflow is used by kernel module packages
https://codeberg.org/project-resistor-kernel/nvidia-open-kmod - For example,
the NVIDIA OpenRM driver
_______________________________________________
rpmfusion-developers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
rpmfusion-developers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
