RPM version goes backward in Rawhide

[drago01]

On Wed, Jul 27, 2011 at 8:39 PM, Michael Schwendt <mschwendt at gmail.com> wrote:
> On Wed, 27 Jul 2011 09:19:08 -0700, JK (Jesse) wrote:
>
>> On 7/27/11 2:03 AM, Michael Schwendt wrote:
>> > There is a big difference between "a package going backwards in its EVR
>> > and staying there" and "a package getting untagged because it breaks koji
>> > buildroot and with the plan to go forward in EVR as soon as the bug is
>> > found and fixed".
>>
>> If it goes backwards to await a fix, that fix needs to be happening
>> within the same day or so.
>
> Panu has mentioned that he will be looking into fixing this unexpected
> breakage. If that isn't acceptable to you, feel free to provide a fix
> faster.
>
>> Not prolonged so that updates fail on users'
>> systems.
>
> Do they fail in this case?
> Do you prefer rpm-build in koji buildroot to fail even longer?
> An issue with rpm-build on Rawhide installations is minor compared with
> Fedora's offical buildsys.
>
>> > In this case, the bad rpm-build broke koji builds, and since Rawhide
>> > may eat babies, it can happen that Rawhide users need downgrade manually
>> > while they have to wait for the fixed rpm-build.

The proper fix would have been to just use epoch. People can call them
evil all they want they are perfectly suitable for that kind of
problems.