diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-July/017224.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-1be510f9529cb082f802408b472a77d074b394c0.tar archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2 archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz archives-1be510f9529cb082f802408b472a77d074b394c0.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2012-July/017224.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-July/017224.html | 121 |
1 files changed, 121 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-July/017224.html b/zarb-ml/mageia-dev/2012-July/017224.html new file mode 100644 index 000000000..ec5734afc --- /dev/null +++ b/zarb-ml/mageia-dev/2012-July/017224.html @@ -0,0 +1,121 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Security%20updates%20-%20Help%20needed%20%28also%0A%09forgot%09avidemux%20and%20gstreamer0.10-ffmpeg%29&In-Reply-To=%3C20120708114936.GT21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="017202.html"> + <LINK REL="Next" HREF="017227.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)</H1> + <B>nicolas vigier</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Security%20updates%20-%20Help%20needed%20%28also%0A%09forgot%09avidemux%20and%20gstreamer0.10-ffmpeg%29&In-Reply-To=%3C20120708114936.GT21938%40mars-attacks.org%3E" + TITLE="[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)">boklm at mars-attacks.org + </A><BR> + <I>Sun Jul 8 13:49:36 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="017202.html">[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg) +</A></li> + <LI>Next message: <A HREF="017227.html">[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17224">[ date ]</a> + <a href="thread.html#17224">[ thread ]</a> + <a href="subject.html#17224">[ subject ]</a> + <a href="author.html#17224">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Fri, 06 Jul 2012, Claire Robinson wrote: + +><i> +</I>><i> This has nothing to do with being rude. +</I>><i> +</I>><i> As I said previously, this is being blown wildly out of proportion. In +</I>><i> reality it centres around one packager and two bugs. In both these bugs the +</I>><i> packager expected QA to validate updates where one was an xinetd service +</I>><i> which expressly stated it was disabled by default but in actual fact was +</I>><i> enabled and in the other a mailing list with a web interface which simply +</I>><i> couldn't work in it's default configuration. +</I>><i> +</I>><i> What it being thrown at us is that we are unreasonably expecting every +</I>><i> single little bug to be fixed without any common and need to make drastic +</I>><i> changes to our policies. +</I>><i> +</I>><i> We attended the packager meeting on Wednesday to respond to this and +</I>><i> discuss it. At the meeting it was agreed that we had not changed the way we +</I>><i> have been doing things since day one and that the right way forward was to +</I>><i> continue doing what we were doing, with both packagers and QA using common +</I>><i> sense. +</I> +The argument you keep repeating about your opinion being common sense is +insulting for the people who do not have the same opinion. You could at +least admit that other people may have a different point of view, +without saying they don't have common sense. + +><i> The following day the same far fetched accusations are thrown at us again, +</I>><i> now escalated to the ML, suggesting we caused a months delay and suggesting +</I>><i> a solution to the accusation being we begin to 'rubber stamp' security +</I>><i> updates regardless of if they actually work or not or an internet facing +</I>><i> service which says it's disabled is actually not so. +</I>><i> +</I>><i> In both cases there were simple ways to fix them. In one it was just to +</I>><i> alter the description (2 minutes) so it didn't say it was disabled and in +</I>><i> the other it was either to add a suggest or alter the default configuration +</I>><i> so it didn't require the missing suggest (2 minutes). +</I>><i> +</I>><i> We have to use common sense in QA and only ask that, to avoid all this +</I>><i> unpleasantness in the future, common sense is used by the packager also. +</I>><i> All this is a reaction to 4 minutes of additional work. That is not common +</I>><i> sense to me. +</I> +Of course if you considere packagers should blindly apply any change +requested without any possible discussion because you decided it's common +sense, it only takes 2 minutes. But conscientious packagers usually try +to understand the problem they are fixing, think about the potential +problems introduced by the change, look at the alternative solutions, +etc ... + +Also adding new suggests or changing default configuration should be +avoided in updates. The new suggest will be installed even for people +who already have a working setup. And the configuration file will be +updated for the people who did not need to modify it and don't +necessarily expect this kind of change in an update. + +><i> If we're expected to validate updates in the state these two bugs reached +</I>><i> us then we may as well not be here at all. +</I> +The goal of updates testing is to find regressions, not to do extensive +testing to find new unrelated bugs. This kind of testing can be useful, +but not as part of updates testing, and preferably on Cauldron. + +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="017202.html">[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg) +</A></li> + <LI>Next message: <A HREF="017227.html">[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17224">[ date ]</a> + <a href="thread.html#17224">[ thread ]</a> + <a href="subject.html#17224">[ subject ]</a> + <a href="author.html#17224">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |