epel

#301 EPEL10 installability CI requires improvements and fixes
Closed: Fixed by dherrera. Opened by dherrera.

Closed: Fixed
Reopen Issue

I'm starting to write this to track the work needed to get this done.

Ideally we want these to run correctly on Pull Requests and on bodhi.

I've heard that they are not always accurate, so they shouldn't block things, but just having the result/logs can be a valuable asset for contributors, so we must make sure these work correctly.

Metadata Update from @dherrera:
- Issue assigned to dherrera

Until last week, when the CI ran on pull requests that targeted EPEL10 branches, it failed with the following message.

ERROR: Profile "epel10" doesn't exist in config.json

Right now even if the dist-git tests are not working, the installability are.
This work is being tracked on https://pagure.io/fedora-ci/general/issue/491

With the latest merged fixes, installability tests are working both on PRs and on Bohdi for the EPEL10 leading branch.

Just as a caution, tests won't include the EPEL testing repository when checking for installability, so it is recommended to push updates together to Bohdi on the cases where there are required dependency changes.

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

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/301

Please continue any further discussion there.
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.