I’m using Termius as an SSH client and I wanted to use its SFTP feature but, since I installed it via snap, I can’t.
The problem is that Termius is distributed only as snap or .deb file, and there is (apparently) no option to build it from source so my only option seems to be converting the .deb package to an .rpm one using alien…
I tried running sudo alien -r ./Termius.deb in the folder where I downloaded the package but I get this error:
Warning: Skipping conversion of scripts in package termius-app: postinst postrm
Warning: Use the --scripts parameter to include the scripts.
Package build failed. Here's the log of the command (cd termius-app-7.49.0; rpmbuild --buildroot='/home/lez/Downloads/Termiusus/termius-app-7.49.0' -bb --target x86_64 'termius-app-7.49.0-2.spec'):
error: line 5: Empty tag: Summary:
Building target platforms: x86_64
Building for target x86_64
The sed line fixes this error error: line 5: Empty tag: Summary:
If you do not already have rpmbuild installed, you do so with: sudo dnf install rpm-build
The build directory is removed as part of the rpmbuld process and you find the rpm in the same directory as the deb file.
Unfortunately, I’ve written an email to Termius customer support to ask why, and they answered me it was because the snap version is sandboxed.
So, I asked them if it was possible for them to provide an .rpm package as well or a flatpak version (to which should be possible to grant access to local storage using flatseal if I’m not wrong) but of course I was ignored.
Thanks to your answer, I was able to build the .rpm file successfully, and it seems to be working properly now that I have installed it!
If it was something I was able to do with just the .deb file I really don’t understand why the Termius team (which has access to the source code as well) doesn’t provide an .rpm to be downloaded from their website…
PS: Since the problem appeared to be an empty line in that .spec file, would it have been ok to manually fill it using something like sudo nano termius-app-7.49.0-2.spec? Or should I prefer the sed -i way for some reason?