Arch Linux User Repository

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!

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/

please add libgl as a dependency as --cli and everything else fails if you do not have libgl installed

The error @bmckain mentions comes from the recent changes made definitive by github, see here. I would suggest to explicitly use https as follows (I'm not aware of other ways of proposing a contribution than through comments).

diff --git a/PKGBUILD b/PKGBUILD
index 9f58a3a..8535812 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -19,7 +19,7 @@ conflicts=('protonmail-bridge-bin')
 options=('!emptydirs' '!strip')

 # Source to compile to a specific tag
-source=("git://github.com/ProtonMail/proton-bridge.git#tag=br-${pkgver}"
+source=("git+https://github.com/ProtonMail/proton-bridge.git#tag=br-${pkgver}"
         "protonmail-bridge.desktop")

 # Source to compile to a specific commit

It would appear there are issues with the pkgbuild again. The error message

The unauthenticated git protocol on port 9418 is no longer supported.

is showing when I tried to upgrade to 2.1.1 from 1.8.12 or even do a clean install.

I keep getting this error when I try to run mkpkg (please let me know how to improve formatting if possible)

==> Starting prepare()...

make -C internal/frontend -f Makefile.local clean

make[1]: Entering directory '/home/zodi/protonmail-bridge/src/proton-bridge/internal/frontend'

rm -f

make[1]: Leaving directory '/home/zodi/protonmail-bridge/src/proton-bridge/internal/frontend'

rm -rf ./vendor

rm -rf vendor-cache

rm -rf cmd/Desktop-Bridge/deploy

rm -rf cmd/Import-Export/deploy

rm -f build last.log mem.pprof main.go

rm -f resource.syso

rm -f release-notes/bridge.html

rm -f release-notes/import-export.html

==> Starting build()...

/usr/bin/go

cd ./utils/ && ./credits.sh bridge

git clone https://github.com/therecipe/env_linux_amd64_513.git vendor-cache/github.com/therecipe/env_linux_amd64_513

Cloning into 'vendor-cache/github.com/therecipe/env_linux_amd64_513'...

remote: Enumerating objects: 9446, done.

remote: Total 9446 (delta 0), reused 0 (delta 0), pack-reused 9446

Receiving objects: 100% (9446/9446), 129.24 MiB | 2.65 MiB/s, done.

Resolving deltas: 100% (4194/4194), done.

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/...

go mod vendor

ln -sf /home/zodi/protonmail-bridge/src/proton-bridge/vendor-cache/github.com/therecipe/env_linux_amd64_513 vendor/github.com/therecipe/env_linux_amd64_513

rm -rf deploy linux cmd/Desktop-Bridge/deploy

cp cmd/Desktop-Bridge/main.go .

qtdeploy -tags=' build_qt' -ldflags '-X github.com/ProtonMail/proton-bridge/internal/constants.Version=2.1.1+git -X github.com/ProtonMail/proton-bridge/internal/constants.Revision=61e4ca5814 -X github.com/ProtonMail/proton-bridge/internal/constants.BuildTime=2022-02-26T13:57:11-0500' build desktop

PANI[0000] failed to remove /var/tmp/.env_linux_amd64 error="unlinkat /var/tmp/.env_linux_amd64: operation not permitted"

panic: (*logrus.Entry) 0xc00009d420

goroutine 1 [running]:

github.com/sirupsen/logrus.Entry.log({0xc00009c070, 0xc000144360, {0x0, 0x0, 0x0}, 0x0, 0x0, {0x0, 0x0}, 0x0, ...}, ...)

/home/zodi/go/pkg/mod/github.com/sirupsen/logrus@v1.7.0/entry.go:255 +0x2b3

github.com/sirupsen/logrus.(*Entry).Log(0xc00009d3b0, 0x0, {0xc0000ad9d8, 0x1, 0x1})

/home/zodi/go/pkg/mod/github.com/sirupsen/logrus@v1.7.0/entry.go:283 +0xa8

github.com/sirupsen/logrus.(*Entry).Logf(0xc00009d3b0, 0x0, {0x895191, 0x19}, {0xc0000ada48, 0xc0000ada58, 0x4d86aa})

/home/zodi/go/pkg/mod/github.com/sirupsen/logrus@v1.7.0/entry.go:329 +0x85

github.com/sirupsen/logrus.(*Entry).Panicf(...)

/home/zodi/go/pkg/mod/github.com/sirupsen/logrus@v1.7.0/entry.go:367

github.com/therecipe/qt/internal/utils.RemoveAll({0xc000026280, 0x19})

/home/zodi/go/pkg/mod/github.com/therecipe/qt@v0.0.0-20200701200531-7f61353ee73e/internal/utils/utils.go:37 +0xa5

github.com/therecipe/qt/internal/cmd.InitEnv({0x875417, 0x5}, 0x0, {0xc00002a004, 0x2e})

/home/zodi/go/pkg/mod/github.com/therecipe/qt@v0.0.0-20200701200531-7f61353ee73e/internal/cmd/cmd.go:198 +0x317

main.main()

/home/zodi/go/pkg/mod/github.com/therecipe/qt@v0.0.0-20200701200531-7f61353ee73e/cmd/qtdeploy/main.go:136 +0x9b5

make: *** [Makefile:122: cmd/Desktop-Bridge/deploy/linux/proton-bridge] Error 2

==> ERROR: A failure occurred in build().

Aborting...

Any idea what I might be doing wrong?

With 2.1.0 I am getting /usr/bin/ld: cannot find -lGL adding glu to to makedepends it was able to compile without issue.

Even though 2.1.0 is marked as pre-release in github, they are rolling out that version through their official updater. Also, their PKGBUILD also points to this version.

Edit: Ups, just read comments below... okay, I see they are not very consistent. No rush, we can wait till they change the flag in the following days.

@mjandrews I opened an issue for it: https://github.com/ProtonMail/proton-bridge/issues/240

With regard to the inconsistent information about releases (i.e. GitHub listing v.1.8.12 as pre-release yet it being listed as the latest official binary elsewhere, etc), I was going to open an Issue on GitHub (as suggested by @ali.molaei), but they want a specific template to be used for Issues (understandably) and it did not look like my query would be welcome. On the template, however, they do say to contact bridge@protonmail.ch for matters that don't fit the template. So I did that. I will report back if I learn something that clarifies the situation.

@mjandrews Thanks for your reply.

I understand, and this happened before too, maybe it's better to have a conversation about it with the developers on protonmail's github

You are right, If it is a pre-release, why notifying to update and put it on the website, If it is a final release, why is the github tag wrong?

The team on github is pretty active and will almost answer within a day or so, and fix the issues, I appreciate if you start the conversation there