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/016316.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/016316.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016316.html | 141 |
1 files changed, 141 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016316.html b/zarb-ml/mageia-dev/2012-June/016316.html new file mode 100644 index 000000000..bdc9a72c9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016316.html @@ -0,0 +1,141 @@ +<!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=%3C4FD3085A.7050003%40eesti.ee%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016311.html"> + <LINK REL="Next" HREF="016319.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports policy clarification (and discussion)</H1> + <B>Sander Lepik</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=%3C4FD3085A.7050003%40eesti.ee%3E" + TITLE="[Mageia-dev] Backports policy clarification (and discussion)">sander.lepik at eesti.ee + </A><BR> + <I>Sat Jun 9 10:24:58 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016311.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI>Next message: <A HREF="016319.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16316">[ date ]</a> + <a href="thread.html#16316">[ thread ]</a> + <a href="subject.html#16316">[ subject ]</a> + <a href="author.html#16316">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>08.06.2012 11:38, Samuel Verschelde kirjutas: +><i> I re-read the backports policy, and there's a part I think needs to be pointed +</I>><i> out before people start to backport packages. +</I>><i> +</I>><i> "We need to ensure that upgrades never fail: cauldron must always have a +</I>><i> higher version/release than in stable releases." +</I>><i> +</I>><i> This statement is true, but implies more than what it says. It means that we +</I>><i> can't backport a package for Mageia 1 with a higher version than what we have +</I>><i> in Mageia 2 release (and updates?) media. And this, until we are able to take +</I>><i> backports into account during upgrades. +</I>><i> +</I>><i> Example : +</I>><i> - Mageia 2 has wesnoth 1.10.2 in core/release +</I>><i> - Mageia 1 can't get a higher version in its backports media +</I>><i> +</I>><i> Do you all agree with my understanding of the policy ? +</I>><i> +</I>><i> This is a serious limitation to our ability to backport to Mageia (n-1) and +</I>><i> even to our ability to provide security fixes to backports there (will not +</I>><i> prevent it, but will prevent to do it by a version upgrade, which is the +</I>><i> common way to fix that kind of issue in backports). +</I>><i> +</I>><i> Maybe we shouldn't open backports for Mageia 1, and make sure upgrade to +</I>><i> Mageia 3 can take backports from Mageia 2 into account so that backports to +</I>><i> Mageia 2 are not stopped when Mageia 3 is released. Then we'll be safe. +</I>><i> +</I>><i> Samuel +</I>I reread the backports policy and there are two lines that make backporting from cauldron to +mga1 impossible: +* Backports can be cherry-picked (ie, enable backports, install, disable backports). +* We need to ensure that upgrades never fail + +In this regard we can support backports only with new version that is lower than the one on +next release. If we want to enable backports for mga1 we can backport only from mga2. Not +from cauldron. This way we can submit updates by submitting new backport into mga1 backports +repo (users would still have to update manually AFAIK). + +Any objections? + +-- +Sander + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016311.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI>Next message: <A HREF="016319.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16316">[ date ]</a> + <a href="thread.html#16316">[ thread ]</a> + <a href="subject.html#16316">[ subject ]</a> + <a href="author.html#16316">[ 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> |