https://bugzilla.redhat.com/show_bug.cgi?id=2167539
--- Comment #13 from Adam Williamson <awilliam(a)redhat.com> ---
yeah, IIRC the mass rebuild basically runs `rpmdev-bumpspec` on the spec file,
which *tries* to just increment the release counter by 1, but when a spec
implements the release field in indirect ways (like dogtag-pki does) and it
can't figure out how to do that, it just sticks a .1 on the end as a fallback.
If you don't notice that and take it off again, it'll stick there till the next
mass rebuild when the bot will probably bump it to .2 or something :P
I think there may actually be something you can do to clue rpmdev-bumpspec in
to what number it needs to bump (%release_number in this case) but I don't know
offhand exactly how you do it...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2167539