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/016299.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/016299.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016299.html | 136 |
1 files changed, 136 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016299.html b/zarb-ml/mageia-dev/2012-June/016299.html new file mode 100644 index 000000000..7e5bb21d1 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016299.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=%3C201206082038.43568.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="016298.html"> + <LINK REL="Next" HREF="016304.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=%3C201206082038.43568.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] Backports policy clarification (and discussion)">stormi at laposte.net + </A><BR> + <I>Fri Jun 8 20:38:43 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016298.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI>Next message: <A HREF="016304.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16299">[ date ]</a> + <a href="thread.html#16299">[ thread ]</a> + <a href="subject.html#16299">[ subject ]</a> + <a href="author.html#16299">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le vendredi 8 juin 2012 20:20:54, David W. Hodgins a écrit : +><i> On Fri, 08 Jun 2012 10:22:41 -0400, Samuel Verschelde <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>> +</I>wrote: +><i> > I think you missed my point. If Mageia 1 "backports" has higher versions +</I>><i> > than Mageia 2 "release" (not backports), upgrade can fail because +</I>><i> > currently our tools do not take backports from the target release +</I>><i> > (mageia 2) into account when upgrading a distro. +</I>><i> +</I>><i> In the upgrade from Mandriva 2010.2 to Mageia 1, it was made clear, that +</I>><i> upgrading from a system with 2010.2 Backports was not supported. It may +</I>><i> work, but was not recommended. +</I>><i> +</I>><i> I think we should keep the same policy for the upgrade from Mageia 1 to 2. +</I>><i> I.E. Don't use backports if you are planning on later doing an upgrade, +</I>><i> rather then a clean install. +</I>><i> +</I>><i> That way, Mageia 1 users who want firefox 13 can get it, without us having +</I>><i> to replace the Mageia 2 iso images with an upgraded installer, that will +</I>><i> keep backports enabled for 2, if it was enabled for 1. +</I>><i> +</I>><i> Regards, Dave Hodgins +</I> +Again, this is not the policy we adopted. When we defined the backports policy +(together, although it seems most people are just discovering it now) we said +that we didn't want to have backports that don't work, break a system, or +prevent upgrade. + +However, I think that for DVD upgrade without internet access this is a +sensible option. But the upgrader should detect the situation itself, not hope +that the user will read somewhere in the release notes that it's not +supported. + +And there should be a way for those who have internet access to upgrade online +*with* backports too. + +Samuel +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016298.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI>Next message: <A HREF="016304.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16299">[ date ]</a> + <a href="thread.html#16299">[ thread ]</a> + <a href="subject.html#16299">[ subject ]</a> + <a href="author.html#16299">[ 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> |