Please remove the epel10 branch from the s3fs-fuse repository: https://src.fedoraproject.org/rpms/s3fs-fuse
epel10
I did not remember I had to request this with fedpkg request-branch, I created the branch via git, I could still push the branch but now I can't remove it. And without removing it, I can't use fedpkg request-branch again:
fedpkg request-branch
Requested branch "epel10" already exists. Skipping the operation.
As a side note, looks to me such branches should be protected and maintainers should not be allowed to created them.
As soon as possible. Package is requested at https://bugzilla.redhat.com/show_bug.cgi?id=2369652
I think I will not be able to maintain s3fs-fuse for EPEL10, I guess the koji error when I tried to build is related to this: https://koji.fedoraproject.org/koji/taskinfo?taskID=134154664
Pass: --no-git-branch to fedpkg request-branch?
Valid point, but even with that option:
$ fedpkg request-branch --no-git-branch epel10 Requested branch "epel10" already exists. Skipping the operation.
And indeed I don't see any new issue created at https://pagure.io/releng/fedora-scm-requests/issues.
Should be fixed now... can you retry your build?
@juliogonzalez Hello. :wave: Are you still experiencing issues or can this be closed?
If you are still having problems feel free to reopen the issue and tell us what is happening.
Metadata Update from @james: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Sorry about the delay, but I am have restricted availability these days.
Yes, I am still having the issue (this time I am providing some more output with the verbose and debug options)
root@KOJI:~/fedpkg-s3fs-fuse (rawhide=)$ fedpkg -d -v request-branch --no-git-branch epel10 Creating repo object from /root/fedpkg-s3fs-fuse Pagure API request: https://src.fedoraproject.org/api/0/rpms/s3fs-fuse/git/branches Pagure API response: '{'branches': ['epel10', 'epel7', 'epel8', 'epel9', 'f27', 'f28', 'f29', 'f30', 'f31', 'f32', 'f33', 'f34', 'f35', 'f36', 'f37', 'f38', 'f39', 'f40', 'f41', 'f42', 'main', 'rawhide'], 'default': 'rawhide', 'total_branches': 22}' Requested branch "epel10" already exists. Skipping the operation.
Ignore the fact I am running everything as root. For historic reasons I am using a podman container. No issue got created at https://pagure.io/releng/fedora-scm-requests/issues
Some more info:
dnf update
Easiest short term solution would be removing the branch epel10 from https://src.fedoraproject.org/rpms/s3fs-fuse, but indeed it seems there's some kind of issue with fedpkg itself.
fedpkg
Metadata Update from @juliogonzalez: - Issue status updated to: Open (was: Closed)
No, I meant retry the build... there shouldn't be any need to redo the branch...
Sorry, seems I need more :coffee: :-)
https://koji.fedoraproject.org/koji/taskinfo?taskID=134361329 finished with no errors, so all seems to be OK.
I will close the issue, as the original problem is solved.
However, if possible, I'd like to know what went wrong.
Do I need to send a patch for fedpkg, at least to suggest people to use --no-git-branch if the target branch already exists?
--no-git-branch
Metadata Update from @juliogonzalez: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.