Bug 2032208

Summary: Branch and build openvpn in epel9
Product: [Fedora] Fedora EPEL Reporter: Neal Gompa <ngompa13>
Component: openvpnAssignee: David Sommerseth <dazo>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: carl, davide, daxelrod, dazo, farrotin, huzaifas, klember, matt, michel, redhat-bugzilla, shantanu.gadgil, smooge, steve
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openvpn-2.5.5-4.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-05 01:36:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2032213    
Bug Blocks: 1914423, 2037878    

Description Neal Gompa 2021-12-14 08:02:30 UTC
Please branch and build openvpn in epel9.

Comment 1 Robert Scheck 2022-01-15 12:40:52 UTC
pkcs11-helper-1.27.0-6.el9 has been pushed to the stable repository already...so what's the status of OpenVPN for EPEL 9?

Comment 2 Neal Gompa 2022-01-26 12:12:40 UTC
Will you be able to branch and build openvpn in epel9?
The EPEL Packaging SIG would be happy to be a co-maintainer
if you do not wish to build it on epel9.

Comment 3 David Sommerseth 2022-01-26 16:55:02 UTC
Sorry I haven't responded earlier.  It's been a bit busy on my end, and we're resolving issues related the next bit OpenVPN 2.6 release.

I'm a bit at loss when it comes to the EPEL forking steps, but I'd like that to happen yes.  I have no issues maintaining the package once the branch is available.  It would be great with some pointers how to get the forking process rolling, though.

Comment 4 Shantanu Gadgil 2022-01-26 19:43:01 UTC
Eagerly awaiting on this too. This would also be the tracking ticket for the NetworkManager-gnome bits as well?

Comment 5 Stephen John Smoogen 2022-01-26 21:26:33 UTC
@dazo it should be done via

```
fedpkg request-branch --repo openvpn epel9

```

I can also be added to the branch list if that helps you any.

Comment 6 David Sommerseth 2022-01-27 17:07:56 UTC
Thanks a lot!  This has become far easier than my very vague memories of this when epel-6(!) arrived.

Ticket for epel9 has been issued: https://pagure.io/releng/fedora-scm-requests/issue/41410

Comment 7 David Sommerseth 2022-01-27 17:09:41 UTC
(In reply to Shantanu Gadgil from comment #4)
> Eagerly awaiting on this too. This would also be the tracking ticket for the
> NetworkManager-gnome bits as well?

No, this ticket should only handle the main openvpn package.  The NetworkManager-openvpn package is handled by other persons and teams.

Comment 8 Fedora Update System 2022-01-27 21:43:49 UTC
FEDORA-EPEL-2022-01da713f00 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-01da713f00

Comment 9 Fedora Update System 2022-01-28 01:02:11 UTC
FEDORA-EPEL-2022-01da713f00 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-01da713f00

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2022-02-05 01:36:03 UTC
FEDORA-EPEL-2022-01da713f00 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.