| Git Clone URL: | https://aur.archlinux.org/mullvad-vpn-cli.git (read-only, click to copy) |
|---|---|
| Package Base: | mullvad-vpn-cli |
| Description: | The Mullvad VPN CLI client |
| Upstream URL: | https://www.mullvad.net |
| Licenses: | GPL-3.0-or-later |
| Conflicts: | mullvad-vpn |
| Provides: | mullvad-vpn |
| Submitter: | t1m0 |
| Maintainer: | yochananmarqos |
| Last Packager: | yochananmarqos |
| Votes: | 17 |
| Popularity: | 1.34 |
| First Submitted: | 2020-02-07 18:37 (UTC) |
| Last Updated: | 2024-04-29 15:34 (UTC) |
@leveller: Apparently the original maintainer had no idea what he was doing and just copied and pasted from the mullvad-vpn PKGBUILD. I assumed it was working and did the same.
I don't use this (I use mullvad-vpn-beta), so let me know if it's working now. Also let me know if you'd like to take over maintaining this.
It appears that the openvpn protocol doesn't work, I get this in my systemd journal when trying to connect using openvpn:
mullvad-daemon[489]: Caused by: No OpenVPN binary found at /opt/mullvad-vpn-cli/openvpn
Is that a feature that's been intentionally left out of this AUR build?
@yochananmarqos, @brokenpip3 is not wrong. Having units disabled after install is the default behavior for packages installed from the repos. It is also my opinion that AUR packages should follow the distro's approach.
https://wiki.archlinux.org/title/Systemd#Enable_installed_units_by_default
I also read your other comments regarding this on the mullvad-vpn-bin package page. It seems to me that a post-install message saying that the systemd unit needs to be enabled to be able to connect to the vpn on boot would satisfy both goals.
@yochananmarqos I'm really sorry if my message looks like a passive-aggressive behavior, my intention was the opposite: I kindly ask you to reconsider the daemon enabling. I'm really thankful of you work which is not easy for this mullvad packages, so again sorry if looks like I was disrespectful. Let me have a proper look and I will get back to you, thanks.
@brokenpip3: I've been maintaining the Mullvad packages for over two years and you're the only one who's ever had an issue with the way they are packaged.
There's more to it than just enabling / starting the service. I'm open to suggestions, make a diff of the install file and I'll take a look. Passive-aggressive threats will get you nowhere.
I just read your reply there, I still think that since you are packaging for archlinux you need to stick with the distro way-of-think.
I don't want to create an alternative package just because you enabled the deaemon by default or -worst- I don't want to create a package request to ask TU user to fix this, could you please reconsider this behavior? You already have a post_install file there, imho just put a warning like every packages does. Thanks!
@brokenpip3: I just answered the same question in the mullvad-vpn-bin comments recently.
why automatically enable the mullvad daemon? the post_install should just warn the user to start (enabled at boot is not mandatory) the daemon while using the vpn services. The archlinux way-of-think does not enable any systemd unit file by default (except some rare core cases)
@ArcherN9 I've adopted it, but I'm slow on keeping up with updates. If anyone else uses this and would be better able to keep up with it, I'll gladly transfer maintainership.
Pinned Comments
yochananmarqos commented on 2021-12-01 23:30 (UTC) (edited on 2021-12-01 23:32 (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.