Issue installing along with Slack from RPM on Linux

Frits_Stegmann · December 4, 2024, 9:28am

I have checked the troubleshooting

Bug report

When trying to install the latest release 5.9.0, I get this issue.

Environment

Same a previous issue logged.

How to reproduce

wget https://api.inkdrop.app/download/linux/rpm -O /tmp/inkdrop.rpm && sudo yum install /tmp/inkdrop.rpm && rm /tmp/inkdrop.rpm

Frits_Stegmann · December 4, 2024, 12:40pm

I’m using the archived zip file version for now, but I can’t see a Icon for a Linux desktop file or an example of a Linux desktop file.

craftzdog · December 5, 2024, 12:17am

Hi Frits,

Thanks for reporting.
It looks like the issue is the same as this one:

github.com/ferdium/ferdium-app

Bug: RPM package conflict with another electron app

opened 05:20PM - 03 Jul 22 UTC

closed 02:52AM - 04 Jul 22 UTC

UriMtzF

bug

### Avoid duplicates - [X] I have searched the [issues tracker](https://githu…b.com/ferdium/ferdium-app/issues) for a bug report similar to mine, in vain ### Ferdium Version 6.0.0-nightly 86 ### What Operating System are you using? Other Linux ### Operating System Version Fedora 36 ### What arch are you using? x64 ### Last Known Working Ferdium version 6.0.0-nightly 81 ### Expected Behavior When installing Ferdium it should install when running the command: `sudo dnf install ./Ferdium-linux-6.0.0-nightly.86.rpm` ### Actual Behavior The package manager, after trying to install, will find a conflicting file between Ferdi and other electron package. The conflicting file is under the path: `/user/lib/.build-id/a2/562c52725bb7caa27cd0de814ec368b8c45e7f` This won't let the package be installed ### Steps to reproduce 1. Install GDLauncher version 1.1.25 (the only known electron software that cause conflict) 2. Try to install Ferdium nightly 86 ### Debug link _No response_ ### Screenshots _No response_ ### Additional information To prevent this from conflicting with other Electron based apps, it's necessary to omit all the symlinks, to achieve this, Electron-builder uses `fpm` to have an easier way to build linux apps. The solution is to tell Electron-builder to have some flags on `fpm` while building the rpm to prevent creating those symlinks. According to Electron-builder documentation and fpm documentation this option is `--rpm-rpmbuild-define "_build_id_links none"`, this should be changed on the `electron-builder.yml` file at the root of the project Please refer to the following links to find the proper way to do this: - [Documentation of electron build and the "fpm" option](https://www.electron.build/configuration/linux) - [The fpm usage](https://github.com/jordansissel/fpm/wiki#usage=) - [The macros on rpm, specifically those flags used on fpm](https://github.com/rpm-software-management/rpm/blob/4a9440006398646583f0d9ae1837dad2875013aa/macros.in#L506=) - [A stackoverflow question on avoiding the creation of symlink](https://stackoverflow.com/questions/60673229/fpm-v-1-11-0-vs-inclusion-of-usr-lib-build-id-files) Some sources: - [A Zettlr issue (another open source app based on electron) pointing to the right direction](https://github.com/Zettlr/Zettlr/issues/1321) - [A closed Electron Builder issue that was closed without further info](https://github.com/electron-userland/electron-builder/issues/5227) - [An issue on fpm talking about those "unwanted" directories](https://github.com/jordansissel/fpm/issues/1503) - [A thread from RHEL talking about conflicting files on rpm's](https://access.redhat.com/discussions/5045161)

Slack is also an Electron-based app, and the installer tries to create symlinks to the same paths.
Could you try the --force option?