On Tue, Jan 21, 2025 at 02:13:02PM +0000, Zbigniew Jędrzejewski-Szmek wrote: > At the fundamental level, such automation would effectively do two > steps: > 1. create a no-change commit like we do now, > 2. push the commit and fire off a build. > > (I think we want to keep 1. unchanged. We need to store the information > why did the rebuild and why _somewhere_. Either we keep the current > mechanism which works well and is easy for humans to interact with, > or we store this information in some external database and create new > tools to query this. I don't think we want to do this.) Aleksandra has a long-standing proposal for putting this in a "build id" in the binary RPM. https://github.com/rpm-software-management/rpm/discussions/2031 Is the "why" important long-term? -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader -- _______________________________________________ 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
