Add upstream v3.0.4 of net-vpn/vtun #28466
Conversation
Pull Request assignmentSubmitter: @leakingmemory net-vpn/vtun: @gentoo/proxy-maint (maintainer needed) Linked bugsNo bugs to link found. If your pull request references any of the Gentoo bug reports, please add appropriate GLEP 66 tags to the commit message and request reassignment. Missing Bugzilla accountsWARNING: The following maintainers do not match any Bugzilla accounts: Please either fix the e-mail addresses in metadata.xml or create a Bugzilla account, and request reassignment afterwards. Missing GCO sign-offPlease read the terms of Gentoo Certificate of Origin and acknowledge them by adding a sign-off to all your commits. In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
gentoo-bot
added
maintainer-needed
Pull request CI reportReport generated at: 2022-11-28 20:13 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
…ch is probably at least partly because approx 5 years have gone by with no new upstream releases. Signed-off-by: Jan-Espen Oversand <sigsegv@radiotube.org>
Signed-off-by: Jan-Espen Oversand <sigsegv@radiotube.org>
Signed-off-by: Jan-Espen Oversand <sigsegv@radiotube.org>
leakingmemory
force-pushed
the
net-vpn/vtun-3.0.4
branch
from
22ebb93
to
855c6e5
Compare
Pull request CI reportReport generated at: 2022-11-28 21:08 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
|
Looks like the ebuild was successfully merged after changes. Thanks a lot. I guess the pull request can be closed. |
Added ebuild for upstream release v3.0.4 (2016). It is unfortunately a bit tricky to build and needs patching for libssl datastructures of unknown size that needs to be allocated dynamically. Also the upstream source assumes autoconf+configure will provide HAVE_WORKING_FORK, which it doesn't, so that has to be patched out.
I also believe that the upstream source has bugs with the -n argument (don't fork) and that it fails to set up the tunnel correctly with the -n argument. I'd love to debug that later on, but as it works with the normal forking behaviour I'd argue that it is not a blocker to at least consider including the new upstream version. (terminates with I/O error with -n)
Unfortunately there have been several years of silence upstream, although I think this is one of the best point to point tunneling solutions out there. And it would be a great loss if it goes away.
Regards.
Jan-Espen Oversand