Hello everybody, it's been almost a year that rpmautospec was released in production on Koji builders and its about time for an update. Last week I released version 0.2.6 as a Fedora package and deployed it to Koji in staging infra for testing meanwhile.
So, if you use rpmautospec in your package, please test this new release extensively before we put it into production, using the staging package repositories and `fedpkg-stage`. I want to catch any regressions that this new release might have introduced – some of the changes required substantial refactoring of how changelogs are generated, and while everything held up well in my own tests, I'll feel safer deploying into production if a couple more people put this to the test with their own packages. Thanks! Here are the highlights of this new release, I'll link the corresponding tickets because they contain much detail that doesn't fit into this mail. * Affecting Koji builds * Enable longer changelog entries. https://pagure.io/fedora-infra/rpmautospec/issue/189 https://pagure.io/fedora-infra/rpmautospec/issue/224 Previously, only the subject line of a git commit log was used for the RPM changelog as one bullet point. Now you can continue this bullet point in the body by starting it with an ellipsis ("…", "...") and/or add more bullet points simply by prefixing them with a dash. E.g. this git commit log …: --- 8< --- This is a pretty detailed entry, therefore it ... won't fit into the 50 characters of a commit subject. - And here's another bullet point. Some details that will be ignored. Signed-off-by: Nils Philippsen <n...@redhat.com> --- >8 --- … would become this RPM changelog: --- 8< --- * Fri May 13 2022 Nils Philippsen <n...@redhat.com> - This is a pretty detailed entry, therefore it won't fit into the 50 characters of a commit subject. - And here's another bullet point. --- >8 --- This can be tested by building a package with such normally using the `fedpk * Handle removed changelog file better (e.g. when bringing a package back from retirement). https://pagure.io/fedora-infra/rpmautospec/issue/210 * Don’t trip over gaps in epoch-versions (e.g. if the spec file is missing or can’t be parsed). https://pagure.io/fedora-infra/rpmautospec/issue/237 * Relevant for local use (i.e. doesn't need deployment into production, only the 0.2.6 version installed locally) * Add rpmautospec convert command which converts a package repository to using %autorelease and %autochangelog (thanks to Elliott Sales de Andrade). https://pagure.io/fedora-infra/rpmautospec/issue/201 * Don't use localized dates in changelog entries. https://pagure.io/fedora-infra/rpmautospec/issue/104 * Cope better with spec files outside of git repositories. https://pagure.io/fedora-infra/rpmautospec/issue/214 Cheers, Nils -- Nils Philippsen / Senior Software Engineer / Red Hat PGP fingerprint: D0C1 1576 CDA6 5B6E BBAE 95B2 7D53 7FCA E9F6 395D _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
