On Sun, 2023-07-16 at 15:24 -0400, Christopher wrote: > > > > There is more than one tool in use. The main build tool is Koji, but it > > depends on other underlying tools such as Mock, DNF, RPM, etc. Also keep in > > mind that in Fedora, all binaries are natively compiled, not cross-compiled > > as in Yocto. I.e., the rpmbuild process needs to run on a (real or emulated) > > CPU of the architecture for which you want to build the package. RPMs do not > > typically support cross-compilation. > > When I saw the original post, I was interested to see what responses > it would trigger. I must admit that this one is a bit disappointing. > While I've been building RPMs for Fedora for awhile now, one of the > things that has eluded me is that the Fedora OS composes seem to be > very opaque to me. I know enough to understand that Koji tags rpm > builds from individual buildroots, but from there, the process to > build the repos and the installation media, or how the buildroots are > created in the first place for Koji, or any other weirdness involved > in the construction of the OS as a whole from the individual RPM > builds, all of that seems opaque to me. I think it'd be great if there > was an up-to-date and detailed step-by-step guide for how to build a > Fedora release. Such documentation should be detailed enough that one > could stand up their own fork of the Fedora OS... not because we want > to encourage that... but because that's the level of detail that I > think is needed to allow volunteers to step in and get involved, as > the current folks move on, due to retirement, death, boredom, or > whatever. If such documentation already exists, I don't know where it > could be found. > > Do you know of any such detailed documentation, step-by-step > instructions, or maybe slides/presentations on the compose process or > overall Fedora OS build systems? This is the wrong question, kinda. There is no detailed step-by-step process. The process for creating a compose is, more or less, "push the magic COMPOSE NOW" button. (Okay, there's a *bit* more to it than that, but not a lot). The SOP for it is https://docs.pagure.org/releng/sop_composing_fedora.html . All the complexity, these days, is in what happens when you push the button. Which is so complex I just couldn't stand the thought of sitting down and writing it all out. *basically*...more or less...what happens when you hit the button is that pungi - https://pagure.io/pungi - following the Fedora pungi config - https://pagure.io/pungi-fedora - creates a whole bunch of Koji tasks. Each of those Koji tasks does...something, there are a lot of somethings, often using different tools. The whole process is logged in overwhelming detail - https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20230716.n.0/logs/ . Often the pungi logs (those ones) wind up just pointing you to a Koji task, where you will find the actual logs, e.g. the pungi 'log' for the KDE live media creation is https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20230716.n.0/logs/aarch64-x86_64/livemedia-Spins-KDE.aarch64-x86_64.log , which points you to https://koji.fedoraproject.org/koji/taskinfo?taskID=103428940 where you can find the 'real' logs. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx https://www.happyassassin.net _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
