Arch Linux User Repository

PSA: Upstream does not support building natively for ARM64, only cross-compiling. You can use mullvad-vpn-bin instead.

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

@yochananmarqos I just checked and it doesn't appear to be on the wiki anywhere, weird. I learned about it from other packages and have been using it myself.

@jhenson: I didn't know makepkg could do that, thanks! Where did you find that out? I didn't see anything in the wiki or the man page about it.

If you put ?signed at the end of the git urls makepkg will verify the commit/tag for you. This is needed for building in a clean chroot where the sources are verified outside of the chroot. The validpgpkeys array also needs to list the specific signing sub-key instead of the parent key.

The following patch fixes the chroot verification for me:

diff --git a/PKGBUILD b/PKGBUILD
index [`53c9852`](https://aur.archlinux.org/cgit/aur.git/commit/?h=mullvad-vpn&id=53c9852)..6f2752c 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -16,16 +16,15 @@ depends=('libnotify' 'libappindicator-gtk3' 'libxss' 'nss')
 makedepends=('git' 'cargo' 'npm' 'rpm')
 install="$pkgname.install"
 _commit='0c1a0aca41492fbb9ef1f187122e2f5bda0927ba'
-source=("git+<https://github.com/mullvad/mullvadvpn-app.git#tag=>$pkgver"
-        "git+<https://github.com/mullvad/mullvadvpn-app-binaries.git#commit=>$_commit"
+source=("git+<https://github.com/mullvad/mullvadvpn-app.git#tag=>$pkgver?signed"
+        "git+<https://github.com/mullvad/mullvadvpn-app-binaries.git#commit=>$_commit?signed"
         "$pkgname.desktop"
         'update-relays.sh')
 sha256sums=('SKIP'
             'SKIP'
             '121d90e6683e64d9c0d2dbb7b346fa918bdb37cf21fdaf9f66232304ed23abc2'
             'ec125bc9cfe2403bacfcaebf4b58f88b4d734b0f6194c23016efd7e15684f8e0')
-validpgpkeys=('A6A4778440D27368967A7A3578CEAA8CB72E4467')
-             # Linus Färnstrand (code signing key) <linus at mullvad dot net>
+validpgpkeys=('EA0A77BF9E115615FC3BD8BC7653B940E494FE87') # Linus Färnstrand (code signing key) <linus at mullvad dot net>

 prepare() {
        # Point the submodule to our local copy
@@ -34,13 +33,6 @@ prepare() {
        git config submodule.mullvadvpn-app-binaries.url \
                "$srcdir/mullvadvpn-app-binaries"
        git submodule update
-
-       # Verify git tag
-       git verify-tag "$pkgver"
-
-       # Verify git commit
-       cd "$srcdir/mullvadvpn-app-binaries"
-       git verify-commit "$_commit"
 }

 build() {

Thanks for all your work on this package!

@procyon-lotor: Why are you not running the stable 5.4.2 kernel? See Enable support to run unprivileged containers (optional)

@yochanamarqos

I'm using kernel Linux 5.4rc7.d1117.g1d4c79e-1

here's the pastebin of the build. https://pastebin.com/S1y1hehH

@procyon-lotor: That shouldn't happen during build, but could happen running the GUI. What kernel are you using? Please paste the build log to a pastebin service and link it here, I'll take a look.

@a.liedtke: Please also paste the build log to a pastebin service and link it here.

Get error: 20 error code ELIFECYCLE 21 error errno 1 22 error mullvad-vpn@2019.9.0 pack:linux: gulp pack-linux 22 error Exit status 1 23 error Failed at the mullvad-vpn@2019.9.0 pack:linux script. 23 error This is probably not a problem with npm. There is likely additional logging output above.

Stupid question incoming:

I'm having trouble getting the mullvad build to run correctly.

I get an error message regarding chrome-sandbox not being owned by root and it should be set as chmod 4755.

Having done that, rerunning the build just replaces the files with newly generated.

How do i solve this?

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