summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016311.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016311.html')
-rw-r--r--zarb-ml/mageia-dev/2012-June/016311.html170
1 files changed, 170 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016311.html b/zarb-ml/mageia-dev/2012-June/016311.html
new file mode 100644
index 000000000..9e4ac2dd7
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-June/016311.html
@@ -0,0 +1,170 @@
+<!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=%3Cg89ba9-arf.ln1%40psd.motzarella.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="016317.html">
+ <LINK REL="Next" HREF="016316.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Backports policy clarification (and discussion)</H1>
+ <B>blind Pete</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=%3Cg89ba9-arf.ln1%40psd.motzarella.org%3E"
+ TITLE="[Mageia-dev] Backports policy clarification (and discussion)">0123peter at gmail.com
+ </A><BR>
+ <I>Sat Jun 9 09:06:22 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="016317.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI>Next message: <A HREF="016316.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16311">[ date ]</a>
+ <a href="thread.html#16311">[ thread ]</a>
+ <a href="subject.html#16311">[ subject ]</a>
+ <a href="author.html#16311">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Samuel Verschelde wrote:
+
+&gt;<i> I re-read the backports policy, and there's a part I think needs to be
+</I>&gt;<i> pointed out before people start to backport packages.
+</I>
+I haven't, so if I get things badly wrong don't hesitate to tell me.
+
+&gt;<i> &quot;We need to ensure that upgrades never fail: cauldron must always have a
+</I>&gt;<i> higher version/release than in stable releases.&quot;
+</I>&gt;<i>
+</I>&gt;<i> This statement is true, but implies more than what it says. It means that
+</I>&gt;<i> we can't backport a package for Mageia 1 with a higher version than what
+</I>&gt;<i> we have in Mageia 2 release (and updates?) media. And this, until we are
+</I>&gt;<i> able to take backports into account during upgrades.
+</I>&gt;<i>
+</I>&gt;<i> Example :
+</I>&gt;<i> - Mageia 2 has wesnoth 1.10.2 in core/release
+</I>&gt;<i> - Mageia 1 can't get a higher version in its backports media
+</I>&gt;<i>
+</I>&gt;<i> Do you all agree with my understanding of the policy ?
+</I>
+No. Well assuming that the backports policy is sane, then no.
+
+- Mageia 1 can not get a higher version into _updates_ until
+the new version (or an even higher one) has made its way into
+Mageia 2 _updates_.
+
+- Mageia 1 can not get a higher version into _backports_ until
+the new version (or an even higher one) has made its way into
+Mageia 2 _backports_.
+
+&gt;<i> This is a serious limitation to our ability to backport to Mageia (n-1)
+</I>&gt;<i> and even to our ability to provide security fixes to backports there (will
+</I>&gt;<i> not prevent it, but will prevent to do it by a version upgrade, which is
+</I>&gt;<i> the common way to fix that kind of issue in backports).
+</I>
+I don't see it.
+
+Most backports will have a version not higher than the which
+is provided by the next release and so will just not be a problem.
+
+Even in the *very* strange situation that the back ported package has a
+version number that is higher than that of the next release it is
+workable, all that is needed is the requirement that backports are
+not made available to release N before they are made available to
+release N+1 (Cauldron counts as a release) and that backport media
+be available at upgrade time.
+
+&gt;<i> Maybe we shouldn't open backports for Mageia 1, and make sure upgrade to
+</I>&gt;<i> Mageia 3 can take backports from Mageia 2 into account so that backports
+</I>&gt;<i> to Mageia 2 are not stopped when Mageia 3 is released. Then we'll be safe.
+</I>&gt;<i>
+</I>&gt;<i> Samuel
+</I>
+Extreme hypothetical example:
+
+Cauldron Core has long term support FF 29 and Cauldron Backports
+has this week's official release of FF 41.
+
+Mageia 5 gets released with Core and Core Backports. Sensible
+users get the long term support version. Insane fools who are
+trying to use the notoriously broken FF 35 get FF 41 (which is
+broken in a different way).
+
+--
+blind Pete
+Sig goes here...
+
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="016317.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI>Next message: <A HREF="016316.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16311">[ date ]</a>
+ <a href="thread.html#16311">[ thread ]</a>
+ <a href="subject.html#16311">[ subject ]</a>
+ <a href="author.html#16311">[ 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>