@atti_simon: Try this test package and let me know if that does the trick.
Search Criteria
Package Details: mullvad-vpn 2024.8-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: | 139 |
| Popularity: | 3.50 |
| First Submitted: | 2018-10-24 17:33 (UTC) |
| Last Updated: | 2024-12-13 02:39 (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-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
- git (git-gitAUR, git-glAUR) (make)
- go (go-gitAUR, gcc-go-gitAUR, gcc-go-snapshotAUR, 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.8?signed
- git+https://github.com/mullvad/wireguard-go.git#commit=b1cf09a982bba6f6c63fadc956d88e8c2326d05e?signed
- mullvad-vpn.sh
- no-publish.diff
- no-rpm.diff
yochananmarqos commented on 2020-05-20 21:28 (UTC)
atti_simon commented on 2020-05-20 09:39 (UTC) (edited on 2020-05-20 10:02 (UTC) by atti_simon)
Hello! Just for info, for anyone interested, I've managed to build and install on Raspberry Pi 4, running Manjaro RPI4. I have edited the PKGBUILD and changed the architecture to 'aarch64'. The build fails to package the .deb file, when running: 'npm run pack:linux'
However, I have executed all the other commands from the PKGBUILD manually, including the tests and install commands and everything's okay, the app works well. I've had to update some paths, 'dist/linux-unpacked' becomes 'dist/linux-arm64-unpacked'. I have used the official .deb file from the mullvad website to grab the .desktop file and the icons.
I know this is not an ideal way to build and install this app, but I am happy to be able to use mullvad-vpn on ARM64.
Cheers!
yochananmarqos commented on 2020-05-18 00:41 (UTC)
@bbaserdem: I'm not following why npm-test is failing for you. If you don't need the GUI, there is a CLI-only version in the AUR: mullvad-vpn-cli.
As far as Electron applications, each one is build against a specific Electron version. It doesn't always work out forcing a newer version. At this point tray icons are broken on Electron 8 so Mullvad downgraded to 7 for now. Once the issue is fixed upstream, we'll see.
silverbluep commented on 2020-05-17 17:35 (UTC) (edited on 2020-05-17 17:42 (UTC) by silverbluep)
The gui test fails for me (since I don't have a display available; I'm building in a clean chroot)
Also why is the installer downloading it's own electron version? Shouldn't the package should pull in electron dependency instead. I dont know much about rust to determine if this is a questionable build decision or not.
Eveready commented on 2020-05-14 22:14 (UTC)
@yochananmarqos Thanks a lot!
yochananmarqos commented on 2020-05-14 22:06 (UTC) (edited on 2020-05-14 22:07 (UTC) by yochananmarqos)
@Eveready: Yes, you can remove the build directory after a successful build. To automatically remove it next time, use the -c flag with makepkg; i.e., makepkg -Csrci.
Eveready commented on 2020-05-14 22:00 (UTC)
I'm a bit new at this, so sorry if this is a dumb question... I noticed that the package, once built, is pretty small, whereas the build folder becomes ~3 gigabytes. Is it ok to erase the build directory once the package is built?
XuLin commented on 2020-05-14 02:46 (UTC)
@yochananmarqos: yes, of course. I'll try installing it again to see what happens but thought I'd share what happened.
yochananmarqos commented on 2020-05-14 02:18 (UTC)
@XuLin: Did you perform a clean build as directed in the pinned comment?
XuLin commented on 2020-05-14 01:05 (UTC)
While building the latest version it went fine but never built the binary itself to run the vpn!
/usr/bin/mullvad-vpn: line 2: /opt/Mullvad VPN/mullvad-vpn: No such file or directory
Can't run the app anymore after that.
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.