In T492#7748, @JoshStrobl wrote:

Don't change the default statuses of Tasks or change the assignee.

ok :-)

From AirVPN forums:

This is a hilarious statement. I'm not sure I would like to use a distribution from such a developer, though. Who knows when something
else is going to be broken or will require patching. Many drivers and other sources are on git and it's seems like not enough for him to get things done.

They only have to create a git tag and we can take it from there. This is such a fundamental part of software development and release practices.
You create an immutable point in history, and we package that specific, tested, version. We can ship git versions of packages, and in quite
a few places we do, but this demonstrated disdain for versioning and proper releases makes it, at present, very unattractive.

Once they throw a git tag up on GitHub (all of 2 commands in a terminal) we can reassess this.

Any chance of looking onto this again?

Yep, can go in now

Ugh I might redact that statement?

Build system tells you it failed, and then it succeeds. Documentation for paths is wrong, build system generates a tarball,
which is pretty useless. Extract the tarball, we find a handful of useful files (We won't be using a bundled openvpn binary,
that's a security hole waiting to happen)

 ✓  ikey@solus-bdw  …/airvpn-client/2   master ?  tar xf ../repository/files/eddie-cli_2.11.15_linux_x64_mono.tar.gz 
 ✓  ikey@solus-bdw  …/airvpn-client/2   master ?  ls
eddie-cli_2.11.15_linux_x64_mono
 ✓  ikey@solus-bdw  …/airvpn-client/2   master ?  tree
.
└── eddie-cli_2.11.15_linux_x64_mono
    ├── Eddie-CLI.exe
    ├── Lib.Common.dll
    ├── Lib.Core.dll
    ├── openvpn
    ├── Platforms.Linux.dll
    ├── stunnel
    └── update-resolv-conf

1 directory, 7 files

So yes, it's "doable". Fact of the matter is, the update-resolv.conf script falls into the evil category. As does bundling openvpn, but I can
understand that from a cross platform perspective. Now, given that "Eddie" is a cross-platform OpenVPN wrapper (in essence) - is there any
reason you can't just use Network Manager OpenVPN directly for this? As this will ensure that you use our openvpn binary, and that NM is
able to properly set up gateways and manage /etc/resolv.conf itself (as it currently does)

They have released a new version: https://github.com/AirVPN/airvpn-client/archive/v2.12.4.tar.gz
What do you think? @ikey

No update yet to when the client will be available for Solus?

is there any reason you can't just use Network Manager OpenVPN directly for this? As this will ensure that you use our openvpn binary, and that NM is
able to properly set up gateways and manage /etc/resolv.conf itself (as it currently does)

Just came across this package request since I wanted to install eddie also.

A couple of reasons for not using Network Manager. The first is that it is much easier to switch between many servers rather than importing one by one in NM. The other is that the GUI has a network lock feature, which prevents any non-VPN traffic therefore minimising risk of leaking address. As far as I'm aware, this feature is not implemented in NM. Not a technical person on how vpns work, so personally would like to use the GUI that has the network lock feature than trying to figure out the command line equivalent.

New version is out: https://github.com/AirVPN/Eddie/archive/v2.13.6.tar.gz