diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005379.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005379.html | 192 |
1 files changed, 192 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005379.html b/zarb-ml/mageia-dev/2011-June/005379.html new file mode 100644 index 000000000..950e25072 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005379.html @@ -0,0 +1,192 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process) + </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%0A%20%28was%3A%20Finalizing%20update%20process%29&In-Reply-To=%3CBANLkTinx1Uuquea2GzE%2B7BtboYtgaWvwAQ%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005376.html"> + <LINK REL="Next" HREF="005826.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process)</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missing%20packages%20in%20Mageia%201.%20How%20to%20backport%3F%0A%20%28was%3A%20Finalizing%20update%20process%29&In-Reply-To=%3CBANLkTinx1Uuquea2GzE%2B7BtboYtgaWvwAQ%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process)">ahmadsamir3891 at gmail.com + </A><BR> + <I>Fri Jun 10 18:34:08 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005376.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI>Next message: <A HREF="005826.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5379">[ date ]</a> + <a href="thread.html#5379">[ thread ]</a> + <a href="subject.html#5379">[ subject ]</a> + <a href="author.html#5379">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 10 June 2011 13:44, Wolfgang Bornath <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">molch.b at googlemail.com</A>> wrote: +><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> +Firefox should always go to /updates, not backports, usually it has +many sec fixed, so firefox and thunderbird are special cases. + +><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> +Then he shouldn't use backports; but the point is if a totally new +package, to Mageia 1, that never existed in core, is in backports, the +user shouldn't see any regression with regard to that package as his +experience with it before using backports is null, it didn't exist. + +><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> +There will always be late packages, always. One example is a new +version of foo that was released two days before Mageia's release, it +won't be submitted through freeze, but will go to backports. + +IMHO, backports is way to offer "late" packages to user, whether +they're new packages or newer versions of packages in +core/nonfree/tainted, instead of the user installing them from 3rd +party repos or having to build them himself (not all users are savvy +with [re]building src.rpm's). + +><i> -- +</I>><i> wobo +</I>><i> +</I> + + +-- +Ahmad Samir +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005376.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI>Next message: <A HREF="005826.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5379">[ date ]</a> + <a href="thread.html#5379">[ thread ]</a> + <a href="subject.html#5379">[ subject ]</a> + <a href="author.html#5379">[ 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> |