Le dimanche 05 juillet 2020 à 23:36 +0200, Dan Čermák a écrit : > 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. Well just bumping the changelog by default, and letting the packager remove unecessary lines when he has the time to look at the changelog, is a much friendlier workflow than asking the packager to think about it on every single build, redoing builds when he forgot about it because redoing builds is the only way to get a new changelog included in the binary payload. Regards, -- Nicolas Mailhot _______________________________________________ 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
