Hi guys, the client for Mullvad’s VPN service (mullvad-vpn and mullvad-vpn-daemon) available in the official repositories (extra) has been out of date for a while. The available version is 2025.14-5 whereas the current version is 2026.1-1, which has been available upstream in the Arch repositories (extra) since March 18th 2026 (see here: Arch Linux - Package Search)
Maybe something wrong with connecting upstream sources?
Hi @deesnook,
If you check the branch compare website:
You’ll notice that it’s only the Stable branch that’s behind with the version, for which I don’t have a reason as to why. Perhaps there is some problem it brings with it. I don’t know.
But you’re welcome to switch branches if you need the latest one:
Hope this helps!
It is up-to-date in testing and unstable branches:
If you need the new version, and can’t wait until it appears in stable (and it looks like stable will not update soon), you can always switch branches:
Thanks for pointing this out. There’s no rush, I just wanted to make sure a possible error won’t go unnoticed. I’ll wait for the next stable release then
In a case like this, with a package that comes directly from Arch and doesn’t have any special dependencies, it is possible to just install directly from Manjaro unstable/testing repo or even directly from Arch without changing branches:
sudo pacman -U https://archive.archlinux.org/packages/m/mullvad-vpn/mullvad-vpn-2026.1-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/m/mullvad-vpn-daemon/mullvad-vpn-daemon-2026.1-1-x86_64.pkg.tar.zst
You will have a newer version of the package than the repo and the package manager will inform you so when updating, but other than that, probably it will work fine.
In the worst case, you’ll have to reinstall the repo version and everything would be like before again.
No, please don’t install from the Arch repos. If you decide you can install a single package use the Manjaro unstable branch (even if in the vast majority of cases the packages are the same – but not in all cases)
sudo pacman -U https://ftp.gwdg.de/pub/linux/manjaro/unstable/extra/x86_64/mullvad-vpn-2026.1-1-x86_64.pkg.tar.zst
I think the command handles dependencies.
I hope nobody understood my comment as I was generalizing for whatever package is not fully up to date (compared to unstable or to Arch). I was referring to this particular case and these particular packages.
It’s true that I am of that opinion that Manjaro could fasttrack more application packages, but by no means I am suggesting that my solution it’s a general solution.
As said, it’s not my intention to generalize for other cases, but in this case it’s exactly the same file regardless of the source. I just used the Arch repo where packages archived (Arch’s old packages repo), because I have it already bookmarked and it’s easy to find a package there.
Yes, but it would try to install the dependencies from the normal repo. In this case, the new version of mullvad-vpn-daemon is also needed, so it should be:
sudo pacman -U https://ftp.gwdg.de/pub/linux/manjaro/unstable/extra/x86_64/mullvad-vpn-2026.1-1-x86_64.pkg.tar.zst https://ftp.gwdg.de/pub/linux/manjaro/unstable/extra/x86_64/mullvad-vpn-daemon-2026.1-1-x86_64.pkg.tar.zst
(two packages at the same time)
I’m curently running Mullvad-vpn 2026.2, on all my machines, both testing and stable, installed from the AUR, using mullvad-vpn-bin
But I see the package is updated in testing to 2026.2.1
@Yochanan Are you still maintaining the aur version. According to Octopi, the packager is unknown?
That’s because you haven’t set PACKAGER= in your makepkg.conf
No it’s because that’s what its says in that field in pamac too. This is not about building anything, this si simply about reading the information presented, before doing anything else.
[tracy@daphne ~]$ pacman -Qi mullvad-vpn
Name : mullvad-vpn-bin
Version : 2026.2-1
Description : The Mullvad VPN client app for desktop (desktop
application)
Architecture : x86_64
URL : https://www.mullvad.net
Licenses : GPL-3.0-or-later
Groups : None
Provides : mullvad-vpn
Depends On : alsa-lib gtk3 iputils libnftnl libnotify
nss mullvad-vpn-daemon-bin
Optional Deps : libappindicator: tray icon
Required By : None
Optional For : None
Conflicts With : mullvad-vpn
Replaces : None
Installed Size : 318.99 MiB
Packager : Unknown Packager
Build Date : Wed 29 Apr 2026 09:10:57
Install Date : Wed 29 Apr 2026 10:18:32
Install Reason : Explicitly installed
Install Script : Yes
Validated By : None
Packager : Unknown Packager
PACKAGER= field is embedded is the packages you build, in the .SRCINFO file inside the builded package
That’s because there is no packager for mullvad-vpn-bin. It is in the AUR, so it isn’t a package, but rather a PKGBUILD. PKGBUILDs have maintainers, not packagers (as the user builds the actual package on their system).
You’re the package builder for mullvad-vpn-bin (and any other AUR packages you have on your system). You used the PKGBUILDs in the AUR to build and install the packages on your system.
Already built packages in the repos have packagers, because they are the people who built the actual package that gets installed on your system.
A repo package with a packager:
pamac info mullvad-vpn
Name : mullvad-vpn
Version : 2026.1-1
Description : Mullvad VPN client (desktop application)
URL : https://www.mullvad.net
Licenses : GPL-3.0-or-later
Repository : extra
Installed Size : 39.5 MB
Groups : --
Depends On : electron39 hicolor-icon-theme mullvad-vpn-daemon
Optional Dependencies : libappindicator-gtk3: tray icon [Installed]
Provides : --
Replaces : --
Conflicts With : --
Packager : Carl Smedstad <carsme@archlinux.org>
Build Date : Mon 16 Mar 2026 04:48:16
Validated By : MD5 Sum SHA-256 Sum Signature
An installed AUR package on my system with a PKGBUILD maintainer, and an unknown packager (that is - me):
pamac info qimgv-git
Name : qimgv-git
Version : 1.0.2.r190.g3127a2d-1
Description : Qt6 image viewer with video playback
URL : https://github.com/easymodo/qimgv
Licenses : GPL-3.0-or-later
Repository : AUR
Installed Size : 2.3 MB
Groups : --
Depends On : exiv2 mpv opencv qt6-base qt6-imageformats qt6-multimedia qt6-svg
Optional Dependencies : --
Make Dependencies : cmake git ninja qt6-tools
Check Dependencies : --
Required By : --
Optional For : --
Provides : qimgv
Replaces : --
Conflicts With : qimgv
Packager : Unknown Packager
Maintainer : xiota
First Submitted : Sat 24 Oct 2015 01:41:43
Last Modified : Thu 17 Jul 2025 11:04:01
Votes : 30
Out of Date : --
Build Date : Wed 15 Apr 2026 09:10:08
Install Date : Wed 15 Apr 2026 09:30:33
Install Reason : Explicitly installed
Validated By : None
Backup files : --
Having AUR packages display “Unknown Packager” when pacman -Qi is used actually makes it very easy to identify that a package is not an official repo package.
… and the actual answer. Thanks.
I should also add that the AUR’s various mullvad-vpn options maintained by @Yochanan are very much up-to-date, with the 6 PKGBUILDs all updated on 2026-04-28:
| Name | Version | Votes | Popularity? | Description | Maintainer | Last Updated |
|---|---|---|---|---|---|---|
| mullvad-vpn-beta | 2026.2.stable-1 | 12 | 0.00 | The Mullvad VPN client app for desktop (beta channel) (desktop application) | yochananmarqos | 2026-04-28 18:37 (UTC) |
| mullvad-vpn-daemon-beta | 2026.2.stable-1 | 12 | 0.00 | The Mullvad VPN client app for desktop (beta channel) (daemon and CLI) | yochananmarqos | 2026-04-28 18:37 (UTC) |
| mullvad-vpn-bin | 2026.2-1 | 160 | 4.15 | The Mullvad VPN client app for desktop (desktop application) | yochananmarqos | 2026-04-28 18:28 (UTC) |
| mullvad-vpn-daemon-bin | 2026.2-1 | 160 | 4.15 | The Mullvad VPN client app for desktop (daemon and CLI) | yochananmarqos | 2026-04-28 18:28 (UTC) |
| mullvad-vpn-beta-bin | 2026.2.stable-1 | 14 | 0.00 | The Mullvad VPN client app for desktop (beta channel) (desktop application) | yochananmarqos | 2026-04-28 18:26 (UTC) |
| mullvad-vpn-daemon-beta-bin | 2026.2.stable-1 | 14 | 0.00 | The Mullvad VPN client app for desktop (beta channel) (daemon and CLI) | yochananmarqos | 2026-04-28 18:26 (UTC) |
This is correct
This is wrong
That is because you haven’t configured PACKAGER= in your makepkg.conf, makepkg read that and put it in the .SRCINFO inside the package
You can check prebuild packages I put out there FabioLolix-OS-Archive - Browse /Packages at SourceForge.net
Which have, for qt5-webengine, an AUR pkgbuild
builddate = 1774542563
packager = Fabio 'Lolix' Loli <fabio.loli@disroot.org>
size = 166967394
and my makepkg.conf have
#-- Packager: name/email of the person or organization building packages
#PACKAGER="John Doe <john@doe.com>"
PACKAGER="Fabio 'Lolix' Loli <fabio.loli@disroot.org>"
#-- Specify a key to use for package signing
Why in the world would I want to claim I packaged it? That might be your ego trip, but it’s not mine.
I suppose it would let me know to contact myself, when I install a package from the AUR,
Well that’s great for you. But @Scotty’s answer to my original question is the relevant one.
The part where he is wrong?
FabioLolix-OS-Archive - Browse /Packages at SourceForge.net packages like qt5-webkit, qt5-webengine, webkit2gtk take several hours to build on old computers
So, what does that have to do with me? I mean I don’t care how long it takes for your stuff to build, on any computer. I’m not even interested in it.
So yeah @Scotty’s answer is the relevant answer, everything you’ve posted has no relevance, and this has gotten completely off topic.