F12 update issues

Adam Williamson awilliam at redhat.com
Tue Mar 2 17:31:06 UTC 2010


On Tue, 2010-03-02 at 12:22 -0500, Matthias Clasen wrote:

> > As I said, we really need to have priority PK updates to make that
> > possible. At present there's no way we could guarantee it, even with
> > testing; exactly the same thing could happen again. This didn't happen
> > when F12 first came out, we couldn't have caught it before release; it
> > only appeared after the update set for F12 came to include packages
> > which trigger the bug.
> 
> Maybe I am not making myself clear... what I am asking for, essentially,
> is that we batch updates and test those batches through autoqa before 
> releasing them. That of course has to happen after the release, to test
> problem that only occur with the combination of release + updates.

Well, sure, we can do that. What I'm saying is that even if we were
doing that, and even if it were to have exposed the problem with F12,
there was no way to properly fix it. We're stuck with it. I don't think
the updates involved do anything *wrong*, exactly, they just expose a
flaw in PK. So we can't send the updates back to sender with a note
attached that says 'fix it'.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net



More information about the test mailing list