Nicolas Mailhot via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> writes: > Le dimanche 05 juillet 2020 à 17:46 +0200, Björn Persson a écrit : >> Nicolas Mailhot via devel wrote: >> > So if you want to push Fedora release logic to its ultimate >> > conclusion, >> > the thing that should be in charge of committing the new >> > release/changelog build state to package history in git is bodhi, >> > not >> > koji. >> >> Why do build events need to be recorded in the Git history in the >> first place? > > The changelog is built-in the rpm format. Therefore, it needs to exists > at rpmbuild stage. Therefore, you need to record past changelog state > so new builds are consistent with previous builds. The changelog should be consistent, but it needn't record every single build event. Otherwise OBS would not work at all: the build system bumps the release field automatically on each rebuild, but it does not touch the changelog at all. Cheers, Dan
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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