How To Install Rpm In Ubuntu

How To Install Rpm In Ubuntu

Reading time1 min
#Linux#Software#OpenSource#Ubuntu#RPM#PackageManagement

Mastering RPM Installation on Ubuntu: Bridging Package Management Worlds

Forget switching operating systems or recompiling software—learn the precise, dependable method to install RPM packages on Ubuntu, turning a traditional compatibility hurdle into an everyday capability.


Ubuntu users are no strangers to the .deb package format, seamlessly managed by tools like apt and dpkg. However, occasionally you’ll encounter valuable software or enterprise tools distributed solely as .rpm files—Red Hat’s package format favored by Fedora, CentOS, and other RPM-based distributions.

So, what’s the best way to install RPM packages on Ubuntu without resorting to risky recompilations or switching distros? This guide covers the practical methods and tools to install .rpm packages on your Ubuntu system reliably and cleanly.


Why is this important?

Ubuntu’s default package management is built around Debian packages, but many niche applications, proprietary software, or legacy tools might only be available as RPMs. Rather than compiling from source or changing your OS, mastering RPM installation lets you access a wider ecosystem effortlessly.


The challenge: RPMs on Debian-based systems

Since .rpm and .deb employ different package formats and dependency resolutions, you cannot simply run dpkg -i some-package.rpm—that will result in an error. You need tools capable of converting or handling these files in a way that respects dependencies and system stability.


How to Install RPM Packages on Ubuntu: Step-by-Step

Method 1: Using alien – The go-to conversion tool

The quickest way to get an RPM installed in Ubuntu is through alien, a tool specifically designed to convert between .rpm, .deb, .tgz, and more.

Step 1: Install alien and prerequisite tools

Open a terminal and run:

sudo apt update
sudo apt install alien dpkg-dev debhelper build-essential

Alien depends on some packaging tools for managing conversions properly.

Step 2: Convert the RPM to DEB

Suppose you downloaded example-package.rpm. To convert it:

sudo alien --to-deb example-package.rpm

This will produce a file like example-package.deb.

You can also add the --scripts option if the RPM contains installation scripts that should be preserved:

sudo alien --to-deb --scripts example-package.rpm

Step 3: Install the converted DEB package

Once converted:

sudo dpkg -i example-package.deb

If there are dependency issues:

sudo apt-get install -f

This command fixes missing dependencies by pulling them from Ubuntu repositories.

Example in practice:

Let’s say you want to install Dropbox's unofficial RPM (if no DEB available):

wget https://linux.dropbox.com/packages/fedora/dropbox-123.4.2.rpm
sudo alien --to-deb --scripts dropbox-123.4.2.rpm
sudo dpkg -i dropbox_123.4.2-2_all.deb
sudo apt-get install -f

Method 2: Using rpm command with caution

Ubuntu can install the rpm utility itself, allowing inspection of RPM files. But using it directly for installation is not recommended, as it bypasses Ubuntu's native dependency manager (apt) leading to potential broken systems.

Install rpm utility:

sudo apt install rpm

You can query info using:

rpm -qpi example-package.rpm   # Show package info
rpm -qlp example-package.rpm   # List files inside the package

Avoid installing directly with:

sudo rpm -i example-package.rpm

because it does not check for dependencies against your system's repositories.


Managing dependencies manually

If you must use an RPM or converted DEB package that has unmet dependencies unavailable via apt, consider:

  • Searching for Ubuntu equivalents of those dependencies.
  • Manually downloading needed libraries.
  • Checking if a snap/flatpak/appimage version exists.
  • Ultimately considering building from source if nothing else works safely.

Bonus Tips for Smooth Experience

  • Always review what files an RPM installs before converting/installation (rpm -qlp).
  • Use virtualization (Docker/VM) when testing unknown third-party RPMs.
  • Consider containerization if software environment isolation is needed.
  • For proprietary software vendors offering both RPM and DEB, prefer downloading DEBs directly on Ubuntu.
  • Update your system regularly after manual installations to avoid conflicts.

Wrapping Up — Expand Your Software Toolbox!

While Ubuntu thrives with its native .deb ecosystem, mastering tools like alien makes you flexible enough to bridge worlds effortlessly—opening access to many valuable applications without hopping distros or rebuilding packages yourself.

Give it a try today: download an RPM you need, use alien, and install confidently on your favorite Ubuntu workstation!

Have you tried installing an RPM this way before? Share your experiences or questions in the comments below!


Happy packaging!
— Your friendly Linux enthusiast


References & Further Reading


If you'd like me to cover how to automate this process or handle specific tricky cases (like rpm dependencies or scripts), just ask!