summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005833.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005833.html')
-rw-r--r--zarb-ml/mageia-dev/2011-June/005833.html132
1 files changed, 132 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005833.html b/zarb-ml/mageia-dev/2011-June/005833.html
new file mode 100644
index 000000000..6c9598490
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-June/005833.html
@@ -0,0 +1,132 @@
+<!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=%3C4DFD7B5C.8050806%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="005845.html">
+ <LINK REL="Next" HREF="005373.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Missing packages in Mageia 1. How to backport?</H1>
+ <B>andre999</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=%3C4DFD7B5C.8050806%40laposte.net%3E"
+ TITLE="[Mageia-dev] Missing packages in Mageia 1. How to backport?">andr55 at laposte.net
+ </A><BR>
+ <I>Sun Jun 19 06:30:20 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="005845.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process)
+</A></li>
+ <LI>Next message: <A HREF="005373.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#5833">[ date ]</a>
+ <a href="thread.html#5833">[ thread ]</a>
+ <a href="subject.html#5833">[ subject ]</a>
+ <a href="author.html#5833">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Ahmad Samir a &#233;crit :
+&gt;<i>
+</I>&gt;<i> On 10 June 2011 13:44, Wolfgang Bornath&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">molch.b at googlemail.com</A>&gt; wrote:
+</I>&gt;&gt;<i> 2011/6/10 Michael Scherer&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>&gt;:
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> We have used backports in the past for that, and I see no reason to
+</I>&gt;&gt;&gt;<i> change that.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> If the problem is that backports were too buggy in the past, then we
+</I>&gt;&gt;&gt;<i> should fix backports process, not bypassing them.
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> And if we start by pushing new version in update, people will soon
+</I>&gt;&gt;&gt;<i> wonder why the new version of X is in updates, while the new version of
+</I>&gt;&gt;&gt;<i> Y is not, just because we didn't have X in release and Y was there.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Problem I see:
+</I>&gt;&gt;<i> So far (in Mandriva), example: we have used 2010.0/main/backports to
+</I>&gt;&gt;<i> offer new versions of software which had an older version in 2010/main
+</I>&gt;&gt;<i> but the newer version in 2010.1/main, or as the name says: backporting
+</I>&gt;&gt;<i> a newer version of a software from the current release to a previous
+</I>&gt;&gt;<i> release, as often used for Firefox.
+</I>&gt;<i>
+</I>&gt;<i> Firefox should always go to /updates, not backports, usually it has
+</I>&gt;<i> many sec fixed, so firefox and thunderbird are special cases.
+</I>
+I agree.
+And the same for other software which almost always has security fixes.
+(Of course we should enumerate these exceptions.)
+
+&gt;&gt;<i> For Mageia it means, /backports should hold backports of software
+</I>&gt;&gt;<i> which has an older version in 1/core but a newer version in cauldron.
+</I>&gt;&gt;<i> If we put new software (aka missing packages) in /backports and the
+</I>&gt;&gt;<i> user activates /backports he also runs the risk that existing packages
+</I>&gt;&gt;<i> of his stable installation will be replaced by real backports of newer
+</I>&gt;&gt;<i> versions, backported from Cauldron - which he may not want to do.
+</I>&gt;<i>
+</I>&gt;<i> Then he shouldn't use backports; but the point is if a totally new
+</I>&gt;<i> package, to Mageia 1, that never existed in core, is in backports, the
+</I>&gt;<i> user shouldn't see any regression with regard to that package as his
+</I>&gt;<i> experience with it before using backports is null, it didn't exist.
+</I>
+We should expect that users _selectively_ install from backports.
+That should be documented somewhere for users (if not already).
+It seems almost a case for never activating the backport repositories -- considering that backports
+can be selected without those repositories activated.
+
+&gt;&gt;<i> I wonder why we do not put these &quot;missing packages&quot; in /testing and
+</I>&gt;&gt;<i> after a while in /core or /non-free or /tainted (wherever they
+</I>&gt;&gt;<i> belong). These packages are software which were supposed to be in
+</I>&gt;&gt;<i> /core or /non-free or /tainted, they were just forgotten|came too
+</I>&gt;&gt;<i> late|whatever for Mageia 1 release freeze.
+</I>&gt;<i>
+</I>&gt;<i> There will always be late packages, always. One example is a new
+</I>&gt;<i> version of foo that was released two days before Mageia's release, it
+</I>&gt;<i> won't be submitted through freeze, but will go to backports.
+</I>&gt;<i>
+</I>&gt;<i> IMHO, backports is way to offer &quot;late&quot; packages to user, whether
+</I>&gt;<i> they're new packages or newer versions of packages in
+</I>&gt;<i> core/nonfree/tainted, instead of the user installing them from 3rd
+</I>&gt;<i> party repos or having to build them himself (not all users are savvy
+</I>&gt;<i> with [re]building src.rpm's).
+</I>
+It's usually not strictly necessary to rebuild the rpm's, but it is certainly much nicer to install
+rpm's built for Mageia. Especially for less advanced users.
+And backports is where to put &quot;late&quot; packages.
+
+&gt;&gt;<i> --
+</I>&gt;&gt;<i> wobo
+</I>&gt;&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i>
+</I>
+--
+Andr&#233;
+</PRE>
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="005845.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process)
+</A></li>
+ <LI>Next message: <A HREF="005373.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#5833">[ date ]</a>
+ <a href="thread.html#5833">[ thread ]</a>
+ <a href="subject.html#5833">[ subject ]</a>
+ <a href="author.html#5833">[ 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>