Great!!
But they still not support Wireguard :(
Git Clone URL: | https://aur.archlinux.org/vpn-unlimited-bin.git (read-only, click to copy) |
---|---|
Package Base: | vpn-unlimited-bin |
Description: | VPN Unlimited client application |
Upstream URL: | https://www.vpnunlimitedapp.com |
Licenses: | custom |
Conflicts: | vpn-unlimited |
Provides: | vpn-unlimited |
Submitter: | carsme |
Maintainer: | ItachiSan |
Last Packager: | carsme |
Votes: | 17 |
Popularity: | 0.000024 |
First Submitted: | 2023-08-10 08:56 (UTC) |
Last Updated: | 2024-01-28 23:19 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »
Great!!
But they still not support Wireguard :(
The site will be updated after the official release.
Well, thank you, then, @eduard. If you have any sort of connection with the vpn-unlimited
team, then, would you please tell them to update their website (regarding Linux) when the time comes?
I cannot say according to my NDA agreement. It will be officially released next week.
@eduard, that's interesting. How did you get the link to that binary file? I cannot see anything other than 4.23 at https://www.vpnunlimitedapp.com/downloads/linux.
Early access for Arch Linux users ;) http://apt.keepsolid.com/deb/dists/stable/main/binary-amd64/vpn_unlimited_v7.0_amd64.deb
Done. qt5-webengine
is added (with the same lower bound on version as that of qt5-webkit
) as a dependency.
qt5-webengine is dependency not listed, please add it.
@aytekinar Without qt5-webengine
, the app fails to run:
/usr/share/vpn-unlimited/vpn-unlimited: error while loading shared libraries: libQt5WebEngineWidgets.so.5: cannot open shared object file: No such file or directory
Pinned Comments
carsme commented on 2023-12-28 16:59 (UTC)
NOTE: Issues regarding
icu
library files not being found, such asare not strictly related to this package, but to
boost174
. Each time theicu
package in the official repositories is updated to a new major version,boost174
needs to be rebuilt.You don't need to install any version of
icu
other than the package available in the official repositories. To resolve the issue, either rebuildboost174
yourself or, even better, leave a comment inboost174
so I can publish a new pkgver and as such force a rebuild for all users.