summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016289.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016289.html')
-rw-r--r--zarb-ml/mageia-dev/2012-June/016289.html136
1 files changed, 136 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016289.html b/zarb-ml/mageia-dev/2012-June/016289.html
new file mode 100644
index 000000000..b521b7b7d
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-June/016289.html
@@ -0,0 +1,136 @@
+<!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=%3C201206081622.41169.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="016288.html">
+ <LINK REL="Next" HREF="016290.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=%3C201206081622.41169.stormi%40laposte.net%3E"
+ TITLE="[Mageia-dev] Backports policy clarification (and discussion)">stormi at laposte.net
+ </A><BR>
+ <I>Fri Jun 8 16:22:41 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="016288.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI>Next message: <A HREF="016290.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16289">[ date ]</a>
+ <a href="thread.html#16289">[ thread ]</a>
+ <a href="subject.html#16289">[ subject ]</a>
+ <a href="author.html#16289">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le vendredi 8 juin 2012 16:11:07, andre999 a &#233;crit :
+&gt;<i> Sander Lepik a &#233;crit :
+</I>&gt;<i> &gt; 08.06.2012 11:38, Samuel Verschelde kirjutas:
+</I>&gt;<i> &gt;&gt; I re-read the backports policy, and there's a part I think needs to be
+</I>&gt;<i> &gt;&gt; pointed out before people start to backport packages.
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; &quot;We need to ensure that upgrades never fail: cauldron must always have a
+</I>&gt;<i> &gt;&gt; higher version/release than in stable releases.&quot;
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; This statement is true, but implies more than what it says. It means
+</I>&gt;<i> &gt;&gt; that we can't backport a package for Mageia 1 with a higher version
+</I>&gt;<i> &gt;&gt; than what we have in Mageia 2 release (and updates?) media. And this,
+</I>&gt;<i> &gt;&gt; until we are able to take backports into account during upgrades.
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; Example :
+</I>&gt;<i> &gt;&gt; - Mageia 2 has wesnoth 1.10.2 in core/release
+</I>&gt;<i> &gt;&gt; - Mageia 1 can't get a higher version in its backports media
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; Do you all agree with my understanding of the policy ?
+</I>&gt;<i>
+</I>&gt;<i> I see your point.
+</I>&gt;<i> In most cases, a backport for mga1 would be essentially identical for
+</I>&gt;<i> mga2 (except package file name and corresponding changes in the spec file).
+</I>&gt;<i> It would only differ if dependancies differ, which I suspect is unlikely
+</I>&gt;<i> for wesnoth or most other games, for example.
+</I>&gt;<i> So this means that for a backport to mga1, we should first do one to mga2.
+</I>&gt;<i> This would more than likely be done at the same time by the same
+</I>&gt;<i> packager, so not much more work.
+</I>&gt;<i> The demand for backports to mga1 is not likely to be very high, and
+</I>&gt;<i> would depend on a willing packager.
+</I>
+I think you missed my point. If Mageia 1 &quot;backports&quot; has higher versions than
+Mageia 2 &quot;release&quot; (not backports), upgrade can fail because currently our
+tools do not take backports from the target release (mageia 2) into account
+when upgrading a distro.
+
+Samuel
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="016288.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI>Next message: <A HREF="016290.html">[Mageia-dev] Backports policy clarification (and discussion)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16289">[ date ]</a>
+ <a href="thread.html#16289">[ thread ]</a>
+ <a href="subject.html#16289">[ subject ]</a>
+ <a href="author.html#16289">[ 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>