On Sun, Feb 13, 2022 at 04:27:36PM -0500, Neal Gompa wrote: > I used to be motivated to write such a bot, but after the rpmautospec > thing, I'm not going to bother. I wanted rpmautospec to handle > rebuilds without commits/changelog bumps, because then we could > trigger rebuilds more simply (dependency drift? rebuild in side-tag > then merge once all rebuilds are done). Now it would require > interacting with Git and changelog bumps. > > Essentially, this is the model that is used in openSUSE and it's quite > a bit less stressful.
I think you're mixing up two things here. We *do* want to record the fact that the rebuild happened. It should be visible in the changelog, possibly with some explanatory text and a link to a bug number, and the new build should have a release bump. The way that we cause all those things to happen in Fedora is by commiting to dist-git. With rpmautospec this commit might be empty, but it still needs to exist. The bot for rebuilds would need two privileges: for dist-git and for koji. And it was the same before rpmautospec and now. And I think it's good that rpmautospec deals with changelog/release number generation at the level of a single package, and doesn't try to handle additional disto-wide jobs. Zbyszek _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
