> Can you try again now? we fixed a major issue with mbs, which I wouldn't think was related to this, but who knows.. I tried it, and found the cause of the error now. > So isn't this the relevant part of root.log which could give a hint? Yes, possibly it is related to the issue. > https://koji.fedoraproject.org/koji/taskinfo?taskID=48194471 > BuildrootError: could not init mock buildroot, mock exited with status > 20; see root.log for more information > > https://kojipkgs.fedoraproject.org//work/tasks/4473/48194473/root.log > => looks ok. > https://kojipkgs.fedoraproject.org//work/tasks/4473/48194473/build.log > => empty. The situation is when I got the above error, I got the 4 builds by `fedpkg module-build`. (I am excluding el8 by `platform: [-el8]`) in the module config file ruby.yaml. ``` $ fedpkg module-build Submitting the module build... The builds 9293, 9294, 9295 and 9296 were submitted to the MBS ``` The error happened on build id 9293. But today I got the 3 builds with the same config file except the build id 9293. ``` $ fedpkg module-build Submitting the module build... The builds 9296, 9294 and 9295 were submitted to the MBS ``` I found `ruby-None-None` in the build id 9293. So, I suppose previously it tried to build outputed platform (f30). The other build id 9294 is f32, 9295 is f31, 9296 is f33. ``` $ fedpkg module-build-info 9293 ... Name: ruby NVR: ruby-None-None State: FAILED Koji Task: https://koji.fedoraproject.org/koji/taskinfo?taskID=48194471 ... ``` -- Jun | He - His - Him _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
