Describe the issue Requesting new repos had the automated request/response end up with: "The PDC branch already exists"
When do you need this? (YYYY/MM/DD) 2020/06/05
When is this no longer needed or useful? (YYYY/MM/DD) N/A
If we cannot complete your request, what is the impact? Cannot make HAProxy Dataplane API available in Fedora
This was previously submitted as: https://pagure.io/releng/fedora-scm-requests/issue/25439
From that issue:
================ My three of my new repo requests have been closed as 'invalid' where I don't think they should be. The issues are:
https://pagure.io/releng/fedora-scm-requests/issue/25393 https://pagure.io/releng/fedora-scm-requests/issue/25394 https://pagure.io/releng/fedora-scm-requests/issue/25395
When they got closed as 'invalid' I reopened them with the message:
================== My apologies, but I cannot see a repository for this at: [URL]
If it does exist, how can I find the owner such that I could become a co-maintainer? where [URL] was one of:
https://src.fedoraproject.org/rpms/golang-github-gehirninc-crypt https://src.fedoraproject.org/rpms/golang-github-haproxytech-models https://src.fedoraproject.org/rpms/golang-github-haproxytech-config-parser
I'm guessing that because the follow-up close as 'invalid' is part of some automated process, as I would hope that my question would be answered. Therefore, I'm opening this new ticket in hopes of a review and answer.
@bdperkin this seems to be an issue with the tool used for processing SCM requests. https://pagure.io/fedscm-admin/issue/27
Thanks for submitting this issue, we will update your requests once the repositories are created.
Metadata Update from @mohanboddu: - Issue tagged with: groomed, low-trouble, medium-gain
I manually fixed the issue for now.
@limb Can you verify whether your pagure_api_token token is expired or not?
pagure_api_token
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.