FIXED The "S" option in makepkg -CSi was triggering the error. With makepkg -Ci it works.
When I try to update from 2020.4 to 2020.5 I get the following error, when running makepkg -CSi
:
==> Making package: mullvad-vpn 2020.5-1 (Wed 15 Jul 2020 05:15:27 PM CEST)
==> Retrieving sources...
-> Found mullvad-vpn.sh
==> Validating source files with sha256sums...
mullvadvpn-app ... Skipped
mullvadvpn-app-binaries ... Skipped
mullvad-vpn.sh ... Passed
==> Verifying source file signatures with gpg...
git repo ... SIGNATURE NOT FOUND
git repo ... SIGNATURE NOT FOUND
==> ERROR: One or more PGP signatures could not be verified!
When I clone https://github.com/mullvad/mullvadvpn-app.git and verify it with git tag -v 2020.5
I get:
object 0198a8b98683a768bb8306d7b8ead7f9a0ca114c
type commit
tag 2020.5
tagger Linus Färnstrand <linus@mullvad.net> 1593072334 +0200
2020.5
gpg: Signature made Thu 25 Jun 2020 10:05:35 AM CEST
gpg: using RSA key A6A4778440D27368967A7A3578CEAA8CB72E4467
gpg: Good signature from "Linus Färnstrand (code signing key) <linus@mullvad.net>" [ultimate]
I also tried to import and trust every of Mullvads Developer keys. The error persists. Am I missing something obvious?
Pinned Comments
yochananmarqos commented on 2022-11-11 19:31 (UTC) (edited on 2022-11-13 19:21 (UTC) by yochananmarqos)
PSA: Upstream does not support building natively for ARM64, only cross-compiling. You can use
mullvad-vpn-bin
instead.yochananmarqos commented on 2019-12-07 17:44 (UTC) (edited on 2024-06-06 22:09 (UTC) by yochananmarqos)
--> ALWAYS DO A CLEAN BUILD <--
This package will verify the signature of the git tag / commit. Developer keys are available here and instructions are here. See the PKGBUILD to determine which developer key you need.
Please do not create upstream issues about the AUR package, they do not support it.