Description of problem: Starting from c10s, epel-next is no more - but fedrq still enables it when used with -b c10s -r @epel. From the Python API this causes slowdown and noise as it queries a non-existent repo each time, and the fedrq CLI just fails Version-Release number of selected component (if applicable): fedrq-1.3.0-1.fc42 How reproducible: Always Steps to Reproduce: See https://lists.sr.ht/~gotmax23/fedrq/patches/55705 Actual results: Querying -b c10s -r @epel fails Expected results: Querying -b c10s -r @epel works Additional info:
FEDORA-2024-222d41f180 (fedrq-1.4.0-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-222d41f180
FEDORA-2024-222d41f180 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-222d41f180` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-222d41f180 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-222d41f180 (fedrq-1.4.0-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.