Learn more about these different git repos.
Other Git URLs
This is probably broken in some script that @limb runs, it probably creates the repo, checks some constraints and assigns the repo to me. When the constraints fail, the repo exists, but is not assigned to me. I cannot provide more details, because I have no idea what happens "on the other side".
This already happened twice to me:
https://pagure.io/releng/fedora-scm-requests/issue/10706 https://pagure.io/releng/issue/8233 https://pagure.io/releng/fedora-scm-requests/issue/13178 https://pagure.io/releng/issue/8467
In both cases, the branch was set to epel7 and initial_commit to false, if that makes any difference.
This could be an artifact of the script crashing due to 500 or 400 errors.
https://pagure.io/releng/fedora-scm-requests/issue/14877
https://pagure.io/releng/fedora-scm-requests/issue/14975 https://pagure.io/releng/fedora-scm-requests/issue/14976
I believe this is caused by "initial_commit": false
"initial_commit": false
Either this was fixed, or the previous comment is not true.
I have seen this before, but as @limb mentioned it is random and mostly the script crashing while processing the request.
Is this still happening to anyone?
I did see a case a while back... in that case the user was in packager in fas but had not yet logged into src.fedoraproject.org to refresh their group membership. In that cause it made the repo, tried to give it to them, but failed because pagure thought they were not in packager and left the runner of fedscmadmin as owner.
To fix that I guess we need a check that they are packager in src.fedoraproject.org and if not, print a 'please login and refresh your group membership' message.
I haven't seen this in a while.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.