churchyard reported a new issue against the project: `releng` that you are following: `` 1. I've create a new repository request, where something was wrong 2. @limb processed the request, closed as invalid 3. I fixed the thing and reopened the issue 4. @limb processed the request, closed as invalid again (already exists) 5. as a result, the repo was created, but owned by @limb
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/10716 https://pagure.io/releng/fedora-scm-requests/issue/13178
In both cases, the branch was set to epel7 and initial_commit to false, if that makes any difference. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8468
limb added a new comment to an issue you are following: `` This could be an artifact of the script crashing due to 500 or 400 errors. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8468
churchyard added a new comment to an issue you are following: `` https://pagure.io/releng/fedora-scm-requests/issue/14877 ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8468
churchyard added a new comment to an issue you are following: `` https://pagure.io/releng/fedora-scm-requests/issue/14975 https://pagure.io/releng/fedora-scm-requests/issue/14976 ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8468
churchyard added a new comment to an issue you are following: `` I believe this is caused by `"initial_commit": false` ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8468
rel-eng@lists.fedoraproject.org