Marc Leeman

I think, instead of bumping the gsoap version, it would be better to use the system libraries instead of a wget and compile.

@Sheridan I did the same thing while packaging it for Debian :-/ I'll have a look if I can sync your work with mine to have something similar.

Very nice; a modern build system, a JSON config file, ... I added the debian package files, am now trying to get wsse working to get that windows discovery tool...

FWIW, I am packaging this software for buster; as part of the change, I have replaced the statically linked gsoap with the system libraries. You can find the packaging stuff...

Dang, busted :-P I've added some comments in the ticket, the highlights are: 1. The debian builders do not like git submodules (no network access). In order to avoid having...

To me, it does not really matter; packaging follows (as much as possible) upstream. I have mirrored the packaging structure on the git repo; so if you tag your release...

FYI, there is some low hanging fruit (spelling errors) that got picked up by the debian tooling https://mentors.debian.net/package/openvpn3-linux/ https://mentors.debian.net/package/openvpn3/ ``` authentification authentication [usr/bin/ovpncli] authentification authentication [usr/lib/x86_64-linux-gnu/_ovpncli.so] laoding loading [usr/bin/ovpncli] laoding...

fine with me, I will adjust the client to use your published snapshots. Is there a page where the index can be queried of the releases, any other URL but...

- Starting from your snapshot and by removing all the patches (that I had previously added) gives a clean compilation, so your release tarball is an excellent starting point. If...

Debian packaging (in general) does tend to use smaller sub packages. What I would propose is to: 1. start by packaging `openvpn3-linux` into a package `openvpn3-client`. It describes clearly what...