So there's this CI ticket ATM[0] about whether the environment in which CI tests are run should or should not include and update from the 'buildroot' repo, which contains both: 1. Packages that have been pushed stable since the last time a compose succeeded (for Rawhide that's a Rawhide compose, for Branched it's a Branched compose, for stable releases it's an updates compose) 2. Packages that have active buildroot overrides Thinking about this reminded me again why buildroot overrides are such a bad idea: https://pagure.io/fedora-ci/general/issue/376#comment-830638 Buildroot overrides have unpredictable consequences for builds, updates *and* tests. I really feel like we should consider disallowing them and requiring all rebases to be done using side tags. Side tags are a *much* better design that avoids the problem of packages unexpectedly being built against a buildroot override somebody else submitted, and means test systems aren't stuck in a bind of not really knowing for sure what other packages should be installed when testing any given package. What does everyone else think? Has the time come? Or is there more we need to do to make side tags usable for all cases before getting rid of overrides? [0]: https://pagure.io/fedora-ci/general/issue/376 -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha 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
