scfc reported a new issue against the project: `releng` that you are following: `` For mass rebuilds, the `Release:` header is bumped with `rpmdev-bumpspec`. This does not work properly for spec files that are using special magic:
Version: %{major}.%{minor} -Release: %{?gh_date:1%{specrel}.%{?prever}%{!?prever:%{gh_date}git%{gh_short}}}%{!?gh_date:%{specrel}}%{?dist} +Release: %{?gh_date:1%{specrel}.%{?prever}%{!?prever:%{gh_date}git%{gh_short}}}%{!?gh_date:%{specrel}}%{?dist}.1 Summary: PHP code coverage information
Version: %{major}.%{minor} -Release: %{?gh_date:1%{specrel}.%{?prever}%{!?prever:%{gh_date}git%{gh_short}}}%{!?gh_date:%{specrel}}%{?dist}.1 +Release: %{?gh_date:1%{specrel}.%{?prever}%{!?prever:%{gh_date}git%{gh_short}}}%{!?gh_date:%{specrel}}%{?dist}.2 Summary: PHP code coverage information
In Fedora 29, there are `dnf repoquery '*fc29.[1-9]*' | wc -l` = 291 packages where these bumps apparently did not work as expected. While they are benign, they are confusing.
It is probably not possible to come up with a way to reliably bump all imaginable release strings. However, a good indicator that something is amiss is when `rpmdev-bumpspec` wants to add `.1` to the previous:
[tim@passepartout ~/src/fedora/rpms/php-phpunit-PHP-CodeCoverage]$ rpmdev-bumpspec --verbose php-phpunit-PHP-CodeCoverage.spec php-phpunit-PHP-CodeCoverage.spec - %{?gh_date:1%{specrel}.%{?prever}%{!?prever:%{gh_date}git%{gh_short}}}%{!?gh_date:%{specrel}}%{?dist} + %{?gh_date:1%{specrel}.%{?prever}%{!?prever:%{gh_date}git%{gh_short}}}%{!?gh_date:%{specrel}}%{?dist}.1
[tim@passepartout ~/src/fedora/rpms/php-phpunit-PHP-CodeCoverage]$ ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8411