Arch Linux User Repository

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

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

@Alphabyte: Yes, I'm aware 2024.6-beta1 is out. Notice I updated mullvad-vpn-beta-bin.

Unfortunately, 2024.6-beta1 cannot be built as the maybenot submodule commit cannot be checked out.

FYI, Oscar Nyberg (raksooo)'s PGP key has been updated. See the pinned message to import his new key.

@Slug: Manjaro and other Arch-based distros are not supported. Using the AUR expects one to be up to date with Arch stable. Please use proper support channels such as the Manjaro support forum.

I have problems installing the package on Manjaro latest stable (Vulkan 23.1.4). Here's the output I get :

Building mullvad-vpn-beta...
==> Making package: mullvad-vpn-beta 2024.3.beta1-1 (ter 07 mai 2024 18:36:27)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating mullvadvpn-app git repo...
  -> Updating mullvadvpn-app-binaries git repo...
  -> Found no-rpm.diff
 -> Found mullvad-vpn.sh
==> Validating source files with sha256sums...
mullvadvpn-app ... NOT FOUND
mullvadvpn-app-binaries ... NOT FOUND
no-rpm.diff ... Passed
mullvad-vpn.sh ... Passed
==> ERROR: One or more files did not pass the validity check!
Failed to build mullvad-vpn-beta

It's possible to bypass the validity check, but I'm not comfortable with that solution, since it should work with it. Does this happen only with Manjaro?

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