I got curious and decided to try the app on my testing machine which is running Fedora 25 Beta (Plasma) I copied the whole folder and executed once more polar file that is inside the bin folder this time it doesn't work. I gave it a try and executed polar file that is inside the bin folder and. ![]() Interesting enough we have in this structure libffmpeg.so the shared object that was failing under Fedora.Īt this point I wanted to try if this is a binary application that self-contain all that it needs to work. When you execute alien -g polarr_1.0.0-1_b it will create two folders:įor our needs here they contain the same info and I will stick to this one polarr-1.0.0.orig this folder has the following structure. In this case, if we can see the content of the package it would be simple to check what is failing when alien is converting the deb to rpm. spec" if you were creating a Red Hat package. The package can be built from this temporary directory by running "debian/rules binary", if you were creating a Debian package, or by running "rpmbuild -bb. This is useful if you want to move files around in the package before building it. g, -generate Generate a temporary directory suitable for building a package from, but do not actually create the package. ![]() Since the generated rpm file was failing and dnf provides */libffmpeg.so results didn't help to solve the dependency issue I looked at the alien manual, man alien, and this option will helps us in this case: I did some testing on my Fedora 23 (XFCE) home server, this are my founds.
0 Comments
Leave a Reply. |