Hello,
we did a Copr release last week.
Release notes:
https://docs.copr.fedorainfracloud.org/release-notes/2026-04-16.html
My apologies for not announcing the outage beforehand. It was on a tight
schedule and because of some blockers, I wasn't sure till the very last
moment whether it is going to happen or not.
Jakub
Hello COPR maintainers,
I'm running into a persistent issue with my COPR project and would appreciate your help after exhausting the usual troubleshooting steps.
Project
- Project: https://copr.fedorainfracloud.org/coprs/maltekiefer/fedora-extras/
- Owner: maltekiefer
- Packages: flutter, epson-inkjet-printer-escpr, epson-inkjet-printer-escpr2, jdownloader2
- Source: SCM (git), build method make_srpm, from https://github.com/MalteKiefer/fedora-packages.git
- Enabled chroots: fedora-42-x86_64, fedora-42-aarch64, fedora-43-x86_64, fedora-43-aarch64, fedora-44-x86_64, fedora-44-aarch64, fedora-rawhide-x86_64, fedora-rawhide-aarch64
Problem
Every single build in this project fails at the backend stage, even though the SRPM source build succeeds. The recurring error in the backend log is:
Backend process error: Giving up waiting for copr_base repository, please try to manually regenerate the DNF repository (e.g. by 'copr-cli regenerate-repos <project_name>')
There is not a single successful build in the project's history - latest_succeeded_build is null for every package.
Failed builds (all 13 attempts to date)
10344561 jdownloader2 failed
10344464 flutter failed
10344414 epson-inkjet-printer-escpr failed
10344413 flutter failed
10344412 epson-inkjet-printer-escpr2 failed
10344350 epson-inkjet-printer-escpr failed
10344349 flutter failed
10344348 epson-inkjet-printer-escpr2 failed
10344221 epson-inkjet-printer-escpr2 failed
10344213 epson-inkjet-printer-escpr failed
10344212 flutter failed
10344211 epson-inkjet-printer-escpr2 failed
10344195 epson-inkjet-printer-escpr2 failed
Example: https://copr.fedorainfracloud.org/coprs/maltekiefer/fedora-extras/build/103…
(Source state: succeeded - Build state: failed)
What I've tried
- Resubmitted builds 13 times across all 4 packages — all fail with the same error.
- Ran `copr-cli regenerate-repos maltekiefer/fedora-extras` multiple times. The CLI confirms the action was submitted, but build behavior does not change:
$ copr-cli regenerate-repos maltekiefer/fedora-extras
Submitted action to regenerate repository metadata for the 'maltekiefer/fedora-extras' project.
- Deleted and recreated the project 3 times from scratch - same result.
- Verified that SRPM builds consistently succeed (so the spec files and git sources are fine).
- Chroot configuration is default (no additional_packages, additional_repos, or additional_modules set).
This strongly suggests the repo metadata regeneration for copr_base is not actually completing on the backend, which means no chroot can ever pull its build dependencies and every build times out waiting.
Context
I also posted on Fedora Discussion and was pointed to this list by Barry Scott:
https://discussion.fedoraproject.org/t/ (thread: "Issues with Setting up maltekiefer/fedora-extras COPR – Repeated Failures")
What I need
Could someone with backend access please check whether the regenerate-repos actions for maltekiefer/fedora-extras are actually being processed, or whether something is stuck on the infrastructure side? Happy to provide additional logs, spec files, or run further diagnostics on request.
Thanks very much for your time.
Best regards,
Malte Kiefer