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-June/016768.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016768.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016768.html | 151 |
1 files changed, 151 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016768.html b/zarb-ml/mageia-dev/2012-June/016768.html new file mode 100644 index 000000000..1a7a37e12 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016768.html @@ -0,0 +1,151 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] bug 2317 revisited: --update option should behave like --search-media + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3C4FE5024E.7050304%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016766.html"> + <LINK REL="Next" HREF="016783.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3C4FE5024E.7050304%40laposte.net%3E" + TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">andre999mga at laposte.net + </A><BR> + <I>Sat Jun 23 01:39:58 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016766.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media +</A></li> + <LI>Next message: <A HREF="016783.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16768">[ date ]</a> + <a href="thread.html#16768">[ thread ]</a> + <a href="subject.html#16768">[ subject ]</a> + <a href="author.html#16768">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>AL13N a écrit : +><i> Op vrijdag 22 juni 2012 18:14:50 schreef David W. Hodgins: +</I>><i> +</I>>><i> On Fri, 22 Jun 2012 14:11:58 -0400, AL13N<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>> wrote: +</I>>><i> +</I>>>><i> ok, i guess when people said, supported, i immediately assumed full +</I>>>><i> support. that kind of misled me. +</I>>>><i> +</I>>><i> My understanding, is that backports will have minimal testing. +</I>>><i> +</I>>><i> We ensure the backport will install, on a system that currently +</I>>><i> only has release + updates, and that the basic functions of the +</I>>><i> package work, where it's possible for us to test. +</I>>><i> +</I>>><i> We cannot possibly test every possible combination of selected +</I>>><i> backports, and will not attempt to. +</I>>><i> +</I>>><i> What I don't want to see, which I did with Mandriva backports, +</I>>><i> is cases where unsigned rpm packages were in the repositories, +</I>>><i> or installation required the use of --allow-nodeps or --allow-force, +</I>>><i> due to file conflicts with release or updates packages. Those +</I>>><i> problems were rare, but often enough, that I wouldn't let the end +</I>>><i> users I support install backports themselves. +</I>>><i> +</I>><i> well, imho even with this testing it's still possible, allthough likely rarer +</I>><i> that the user would have to use these or any other manual procedures. even +</I>><i> with updates. +</I>><i> +</I>><i> (unsigned rpms should be caught by the build process, even though it still +</I>><i> sometimes fails for reasons unbeknownst) +</I>><i> +</I>><i> in any case, i don't think of this as supported and won't suggest backports to +</I>><i> any user who doesn't have the necessary skills to fix it himself. +</I>><i> +</I> +Note that it depends what we mean by support. +In terms of support that would be provided by an expensive commercial +entity that specializes in support, some might argue that our release +packages aren't supported. + +For backports, there is the understanding that in addition to being +tested by QA (after initial packager and end-user tests), that the +packager would commit to providing security updates as necessary. This +is much more than "no support at all", as happened with mdv backports. + +Considering that each backport will be a leaf package (or exceptionally, +a leaf group of related packages), any breakage that would occur should +only affect the backport (or backport group) in question. + +In terms of updates to backports, which I think is a good idea for +security fixes, any conflicts introduced should be rare. In those +cases, indeed updates could fail. But I don't think it is much more +likely than with packages from release or update repos. + +Note that an end-user installing the occasional backport, to provide a +specific function desired, should not generally cause any problems. +Even for an end-user with minimal skills. As long as the user +understands that backports have a lower level of support. We have the +discuss list and the forum to help the end-user in the case of problems. + +In sum, I like the idea of saying "tested by QA", as Claire proposed, +which suggests the lower level of support we propose for backports. + +My 2 cents :) + +-- +André + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016766.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media +</A></li> + <LI>Next message: <A HREF="016783.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16768">[ date ]</a> + <a href="thread.html#16768">[ thread ]</a> + <a href="subject.html#16768">[ subject ]</a> + <a href="author.html#16768">[ 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> |