Bug 29997 - openvpn3 : NEW PKG REQUEST
Summary: openvpn3 : NEW PKG REQUEST
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://github.com/OpenVPN/openvpn3
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-04 16:09 CET by Nikolay Sabelnikov
Modified: 2022-02-10 19:41 CET (History)
3 users (show)

See Also:
Source RPM: OpenVPN3
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nikolay Sabelnikov 2022-02-04 16:09:57 CET 
openvpn has not only 2 versions, but also 3, and you only have 2.
Nikolay Sabelnikov 2022-02-04 16:10:02 CET

CC: (none) => 79625490833

Nikolay Sabelnikov 2022-02-04 16:11:05 CET

Source RPM: OpneVPN3 => OpenVPN3

Comment 1 Lewis Smith 2022-02-09 10:56:21 CET 
It looks to me as if OpenVPN:
 http://openvpn.net/
is not the same thing as what you ask for [URL]. OpenVPN is at  2.5.5 15 Dec 2021.
Hence your request for a new package doing presumably the same thing; and about which I can find no information from your given link (other than that the author is a hacker currently working on @Openvpn).
Can you justify why you would like to see Openvpn3 as well as the existing package?

CC: (none) => lewyssmith
Summary: [NEW PKG BUILDER]:openvpn3 => openvpn3 : NEW PKG REQUEST
Severity: normal => enhancement

Comment 2 Nikolay Sabelnikov 2022-02-09 13:10:06 CET 
As I understand from the description, openvpn 3 is needed purely for developers. Therefore, the package can be launched as a devel version.
Nikolay Sabelnikov 2022-02-09 13:10:22 CET

URL: https://github.com/OpenVPN/openvpn3/releases/tag/release%2F3.6.5 => https://github.com/OpenVPN/openvpn3

Comment 3 Morgan Leijström 2022-02-09 13:53:02 CET 
Being only for developers, I think they better download and use the most recent version themselves.

CC: (none) => fri

Comment 4 Lewis Smith 2022-02-10 19:41:39 CET 
I agree with Morgan. Closing this bug.

Resolution: (none) => INVALID
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.