$ 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 don't believe this to be true. It's possible that it might be in some modular content but I don't see any evidence of it.
When do you need this? (YYYY/MM/DD) Soon
When is this no longer needed or useful? (YYYY/MM/DD) EL8 EOL
If we cannot complete your request, what is the impact? No cobbler package for EPEL 8
I do not find cobbler in any of the repositories that EPEL uses to build against. I do see that a branch for it exists on src.centos.org at https://git.centos.org/rpms/cobbler/blob/c8-stream-1.0/f/SPECS/cobbler.spec from 3 years ago but nothing after that.
Metadata Update from @phsmoura: - Issue tagged with: medium-gain, medium-trouble, ops
According to the json that fedpkg is using it is part of rhel-8-for-x86_64-appstream-rpms, rhel-8-for-ppc64le-appstream-rpms, rhel-8-for-s390x-appstream-rpms
But in some ancient unsupported version, I am not sure what to do here.
Since this is a weird one-off case, perhaps we could just process it manually?
It's hard to parse from the JSON used for the EPEL 8 check, but this is getting denied because of the koan and python3-koan packages. These are built from the cobbler spec file and are part of the rhn-tools:1.0 module stream, which is a default stream. This means we can't have a cobbler component in EPEL 8 because the SRPM would conflict.
This will have to be done as a cobbler-epel component/spec file/SRPM, with a cobbler subpackage. I'm actually not 100% sure that will work either, I don't know if koji will choke on the name conflict between the RHEL SRPM and the EPEL RPM. If it does then the binary package would have to be named cobbler-epel as well.
I will proceed with a cobbler-epel package then. Thanks for the investigation.
Metadata Update from @orion: - Issue close_status updated to: It's all good - Issue status updated to: Closed (was: Open)