What is the recommended way to convert .deb packages to .rpm

Hi there,
I was just wondering if there is a recommended method or software such as Alient to convert .deb packages to .rpm packages.

I have successfully converted a .deb package to .rpm with alien in the commandline although the software will not run.

Is there another method that is recommended ?

Converting the .deb to .rpm with alien may work, but dependencies are often different and thus the rpm may not work. I think you will have to find and resolve those problems on your own unless some tool I am not aware of has been released.

Often it is possible to simply download and compile the source code for that package.

1 Like

Yes I was going to try and build it from source, perhaps using a tarball although the developer is reluctant to provide the source, I thought their may be another way.

I happen to think this is the issue yes, the dependencies may be different

Note that if the package is open source (FOSS) then there should be no issues with receiving the source code. If it is not FOSS then the developer may manage it as they choose and getting it to work is between you and the developer since only they will know the full requirements.

1 Like

I beleive it is odd when I get this response from the developer.

So would I be correct in assuming that “secure” and “Privacy” is more about protecting IP or something?

I wonder why their is so much closed source, with the false belief it is somehow more secure.

I guess I need to wait for them, I have been waiting for 2.5 years for them to build a flatpak or rpm version.

Anyways this is off topic. I guess I will run it in a VM on a .deb system. I thought their would be a way to convert to rpm or builld an App Image or something similar

For me the developers of this package are not willing to share their code and so hacker must reengineer a package, it’s much more complicated than looking at the code and manipulate it. That is what the above message to you means.

Your interpretation of that statement agrees with mine and it seems to indicate concerns about IP. When something is closed source the only ones who know the actual “security” of the code are the developers.

The reason for closed source is so the developers have something they can actually charge money for due to the IP rights and the only source for that exact product is theirs. “More secure” is debatable since no one else can look at the code and verify that.

Good luck with the product on your VM.