diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005339.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005339.html | 182 |
1 files changed, 182 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005339.html b/zarb-ml/mageia-dev/2011-June/005339.html new file mode 100644 index 000000000..259cc2e42 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005339.html @@ -0,0 +1,182 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Missing packages in Mageia 1. How to backport? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missing%20packages%20in%20Mageia%201.%20How%20to%20backport%3F&In-Reply-To=%3C4DF206C2.3030700%40mageia.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005336.html"> + <LINK REL="Next" HREF="005343.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Missing packages in Mageia 1. How to backport?</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missing%20packages%20in%20Mageia%201.%20How%20to%20backport%3F&In-Reply-To=%3C4DF206C2.3030700%40mageia.org%3E" + TITLE="[Mageia-dev] Missing packages in Mageia 1. How to backport?">tmb at mageia.org + </A><BR> + <I>Fri Jun 10 13:57:54 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005336.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process) +</A></li> + <LI>Next message: <A HREF="005343.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5339">[ date ]</a> + <a href="thread.html#5339">[ thread ]</a> + <a href="subject.html#5339">[ subject ]</a> + <a href="author.html#5339">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Wolfgang Bornath skrev 10.6.2011 14:44: +><i> 2011/6/10 Michael Scherer<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>>: +</I>>><i> +</I>>><i> We have used backports in the past for that, and I see no reason to +</I>>><i> change that. +</I>>><i> +</I>>><i> If the problem is that backports were too buggy in the past, then we +</I>>><i> should fix backports process, not bypassing them. +</I>>><i> +</I>>><i> And if we start by pushing new version in update, people will soon +</I>>><i> wonder why the new version of X is in updates, while the new version of +</I>>><i> Y is not, just because we didn't have X in release and Y was there. +</I>><i> +</I>><i> Problem I see: +</I>><i> So far (in Mandriva), example: we have used 2010.0/main/backports to +</I>><i> offer new versions of software which had an older version in 2010/main +</I>><i> but the newer version in 2010.1/main, or as the name says: backporting +</I>><i> a newer version of a software from the current release to a previous +</I>><i> release, as often used for Firefox. +</I>><i> +</I>><i> For Mageia it means, /backports should hold backports of software +</I>><i> which has an older version in 1/core but a newer version in cauldron. +</I>><i> If we put new software (aka missing packages) in /backports and the +</I>><i> user activates /backports he also runs the risk that existing packages +</I>><i> of his stable installation will be replaced by real backports of newer +</I>><i> versions, backported from Cauldron - which he may not want to do. +</I>><i> +</I>><i> I wonder why we do not put these "missing packages" in /testing and +</I>><i> after a while in /core or /non-free or /tainted (wherever they +</I>><i> belong). These packages are software which were supposed to be in +</I>><i> /core or /non-free or /tainted, they were just forgotten|came too +</I>><i> late|whatever for Mageia 1 release freeze. +</I>><i> +</I> +well, media/*/release tree is frozen, so _nothing_ new goes in there. + +So the path would then be */updates_testing -> */updates _if_ we decide +that's the way to go... + +Problem is that a "missing" package introcuced in updates also can +introduce regressions with wrong obsoletes/provides or %pre/%post scripts. + +So it has to go through the same qa as the rest of the stuff heading for +*/updates + +So question becomes, do we have enough qa/security people to make it work ? + +And if we introduce "filtering" on what goes in and what does not, +then who decides ? + +-- +Thomas + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005336.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process) +</A></li> + <LI>Next message: <A HREF="005343.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5339">[ date ]</a> + <a href="thread.html#5339">[ thread ]</a> + <a href="subject.html#5339">[ subject ]</a> + <a href="author.html#5339">[ 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> |