On Thu, Dec 19, 2024 at 10:35:52AM +0100, Vít Ondruch wrote: > > Dne 19. 12. 24 v 9:55 Daniel P. Berrangé napsal(a): > > 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 would be more then happy if there was some automation helping with e.g. > mass rebuild of Ruby, which is my main use case for having PP. But I don't > think it is realistic to expect anything like this any time soon 😔 A no-change rebuild conceptually ought to be fairly easy. Upstream projects frequently have all sorts of automations that are way more complex than this, using github actions / gitlab CI, and or bots interacting with pull requests. For a no-op rebuild of dependent packages, if we required %autorelease/ %autochangelog, then a CI action should be little more than verifying that the pull request had a single commit with no files modified, auto approving it, and auto triggering a koji build. Creating such a compliant pull request should be little more than a pair of git commit --allow-empty && git push, the latter with some -o options set to create the pull request, which could be wrapped in a 'fedpkg' command. I've never used Forgejo, so don't know exactly what features we'll be able to benefit from, but I hope it would make it easier to do these kind of simple automations. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- _______________________________________________ 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
