RPM install fails on openSUSE distributions (Tumbleweed)

[pgonin]

Thanks in advance for your bug report!

• [X] Have you reproduced issue in safe mode?
• [X] Have you used the debugging guide to try to resolve the issue?
• [X] Have you checked our FAQs to make sure your question isn't answered there?
• [X] Have you checked to make sure your issue does not already exist?
• [X] Have you checked you are on the latest release of Pulsar?

What happened?

Install of RPM fails with error Problem: nothing provides 'libuuid' needed by the to be installed pulsar-1.114.0-1.x86_64

Pulsar version

1.114.0

Which OS does this happen on?

🐧 OpenSUSE based

OS details

Tumbleweed

Which CPU architecture are you running this on?

x86_64/AMD64

What steps are needed to reproduce this?

When trying to install Pulsar (v1.114.0) on openSUSE (tumbleweed) with RPM https://github.com/pulsar-edit/pulsar/releases/download/v1.114.0/Linux.pulsar-1.114.0.x86_64.rpm Using command sudo zypper in https://github.com/pulsar-edit/pulsar/releases/download/v1.114.0/Linux.pulsar-1.114.0.x86_64.rpm It fails with error:

Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides 'libuuid' needed by the to be installed pulsar-1.114.0-1.x86_64
 Solution 1: do not install pulsar-1.114.0-1.x86_64
 Solution 2: break pulsar-1.114.0-1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c/d/?] (c): 2
Resolving dependencies...
Resolving package dependencies...

The following package is going to be upgraded:
  pulsar

1 package to upgrade.
Overall download size: 137.8 MiB. Already cached: 0 B. After the operation, 13.4 MiB will be freed.
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: pulsar-1.114.0-1.x86_64 (Plain RPM files cache)                                                 (1/1), 137.8 MiB    
Linux.pulsar-1.114.0.x86_64.rpm:
    Package header is not signed!

pulsar-1.114.0-1.x86_64 (Plain RPM files cache): Signature verification failed [6-File is unsigned]
Abort, retry, ignore? [a/r/i] (a): i

Checking for file conflicts: .............................................................................................[done]
(1/1) Installing: pulsar-1.114.0-1.x86_64 ................................................................................[done]

Ignoring is ok since libuuid is actually available on openSUSE (Tumbleweed) but from a different package:

zypper se libuuid
Loading repository data...
Reading installed packages...

S  | Name                 | Summary                       | Type
---+----------------------+-------------------------------+--------
i+ | libuuid-devel        | Development files for libuuid | package
   | libuuid-devel-32bit  | Development files for libuuid | package
   | libuuid-devel-static | Development files for libuuid | package
i+ | libuuid1             | Library to generate UUIDs     | package
i+ | libuuid1-32bit       | Library to generate UUIDs     | package

Additional Information:

No response

[Daeraxa]

I did a quick search for this and it appears this is specific to Electron, it would be interesting to see if this is still a problem on the modern Electron branch.

[confused-Techie]

@Daeraxa Man, I was hoping this was a sub-dependency of something declared in our control.in file.

Do you think that'd be a valid way to override this? Or does the generated Electron package basically have final say

[Daeraxa]

Honestly not sure, from what I understand it is because RedHat based distros are using the libuuid library but SUSE uses libuuid1 to provide the same thing (mentioned in the issue, which is also the name of it in Debian). Never really done that much of a deep dive into packages like this. Could well be worth adding it. I assume it is electron-builder that is making the assumption that the RPM is RedHat based and not SUSE, therefore picks the RedHat library name.