Package Base Details: protonmail-bridge

Git Clone URL: https://aur.archlinux.org/protonmail-bridge.git (read-only, click to copy)
Keywords: bridge email mail protonmail protonmail-bridge
Submitter: aimileus
Maintainer: ali.molaei (PMBridge-Devs, BenTheTechGuy, carsme)
Last Packager: BenTheTechGuy
Votes: 110
Popularity: 5.55
First Submitted: 2018-03-02 16:03 (UTC)
Last Updated: 2024-03-21 17:22 (UTC)

Pinned Comments

carsme commented on 2023-12-08 22:34 (UTC) (edited on 2023-12-08 22:35 (UTC) by carsme)

NOTICE: This pkgbase is now produces two packages:

  • protonmail-bridge-core: Containing the core daemon & CLI program.
  • protonmail-bridge: Containing the Qt desktop application.

The second package depends on the first. If you don't have a need for the desktop application, you can now choose to only install protonmail-bridge-core.

This packaging change should be seamless and no action should be required before or after the upgrade.

Thanks to @ali.molaei and @BenTheTechGuy for the feedback regarding this change!

bthompson commented on 2021-06-17 04:13 (UTC)

Just having pass installed with a key set up wasn't enough for me, I had to follow this: https://pychao.com/2020/06/10/update-on-using-protonmail-bridge-on-headless-wordpress-linux-servers/

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 27 Next › Last »

ali.molaei commented on 2023-11-11 14:41 (UTC)

@Antiz as I said, I'm right now working on changes suggested by @mirlinf, give me some time to see if i can get it working, if not I'll reply here

Antiz commented on 2023-11-11 14:37 (UTC) (edited on 2023-11-11 14:38 (UTC) by Antiz)

@usenetuser upstream source code is being updated, I'm not just able to build it reliably, this shouldn't be deleted :)

@ali.molaei actually, the above is starting to be debatable I think.
I know you've been working hard to build/package this properly for quite some times now (and thanks a lot for that!).
But in the end, that package received its last update more than a year ago and is severely outdated, is there a point to let it there in its current state?

At that point, I'm starting to wonder if it wouldn't be better to just remove it for the time being, at least to avoid people being mislead to that critically outdated package. Nothing prevents you to re-push it once the current issues are solved.

I'm eventually considering accepting the current deletion request to be honest. But we can exchange about the current state of this package if you're up for it. Having a wide and clear vision on how things evolved (or not) since a year would help taking the best decision.

ali.molaei commented on 2023-11-11 14:10 (UTC)

@usenetuser upstream source code is being updated, I'm not just able to build it reliably, this shouldn't be deleted :)

usenetuser commented on 2023-11-11 14:09 (UTC) (edited on 2023-11-11 14:10 (UTC) by usenetuser)

@ali.molaei Apologies for the misfiling. The package has been marked flagged out of date on-and-off for several years (including times when it was actually up to date). My comment was intended to assist users by directing them to a maintained package. I think this package should be deleted as the binary version works just fine and is supported by upstream.

It is dangerous to have a package this out of date in the repo.

ali.molaei commented on 2023-11-11 14:07 (UTC)

@usenetuser WOW, so now it's a deletion request :| Do you understand I'm working on the package right now?

ali.molaei commented on 2023-11-11 13:35 (UTC)

@usenetuser what's wrong with you? 1. This package doesn't need to be orphaned 2. Time and time again I mentioned that there are problems building this package's new version, so you can help to build it if you want, not orphan it and read the comments 3. protonmail-bridge-bin that you mentioned is also maintained by me, so I'm well aware that this is out of date and "the out of date" flag is there for this exact reason 4. I'm activly trying to fix the problem considering @merlinf's comment from "TODAY" and am receiving an orphan request, thats a bit disappointing:)

usenetuser commented on 2023-11-11 13:02 (UTC)

This package is wildly out of date and should not be used. Use the binary instead: https://aur.archlinux.org/packages/protonmail-bridge-bin

merlinf commented on 2023-11-11 07:55 (UTC)

@ali.molaei @yochananmarqos I have a PKGBUILD that builds on one machine and on the other it doesn't because of the Makefile step where it installs built files to the ./cmd directory. It may be helpful: https://github.com/fejzuli/pkgbuilds/tree/master/WIP-proton-bridge

The set-qt-dir.patch fixes

CMake Error at cmake-build-release/cmake_install.cmake:87 (file):
  file INSTALL cannot find "/usr/qml": No such file or directory.

yochananmarqos commented on 2023-09-30 22:13 (UTC) (edited on 2023-09-30 22:14 (UTC) by yochananmarqos)

@ali.molaei: Since it's an upstream issue and no one downstream can do anything about it, just unflag the package. Otherwise, some idjit is going to create another orphan request and it will be automatically accepted again since it's been so long.

I have a WIP PKGBUILD, however, with PR 347, this still happens as already mentioned in #346:

CMake Error at cmake-build-release/cmake_install.cmake:87 (file):
  file INSTALL cannot find "/usr/qml": No such file or directory.

ali.molaei commented on 2023-09-30 20:17 (UTC)

@garlicbreadwolfs i hope you'd read the comments before marking this as orphan, if you can build this package from source, please let me know how

https://github.com/ProtonMail/proton-bridge/issues/346