ProtonMail / proton-bridge

Proton Mail Bridge application
GNU General Public License v3.0
1.14k stars 155 forks source link

Unable to install on Fedora Silverblue and Kinoite (rpm-ostree based systems) #368

Closed nirvinm closed 1 year ago

nirvinm commented 1 year ago

The recent release of proton-bridge v3.0.20 (v3.0.x) is not getting installed in rpm-ostree based immutable distros like Fedora Silverblue / Kinoite / CoreOS. Previous versions (2.x) installed and worked fine.

Expected Behavior

Proton Bridge should be installed on Fedora Silverblue.

Current Behavior

$ rpm-ostree install protonmail-bridge-3.0.20-1.x86_64.rpm

error: Importing package 'protonmail-bridge': Analyzing /ch.proton.bridge-gui.desktop: Unsupported path; see https://github.com/projectatomic/rpm-ostree/issues/233

Steps to Reproduce

  1. Install Fedora Silverblue or Kinoite
  2. Download Proton Bridge RPM package.
  3. Install it with rpm-ostree install ./protonmail-bridge-3.0.20-1.x86_64.rpm

Version Information

protonmail-bridge-3.0.20-1.x86_64.rpm

Context (Environment)

Platform: Linux OS: Fedora Silverblue 37

Possible Implementation

Possibly related to https://github.com/coreos/rpm-ostree/issues/233

Proton Bridge RPM is trying to write to non-standard directory which is not supported by rpm-ostree.

LBeernaertProton commented 1 year ago

Hey @nirvinm . Thanks for reporting this issue. Please follow the progress on #363 for future updates.

Closing as duplicate.

nirvinm commented 1 year ago

I agree this is same issue as #363. But this issue should not be closed because in this case, I could not install Proton Bridge at all. Maybe #363 should be closed in favor of this?

LBeernaertProton commented 1 year ago

The root cause of the issue is the same. Internally we generate the RPM files from the Deb file. Hence, when we fix the deb file we will by extension fix the RPM file. Should it happen again for another reason, please feel free to post and we will re-open the ticket.

LBeernaertProton commented 1 year ago

@nirvinm We have released a fix with 3.0.21 that should address the problem.

nirvinm commented 1 year ago

Thanks for resolving. It works now.