#12704 Enable epel10 branch for iptstate package
Closed: Fixed 16 days ago by jnsamyak. Opened 19 days ago by psutter.

I made a mess, sorry!

Tried to create epel10 branch using git directly by just pushing a local one. Now I'm stuck just like in #12607.

BTW: The suggested flag to request-branch didn't work for me:

[psutter@vfed iptstate]$ fedpkg request-branch --no-git-branch epel10
Requested branch "epel10" already exists. Skipping the operation.

I guess what I need now is something along the lines of:

koji add-pkg --owner psutter epel10.1 iptstate

But I have no permissions to do that myself.


Your ticket header mentions ipstate, but the comments says iptstate - can you clarify?

Metadata Update from @jnsamyak:
- Issue tagged with: low-gain, medium-trouble, ops

18 days ago

Your ticket header mentions ipstate, but the comments says iptstate - can you clarify?

Oh, sorry! Typo in title, this is about iptstate package.

@psutter, can you try again?

➜ jnsamyak@fedora ~ koji list-pkgs --package iptstate | grep epel10
iptstate epel10.1 psutter
➜ jnsamyak@fedora ~ koji add-pkg --owner psutter epel10.1 iptstate
Package iptstate already exists in tag epel10.1
Adding 0 packages to tag epel10.1

It seems to be working fine from what I can see branch is there, and owner is also set correctly and is tagged into the correct tag

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

17 days ago

Looking good: https://koji.fedoraproject.org/koji/taskinfo?taskID=131933394
Thanks for the heads-up, @jnsamyak! Did someone fix it and missed to update the ticket or is 'fedpkg request-branch --no-git-branch' working despite the error message and results are delayed?

There might be a delay in the results, which should have fixed it, but it might be a race case that has happened! Awesome, if you have anything else please free to let me know

Metadata Update from @jnsamyak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

16 days ago

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog