Request for a new branch failed with a traceback #12197

Closed
opened 2024-09-23 13:35:50 +00:00 by psss · 2 comments

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
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
Contributor

@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.

@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](https://pagure.io/releng/issues/).
Contributor

Metadata Update from @zlopez:

  • Issue close_status updated to: Will Not/Can Not fix
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @zlopez**: - Issue close_status updated to: Will Not/Can Not fix - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#12197
No description provided.