Arch Linux User Repository

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/

This package is now being built from source. if you want the binary version, use protonmail-bridge-bin package

@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

@ali.molaei I take your point. Just to provide some context, today the gui app started saying my version out of date and nagging me to update. I did what I described below with PKGBUILD and now the app is happy again. Also here https://protonmail.com/bridge/install it lists 1.8.12 as the latest version. I see now, and it not notice before, that on GitHub 1.8.12 is listed as pre-release and 1.8.10 is "Latest", but something funny is happening if a) the app itself is nagging me to get the latest version and b) the official binaries are 1.8.12 not 1.8.10. It seems like an inconsistency to me and maybe that just have not flagged 1.8.12 as "Latest" on GitHub but are seemingly treating it as the stable version everywhere else.

@mjandrews This package has never been on the latest commit, this is the latest stable release, and 1.8.11, 1.8.12 releases are marked as "Pre-release" on Github (https://github.com/ProtonMail/proton-bridge/releases) so, this package is up-to-date in my opinion; if you want an up-to-latest-commit package I recommend you to create a separate protonmail-bridge-git package.

About the commit being used for this package, it is one commit after the 1.8.10 which is just fixing go.sum file which was preventing the package from being compiled. it will be replaced by a tag when another stable release is available.

Here's my patch of PKGBUILD to get it working with latest version as of December 6, 2021

From 497bd49c4ef955472b1db97dba07710b44a54585 Mon Sep 17 00:00:00 2001
From: Mark Andrews <mjandrews.org@gmail.com>
Date: Mon, 6 Dec 2021 14:40:59 +0000
Subject: [PATCH] Use latest commit from upstream Git repo

Bump latest version to 1.8.12
---
 PKGBUILD | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index fbcfcf1..56ea4a2 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@
 # Contributor: aimileus <me at aimileus dot nl>

 pkgname=protonmail-bridge
-pkgver=1.8.10
+pkgver=1.8.12
 pkgrel=2
 pkgdesc="Integrate ProtonMail paid account with any program that supports IMAP and SMTP"
 arch=('x86_64')
@@ -23,7 +23,7 @@ options=('!emptydirs' '!strip')
 #        "protonmail-bridge.desktop")

 # Source to compile to a specific commit
-source=("git+https://github.com/ProtonMail/proton-bridge.git#commit=a219ecf3cbe4fa31517136131fc585e93b86c3dd"
+source=("git+https://github.com/ProtonMail/proton-bridge.git"
         "protonmail-bridge.desktop")

 sha256sums=('SKIP'
-- 
2.34.1

I was also failing to update/install in the same way as @rockryeidel but on paru. I tried the usual cache cleaning/rebuild methods with paru --redownload --rebuild <pkg_name> and paru -Scc to no avail.

The solution I found was to remove (or more cautiously move it elsewhere) the ~/.cache/paru/clone/protonmail-bridge/ directory and its contents

@rockryeidel can you try a clean build? I'm not familiar with pamac, but you can download the PKGBUILD on your system and put it in a package, then run makepkg in that folder and see if it builds?

No pgp in this package is prompted to enter the key ring and hopes to be repaired. Or can it be poured manually? How much is it

I am getting this error when attempting updated from 1.8.10-1:

ERROR: /var/tmp/pamac-build-rockyreidel/protonmail-bridge/proton-bridge is not a clone of https://github.com/ProtonMail/proton-bridge.git Aborting...

Any advice on further troubleshooting this? I don't believe there are any modifications on my build.

Update: Resetting the package build files resolved this. I must have had some edits to my build files previously.

I can confirm it works now, thank you for the really quick fix!

@lbravo Thanks for letting me know, this should be working now