On Thu, Dec 19, 2024 at 1:55 AM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote: > > On Thu, Dec 19, 2024 at 09:26:37AM +0100, Vitaly Zaitsev via devel wrote: > > On 18/12/2024 22:59, Simon de Vlieger wrote: > > > What I'd like to see is to remove provenpackagers, do everything through > > > PRs and have a separate SIG/group that can fast-track and merge any PR. > > > > Not an option because when we update some important libraries, we need to > > rebuild more than 50 packages. If we have to use pull requests and wait for > > them to be merged, it will take forever to push updated versions of these > > libraries. > > For these situations IMHO it would be better if we did not need to have > provenpackagers trigger the rebuilds. We should have a fully automatable > way for *any* package to trigger a rebuild of dependent things. If the > person does not need to make any changes to the spec, directly, only > through an automated tool, there would be no need for the elevated > provenpackagers privilege and it would also avoid any risk of complaints > of unrelated changes being made at the same time. > > In the context of such rebuilds, provenpackagers is simply a workaround > for our insufficient automation. > I have been beating this hammer ever since I experienced it on openSUSE with the Open Build Service. As soon as we became aware it was technically possible, we should have started developing similar capabilities in Koji. We kind of did with Koschei, but we never integrated it into the workflow. Auto-spawning side tags and doing revdep rebuilds without ever touching the package is something I want to have. There are some things we have to start letting go of in order to make it work, though. Like requiring bumps in git for no-change rebuilds. Unfortunately, I have not been able to convince anyone this is a useful endeavor for Fedora in the near decade I've been talking about this. -- 真実はいつも一つ!/ Always, there's only one truth! -- _______________________________________________ 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