diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006141.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006141.html | 116 |
1 files changed, 116 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006141.html b/zarb-ml/mageia-dev/2011-June/006141.html new file mode 100644 index 000000000..ca1ee6771 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006141.html @@ -0,0 +1,116 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Backports policy proposal + </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%20proposal&In-Reply-To=%3C4E0B7AA4.6060801%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006087.html"> + <LINK REL="Next" HREF="006004.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports policy proposal</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20proposal&In-Reply-To=%3C4E0B7AA4.6060801%40laposte.net%3E" + TITLE="[Mageia-dev] Backports policy proposal">andr55 at laposte.net + </A><BR> + <I>Wed Jun 29 21:19:00 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006087.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI>Next message: <A HREF="006004.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6141">[ date ]</a> + <a href="thread.html#6141">[ thread ]</a> + <a href="subject.html#6141">[ subject ]</a> + <a href="author.html#6141">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Michael Scherer a écrit : +><i> Le lundi 27 juin 2011 à 21:42 -0400, andre999 a écrit : +</I>>><i> Michael Scherer a écrit : +</I>>>><i> +</I>>>><i> Le vendredi 24 juin 2011 à 16:20 -0400, andre999 a écrit : +</I>>>>><i> Michael Scherer a écrit : +</I>>><i> +</I>>><i> [...] +</I>>><i> +</I>>>>>><i> - cannot be backported if the package was just created and is thus basically untested in cauldron +</I>>>>><i> +</I>>>>><i> What about corner cases where a potential backport is incompatible with changes introduced in +</I>>>>><i> cauldron ? Should we leave such packages to third parties ? (I would tend to say yes.) +</I>>>><i> +</I>>>><i> Give a more precise example. +</I>>><i> +</I>>><i> Suppose leaf package fooa depends on foob. foob is part of the current release. +</I>>><i> Cauldron replaces foob with fooc. fooa is incompatible with fooc. +</I>><i> +</I>><i> Then why do we replace foob by it in the first place if this break fooa ? +</I> +(see below) + +>><i> fooa is requested by some users, and future versions of fooa are intended to be +</I>>><i> compatible with fooc. +</I>>><i> In this case, even though it wouldn't be testable in cauldron, it could be tested in +</I>>><i> backports-testing, and I think it could be a good idea to allow it. +</I>>><i> +</I>>><i> Even if fooc compatibility wouldn't be available for the next Mageia release, a user +</I>>><i> could avoid updating for a release in order to keep using fooa. +</I>>><i> However, if there were no intention to make fooa compatible with fooc, maybe it should +</I>>><i> be denied. +</I>><i> +</I>><i> The example is bogus. If we have fooa in the distro and we upload fooc +</I>><i> that break it, then we have to fix the breakage as a priority. Usually, +</I>><i> that would be having foob and fooc as parallel installablable. +</I> +The idea is that fooa is not in release, but is compatible with release, and not with +cauldron. (More details below.) + +><i> Anyway, the question is "how often does it" happens ? Because "it may +</I>><i> happen" is not a justification" if in practice, it never happen. And not +</I>><i> having a backport is not the end of the world so unless the problem is +</I>><i> quite frequent ( and so far, this one is far from being frequent , +</I>><i> especially since it is based on a wrong supposition in the first part ), +</I>><i> I do not think this would be blocking. +</I> +Often enough there will be changes in cauldron to newer packages not entirely compatible +with the older ones they are replacing. And other existing packages are dependant on +them, so they have to be fixed in cauldron. +Backport requests could be compatible with release but not cauldron. I wouldn't expect +that to be frequent, but such requests have already happened. +In some cases the updates for compatibility from upstream could just be late in coming. + +The question is, should we allow such backports under certain circumstances ? +I'm not necessarily saying yes. +Maybe we should say not for now, to be reviewed later ? + +-- +André +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006087.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI>Next message: <A HREF="006004.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6141">[ date ]</a> + <a href="thread.html#6141">[ thread ]</a> + <a href="subject.html#6141">[ subject ]</a> + <a href="author.html#6141">[ 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> |