After manual extraction, some binaries may not be executable. Fix with:
Now armed with the alien tool, Alex navigated to his Downloads folder where the .deb file sat innocently.
Even a simple .deb might rely on package names that Fedora’s repositories don’t recognise.
alien --to-rpm --scripts mysoftware.deb
While the steps outlined above are technically correct, it's important to reiterate that . It reached its official end-of-life (EOL) in July 2013. This means: install deb package on fedora 17 user new
This information helps you manually install any required libraries on Fedora.
Do not force square pegs into round holes. Use Fedora’s native package manager ( yum ) for a smooth experience.
Are you comfortable using the , or do you prefer a graphical interface ?
The biggest challenge when converting a .deb is that the required libraries or packages have different names on Fedora. For example, a Debian package might depend on libssl1.1 , while Fedora uses openssl . When you run alien and then yum localinstall , yum will search for the exact dependency names from the .deb metadata – and fail. After manual extraction, some binaries may not be executable
The command to use is yum localinstall , which tells yum to treat a local RPM file as if it were from an online repository:
Alien is the most common way to try and make a .deb package work on Fedora by converting it into an .rpm package.
Most popular software is already packaged for Fedora. Install with sudo yum install <package> .
Now you have the knowledge to install that stubborn .deb package on Fedora 17. Proceed with caution, and happy Linux learning! alien --to-rpm --scripts mysoftware
He spent the next hour on the forums, learning about rpm -e to erase the package and cleaning up his database.
cd Downloads
: Converting a package with Alien does not guarantee it will run perfectly. The software might still look for Debian-specific system files that do not exist on Fedora.