Bug 2121785

Summary:	Please branch and build kronosnet in epel8 and epel9
Product:	[Fedora] Fedora EPEL	Reporter:	Davide Cavalca <davide>
Component:	kronosnet	Assignee:	Fabio Massimo Di Nitto <fdinitto>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel9	CC:	fdinitto, mkelly
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-26 18:04:24 UTC	Type:	Bug
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:
Bug Blocks:	1914423, 2121777

Description Davide Cavalca 2022-08-26 15:41:45 UTC

Please branch and build kronosnet in epel8 and epel9.

If you do not wish to maintain kronosnet in epel8 and epel9,
or do not think you will be able to do this in a timely manner,
the EPEL Packagers SIG would be happy to be a co-maintainer of the package;
please add the epel-packagers-sig group through
https://src.fedoraproject.org/rpms/kronosnet/addgroup
and grant it commit access, or collaborator access on epel* branches.

Comment 1 Davide Cavalca 2022-08-26 15:42:03 UTC

Note: this is part of the High Availability add-on in RHEL, so it's eligible for EPEL per the policy.

Comment 2 Fabio Massimo Di Nitto 2022-08-26 16:48:58 UTC

It is also part of Centos 8/9 HA channel, so I am not sure why do we need epel branches? why add overhead when you can just enable the channel?

Comment 3 Davide Cavalca 2022-08-26 17:09:53 UTC

EPEL packages can't depend on HA (as EPEL itself can and does conflict with it and other layered products): https://docs.fedoraproject.org/en-US/epel/epel-policy/#_policy
We need this package in EPEL as it's a BR for corosync (see the depends on BZ), which in turn is a BR for asterisk, which we're trying to get branched in EPEL 8 and EPEL 9.

Comment 4 Fabio Massimo Di Nitto 2022-08-26 18:04:24 UTC

(In reply to Davide Cavalca from comment #3)
> EPEL packages can't depend on HA (as EPEL itself can and does conflict with
> it and other layered products):
> https://docs.fedoraproject.org/en-US/epel/epel-policy/#_policy
> We need this package in EPEL as it's a BR for corosync (see the depends on
> BZ), which in turn is a BR for asterisk, which we're trying to get branched
> in EPEL 8 and EPEL 9.

oh I see, they have changed the policy since last time I poked at EPEL.

Thanks for the pointer et all.

I have now added epel-packagers-sig group to kronosnet with commit access.

Cheers
Fabio

Comment 5 Davide Cavalca 2022-08-26 20:09:11 UTC

To close the loop, this turned out to be more complicated, because RHEL does ship libknet1 and libknet1-devel in CRB, both on RHEL8 and RHEL9, so kronosnet proper can't be branched in EPEL. To resolve this I've requested a standalone kronosnet-epel package in https://pagure.io/releng/fedora-scm-requests/issue/46894 that we will use to provide the missing packages (meaning, everything _except_ the ones already provided by RHEL in CRB).

Comment 6 Fabio Massimo Di Nitto 2022-08-27 04:29:37 UTC

I would probably check why it´s in CRB. AFAIK It should only be in the HA channel. It might be an oversight at compose time.