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

The problem seems to be that Protonmail is flagging 2.3.0-1 as out of date (via the app -- at least on my machine -- https://postimg.cc/ZWqXV3MC), despite: (1) GitHub stating that it is the latest version (https://github.com/ProtonMail/proton-bridge); and (2) the ProtonMail Bridge download for Linux providing 2.3.0-1 (https://proton.me/mail/bridge#download).

Not much can be done from the AUR package maintainer's perspective. It is officially up to date -- though the app reports otherwise.

@dct As you can see, checking for an update on 2.3.0 is saying it's up-to-date https://postimg.cc/ykFZhLWV

Also, the version being served on the https://proton.me/mail/bridge#download is 2.3.0 (deb and PKGBUILD) https://postimg.cc/pmC54yD4

More than that, the GitHub repo marked this release as a pre-release, so I consider 2.4.0 as a pre-release.

I don't know what you want me to do about the GitHub repo, it's not in my control, you can always open an issue there and ask about what's going on with the pre-release tag and versions on windows being updated to 2.4.0, you can also submit an AUR package called protonmail-bridge-pre-release or protonmail-bridge-beta or anything you want, anytime you want, please consider my concern not wanting to update immediately after a pre-release, introducing potential bugs, etc... It's not "failing" to update, it's a choice not to update to the latest commit/beta/pre-release

i flagged it cause protonmail-bridge keeps saying its out of date on this machine only. not my windows or mac and they are running 2.4.0. either update the github package or i will submit the arch pkgbuild for it myself since this will be the third release you have failed to update in the last year.

2.4.0 is a pre-release, please do not flag the package out of date for pre-releases

Hi,

I don't know if there's an issue with the export PATH=$PATH:$(go env GOPATH)/bin/ part or if it's intended but building protonmail-bridge creates the "go" directory (containing the bin and pkg directories) in the user's home directory (~) and just leave it there afterwards.
Do you think this could this be avoided (like putting this directory in ${srcdir} or /tmp for instance?) or at least be deleted from the user's home dir after the building is over?

Can you please consider pulling from the tar.gz source instead of the git tag so we can sha256sum the file? Thanks.

I confirm that this package is out of date as of 2022-08-12 , and that dct's update 2022-08-06 18:35 (UTC) works.

I fixed the PKGBUILD to point to the latest commit and changed the git source tag to the correct one. You still need the .desktop file to correctly package it.

# Maintainer: Ali Molaei <ali dot molaei at protonmail dot com>
# Contributor: Lenovsky <lenovsky at pm dot me>
# Contributor: aimileus <me at aimileus dot nl>

pkgname=protonmail-bridge
pkgver=2.2.2
pkgrel=1
pkgdesc="Integrate ProtonMail paid account with any program that supports IMAP and SMTP"
arch=('x86_64')
url="https://protonmail.com/bridge"
license=('GPL3')
makedepends=('go' 'gcc' 'git')
depends=('hicolor-icon-theme' 'libsecret' 'ttf-dejavu')
optdepends=(
    'org.freedesktop.secrets: Applications that support Freedesktop secrets api'
    'gnome-keyring: gnome-keyring support'
    'pass: pass support'
)
conflicts=('protonmail-bridge-bin')
options=('!emptydirs' '!strip')

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

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

sha256sums=('SKIP'
            '226bc140ec5c34cfdff42b33058d045446a4006518d2660db932c7f51632b48a')

prepare() {
    cd ${srcdir}/proton-bridge/
    sed -i s/1.8.0+git/1.8.1+git/ Makefile
    export PATH=$PATH:$(go env GOPATH)/bin/  
    make clean
}

Fixing cloning problem now, @chovy are you sure? I don't think it's out of date https://github.com/ProtonMail/proton-bridge/releases

out of date now.