On Sat, Jan 18, 2025 at 10:44 AM Fabio Valentini <decathorpe@xxxxxxxxx> wrote: > So if you see packages that *change* (either their dependencies, or > their contents - but ignoring codegen differences with new compiler > versions etc.) between the last build before the mass rebuild and the > build performed during the mass rebuild, that's a sign that the update > was not pushed "correctly" in the first place, IMO. I would agree. So, the question is, can "we" change something to try to make doing the "correct" thing easier? Could fedpkg push be changed to automatically also do a build (or perhaps better, scratch-build?) so that any unexpected FTBFS is seen quicker? Yes, there are cases where you would not want that (especially for soname bumps where you need a side-tag so you would not want an auto full build), but would adding something like a "--no-auto-build" option at least force things to being explicit? FWIW (for my simple packages) I almost always do a scratch-build right after a push, as architecture specific build issues is something I am not setup to test locally. -- _______________________________________________ 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
