An epel8 branch for rpms/asio cannot be created through fedpkg request-branch due to it throwing "This package is already an EL package and is built on all supported arches, therefore, it cannot be in EPEL." However, the reason it's throwing this is because it has a package listed in the mariadb module, but that package is filtered from distribution.
fedpkg request-branch
When do you need this? (YYYY/MM/DD) 2020/03/24
When is this no longer needed or useful? (YYYY/MM/DD) 2029/05/31
If we cannot complete your request, what is the impact? We'd be unable to push releases to epel8.
I will work on it asap. This needs some fixes on fedscm-admin which processes the tickets as well.
So, I am not sure why this is wanted... can you explain?
The aiso package only makes a 'aiso-devel' package, which is in code ready builder module, which you can build against in koji right now.
Or did you want to somehow distribute it via epel to some place that doesn't have code ready builder?
Huh, apparently it does exist in PowerTools/CRB, we probably don't need this then...
Closing it as its not needed.
Please reopen if thats not the case.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@mohanboddu @raineforest It looks like Red Hat dropped it from CRB/PowerTools in 8.2. Can we get this re-opened and grant the exception?
Reopening since it was removed.
Metadata Update from @raineforest: - Issue status updated to: Open (was: Closed)
This should be fixed now. Sorry for the delay.