#10997 Please branch kronosnet for epel8 and epel9
Closed: Invalid by dcavalca. Opened by dcavalca.

  • Describe the issue
    kronosnet is part of the High Availability add-on. In https://bugzilla.redhat.com/show_bug.cgi?id=2121785 the maintainer added the epel-packagers-sig group to allow us to branch it for EPEL per the policy (https://docs.fedoraproject.org/en-US/epel/epel-policy/#_policy), but fedpkg isn't happy:
$ fedpkg request-branch epel8
Could not execute request_branch: This package is already an EL package and is built on all supported arches, therefore, it cannot be in EPEL. If this is a mistake or you have an exception, please contact the Release Engineering team.

I'm hereby requesting and exception so this package can be branched for epel8 and epel9 per the bugzilla. Thanks!

  • When do you need this? (YYYY/MM/DD)
    within a week would be nice

  • When is this no longer needed or useful? (YYYY/MM/DD)
    n/a

  • If we cannot complete your request, what is the impact?
    we can't package kronosnet in EPEL, which blocks corosync, which blocks asterisk


@carlwgeorge pointed out fedpkg is right here, because we do ship libknet1 in RHEL.

Metadata Update from @dcavalca:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

Metadata