Skip to content

Split tainted Repository install out, so it can be installed if RPM F…#1343

Open
technicks89 wants to merge 4 commits into
ChrisTitusTech:mainfrom
technicks89:1259_RPM_Fusion_Refactor
Open

Split tainted Repository install out, so it can be installed if RPM F…#1343
technicks89 wants to merge 4 commits into
ChrisTitusTech:mainfrom
technicks89:1259_RPM_Fusion_Refactor

Conversation

@technicks89

Copy link
Copy Markdown
Contributor

…usion is already installed

Type of Change

  • Refactoring

Description

Split Tainted Repo install from RPM Fusion to allow users to install tainted if they already have Fusion installed

Issues / other PRs related

Screenshots (if applicable)

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR refactors the Fedora RPM Fusion setup script to separate installing the “tainted” RPM Fusion repositories from the base RPM Fusion repositories, so users can add tainted repos even when RPM Fusion is already installed (addressing issue #1259).

Changes:

  • Split tainted repository installation into a dedicated installRPMFusionTainted() function invoked after installRPMFusion().
  • Adjusted the base RPM Fusion install flow to emit an “already installed” message when repo files are present.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread core/tabs/system-setup/fedora/rpm-fusion-setup.sh Outdated
Comment thread core/tabs/system-setup/fedora/rpm-fusion-setup.sh Outdated
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fcd91a42-f079-4ba1-95ea-1dc9d075f49f

📥 Commits

Reviewing files that changed from the base of the PR and between 02feceb and 510996c.

📒 Files selected for processing (1)
  • core/tabs/system-setup/fedora/rpm-fusion-setup.sh
🚧 Files skipped from review as they are similar to previous changes (1)
  • core/tabs/system-setup/fedora/rpm-fusion-setup.sh

📝 Walkthrough

Summary by CodeRabbit

  • New Features
    • Improved Fedora RPM Fusion setup with clearer separation between standard and optional tainted repositories.
    • Added Fedora-version-aware behavior when configuring repositories and enabling codecs.
    • Detects whether RPM Fusion repository files are already present and avoids unnecessary changes.
    • Prompts for missing tainted packages and provides updated status messaging after enabling them.

Walkthrough

The Fedora RPM Fusion setup caches the Fedora version, separates standard and tainted repository handling, and invokes both flows after environment validation.

Changes

RPM Fusion setup

Layer / File(s) Summary
Standard repository installation
core/tabs/system-setup/fedora/rpm-fusion-setup.sh
installRPMFusion uses the cached Fedora version to configure standard RPM Fusion repositories and appstream data without handling tainted repositories.
Tainted repository installation and invocation
core/tabs/system-setup/fedora/rpm-fusion-setup.sh
installRPMFusionTainted detects, prompts for, installs, and enables tainted repositories; the script now invokes both installation functions.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Suggested reviewers: christitustech

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant RPMFusionSetup
  participant RPM
  User->>RPMFusionSetup: Run RPM Fusion setup
  RPMFusionSetup->>RPM: Read Fedora version
  RPMFusionSetup->>RPM: Install standard repositories
  RPMFusionSetup->>RPMFusionSetup: Check tainted repository packages
  RPMFusionSetup->>User: Prompt for tainted repositories
  User->>RPMFusionSetup: Approve installation
  RPMFusionSetup->>RPM: Install and enable tainted repositories
Loading
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title matches the main change: separating tainted RPM Fusion installation for cases where standard Fusion is already installed.
Description check ✅ Passed The description is directly about splitting tainted repo installation from RPM Fusion installation, which matches the changeset.
Linked Issues check ✅ Passed The PR now offers tainted repo installation even when non-tainted RPM Fusion is present, satisfying #1259.
Out of Scope Changes check ✅ Passed The additional Fedora version handling and repo enablement changes are implementation details of the same RPM Fusion refactor.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
core/tabs/system-setup/fedora/rpm-fusion-setup.sh (1)

6-16: 🎯 Functional Correctness | 🔵 Trivial | 💤 Low value

Reuse FEDORA_VERSION in the RPM Fusion URLs
The URLs still call rpm -E %fedora even though FEDORA_VERSION is already computed above; use the cached value there too.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@core/tabs/system-setup/fedora/rpm-fusion-setup.sh` around lines 6 - 16,
Update installRPMFusion to interpolate the existing FEDORA_VERSION variable in
both RPM Fusion release URLs instead of invoking rpm -E %fedora again; leave the
repository checks and installation flow unchanged.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@core/tabs/system-setup/fedora/rpm-fusion-setup.sh`:
- Around line 6-16: Update installRPMFusion to interpolate the existing
FEDORA_VERSION variable in both RPM Fusion release URLs instead of invoking rpm
-E %fedora again; leave the repository checks and installation flow unchanged.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: dd2e8689-69f9-4e36-9c57-e67502405c02

📥 Commits

Reviewing files that changed from the base of the PR and between 41fc991 and 02feceb.

📒 Files selected for processing (1)
  • core/tabs/system-setup/fedora/rpm-fusion-setup.sh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Oversight]: RPM Fusion option should install tainted repositories if other repositories are already installed

2 participants