Evolution update in F13
braden at endoframe.com
Tue Jun 29 04:17:52 UTC 2010
On Fri, 2010-06-25 at 16:27 -0700, Jesse Keating wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Can anybody tell me what went wrong with this update? It was submitted
> at 15:09 on 06-23, then made it into testing at 16:19 on 06-24 and was
> submitted for stable two hours later. Between that submission and the
> push to stable (push to stable happened at 18:09 on 06-25) numerous
> negative karma came in due to broken deps. The update went out anyway,
> and now we have a mess of broken updates on a critical path package, and
> have to scramble to fix it with more updates, on a Friday.
> Can anybody help me understand the scenario here? Should we start
> filtering out push requests that have more than -2 karma?
Updating F13 now works; but a yum upgrade from F12 still seems busted.
Braden McDaniel <braden at endoframe.com>
More information about the devel