Yum broken = no testing

[Christopher Aillon]

seth vidal wrote:
>>Well...  it'd be much easier for a user running the current python to 
>>get a new yum RPM to be able to fix their system than to go through the 
>>dependency fun that is upgrading python when something like yum is 
>>"busted".  I am OK with this not going into the upstream yum package, 
>>but it might be worth adding to our packages for the time being....
> 
> 
> so by that argument, if gtk had an api break then mozilla should work
> around it, rather than making the fix occur in gtk?


Historically, that's more or less what happens (though they do try and 
get a fix made upstream as well).