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: 2.75
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 .. 9 10 11 12 13 14 15 16 17 18 19 .. 27 Next › Last »

ali.molaei commented on 2021-04-30 15:25 (UTC)

@eimis yes it's the problem, and more than that, 1.7.0 and 1.7.1 are marked as pre-releases

@Spixmaster https://github.com/ProtonMail/proton-bridge/issues/174#issuecomment-827530618

eimis commented on 2021-04-30 14:38 (UTC)

Version 1.7.1 is already out. Where is the problem with updating?

maybe this:

Updating files: 100% (9714/9714), done.
if [ "linux" == "darwin" ]; then cp -f "./utils/QTBUG-88600/libqcocoa.dylib" "./vendor-cache/github.com/therecipe/env_linux_amd64_513/5.13.0/clang_64/plugins/platforms/"; fi;
go install -v -tags=no_env github.com/therecipe/qt/cmd/...
/home/eimis/go/pkg/mod/github.com/therecipe/qt@v0.0.0-20200701200531-7f61353ee73e/internal/binding/files/docs/mod.go:4:2: no required module provides package github.com/therecipe/qt/internal/binding/files/docs/5.12.0; to add it:
    go get github.com/therecipe/qt/internal/binding/files/docs/5.12.0
/home/eimis/go/pkg/mod/github.com/therecipe/qt@v0.0.0-20200701200531-7f61353ee73e/internal/binding/files/docs/mod.go:5:2: no required module provides package github.com/therecipe/qt/internal/binding/files/docs/5.13.0; to add it:
    go get github.com/therecipe/qt/internal/binding/files/docs/5.13.0
make: *** [Makefile:180: prepare-vendor] Error 1
==> ERROR: A failure occurred in prepare().
    Aborting...

Spixmaster commented on 2021-04-30 10:21 (UTC)

Version 1.7.1 is already out. Where is the problem with updating?

ali.molaei commented on 2021-04-25 16:57 (UTC)

I am aware of 1.7.0 but there are some issues building the package, waiting for upstream to resolve it

ali.molaei commented on 2021-04-03 06:34 (UTC) (edited on 2021-04-03 06:38 (UTC) by ali.molaei)

@iyanmv It's a little bit of a legacy that I am not downloading the tar.gz file

First, the GitHub repository didn't have tags when we started to build it from the source

Second, Sometimes we want to add a fix like the last version which we compiled from one commit after the 1.6.6 tag

Third, I think tar.gz files didn't have proper versioning sometimes, I was switched to tar.gz in 2020-05-25 and switched back to git and tags in 2020-08-14, before that it was using the tar.gz

About the build function though, you are right, I will fix that in the next version

iyanmv commented on 2021-04-02 12:50 (UTC)

Hi ali.molaei! Thanks for maintaining this package. Just a few things I saw today when installing it. Why don't you use the tar.gz from the version instead of cloning the git repo?

source=(https://github.com/ProtonMail/proton-bridge/archive/refs/tags/br-${pkgver}.tar.gz)

Also, you shouldn't build the package in the prepare function. Use build instead [1].

[1] https://wiki.archlinux.org/index.php/Creating_packages#build()

Spixmaster commented on 2021-03-05 05:53 (UTC)

@ali.molaei I thought my problem was a different one. Nevertheless, it is working now. Thank you for your work.

ali.molaei commented on 2021-03-04 20:22 (UTC)

@Spixmaster I'm well aware of this issue, if you read the comments, I mentioned it before :)

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

Actually, this commit is fixed the issue, But it's not included in the latest tag

Spixmaster commented on 2021-03-04 19:58 (UTC)

The package is not building.

go: downloading golang.org/x/tools v0.0.0-20200117012304-6edc0a871e69
go: downloading golang.org/x/sys v0.0.0-20200323222414-85ca7c5b95cd
/home/user/.go/pkg/mod/github.com/therecipe/qt@v0.0.0-20200701200531-7f61353ee73e/internal/binding/files/docs/mod.go:4:2: no required module provides package github.com/therecipe/qt/internal/binding/files/docs/5.12.0; to add it:
        go get github.com/therecipe/qt/internal/binding/files/docs/5.12.0
/home/user/.go/pkg/mod/github.com/therecipe/qt@v0.0.0-20200701200531-7f61353ee73e/internal/binding/files/docs/mod.go:5:2: no required module provides package github.com/therecipe/qt/internal/binding/files/docs/5.13.0; to add it:
        go get github.com/therecipe/qt/internal/binding/files/docs/5.13.0
make: *** [Makefile:172: prepare-vendor] Fehler 1
==> FEHLER: Ein Fehler geschah in prepare().
    Breche ab...
error making: protonmail-bridge

ali.molaei commented on 2021-03-01 09:12 (UTC)

@captainfeeny thanks for letting me know a new tag is on GitHub, but I'm not gonna update this package until this issue gets fixed

I can fix it temporarily in the PKGBUILD but I don't, the reason is it makes the PKGBUILD specific to some versions and makes it not a general script.

And also, On the website, the latest version is still 1.6.3, so I will wait until at least it changes