Partner links

The pain of trying to install a .deb package on Fedora using Alien

Springseed alien error

During my search for a good Markdown text editor for Linux, I came across a few that had binary installation only for Debian and Ubuntu distributions. See The search for a usable Markdown editor for my Linux desktop.

Because my main Linux desktop is powered for Fedora, I decided to find an alternate method of installing those applications other than compiling them from source. Call it a lazy approach, but sometimes you have to find shortcuts.

The only other method that I am aware of is to use alien to convert the .deb package to a .rpm package, then install the generated RPM package using either yum or alien itself. Unfortunately, all my attempts at that failed.

Here’s what happened.

1. For Atom, the best Markdown-capable editor that I came across, the reason it failed was because libchromiumcontent.so was required, but it could not be installed. There’s a lengthy discussion about issues with libchromiumcontent.so on GitHub, but no suggestion there solved the installation attempt of an alien-generated file.
Atom libchromiumcontent.so

2. For Haroopad, another very good Markdown-capable editor, the problem was with libudev.so.0. I spend almost three hours trying to find a workaround to this one. Yep, I tried symlinking to libudev.so.1.5.x and libudev.so.1 but it didn’t work. I even tried <strong>yum distro-sync</strong> to no avail.
Haroopad libudev.so.0

3. The last attempt was with Springseed, but the reason for failure was slightly different. Couldn’t make head or tail out of the error, so I gave up on it. Will take another stab at it later.
Springseed alien error

So using alien to generate an RPM package from a DEB package is easy. Installing the generated RPM package is where the headache awaits. By the way, to install alien on Fedora, type: <strong>yum install alien</strong>.

Share:

Share on facebook
Facebook
Share on twitter
Twitter
Share on pinterest
Pinterest
Share on linkedin
LinkedIn

Partner links

Newsletter: Subscribe for updates

Subscribe
Notify of
guest
7 Comments
Inline Feedbacks
View all comments
txtechdog
txtechdog
7 years ago

Ok. First, you don’t show the commands you are running to try to install these packages, so this is just guesswork.

If you are using yum to install the packages created by alien, then I would run the following command as root:

yum -y localinstall package_name.rpm

This would allow yum to try to resolve the library dependencies for you. If that didn’t solve the problem, then:

yum whatprovides */libchromiumcontent.so

And if this doesn’t solve the problem, then you would probably have to download and build the dependencies manually.

The last problem is because the person who created the .deb file incorrectly includes / and /usr/bin in their filelist when they shouldn’t have.

All in all, the problem isn’t with how alien is creating the RPMs , it’s the dependencies that are an issue and an incorrectly built .deb package.

So what I’m saying is don’t blame the alien tool. The problem is that translating dependencies between Debian and RPM based systems isn’t always as straight forward as it seems.

Tomás
Tomás
7 years ago

As a fellow Fedora 20 x64 user, I have made the same experiences with “alien”. To get Atom running, I instead followed these instructions to build from source: https://gist.github.com/mojavelinux/225d01e621f467db1c75

Thanks for mentioning gitbook in your related article, I somehow missed that project entirely!
Fixing its install script is trivial indeed.
It tries to symlink “/usr/lib64/libudev.so.1”, a file that does not exist on Fedora 20 x64. Changing it to “/usr/lib64/libudev.so” yielded success.

Tomás
Tomás
Reply to  finid
7 years ago

I have no answer to that, but why do you even want to install with root permissions?

All the installer does is create/symlink files in “~/.gitbook”, “~/.local/share/applications” and “~/Desktop” and use xdg-desktop-menu. None of the above needs root permissions!

Tomás
Tomás
Reply to  finid
7 years ago

You’re absolutely correct!
I got confused with “.so.1″ .”so.0” when I initially used Gitbook directly (without installing) and created a symlink myself.

My original comment on the symlink issue can be disregarded.

Get the latest

On social media

Security distros

Hacker
Linux distros for hacking and pentesting

Crypto mining OS

Bitcoin
Distros for mining bitcoin and other cryptocurrencies

Crypto hardware

MSI GeForce GTX 1070
Installing Nvidia GTX 1070 GPU drivers on Ubuntu

Disk guide

LVM
Beginner's guide to disks & disk partitions in Linux

Bash guide

Bash shell terminal
How to set the PATH variable in Bash
Categories
Archives
7
0
Hya, what do you think? Please comment.x
()
x