On Thu, Oct 2, 2014 at 3:33 AM, Stephan Kulow
Am 01.10.2014 um 23:25 schrieb Claudio Freire:
True, but not totally true. You can never fix this timing issue. Eventually, snapshots will be delayed for whichever reason. You don't want a rolling distro that gets no security patches. If anything, a rolling distro should be more up-to-date than released versions, and yet releases got the security patch a few days before Factory. That makes it a show-stopper for many potential users of rolling distros.
We have a factory update repo for security updates and we used it for the first time. I wonder why you still keep asking for it.
You're right. I got my point across, that's enough.
Considering that Factory now IS published, I think we can assume that the problem was identified (let's hope so)... identifying the problem is always the first right step in the direction of getting a proper solution.
Indeed, if openQA could be taught to detect this particular (or similar) issue, it would be great.
staging projects and Factory are different enough to make this slip happen and this (as we call it in German) "Mut zur Lücke" (the courage to admit when one doesn't know everything) is part of the designed process. It's a compromise to get this thing done at all.
I understand that.
We run 6 tests for every staging project - all on x86_64, we run 103 for Factory. And we already track 16 of them as known failures to get an update out at all. In a perfect world this would be 0, but lvm crashes the kernel, USB boot of live cds is broken, ...
I.e. to get 0928 out, I had to accept a broken lxde - even though libfm went into 1001 and the next snapshot will most likely have a fixed lxde again.
Are you referring to the impracticality of adding more tests on the staging projects?
The whole process is *allowed* to fail - that it failed in the week we had one of the most problematic security problem in UNIX is unfortunate, but that's what security update repos are for.
And that's going to happen again in all likelihood, that's my point. Occurrences like these are to be expected. Unlikely, but expectable. But as there's already an update repo and this event will probably make it so that it's used with less hesitation, there's nothing else I can say. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org