I have got a package yudit get reviewed rhbz#2294718 and subsequently requested a repo by command fedpkg request-repo yudit 2294718 The repo is created but is owned by releng-bot so I can not push to it
fedpkg request-repo yudit 2294718
When do you need this? (2025/05/01)
When is this no longer needed or useful? NA
If we cannot complete your request, what is the impact? The new package could not be pushed to rawhide
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
Metadata Update from @jnsamyak: - Issue tagged with: low-gain, low-trouble, ops
This should be fixed now, if not please let us know!
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
I'm currently testing update for it in staging, that should prevent this in future. It would enough to run @releng-bot retry in the ticket and it should fix it.
In case it helps I got the following message releng-bot added a new comment= to an issue you are following:``Error happened during processing:```Traceb= ack (most recent call last):=C2=A0 File "/opt/app-root/src/toddlers/plugins= /scm_request_processor.py", line 189, in process=C2=A0 =C2=A0 self.process_= ticket(issue)=C2=A0 File "/opt/app-root/src/toddlers/plugins/scm_request_pr= ocessor.py", line 297, in process_ticket=C2=A0 =C2=A0 self.create_new_repo(= =C2=A0 File "/opt/app-root/src/toddlers/plugins/scm_request_processor.py", = line 567, in create_new_repo=C2=A0 =C2=A0 self.dist_git.new_project(=C2=A0 = File "/opt/app-root/src/toddlers/utils/pagure.py", line 372, in new_project= =C2=A0 =C2=A0 raise PagureError(toddlers.exceptions.pagure_error.PagureErro= r: Couldn't create project 'rpms/yudit' Request to 'https://src.fedoraproject.org/api/0/new':{'namespace': 'rpms', = 'name': 'yudit', 'default_branch': 'rawhide', 'description': 'The yudit pac= kage\n', 'url': '', 'wait': True, 'create_readme': True} Response:None" Now the problem is fixed and I have published the package=C2=A0
=20 =20 On Wed, 30 Apr 2025 at 4:36 pm, Michal Kone=C4=8Dn=C3=BD<pagure@pagure.io=
wrote: =20 zlopez added a new comment to an issue you are following: I'm currently testing update for it in staging, that should prevent this in= future. It would enough to run @releng-bot retry in the ticket and it shou= ld fix it.
I'm currently testing update for it in staging, that should prevent this in= future. It would enough to run @releng-bot retry in the ticket and it shou= ld fix it.
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/12712 =20