This bug was fixed in the package vtun - 3.0.4-2ubuntu0.22.04.1
---
vtun (3.0.4-2ubuntu0.22.04.1) jammy; urgency=medium
* Fix failure to run vtun in standalone server mode. (LP: #1881522)
- run autoupdate to update configure.in to use the syntax of
current version of Autoc
This bug was fixed in the package vtun - 3.0.4-2ubuntu0.20.04.1
---
vtun (3.0.4-2ubuntu0.20.04.1) focal; urgency=medium
* Fix failure to run vtun in standalone server mode. (LP: #1881522)
- run autoupdate to update configure.in to use the syntax of
current version of Autoc
The rebuilds succeeded, now we need to wait for the excuses report to be
updated with the new tests that can now run in the architectures that
weren't built before, but are built now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Running autoupdate, or any such tool (like autoreconf and others) in an
SRU is a bit scary. The change it introduces to the configure script
cannot be easily verified, as it's usually a huge diff.
What I would suggest for future SRUs of this type, is to think carefully
about what could go wrong wi
This bug was fixed in the package vtun - 3.0.4-2ubuntu0.23.10.1
---
vtun (3.0.4-2ubuntu0.23.10.1) mantic; urgency=medium
* Fix failure to run vtun in standalone server mode. (LP: #1881522)
- run autoupdate to update configure.in to use the syntax of
current version of Auto
I can confirm that the vtun package in focal-proposed has fixed the bug
for me.
Test done:
1. Install vtun from focal-proposed
2. Execute vtund.
$ vtund
vtund[2554]: Can not open /etc/vtund.conf
VTun ver 3.X 02/18/2024
Usage:
Server:
vtund <-s|-i> [-f file] [-P port] [-L local addres
I can confirm that the vtun package in jammy-proposed has fixed the bug
for me.
Test done:
1. Install vtun from jammy-proposed
2. Execute vtund.
$ vtund
vtund[1567]: Can not open /etc/vtund.conf
VTun ver 3.X 02/18/2024
Usage:
Server:
vtund <-s|-i> [-f file] [-P port] [-L local addres
I can confirm that the vtun package in mantic-proposed has fixed the bug
for me.
Test done:
1. Install vtun from mantic-proposed
2. Execute vtund.
$ vtund
vtund[2312]: Can not open /etc/vtund.conf
VTun ver 3.X 02/18/2024
Usage:
Server:
vtund <-s|-i> [-f file] [-P port] [-L local addr
