On 24/03/2022 02:50, Stella Ashburne wrote:

[...snip...]

The Fedora build you point at uses the standard upstream distro
repository build system.  And a similar infrastructure is also used for
the Fedora Copr builds.  Btw. openvpn-2.5.6 builds are already in all
the Fedora pipes.

From January 1, 2022 to February 28, 2022, whenever I installed
openvpn-2.5.5-1.fc35, openvpn-2.5.5-2.fc35 and openvpn-2.5.5-3.fc35
onto Fedora 35, there were warnings about "globs" not being
supported; nevertheless I continued with the installation of
OpenVPN.

If you had checked the latest "rpm -q --changelog openvpn" you would find:

* Thu Jan 27 2022 David Sommerseth <dav...@openvpn.net> - 2.5.5-3
- Fix systemd related scriptlet error (#1887984)

That number in parentheses points at the Red Hat Bugzilla ticket:
<https://bugzilla.redhat.com/show_bug.cgi?id=1887984>

[...snip...]
The .deb package repositories hosted on
<http://build.openvpn.net/debian/openvpn/> is a different story, as
that's based on infrastructure managed by the OpenVPN project.  This
infrastructure has been through some massive overhaul, and it seems
Samuli hit some dark corners there causing issues with the builds for
this repository.

According to Gert Doering, Samuli's problems with building a .deb
package of OpenVPN were caused by: (sic) I guess that Samuli's build
machine (which is a VM in some AWS VPC) has issues unrelated to
Debian or OpenVPN - but fixing takes time, so won't always be
possible "right the same day". >
Anyway, it would be good if Samuli could elaborate the types of
"esoteric technical problems" that prevented him from building
packages of OpenVPN for Debian distro.

It's related to a massive change of build infrastructure which has been going on for some months already, and some corner cases from the ported build code from the old setup failed. The details here is not really relevant for the OpenVPN user community. Feel free to join our IRC channels and ask about details there, if you feel the need to understand this in detail.

The whole infrastructure has grown a lot since the community got a real kickstart back in 2009-ish, where it really picked up pace and become more of a real open source community. The issues we've stumbled across are related to lots of things which has changed and grown over many years, and sometimes a proper overhaul is needed - and that may break some unexpected things along the way.

The more important detail: This is being worked on and will be resolved.


[...snip...]

The Fedora Copr repos is somewhat similar to Ubuntu PPA.  These
repositories does not have the same strict version upgrade policy, but
also does not carry the same types of stability guarantees.

The project provided apt repository is also a best-effort repository.
There are no guarantees it won't break, but we try to fix things as soon
as possible.  On the other hand, the official OpenVPN 2.x releases from
the project are generally very stable. But it does not go through the
same set of testing which many distributions does before shipping it.


I hope this could clarify a bit of the differences and align some of the
expectations better.

Yes, your clarification helps a lot for folks like us. Could someone
upload such clarification to the OpenVPN's wiki for Debian packages
please?

Sure, I'll put it on my todo list.


--
kind regards,

David Sommerseth
OpenVPN Inc



_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to