I did run scratch build for modules/ruby wip/2.7 branch on remote origin that is created by my mistake.
wip/2.7
origin
$ git branch -r j/wip/2.7 origin/2.4 origin/2.5 origin/2.6 origin/2.7 origin/HEAD -> origin/master origin/f26 origin/f28 origin/f29 origin/master origin/private-jaruga-master $ git branch 2.5 2.6 2.7 master * wip/2.7 $ fedpkg module-build --scratch Submitting the module build... The builds 10089, 10090, 10091 and 10092 were submitted to the MBS Build URLs: https://mbs.fedoraproject.org/module-build-service/2/module-builds/10089 https://mbs.fedoraproject.org/module-build-service/2/module-builds/10090 https://mbs.fedoraproject.org/module-build-service/2/module-builds/10091 https://mbs.fedoraproject.org/module-build-service/2/module-builds/10092 $ fedpkg module-build-info 10089
I faced the following error. I assume this comes from foo/bar branch name. Do you know what's the reason?
foo/bar
https://koji.fedoraproject.org/koji/taskinfo?taskID=51000243
FileNotFoundError: [Errno 2] No such file or directory: '/etc/mock/koji/scrmod-ruby-wip/2.7-3420200907130559-058368ca_2+10089-build-22655560-2043316.cfg'
This issue is 100% an operational issue on that Koji builder. It's not anything mbs is doing.
Metadata Update from @mikem: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/mbs/issues/1652
Please continue any further discussion there.