Package Details: mullvad-vpn 2020.6-1

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: GPL3
Submitter: gin078
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 36
Popularity: 2.40
First Submitted: 2018-10-24 17:33
Last Updated: 2020-10-20 15:38

Pinned Comments

yochananmarqos commented on 2019-12-07 17:44

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

aurjin commented on 2020-06-25 18:56

Also experiencing the same issue as @wazlecracker

tuse commented on 2020-06-25 18:54

Having the same issue as @wazlecracker. I'm on Manjaro and Rust is at 1.44.0 in the repos, so I guess I just have to wait? (Yes I'm a newbie)

yochananmarqos commented on 2020-06-25 17:09

@wazlecracker: I had that issue with rust 1.44.0, I believe. Make sure you have 1.44.1 installed.

wazlecracker commented on 2020-06-25 16:30

Failing to build both within pamac and cloning then makepkg -si. Get these errors:

test routing::imp::imp::test::test_drop ... FAILED
test routing::imp::imp::test::test_drop_in_executor ... FAILED

failures:

---- routing::imp::imp::test::test_drop stdout ----
thread 'routing::imp::imp::test::test_drop' panicked at 'Failed to initialize route manager: ExclusionsRoutingTableSetup(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })', talpid-core/src/routing/linux.rs:920:13

---- routing::imp::imp::test::test_drop_in_executor stdout ----
thread 'routing::imp::imp::test::test_drop_in_executor' panicked at 'Failed to initialize route manager: ExclusionsRoutingTableSetup(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })', talpid-core/src/routing/linux.rs:908:27
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
routing::imp::imp::test::test_drop
routing::imp::imp::test::test_drop_in_executor

test result: FAILED. 17 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out

error: test failed, to rerun pass '-p talpid-core --lib'

yochananmarqos commented on 2020-06-08 20:07

@atti_simon: I figured something like that would come up. I would open an issue upstream to ask about supporting arm64.

atti_simon commented on 2020-06-08 18:46

@yochananmarqos: Sorry for the late reply, I have now tried the aarch64 test package provided earlier. The build aborts with the following error:

   Compiling mullvad-cli v2020.4.0 (/home/xxxxxx/aur/mullvad-vpn-test/src/mullvadvpn-app/mullvad-cli)
error: could not find native static library `wg`, perhaps an -L flag is missing?

error: aborting due to previous error

error: could not compile `talpid-core`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
    Aborting...

yochananmarqos commented on 2020-06-08 16:33

@bbaserdem: I commented out the NPM test.

bbaserdem commented on 2020-06-08 06:12

@yochananmarqos; the test requires an attached X session. In clean chroot; I would not run makepkg as the logged in user (chroot does not have an active display) hence the gui runtime tests fail. It's not that I don't need the gui; it's that the gui test line cannot be run from within a chroot. (maybe it can with some dummy x session; but I have no idea how/if it can be done)

Regular users can run it; cause i assume running makepkg as your own user pulls in the XAUTHORITY variable.

Also; understandable regression from electron 8; i have another package that is affected.

yochananmarqos commented on 2020-05-25 00:18

@happybike: There is no signature file for this package as it pulls from verified git commits, not binaries. The same signing keys are used.

happybike commented on 2020-05-24 19:26

I'm an Arch noob trying to wrap my mind around securely downloading packages from the AUR. I don't quite understand how to verify the software using the gpg key because when I downloaded this package via git, it didn't download the signature file. The only .asc I see in the package is the code signing key. Thanks for any help you may provide!