V Sun, Feb 16, 2025 at 06:58:19PM -0500, Neel Chauhan napsal(a): > Hi, > > I'm trying to create an EPEL 10 branch for a package I maintain, ttyd: > https://pagure.io/releng/fedora-scm-requests/issue/72348 > > I am getting this issue in Pagure: > > === > Traceback (most recent call last): > File "/opt/app-root/src/toddlers/plugins/scm_request_processor.py", line > 189, in process > self.process_ticket(issue) > File "/opt/app-root/src/toddlers/plugins/scm_request_processor.py", line > 301, in process_ticket > self.create_new_branch(issue, issue_body) > File "/opt/app-root/src/toddlers/plugins/scm_request_processor.py", line > 778, in create_new_branch > self.dist_git.new_branch( > File "/opt/app-root/src/toddlers/utils/pagure.py", line 500, in new_branch > raise PagureError( > toddlers.exceptions.pagure_error.PagureError: Couldn't create branch in > project 'rpms/ttyd' > > Request to 'https://src.fedoraproject.org/api/0/rpms/ttyd/git/branch': > {'branch': 'epel10', 'from_commit': > '06bfff8ce8cca42ac22e297e9c880809b630abe9'} > > Response: > {'error': 'Did not manage to rebase this pull-request', 'error_code': > 'ENOCODE'} > > Status code: 400 > === > > Could a sysadmin/developer (whoever's responsible) please fix this? > It is exaplained in <https://pagure.io/releng/fedora-scm-requests> description that failed SCM request needs to manually reported to <https://pagure.io/releng/issues>. Please, do that. -- Petr
Attachment:
signature.asc
Description: PGP signature
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue