<!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=%3C201206081038.06735.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="016441.html">
<LINK REL="Next" HREF="016267.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=%3C201206081038.06735.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] Backports policy clarification (and discussion)">stormi at laposte.net
</A><BR>
<I>Fri Jun 8 10:38:06 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016441.html">[Mageia-dev] Proposed Feature:Backports_update_applet
</A></li>
<LI>Next message: <A HREF="016267.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16265">[ date ]</a>
<a href="thread.html#16265">[ thread ]</a>
<a href="subject.html#16265">[ subject ]</a>
<a href="author.html#16265">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>I re-read the backports policy, and there's a part I think needs to be pointed
out before people start to backport packages.
"We need to ensure that upgrades never fail: cauldron must always have a
higher version/release than in stable releases."
This statement is true, but implies more than what it says. It means that we
can't backport a package for Mageia 1 with a higher version than what we have
in Mageia 2 release (and updates?) media. And this, until we are able to take
backports into account during upgrades.
Example :
- Mageia 2 has wesnoth 1.10.2 in core/release
- Mageia 1 can't get a higher version in its backports media
Do you all agree with my understanding of the policy ?
This is a serious limitation to our ability to backport to Mageia (n-1) and
even to our ability to provide security fixes to backports there (will not
prevent it, but will prevent to do it by a version upgrade, which is the
common way to fix that kind of issue in backports).
Maybe we shouldn't open backports for Mageia 1, and make sure upgrade to
Mageia 3 can take backports from Mageia 2 into account so that backports to
Mageia 2 are not stopped when Mageia 3 is released. Then we'll be safe.
Samuel
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016441.html">[Mageia-dev] Proposed Feature:Backports_update_applet
</A></li>
<LI>Next message: <A HREF="016267.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16265">[ date ]</a>
<a href="thread.html#16265">[ thread ]</a>
<a href="subject.html#16265">[ subject ]</a>
<a href="author.html#16265">[ 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>