fedora-infrastructure

#12197 Request for a new branch failed with a traceback
Closed: Will Not/Can Not fix by zlopez. Opened by psss.

Closed: Will Not/Can Not fix
Reopen Issue

It seems that the rel-eng bot is unhappy today:
https://pagure.io/releng/fedora-scm-requests/issue/67755

Remote end closed connection without response

@psss That sometimes happen when communicating with fasjson or other services. It's a temporary issue and it is solved by simply typing "retry" in the ticket.

The following issue after that is something completely unrelated and it seems that the epel10 branch is not allowed by some hook set on the project.

I recommend opening issue in releng issue tracker for that.

Metadata Update from @zlopez:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Lowest
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.