Peter Oliver kirjoitti 19.7.2021 klo 10.53:
On Mon, 19 Jul 2021, 08:08 Otto Urpelainen, <oturpe@xxxxxx> wrote:
However, copr seems to understand rpmautospec.
Not really. The release will always be 1. When a package builds again,
end users won't receive the updated version.
https://pagure.io/fedora-infra/rpmautospec/issue/199
Thank you for correcting me. This is a reminder for me to always check
the output, rather than just being happy when there are no errors.
Now that I have used rpmautospec a little, I have also discovered that
it only considers the first line of Git changelog. The rest is silently
dropped. So what would be like this in rpm changelog language:
- Update to version 1.2.3
- Re-enable the test suite
- Fixes rhbz#123456
- Fixes rhbz#234567
is this oneliner in rpmautospec language:
Update to version 1.2.3; Re-enable the test suite; Fixes
rhbz#123456; Fixes rhbz#234567
That is not your usual Git changelog entry, but something special to
rpmautospec. Worse, forgetting that you should not use newlines produces
a specfile changelog with information missing.
This situation considerably reduces my enthuasism about rpmautospec. For
some reason I thought I could think about it as "just fill the Git
changelog, you get rpm changelog for free".
Otto
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure
