Sounds good. I took a look at the "multi builds" page - it describes the process neatly, but I think there's one thing that could be added there: what if you already built a package in the main tag (but it didn't go through bodhi and get to stable)? Will it be included in the newly-created side tag, or do you need to execute some command to add it there?

However, I think side-tags should be the preferred solution, as their impact is isolated. Buildroot overrides create temporary broken dependencies for everybody, while side-tags don't.

And than instead of describing the details, link to https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/

... (in fact, we could have a discussion about getting rid of buildroot overrides, at this point).

https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_G... Shouldn't it be somehow aligned with this ^^ chapter? Maybe the chapter should be referenced at least, because it explains how to request the side tag.

Dne 23. 09. 21 v 11:29 Miro Hrončok napsal(a): > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_G... > > > Says: > > """ > You may need a buildroot override to complete a multi-package update > successfully. For instance in the case described above, you may need > to rebuild bar against the new libfoo package and submit both packages > together as a multi-package update. However, in the normal course of > events, you would not be able to build another package against your > new libfoo build until it reached the stable state. To resolve this > dilemma, you can request a buildroot override, which causes the libfoo > build to be included in the buildroot for a short time in order to get > the bar package build done. > """ > > However, I think side-tags should be the preferred solution, as their > impact is isolated. Buildroot overrides create temporary broken > dependencies for everybody, while side-tags don't. > > My understanding was that this is the de-facto consensus, so I'd lie > to update the docs to say something like: > > """ > You may need to build the inter-dependent packages in a side tag. > For instance in the case described above, you may need to rebuild bar > against the new libfoo package and submit both packages together as a > multi-package update. However, in the normal course of events, you > would not be able to build another package against your new libfoo > build until it reached the stable state. To resolve this dilemma, you > can request a side tag and build both packages in it, which causes the > libfoo build to be included in the bar build's buildroot. > """ > > And than instead of describing the details, link to > https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/ > > Any suggestions or objections? > _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_G... Says: """ You may need a buildroot override to complete a multi-package update successfully. For instance in the case described above, you may need to rebuild bar against the new libfoo package and submit both packages together as a multi-package update. However, in the normal course of events, you would not be able to build another package against your new libfoo build until it reached the stable state. To resolve this dilemma, you can request a buildroot override, which causes the libfoo build to be included in the buildroot for a short time in order to get the bar package build done. """ However, I think side-tags should be the preferred solution, as their impact is isolated. Buildroot overrides create temporary broken dependencies for everybody, while side-tags don't. My understanding was that this is the de-facto consensus, so I'd lie to update the docs to say something like: """ You may need to build the inter-dependent packages in a side tag. For instance in the case described above, you may need to rebuild bar against the new libfoo package and submit both packages together as a multi-package update. However, in the normal course of events, you would not be able to build another package against your new libfoo build until it reached the stable state. To resolve this dilemma, you can request a side tag and build both packages in it, which causes the libfoo build to be included in the bar build's buildroot. """ And than instead of describing the details, link to https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/ Any suggestions or objections?