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.

@Anteduck: That's why it's best to build in a clean chroot so user / system variables don't interfere. However, that flag is part of Rust package guidelines, so I added it.

The PKGBUILD doesn't work if you have a different target directory specified in .cargo/config. Here's a patch that explicitly specifies the target directory:

--- PKGBUILD.old    2021-04-21 20:10:03.284860579 +0900
+++ PKGBUILD    2021-04-21 20:04:14.458205960 +0900
@@ -39,7 +39,7 @@
    sed -i "s/'deb', 'rpm'/'deb'/g" gui/tasks/distribution.js

    echo "Removing old Rust build artifacts"
-   cargo clean
+   cargo clean --target-dir target

    export GOPATH="$srcdir/gopath"
    go clean -modcache
@@ -76,13 +76,13 @@

    echo "Building Rust code in release mode using $RUSTC_VERSION..."

-   cargo build --release --locked
+   cargo build --release --locked --target-dir target

    mkdir -p dist-assets/shell-completions
    for sh in bash zsh fish; do
        echo "Generating shell completion script for $sh..."
-       cargo run --bin mullvad --release --locked -- shell-completions "$sh" \
-           dist-assets/shell-completions/
+       cargo run --bin mullvad --release --locked --target-dir target -- \
+           shell-completions "$sh" dist-assets/shell-completions/
    done

    echo "Copying binaries"
@@ -99,10 +99,10 @@
    done

    echo "Updating relay list..."
-   cargo run --bin relay_list --release > dist-assets/relays.json
+   cargo run --bin relay_list --release --target-dir target > dist-assets/relays.json

    echo "Updating API address cache..."
-   cargo run --bin address_cache --release > dist-assets/api-ip-address.txt
+   cargo run --bin address_cache --release --target-dir target > dist-assets/api-ip-address.txt

    # Build Electron GUI app
    pushd gui
@@ -115,7 +115,7 @@

 #check() {
 #  cd "$srcdir/mullvadvpn-app"
-#  cargo test --release --locked
+#  cargo test --release --locked --target-dir target
 #
 #  cd gui
 #  npm test

@Hubro: I updated the requirements to match Mullvad.

FYI, Node.js 10 is EOL at the end of the month.

@hubro

So try a newer nodejs like erbium or whatever

@andykluger

Yep, still happens after clearing ~/.npm. I've tried installing this package with paru, still same error. I haven't tried installing it completely manually yet.

Which nodejs-providing package do you have installed?

$ pacman -Q | grep -i node
node-gyp 7.1.2-1
nodejs-lts-dubnium 10.24.0-1
perl-tree-dag-node 1.31-2

I noticed node-gyp is installed as a system package, so I tried to delete it. Turns out it's a required dependency of npm:

$ pacman -R node-gyp
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing node-gyp breaks dependency 'node-gyp' required by npm

I tried 3 times, with clean build:

~/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui ~/.cache/yay/mullvad-vpn/src/mullvadvpn-app
Installing JavaScript dependencies...
npm ERR! code 1
npm ERR! path /home/alex/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install
npm ERR! socket hang up
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using node-pre-gyp@0.15.0
npm ERR! node-pre-gyp info using node@15.14.0 | linux | x64
npm ERR! node-pre-gyp WARN Using needle for node-pre-gyp https download 
npm ERR! node-pre-gyp info check checked for "/home/alex/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools/bin/grpc_tools.node" (not found)
npm ERR! node-pre-gyp http GET https://node-precompiled-binaries.grpc.io/grpc-tools/v1.9.1/linux-x64.tar.gz
npm ERR! node-pre-gyp ERR! install error 
npm ERR! node-pre-gyp ERR! stack Error: socket hang up
npm ERR! node-pre-gyp ERR! stack     at connResetException (node:internal/errors:642:14)
npm ERR! node-pre-gyp ERR! stack     at TLSSocket.socketCloseListener (node:_http_client:445:25)
npm ERR! node-pre-gyp ERR! stack     at TLSSocket.emit (node:events:381:22)
npm ERR! node-pre-gyp ERR! stack     at node:net:666:12
npm ERR! node-pre-gyp ERR! stack     at TCP.done (node:_tls_wrap:577:7)
npm ERR! node-pre-gyp ERR! System Linux 5.11.14-arch1-1
npm ERR! node-pre-gyp ERR! command "/usr/bin/node" "/home/alex/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools/node_modules/.bin/node-pre-gyp" "install"
npm ERR! node-pre-gyp ERR! cwd /home/alex/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
npm ERR! node-pre-gyp ERR! node -v v15.14.0
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v0.15.0
npm ERR! node-pre-gyp ERR! not ok

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alex/.cache/yay/mullvad-vpn/src/npm-cache/_logs/2021-04-18T08_56_15_597Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
error making: mullvad-vpn

I get this error when trying to build in a VM, doesn't matter which VM hypervisor I use:

[23:00:54] 'builder-linux' errored after 12 s
[23:00:54] Error: /home/goatroth/git/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/app-builder-bin/linux/x64/app-builder exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
    at ChildProcess.<anonymous> (/home/goatroth/git/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/builder-util/src/util.ts:243:14)
    at Object.onceWrapper (node:events:476:26)
    at ChildProcess.emit (node:events:369:20)
    at ChildProcess.emit (node:domain:532:15)
    at maybeClose (node:internal/child_process:1067:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
    at Process.callbackTrampoline (node:internal/async_hooks:132:14)
[23:00:54] 'pack-linux' errored after 33 s
==> ERROR: A failure occurred in build().
    Aborting...

@Hubro

Have you tried clearing your ~/.npm junk?

Which nodejs-providing package do you have installed?

Do you have the same problem when installing the normal way, without yay?

@beckab: Ah, good point. I'll just drop them.

@yochananmarqos It seems neither networkmanager nor resolvconf are necessary as dependencies. The Mullvad app checks how DNS is set on your system and acts accordingly. If resolvconf/networkmanager/systemd-resolved are not used it manually writes /etc/resolv.conf.

See here: https://github.com/mullvad/mullvadvpn-app#environment-variables-controlling-the-execution

Thank you for your work packaging this!