When testing the request locally I got expired token, let me renew the token and see if that will help.

My bad, I was using pagure token instead of dist-git token. With dist-git token I got the same error, but I don't see anything in journal or httpd log on pkgs01.

Another thing that is strange to me is the mention of pull request, we don't work with pull request when creating new branch.

Independent of fixing whatever bug caused the crash, is it possible to create the epel10 branch for the pyOpenSSL package so that Jeremy can build?

Thanks

And looking at the pagure code it shouldn't even touch the code that is throwing the exception.

Independent of fixing whatever bug caused the crash, is it possible to create the epel10 branch for the pyOpenSSL package so that Jeremy can build?

Thanks

That should be possible. @jnsamyak Could you look at that?

Looking into it now

Okay this got triggered at one more rpm and it just worked fine there, https://pagure.io/releng/fedora-scm-requests/issue/68614

Not sure what happened here, because I tried digging into the logs but couldn't find anything related, so I'll work on creating it manually now

Okay i managed to create one branch from rawhide, and pushed another branch epel10 from it, and added it to koji using

koji add-pkg epel10.0 pyOpenSSL --owner jcline

Adding 1 packages to tag epel10.0

Can you check now, if you are okay with this change, and is able to build a package?

I tested it today on staging pyOpenSSL dist-git repository and the branch was created without issue. I assume there is either something set in settings of pyOpenSSL repository or something in metadata.

But it seems that this happened only for pyOpenSSL, so we will fix it by just creating the branch manually for now.

There was one idea shared by @humaton that the issue could have happened because pyOpenSSL is already packaged in RHEL 10, but I checked that and it's not the case. But before the check we rather blocked the epel10 branch in koji so we don't mess anything. So if you are still unable to build it's because of that. I'm currently waiting for @jnsamyak to unblock it again.

The package should be unblocked again. @jcline Could you confirm that the epel10 package could be built?

Yep, all good for me.

Closing this as fixed, thanks for confirmation.