Package Details: protonmail-bridge 3.10.0-1

Git Clone URL: https://aur.archlinux.org/protonmail-bridge.git (read-only, click to copy)
Package Base: protonmail-bridge
Description: Integrate ProtonMail paid account with any program that supports IMAP and SMTP (Qt desktop application)
Upstream URL: https://github.com/ProtonMail/proton-bridge
Keywords: bridge email mail protonmail protonmail-bridge
Licenses: GPL-3.0-only
Submitter: aimileus
Maintainer: ali.molaei (PMBridge-Devs, BenTheTechGuy, carsme)
Last Packager: BenTheTechGuy
Votes: 106
Popularity: 3.09
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 2 3 4 5 6 7 8 9 10 11 12 .. 27 Next › Last »

Antiz commented on 2023-11-12 14:21 (UTC) (edited on 2023-11-12 14:22 (UTC) by Antiz)

@merlinf In fact, packages are never completely removed but only "archived" instead so the comments wouldn't be gone for good.

Anyway, @ali.molaei would be great if at least the pkgdesc could warn about the actual state of the package, as well as a "WARNING" pinned comment to, at least, make sure people are not misled to this package for the time being, as well as preventing useless orphan/deletion requests (you can state that in the said comment).

I'm refusing the current deletion request ;)

merlinf commented on 2023-11-12 14:00 (UTC)

@Antiz It is evident that multiple people want this package to work again and that the maintainer @ali.molaei is very active and responded within the same day.

I believe that the existence of this package in the AUR gives our efforts to fix it some discoverability and may attract someone that does get it working.

If this package really needs to get deleted I propose that @ali.molaei move the repo to one of the major hosts and create a backup of the comments there and then pin a comment on the binary repo to call for support on this package.

merlinf commented on 2023-11-12 13:58 (UTC)

@yochananmarqos yes that is the exact same error. It doesn't happen in one of my local nspawn containers which gives me hope that it is fixable, but I needed a break from the constant building so I couldn't figure out why that is.

ali.molaei commented on 2023-11-12 11:00 (UTC)

I cannot make it work, it complains about some QML Components not being installed (But I believe they are) so I'm out of ideas _(--)/

ali.molaei commented on 2023-11-11 18:44 (UTC) (edited on 2023-11-11 18:47 (UTC) by ali.molaei)

UPDATE: I am able to build the package now, but the built binary is not run able (I think because of some wrong build environment variables etc). I'm now trying to build it in an isolated environment with just qt6 present to see what's the result.

Beside this update, I was thinking there are some valuable comments and information here that would be a shame to be lost with deletion of this package, what's your opinion about one of these solutions:

  1. I can add a big warning to be printed in the terminal when installing this package to warn people about the state of this package and which alternatives they have

  2. I can make this package a decoy to install protonmail-bridge-bin for now

  3. A pinned comment here explaining the situation

@Antiz @yochananmarqos @merlinf @usenetuser

BTW, I'm still working on this, sorry it takes time, it takes time to build it each time I change something

yochananmarqos commented on 2023-11-11 17:31 (UTC)

@merlinf: Ah, the set-qt-dir.patch does the trick.

My WIP PKGBUILD is similar and sounds like I'm seeing the same error:

-- Installing: /build/protonmail-bridge/src/proton-bridge/cmd/Desktop-Bridge/deploy/linux/lib/libQt6QmlCore.so.6.6.0
+ check_exit 'install failed'
+ '[' 0 -ne 0 ']'
mv "/build/protonmail-bridge/src/proton-bridge/bridge" "/build/protonmail-bridge/src/proton-bridge/cmd/Desktop-Bridge/deploy/linux/bridge"
cp -pf ./dist/bridge.svg cmd/Desktop-Bridge/deploy/linux/logo.svg
cp -pf ./LICENSE cmd/Desktop-Bridge/deploy/linux/
cp -pf ./Changelog.md cmd/Desktop-Bridge/deploy/linux/
cp -pf ./dist/proton-bridge.desktop cmd/Desktop-Bridge/deploy/linux/
mv proton-bridge cmd/Desktop-Bridge/deploy/linux/
mv: cannot stat 'proton-bridge': No such file or directory
make: *** [Makefile:134: cmd/Desktop-Bridge/deploy/linux] Error 1

Antiz commented on 2023-11-11 14:46 (UTC)

@ali.molaei Alright, sure. Thanks a lot for your efforts!
Hopefully you can manage to get it working :)

Let's wait for your input, I remain available if needed!

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 :)