Learn more about these different git repos.
Other Git URLs
See https://pagure.io/releng/fedora-scm-requests/issue/21666
But the git repo doesn't exists:
$ fedpkg clone php-laminas-permissions-acl Cloning into 'php-laminas-permissions-acl'... No such repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Could not execute clone: Failed to execute command.
@limb there is an issue with that request, the branch may exists in PDC but the project wasn't created in dist-git: https://src.fedoraproject.org/rpms/php-laminas-permissions-acl
Could you by-pass the PDC step?
(Also: are you running the latest version of fedscm-admin? I thought we had changed a bit this message)
fedscm-admin (I have 1.0.11) doesn't offer that option, perhaps it should. Can it be deleted from the PDC?
ping.. kind reminder....
See my previous reply?
This should be fixed now. @limb Can you give it a try.
I got urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='src.fedoraproject.org', port=443): Max retries exceeded with url: /api/0/new (Caused by ResponseError('too many 400 error responses')) and it's still not clonable.
This happened before which is a network problem https://pagure.io/releng/issue/7961
Give it some time.
Ping @kevin
PDC branch already exists, can you re-delete from PDC please?
So how to solves this ?
This package is optional but used during build of some others, so which have "bootstrap" build for now.
I think if it's removed from the PDC I can re-run this and it should work. @mohanboddu @kevin
@remi This should be fixed now.
https://src.fedoraproject.org/rpms/php-laminas-permissions-acl
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Indeed, fixed,
Thanks @mohanboddu
Metadata Update from @remi: - Issue status updated to: Open (was: Closed)
Looks like there is still a problem, cannot request F32 branch https://pagure.io/releng/fedora-scm-requests/issue/22120
Invalid body, keys: sls missing
I suspect this is a mass branching artifact and will work once that's done.
Everything seems ok now.
Metadata Update from @remi: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.