@TSTSTS: No. See the pinned comment?
Search Criteria
Package Details: mullvad-vpn 2024.7-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/mullvad-vpn.git (read-only, click to copy) |
|---|---|
| Package Base: | mullvad-vpn |
| Description: | The Mullvad VPN client app for desktop |
| Upstream URL: | https://www.mullvad.net |
| Licenses: | GPL-3.0-or-later |
| Submitter: | gin078 |
| Maintainer: | yochananmarqos |
| Last Packager: | yochananmarqos |
| Votes: | 137 |
| Popularity: | 2.73 |
| First Submitted: | 2018-10-24 17:33 (UTC) |
| Last Updated: | 2024-10-30 16:32 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- iputils (busybox-coreutilsAUR, iputils-gitAUR)
- libnftnl (libnftnl-fullconeAUR, libnftnl-gitAUR)
- libnotify (libnotify-gitAUR)
- nss (nss-hgAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust, rustup) (make)
- git (git-gitAUR, git-glAUR) (make)
- go (go-gitAUR, gcc-go-gitAUR, gcc-go-snapshotAUR, go-sylixosAUR, gcc-go) (make)
- libxcrypt-compat (make)
- nvmAUR (nvm-gitAUR) (make)
- protobuf (protobuf-gitAUR) (make)
Required by (3)
Sources (7)
- git+https://github.com/mullvad/maybenot.git#commit=b06094e81701782d28cd2312f58e0654109d04ce
- git+https://github.com/mullvad/mullvadvpn-app-binaries.git#commit=049d5d3bc0c86c29c20f2073460186a83c1d7094?signed
- git+https://github.com/mullvad/mullvadvpn-app.git#tag=2024.7?signed
- git+https://github.com/mullvad/wireguard-go.git#commit=b1cf09a982bba6f6c63fadc956d88e8c2326d05e?signed
- mullvad-vpn.sh
- no-publish.diff
- no-rpm.diff
yochananmarqos commented on 2021-10-25 22:55 (UTC)
TSTSTS commented on 2021-10-25 22:54 (UTC)
Does it take some time to replicate from source to wherever the packages come from? I am getting the error still.
yochananmarqos commented on 2021-10-25 22:24 (UTC)
@tsweet64: Detected by what? AUR helpers are indeed helpful, but not supported.
Apparently no one has been able to update from 2021.4-1 to 2021.5-1 due to the issue I just fixed, so bumping the pkgrel accomplishes nothing. Just build it.
tsweet64 commented on 2021-10-25 22:02 (UTC)
Had the same issue, thanks. You may want to consider bumping the pkgrel number so that the updated PKGBUILD is detected.
yochananmarqos commented on 2021-10-25 21:46 (UTC)
@TSTSTS: Oops, forgot to uncomment the PGP key. Try it again now.
TSTSTS commented on 2021-10-25 20:04 (UTC)
I am having some issues. When running Paru, I get
==> Making package: mullvad-vpn 2021.5-1 (Mon 25 Oct 2021 02:56:03 PM CDT) ==> Retrieving sources... -> Updating mullvadvpn-app git repo... Fetching origin -> Updating mullvadvpn-app-binaries git repo... Fetching origin -> 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... mullvadvpn-app git repo ... Passed mullvadvpn-app-binaries git repo ... FAILED (invalid public key 8339C7D2942EB854E3F27CE5AEE9DECFD582E984) ==> ERROR: One or more PGP signatures could not be verified! error: failed to download sources for 'mullvad-vpn-2021.5-1': error: packages failed to build: mullvad-vpn-2021.5-1
I tried following the steps here https://mullvad.net/en/help/verifying-signatures/ and got
~ gpg2 --verify MullvadVPN-*.deb.asc gpg: assuming signed data in 'MullvadVPN-2021.5_amd64.deb' gpg: Signature made Mon 25 Oct 2021 05:03:16 AM CDT gpg: using RSA key CA83A46153BC58D69518ED49A26581F219C8314C gpg: BAD signature from "Mullvad (code signing) admin@mullvad.net" [ultimate] ➜ ~
Is this something I am doing wrong?
thx
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-bininstead.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.