Gave to thrnciar.

Enabled monitoring.

Is there a chance the error happens because --no-initial-commit? A main branch alias is attempted, but there is no rawhide and it fails?

@churchyard so far I think this is network related issue. It happens randomly. The only solution I can see is to make the process more transactional and retry failed steps.

All of my new repo request are with --no-initial-commit and all of my new repo requests after the master to rawhide migration end up with this failure. Is it indeed random?

All of my new repo request are with --no-initial-commit and all of my new repo requests after the master to rawhide migration end up with this failure. Is it indeed random?

Ok, let me check again. I have looked into it before the master->rawhide migration. Because it was happening back then.

Again in https://pagure.io/releng/fedora-scm-requests/issue/36653

I've taken the auditwheel package. I need somebody from here to create the main branch alias.

@churchyard the SCM request should be fixed.

Is the main branch an alias of rawhide in the auditwheel package?

@churchyard yes.

Thanks. What about https://pagure.io/releng/issue/10264#comment-747316 ? Any luck?

Thanks. What about https://pagure.io/releng/issue/10264#comment-747316 ? Any luck?

Well, I found a way to create a branch without any commit in it and also how to create a branch alias for it. But I got a different exception from pagure.

The blunt solution would be to ignore --no-initial-commit but that is not something users will appreciate...

The blunt solution would be to ignore --no-initial-commit but that is not something users will appreciate...

We would not ;)

closing in favor of #10512