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/016300.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/016300.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016300.html | 139 |
1 files changed, 139 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016300.html b/zarb-ml/mageia-dev/2012-June/016300.html new file mode 100644 index 000000000..3332aecb7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016300.html @@ -0,0 +1,139 @@ +<!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=%3C201206082040.04165.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="016291.html"> + <LINK REL="Next" HREF="016301.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=%3C201206082040.04165.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] Backports policy clarification (and discussion)">stormi at laposte.net + </A><BR> + <I>Fri Jun 8 20:40:04 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016291.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI>Next message: <A HREF="016301.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16300">[ date ]</a> + <a href="thread.html#16300">[ thread ]</a> + <a href="subject.html#16300">[ subject ]</a> + <a href="author.html#16300">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le vendredi 8 juin 2012 16:58:24, andre999 a écrit : +><i> Samuel Verschelde a écrit : +</I>><i> > Le vendredi 8 juin 2012 16:11:07, andre999 a écrit : +</I>><i> >> Sander Lepik a écrit : +</I>><i> >>> 08.06.2012 11:38, Samuel Verschelde kirjutas: +</I>><i> >>>> I re-read the backports policy, and there's a part I think needs to be +</I>><i> >>>> pointed out before people start to backport packages. +</I>><i> >>>> +</I>><i> >>>> "We need to ensure that upgrades never fail: cauldron must always have +</I>><i> >>>> a higher version/release than in stable releases." +</I>><i> >>>> +</I>><i> >>>> This statement is true, but implies more than what it says. It means +</I>><i> >>>> that we can't backport a package for Mageia 1 with a higher version +</I>><i> >>>> than what we have in Mageia 2 release (and updates?) media. And this, +</I>><i> >>>> until we are able to take 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> >> I see your point. +</I>><i> >> In most cases, a backport for mga1 would be essentially identical for +</I>><i> >> mga2 (except package file name and corresponding changes in the spec +</I>><i> >> file). It would only differ if dependancies differ, which I suspect is +</I>><i> >> unlikely for wesnoth or most other games, for example. +</I>><i> >> So this means that for a backport to mga1, we should first do one to +</I>><i> >> mga2. This would more than likely be done at the same time by the same +</I>><i> >> packager, so not much more work. +</I>><i> >> The demand for backports to mga1 is not likely to be very high, and +</I>><i> >> would depend on a willing packager. +</I>><i> > +</I>><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> > Samuel +</I>><i> +</I>><i> But wouldn't current tools update backports if backports are active ? +</I> +No, they wouldn't :) +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016291.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI>Next message: <A HREF="016301.html">[Mageia-dev] Backports policy clarification (and discussion) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16300">[ date ]</a> + <a href="thread.html#16300">[ thread ]</a> + <a href="subject.html#16300">[ subject ]</a> + <a href="author.html#16300">[ 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> |