Arch Linux User Repository

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

--> ALWAYS DO A CLEAN BUILD <--

This package will verify the signature of the git tag. Developer keys are available here and instructions are here. See the PKGBUILD to determine which developer key you need.

@gmes78: Thank you for the suggestion, however this is more of an upstream issue, not a packaging issue. Ultimately upstream developers need to address things like this as not to burden downstream and end users.

Since the PKGBUILD follows the upstream build.sh, I suggest creating a pull request.

Either way, sccache is your friend.

Here's a patch for building every Rust binary at the same time, improving build times and avoiding unnecessary rebuilds (I had a problem where the mullvad binary was rebuilt for each shell completion generation, this fixes that.)

diff --git a/PKGBUILD b/PKGBUILD
index 1d9bc1d..a1e4e09 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -86,6 +86,7 @@ build() {
   echo "Building Rust code in release mode using ${RUSTC_VERSION}..."

   cargo_crates_to_build=(
+    -p mullvad-api --bin relay_list
     -p mullvad-daemon --bin mullvad-daemon
     -p mullvad-cli --bin mullvad
     -p mullvad-setup --bin mullvad-setup
@@ -99,12 +100,12 @@ build() {
   mkdir -p build/shell-completions
   for sh in bash zsh fish; do
     echo "Generating shell completion script for ${sh}..."
-    cargo run --bin mullvad --frozen --release -- shell-completions ${sh} \
-      build/shell-completions/
+    target/release/mullvad shell-completions ${sh} build/shell-completions/
   done

   echo "Updating relays.json..."
-  cargo run --bin relay_list --frozen --release > dist-assets/relays.json
+  target/release/relay_list > dist-assets/relays.json
+  cp dist-assets/relays.json build/relays.json

   # Move binaries to correct locations in dist-assets
   binaries=(

(The cp command at the end fixes the file source doesn't exist from=<build path>/mullvad-vpn-beta/src/mullvadvpn-app/build/relays.json warning during npm build pack:linux, though I'm not sure if it's necessary.)

@bluetail: Please don't flag a package out of date that's already up to date. Good grief.

@ptr1337: If you're using rustup, your toolchain is out of date.

Does not compile inside of chroot:

error[E0635]: unknown feature `proc_macro_span_shrink`
  --> /tmp/pkg/src/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/proc-macro2-1.0.56/src/lib.rs:92:30
   |
92 |     feature(proc_macro_span, proc_macro_span_shrink)
   |                              ^^^^^^^^^^^^^^^^^^^^^^

   Compiling tinyvec_macros v0.1.0
   Compiling base16ct v0.1.1
   Compiling opaque-debug v0.3.0
   Compiling want v0.3.0
   Compiling httpdate v1.0.1
   Compiling untrusted v0.7.1
   Compiling tinyvec v1.5.1
   Compiling paste v1.0.12
For more information about this error, try `rustc --explain E0635`.
error: could not compile `proc-macro2` (lib) due to previous error
warning: build failed, waiting for other jobs to finish...

Edit: This was resolved - I think I had to update my Arch Linux system.

When I ran $ makepkg -sirc, I received some sort of connection error below (both with and without Mullvad VPN activated) and I do not use a proxy. (I have been able to build this package before behind Mullvad VPN in the past and I have updated my system.)

I also have the complete log.

~/AUR/mullvad-vpn-beta/src/mullvadvpn-app
~/AUR/mullvad-vpn-beta/src/mullvadvpn-app/gui ~/AUR/mullvad-vpn-beta/src/mullvadvpn-app
Installing JavaScript dependencies...
npm ERR! code ECONNREFUSED
npm ERR! syscall connect
npm ERR! errno ECONNREFUSED
npm ERR! FetchError: request to https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz failed, reason: connect ECONNREFUSED 2606:4700::6810:1b23:443
npm ERR!     at ClientRequest.<anonymous> (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
npm ERR!     at ClientRequest.emit (node:events:513:28)
npm ERR!     at TLSSocket.socketErrorListener (node:_http_client:488:9)
npm ERR!     at TLSSocket.emit (node:events:525:35)
npm ERR!     at emitErrorNT (node:internal/streams/destroy:151:8)
npm ERR!     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
npm ERR!     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
npm ERR!  FetchError: request to https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz failed, reason: connect ECONNREFUSED 2606:4700::6810:1b23:443
npm ERR!     at ClientRequest.<anonymous> (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
npm ERR!     at ClientRequest.emit (node:events:513:28)
npm ERR!     at TLSSocket.socketErrorListener (node:_http_client:488:9)
npm ERR!     at TLSSocket.emit (node:events:525:35)
npm ERR!     at emitErrorNT (node:internal/streams/destroy:151:8)
npm ERR!     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
npm ERR!     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
npm ERR!   code: 'ECONNREFUSED',
npm ERR!   errno: 'ECONNREFUSED',
npm ERR!   syscall: 'connect',
npm ERR!   address: '2606:4700::6810:1b23',
npm ERR!   port: 443,
npm ERR!   type: 'system'
npm ERR! }
npm ERR! 
npm ERR! If you are behind a proxy, please make sure that the
npm ERR! 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/uSER/AUR/mullvad-vpn-beta/src/npm_cache/_logs/2022-10-23T11_15_29_303Z-debug-0.log
==> ERROR: A failure occurred in prepare().
    Aborting...

@Technetium1: Instead of whining and complaining about what you don't like, please propose the change you want made. This has been discussed here before.

I don't feel like I should have to mask a service I don't use. Please check to see if the service was already enabled in the first place.

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