How to Install RPM Packages on Ubuntu 26.04, 24.04 and 22.04

Last updated Friday, May 8, 2026 1:50 pm Joshua James 6 min read 1 comment

Ubuntu cannot install RPM packages natively because APT and dpkg expect DEB files. When you need to install RPM packages on Ubuntu anyway, Alien can convert simpler RPM files into DEB packages that APT understands. That fallback works best for self-contained software, not large desktop applications with distro-specific dependencies.

On Ubuntu 26.04, 24.04, and 22.04, Alien installs from the default repositories. The same workflow applies across all three releases. Install Alien, check the RPM architecture, convert the file, install the generated DEB with APT, and then test the program immediately for runtime library problems.

Install RPM Packages on Ubuntu with Alien

Start with package metadata refresh, then install Alien from Ubuntu’s Universe repository. Alien also pulls in the RPM tooling and packaging helpers it needs to inspect RPM headers and build a local DEB package.

Before you convert, check whether the vendor offers a DEB package or APT repository. DEB is Ubuntu’s native package format, and a maintained Snap, AppImage, or Flatpak package on Ubuntu may still be cleaner than converting an RPM when no DEB build exists.

Update Ubuntu and Install Alien

Refresh APT first so Ubuntu sees the current package metadata before you add the conversion tool.

sudo apt update

These commands use sudo for package-management tasks. If your account is not in the sudoers file yet, use root or follow the guide on how to add a new user to sudoers on Ubuntu.

Alien lives in Ubuntu’s Universe repository on 26.04, 24.04, and 22.04. If APT returns Unable to locate package alien on a minimal install, enable Universe and Multiverse in Ubuntu first, then retry the install.

sudo apt install -y alien

Installing Alien also pulls in rpm, rpm2cpio, debhelper, and build helpers such as build-essential on lean systems. Running sudo apt install rpm alone fixes rpm: command not found for inspection work, but it does not make Ubuntu an RPM-based system or let APT install .rpm files directly.

Avoid using sudo rpm -i package.rpm as a shortcut on Ubuntu. That bypasses the normal APT and dpkg ownership path, which makes dependency resolution, updates, and removal harder to reason about later.

Confirm the converter is available before you touch the RPM you actually care about.

alien --version
alien version 8.95.9-1

Ubuntu 24.04 currently reports alien version 8.95.6, and Ubuntu 22.04 reports alien version 8.95.5. Any version output confirms Alien is installed correctly.

Check the RPM File Architecture on Ubuntu

Confirm your architecture before you convert anything. Ubuntu reports 64-bit x86 systems as x86_64 at the kernel level, even though DEB packages often use the amd64 label for the same hardware.

uname -m
x86_64

Then check the downloaded file itself. Replace package-name.rpm with the RPM you already saved to your system.

file "$HOME/Downloads/package-name.rpm"

A valid package reports an RPM archive. For example:

hello-2.12.2-1.el9.x86_64.rpm: RPM v3.0 bin i386/x86_64

If file reports HTML, ASCII text, or another non-RPM type, download the package again from the vendor’s direct RPM URL instead of the landing page that led to it.

Convert the RPM to a DEB Package with Alien on Ubuntu

Run the next block from the directory that already contains the RPM. That keeps the generated DEB beside the source file, and the --to-deb flag makes the conversion target explicit when you revisit the command later.

cd ~/Downloads
sudo alien --to-deb package-name.rpm

Alien rewrites the output filename into Debian style with underscores. A successful conversion ends with a generated line like this:

hello_2.12.2-2_amd64.deb generated

Some RPMs also print a NOKEY warning during conversion because Ubuntu has not imported the RPM signing key. Treat that as a trust warning, not as proof that the package is unusable. Verify the RPM from the vendor’s official checksum, signature, or download page before you install the converted DEB.

Install the Converted DEB Package with APT on Ubuntu

Use the exact DEB filename Alien just printed. Installing the local file through APT is safer than dpkg -i because APT can try to resolve repository dependencies in the same step.

sudo apt install ./package-name_1.0-2_amd64.deb

The ./ prefix tells APT to install a local file instead of searching the repositories. For the sample hello conversion, that filename is hello_2.12.2-2_amd64.deb. If APT stops on missing repository dependencies, repair the package state once before you retry the local DEB.

sudo apt --fix-broken install

Relevant output from a successful local install includes:

Selecting previously unselected package hello.
Unpacking hello (2.12.2-2) ...
Setting up hello (2.12.2-2) ...

If you need the package name for later verification or removal, read it from the generated DEB metadata:

dpkg-deb -f ./package-name_1.0-2_amd64.deb package
hello

Verify the Converted Package on Ubuntu

Check the installed state next. Replace package-name with the package name inside the converted DEB, not the original RPM filename.

dpkg -s package-name | grep '^Status:'
Status: install ok installed

If the package installs a command-line tool, run it immediately. A compatible EPEL 9 hello package returned Hello, world! on Ubuntu 26.04, 24.04, and 22.04 after conversion. A newer RPM built against a newer base system can still install and then fail at runtime, so the launch test matters as much as the package-state check.

Troubleshoot RPM Package Conversion on Ubuntu

Most Alien problems show up after the .deb exists, not while the file is being converted. These are the failure modes that show up most often on Ubuntu and the quickest way to identify them.

RPM Command Not Found on Ubuntu

If a vendor README tells you to run rpm and Ubuntu reports the command is missing, install Alien for conversion work or install rpm only when you need inspection tools.

bash: line 1: rpm: command not found

Do not treat the rpm package as a normal installer for Ubuntu. Use Alien to produce a DEB package, then install that local DEB through APT so the package lands in Ubuntu’s native package database.

Converted Package Installs but Fails to Start on Ubuntu

A successful apt install does not guarantee the binary matches Ubuntu’s libc or library stack. Start the program from a terminal once so the loader error stays visible instead of disappearing behind a desktop launcher.

program-name

A runtime failure can look like this:

hello: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by hello)

This kind of error means the RPM was built for a newer base system than your Ubuntu release provides. At that point, stop forcing the conversion and look for an older vendor RPM, a native DEB package, or another supported package format instead.

Alien Cannot Read the Downloaded RPM File on Ubuntu

If Alien throws an unknown-file-type error or exits immediately, inspect the download itself before you blame the converter. The file command should identify an RPM archive. HTML or plain text usually means the browser or curl saved a landing page, login prompt, or 404 response instead of the package.

Download the RPM again from the vendor’s direct package URL, not the page that leads to it, then repeat the conversion once the archive identifies cleanly as an RPM.

APT Cannot Finish the Converted DEB Install on Ubuntu

A local apt install ./package-name_...deb can still fail if the converted package expects library names or package versions Ubuntu does not ship. Repair the interrupted install once, then decide whether the package is worth forcing further.

sudo apt --fix-broken install

If the same dependency chain fails again after --fix-broken, stop there. That usually means the RPM depends on packages Ubuntu does not provide under compatible names, and a native package is the safer path.

Remove Alien and Converted RPM Packages on Ubuntu

Remove the converted application and Alien as separate steps. That keeps the cleanup predictable, and it lets you verify the converted package is gone before you remove the converter itself.

Remove the Converted Package on Ubuntu

Use the package name from the earlier dpkg check, not the original RPM filename. Replace remove with purge if you also want package-managed configuration files removed.

sudo apt remove package-name

Verify the removal with dpkg rather than repository candidate data. Ubuntu may still show a repository candidate if it already ships a package with the same name in its own archives.

dpkg -l package-name | grep '^ii' || echo "package-name is not installed"
package-name is not installed

Remove Alien on Ubuntu

Once you are done converting RPM files, remove Alien itself without automatic cleanup first. On reused systems, a blind autoremove can sweep up unrelated packages you still want to review.

sudo apt remove alien

If you decide to clear Alien’s leftover dependencies too, preview autoremove first. Continue only when the list contains packages you no longer need.

sudo apt autoremove --dry-run

If the dry run lists only packages you recognize as Alien leftovers, run the real cleanup:

sudo apt autoremove

Ubuntu’s package metadata should show Alien as removed while keeping the current repository candidate available.

apt-cache policy alien
alien:
  Installed: (none)
  Candidate: 8.95.9-1
  Version table:
     8.95.9-1 500
        500 http://au.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages

On Ubuntu 24.04 the candidate currently shows 8.95.6, and on Ubuntu 22.04 it shows 8.95.5. The important signal is Installed: (none).

Delete the Downloaded RPM and Generated DEB Files on Ubuntu

After the application is either working or fully removed, you can delete the downloaded archives from your home directory.

rm "$HOME/Downloads/package-name.rpm" "$HOME/Downloads/package-name_1.0-2_amd64.deb"

This only removes the local files. It does not uninstall anything that APT already added to the system.

Conclusion

Alien gives Ubuntu a workable escape hatch when a vendor only ships an RPM, but the converted package still needs a real launch test before you trust it. When you return to normal Ubuntu packages, update packages via the Ubuntu command line; if a test conversion goes sideways, remove packages on Ubuntu from the command line and start clean.

Follow LinuxCapable

Want more LinuxCapable guides in Google?

Add LinuxCapable as a preferred source so Google can show more of our fresh Linux tutorials in Top Stories and From your sources when relevant.

Add LinuxCapable as a preferred source on Google
Search LinuxCapable

Need another guide?

Search LinuxCapable for package installs, commands, troubleshooting, and follow-up guides related to what you just read.

Found this guide useful?

Support LinuxCapable to keep tutorials free and up to date.

Buy me a coffeeBuy me a coffee

1 thought on “How to Install RPM Packages on Ubuntu 26.04, 24.04 and 22.04”

Before commenting, please review our Comments Policy.
Formatting tips for your comment

You can use basic HTML to format your comment. Useful tags currently allowed in published comments:

You type Result
<code>command</code> command
<strong>bold</strong> bold
<em>italic</em> italic
<blockquote>quote</blockquote> quote block

Got a Question or Feedback?

We read and reply to every comment - let us know how we can help or improve this guide.

Let us know you are human: