summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016268.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016268.html')
-rw-r--r--zarb-ml/mageia-dev/2012-June/016268.html144
1 files changed, 144 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016268.html b/zarb-ml/mageia-dev/2012-June/016268.html
new file mode 100644
index 000000000..4b0ee2789
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-June/016268.html
@@ -0,0 +1,144 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Backports policy clarification (and discussion)
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C201206081051.52086.stormi%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="016267.html">
+ <LINK REL="Next" HREF="016271.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Backports policy clarification (and discussion)</H1>
+ <B>Samuel Verschelde</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C201206081051.52086.stormi%40laposte.net%3E"
+ TITLE="[Mageia-dev] Backports policy clarification (and discussion)">stormi at laposte.net
+ </A><BR>
+ <I>Fri Jun 8 10:51:52 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="016267.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI>Next message: <A HREF="016271.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16268">[ date ]</a>
+ <a href="thread.html#16268">[ thread ]</a>
+ <a href="subject.html#16268">[ subject ]</a>
+ <a href="author.html#16268">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le vendredi 8 juin 2012 10:49:42, Sander Lepik a &#233;crit :
+&gt;<i> 08.06.2012 11:38, Samuel Verschelde kirjutas:
+</I>&gt;<i> &gt; I re-read the backports policy, and there's a part I think needs to be
+</I>&gt;<i> &gt; pointed out before people start to backport packages.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; &quot;We need to ensure that upgrades never fail: cauldron must always have a
+</I>&gt;<i> &gt; higher version/release than in stable releases.&quot;
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; This statement is true, but implies more than what it says. It means that
+</I>&gt;<i> &gt; we can't backport a package for Mageia 1 with a higher version than what
+</I>&gt;<i> &gt; we have in Mageia 2 release (and updates?) media. And this, until we are
+</I>&gt;<i> &gt; able to take backports into account during upgrades.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Example :
+</I>&gt;<i> &gt; - Mageia 2 has wesnoth 1.10.2 in core/release
+</I>&gt;<i> &gt; - Mageia 1 can't get a higher version in its backports media
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Do you all agree with my understanding of the policy ?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; This is a serious limitation to our ability to backport to Mageia (n-1)
+</I>&gt;<i> &gt; and even to our ability to provide security fixes to backports there
+</I>&gt;<i> &gt; (will not prevent it, but will prevent to do it by a version upgrade,
+</I>&gt;<i> &gt; which is the common way to fix that kind of issue in backports).
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Maybe we shouldn't open backports for Mageia 1, and make sure upgrade to
+</I>&gt;<i> &gt; Mageia 3 can take backports from Mageia 2 into account so that backports
+</I>&gt;<i> &gt; to Mageia 2 are not stopped when Mageia 3 is released. Then we'll be
+</I>&gt;<i> &gt; safe.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Samuel
+</I>&gt;<i>
+</I>&gt;<i> I think backports should be open until new stable is released. So we should
+</I>&gt;<i> not open backports for mga1 and when mga2 is released then backports for
+</I>&gt;<i> mga2 will be closed. It's the only way we can manage upgrades with our
+</I>&gt;<i> current packager resources.
+</I>&gt;<i>
+</I>
+And what about security issues and bugs to those backports? It will use more
+packager ressource to patch backports than to provide newer versions, won't
+it?
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="016267.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI>Next message: <A HREF="016271.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16268">[ date ]</a>
+ <a href="thread.html#16268">[ thread ]</a>
+ <a href="subject.html#16268">[ subject ]</a>
+ <a href="author.html#16268">[ 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>