Your drollery circuits seem to be in better fettle than mine this week. I had a screaming melt-down at the "Windows Security Center technician" that informed me of a problem and that I would be report him to the FBI. I think I need more fiber. On Sat, Sep 12, 2015 at 4:30 AM, Jason Ryan <jasonwryan@gmail.com> wrote:

On 12/09/15 at 10:25am, Florent M wrote:

...

Please update openvpn package to 2.3.8 asap.

Our best people are leaping into action.

Remain at your desk, we'll contact you when the procedure is complete.

/J

--

http://jasonwryan.com/ GPG: 7817 E3FF 578E EEE1 9F64 D40C 445E 52EA B1BD 4E40

-- Fred Schiff (eldersprig@gmail.com)

Hi, Thanks Thomas to your explanations, I don't know enough openvpn to view this problem. Also thanks to Seblo to provide openvpn 2.3.8 in testing (maybe you can use systemd unit file provided by openvpn ?) Thanks everyone. 2015-09-15 18:57 GMT+02:00 Thomas Bächler <thomas@archlinux.org>:

Am 12.09.2015 um 10:25 schrieb Florent M:

...

Hi everyone,

There are some reasons that openvpn in core is 2.3.6 ?

Please update openvpn package to 2.3.8 asap.

Just update PKGBUILD to 2.3.8, it works

It does NOT work.

It fails to launch when using a passphrase-protected private key. The whole code path that is supposed to call systemd-ask-password is borked. There will be no update until this is fixed - unfortunately, I did not get to posting to their mailing list yet.

, and remove openvpn@.service

...

because systemd service files are now provided by OpenVPN.

This is already done in my local working copy, probably did not check it into trunk yet.