On Tue, Jan 21, 2020 at 4:39 AM Pavel Raiskup <praiskup(a)redhat.com> wrote:
On Tuesday, January 21, 2020 10:20:10 AM CET Vít Ondruch wrote:
> I would expect that adding some keyword such as "[skip changelog]" (there
are
> quite commonly used similar hints for CI nowadays [1]) would instruct the
> generator to leave the second commit out of the changelog, because it does not
> provide any additional value to user.
Yes, but people can forget to put there the keyword, and push - and later
still affect the %changelog - and so we would have to have a way to adjust
changelog by "patch" or something.
Again, as example, take a look at gnulib, to build-aux/gitlog-to-changelog
and it treats *.amend files, --ignore-matching, --ignore-line, etc.
> > In ideal world, shouldn't the bodhi change description be equivalent to
> > %changelog, or at least a super-set of %changelog? If these were equivalent,
> > maintainers woudl have to think more about %changelog.
>
>
> Don't forget that single Bodhi update might ship several builds.
Correct, no need to not provide all the %changelogs.
I don't think people realize this, but while from DNF the updateinfo
and changelog data are separate, when Bodhi generates update notices
that are sent as emails and used in feeds, both pieces of information
are presented together.
So ideally, there should be different information in updateinfo and
changelog. The former is user-centric and the latter is packager
centric.
--
真実はいつも一つ!/ Always, there's only one truth!