Package Details: mullvad-vpn 2024.2-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: GPL-3.0-or-later
Submitter: gin078
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 131
Popularity: 4.46
First Submitted: 2018-10-24 17:33 (UTC)
Last Updated: 2024-04-29 15:34 (UTC)

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

yochananmarqos commented on 2019-12-07 17:44 (UTC) (edited on 2020-11-17 03:00 (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.

Latest Comments

« First ‹ Previous 1 .. 29 30 31 32 33 34 35 36 37 38 39 Next › Last »

yochananmarqos commented on 2019-12-02 15:10 (UTC) (edited on 2019-12-02 15:22 (UTC) by yochananmarqos)

I can reproduce the error, I'll work on it.

@coderobe: Oh, I see what you mean. I'll do some research about it.

coderobe commented on 2019-12-02 15:00 (UTC)

@yochananmarqos: the difference is that your sources are not checked into SRCDEST. Please follow our guidelines for this.

Taijian commented on 2019-12-02 12:53 (UTC)

@blackpoll: The mullvad-vpn-bin package works fine and is quick and easy to install.

Taijian commented on 2019-12-02 12:46 (UTC)

Two things:

1) gui testing fails under wayland (..cannot open display...)

2) the 'cannot stat dist/linux-unpacked/' issue also occurs when building in a clean chroot (via clean-chroot-manager). So that needs to be fixed.

@yochananmarqos: Could you try the clean chroot build? Then compare your live system and see what the difference is, presuming that the build works for you in your 'regular' system?

FuelFlo commented on 2019-12-02 11:26 (UTC)

Hey, i have the same problem. None of the 3 changes in PKGBUILD worked for me. I'm still getting:

==> Entering fakeroot environment... ==> Starting package()... install: cannot stat 'dist/linux-unpacked/*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

...using pamac and/or yay.

<deleted-account> commented on 2019-12-02 06:03 (UTC)

@yochananmarqos I get the following errors when trying your recommended fixes:

cp: cannot stat 'dist/linux-unpacked/.': No such file or directory and install: cannot stat 'dist/linux-unpacked/*': No such file or directory

I'm using makepkg -si. Would it perhaps have anything to do with the new rust/cargo dependency?

yochananmarqos commented on 2019-12-02 02:23 (UTC) (edited on 2019-12-02 15:15 (UTC) by yochananmarqos)

@davedatum @ruabmbua @blackpoll: EDIT: I can reproduce it, working on it.

@coderobe: What does git submodule update --init --recursive not accomplish that the VCS package guidelines example does? The submodules are nested and the --recursive flag pulls them all.

coderobe commented on 2019-12-01 22:25 (UTC)

@yochananmarqos: Git submodules in sources require a bit more work. git submodule update --init --recursive is not sufficient. Please take a look at https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git_Submodules

blackpoll commented on 2019-12-01 21:47 (UTC)

==> Starting package()... cp: cannot stat 'dist/linux-unpacked/*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

There are multiple versions now of Mullvad in the AUR. Which one is recommended to properly work and update?

ruabmbua commented on 2019-12-01 19:02 (UTC)

Same problem here:

==> Starting package()... cp: cannot stat 'dist/linux-unpacked/*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...