build(rpm): add conditional openSUSE Leap/Tumbleweed python paths and update Tumbleweed CUDA#5353
build(rpm): add conditional openSUSE Leap/Tumbleweed python paths and update Tumbleweed CUDA#5353gummiangler wants to merge 1 commit into
Conversation
Bundle ReportBundle size has no change ✅ |
|
Looks like it failed -> https://copr.fedorainfracloud.org/coprs/lizardbyte/pulls/build/10657213/ Also, I think Tumebleweed could use uv, which is the preferred option going forward for Python tooling. https://software.opensuse.org/package/python-uv ... doesn't seem available in Leap though. |
|
@ReenigneArcher
This is an environmental and repository configuration issue inherent to the Copr project settings rather than the Sunshine.spec file or source code. To fix this, someone needs to adjust the project's Copr settings for the opensuse-tumbleweed-x86_64 chroot. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5353 +/- ##
==========================================
- Coverage 27.53% 27.53% -0.01%
==========================================
Files 113 113
Lines 25593 25593
Branches 11237 11237
==========================================
- Hits 7048 7047 -1
+ Misses 17021 16451 -570
- Partials 1524 2095 +571
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
|
|
I can adjust it, but I'll need to know specifically what to change. In the past I've only had to enable the chroots and never had to customize them. Even previously when I tried tumbleweed I got much further than this error. |
|
Fedora infrastructure migrated its backends to use dnf5 by default for specific chroots. Older versions of dnf would simply warn and skip missing .asc metadata files for local build directories. This could be the problem Until the Fedora Copr team updates their Tumbleweed bootstrap logic, i guess turning off gpgcheck and repo_gpgcheck for the chroot initialization is the best workaround. I don't know much about COPR, but as far as I can tell, under the Chroots configuration for opensuse-tumbleweed-x86_64, Copr provides a text area to inject custom raw Mock options.
Maybe there is a checkbox or something like this there too. |
|
@gummiangler these are the options I see when I try to edit a chroot. 
|
|
Based on those options, the easiest and best fix is to change Mock bootstrap from "Use project settings" to Disable. Right now, Copr is pulling a pre-configured openSUSE container image to act as a bootstrap manager. That image has outdated GPG keys and uses dnf5, which panics over the lack of metadata signatures (repomd.xml.asc) for some reason. But as far as i know Fedora’s Copr build hosts are fully updated and perfectly capable of handling Tumbleweed directly without needing a bootstrap wrapper. |
|
|
Again the build failed and again its a problem with Copr. When you turned off Mock's bootstrap setting, the host's native dnf5 took over the installation task. However, because the host is running a different operating system, it doesn't have openSUSE's official repository signing keys trusted inside its local security configuration. When dnf5 went to unpack the very first core package (openSUSE-release), it couldn't verify that the package's digital signature was authentic and untampered with. To get around this, we need to tell the host's package manager to skip the signature validation check specifically for this initialization phase. But i dont know where we can set gpgcheck=0. |
|
I finally found the exact upstream issue, and it turns out we actually can't fix it from our side at all. Someone just opened a pull request to fix this on the backend fedora-copr/copr#4359. The real problem is that openSUSE Tumbleweed's new dnf5 defaults strictly to repo_gpgcheck=1, but Copr doesn't sign its own repository metadata yet. It has nothing to do with our config or our keys. The fix they are merging right now will explicitly inject repo_gpgcheck=0 into the backend templates for Copr repos to bypass this exact bootstrap crash. We just have to wait for them to deploy the fix. You can revert the changes to the chroot. |
|
@gummiangler thanks for looking into it! |
2 participants
Description
This PR introduces conditional Python interpreter paths and updated versions/dependencies for openSUSE Leap and Tumbleweed within the RPM spec file.
openSUSE Leap: Explicitly uses python311 and points CMake to /usr/bin/python3.11.
openSUSE Tumbleweed: Switches to the generic python3 stack, updates GCC to version 15, and bumps the target CUDA version to 13.2.0 (Build 595.45.04).
Note regarding CUDA: These changes were successfully tested and compiled on a local openSUSE Tumbleweed system using the pre-installed system CUDA 13.2.0. The build configuration is identical to the one intended for the download script, except that the local build skipped the install_cuda function and its patching logic. If any unexpected build errors occur on COPR for Tumbleweed, it is highly recommended to check whether the cuda-13-math_functions.patch conflicts with the CUDA 13.2.0 headers.
Screenshot
Issues Fixed or Closed
Roadmap Issues
Type of Change
Checklist
AI Usage