Install RPM Fusion on AlmaLinux 9 – Quick and Dirty
If you’re running AlmaLinux 9 and want that sweet extra set of packages, this is how to get RPM Fusion on your box without blowing up your system.
Why you need RPM Fusion
AlmaLinux’s default repos are great for stability but they leave out a handful of useful drivers, codecs, and software. RPM Fusion fills those gaps with free, community‑maintained packages that keep everything working smoothly—even after an upgrade or a bad driver install that breaks your audio or GPU.
1. Make sure the base system is clean
sudo dnf update --refresh
A fresh system ensures that no old metadata or broken dependencies will trip up the repo setup later. I’ve seen this happen after a half‑finished upgrade where leftover packages caused RPM Fusion to refuse installation.
2. Install the EPEL repository first
sudo dnf install -y epel-release
RPM Fusion depends on some EPEL utilities. Without it you’ll hit “no such package” errors and waste time chasing missing dependencies. Think of EPEL as the base layer that makes everything else stick.
3. Grab the RPM Fusion repo files
sudo dnf install -y https://mirrors.rpmfusion.org/free/el/rpm-fusion-free-release-9.noarch.rpm \
https://mirrors.rpmfusion.org/nonfree/el/rpm-fusion-nonfree-release-9.noarch.rpm
These RPMs add the repo metadata to your system. The URLs are hard‑coded for AlmaLinux 9; if you copy a CentOS 8 link it’ll fail. I’ve tried that once and the whole process broke in half.
4. Verify the repos are enabled
sudo dnf repolist | grep rpmfusion
You should see something like:
rpmfusion-free/9/x86_64 RPM Fusion (Free) for AlmaLinux 9 rpmfusion-nonfree/9/x86_64 RPM Fusion (Non‑Free) for AlmaLinux 9
A quick sanity check before you start pulling packages. It saves a lot of frustration if the repos never actually got added.
5. Enable the “enabled” flags
If either repo shows up as disabled, enable it:
sudo dnf config-manager --set-enabled rpmfusion-free rpmfusion-nonfree
Some installations disable them by default to keep the system lean. You’ll hit “no matching packages” otherwise.
6. Clean the cache and update metadata
sudo dnf clean all && sudo dnf makecache
After adding new repos you want fresh metadata so DNF can see every package available. A stale cache is a common source of “package not found” headaches.
7. Test a quick install
sudo dnf install gstreamer1-plugins-base
If that succeeds, the whole setup works. If it stalls or reports missing dependencies, double‑check the steps above—especially the repo URLs and EPEL installation.
A test install guarantees you can actually pull packages from RPM Fusion. I’ve had users hit a weird “missing architecture” error when they missed the nonfree repo; this catch will surface that early.
8. Optional: Keep the repos updated automatically
Add a cron job or use DNF‑systemd‑timer:
sudo systemctl enable --now dnf-makecache.timer
Keeps the cache fresh without manual intervention, so you never run into “no such package” because the metadata expired. Useful if you’re on a server that gets patched nightly.
TL;DR
1. sudo dnf update --refresh
2. sudo dnf install -y epel-release
3. sudo dnf install -y https://mirrors.rpmfusion.org/free/el/rpm-fusion-free-release-9.noarch.rpm https://mirrors.rpmfusion.org/nonfree/el/rpm-fusion-nonfree-release-9.noarch.rpm
4. Verify with dnf repolist | grep rpmfusion
5. Enable if needed: sudo dnf config-manager --set-enabled rpmfusion-free rpmfusion-nonfree
6. Clean and make cache
7. Try installing a package
That’s it—your AlmaLinux 9 now has the full RPM Fusion collection at its fingertips.
