New bodhi release in production

Luke Macken lmacken at redhat.com
Fri Aug 13 16:48:30 UTC 2010


On 08/12/2010 07:47 PM, Orcan Ogetbil wrote:
> On Thu, Aug 12, 2010 at 5:57 PM, Luke Macken wrote:
>>        - Minimum time-in-testing requirements
>>            - When someone tries to push an update to stable, bodhi will
>>              look to see if it has the appropriate karma, or if it has
>>              been in testing for more than N days.
>
> I have another question:
>
> What happens if a package is submitted to testing the same day on
> F-(x) and F-(x+1), then the F-(x) package reaches +3 karma the next
> day and is automatically pushed to stable? Let's say the F-(x+1)
> package still has 0 karma (or maybe even negative karma).
>
> The F-(x) package will have higher EVR than the F-(x+1)  one. This
> will break the upgrade path. Is there any measures to prevent this?

Bodhi checks for broken upgrade paths upon submission, but this would 
not mitigate the breakage that you describe here.

luke


More information about the devel mailing list