summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005286.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005286.html')
-rw-r--r--zarb-ml/mageia-dev/2011-June/005286.html187
1 files changed, 187 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005286.html b/zarb-ml/mageia-dev/2011-June/005286.html
new file mode 100644
index 000000000..dfc8ae3e0
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-June/005286.html
@@ -0,0 +1,187 @@
+<!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=%3CBANLkTikn%3D668xKOY0Jt4qaBf2XpihjynKg%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="005278.html">
+ <LINK REL="Next" HREF="005322.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Missing packages in Mageia 1. How to backport?</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&In-Reply-To=%3CBANLkTikn%3D668xKOY0Jt4qaBf2XpihjynKg%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] Missing packages in Mageia 1. How to backport?">ahmadsamir3891 at gmail.com
+ </A><BR>
+ <I>Thu Jun 9 18:42:12 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="005278.html">[Mageia-dev] Missing packages in Mageia 1. How to backport?
+</A></li>
+ <LI>Next message: <A HREF="005322.html">[Mageia-dev] Missing packages in Mageia 1. How to backport?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5286">[ date ]</a>
+ <a href="thread.html#5286">[ thread ]</a>
+ <a href="subject.html#5286">[ subject ]</a>
+ <a href="author.html#5286">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On 9 June 2011 14:22, Oliver Burger &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">oliver.bgr at googlemail.com</A>&gt; wrote:
+&gt;<i> Dexter Morgan &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dmorganec at gmail.com</A>&gt; schrieb am 09.06.2011
+</I>&gt;<i>
+</I>&gt;&gt;<i> On Thu, Jun 9, 2011 at 11:54 AM, Colin Guthrie &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>&gt;
+</I>&gt;&gt;<i> wrote:
+</I>&gt;<i>
+</I>&gt;&gt;<i> &gt; I think updates would be the right place.
+</I>&gt;<i>
+</I>&gt;&gt;<i>
+</I>&gt;<i>
+</I>&gt;&gt;<i> Please no 3rd repo :)
+</I>&gt;<i>
+</I>&gt;&gt;<i> But i agree with you for updates for &quot;new&quot; packages ( no &quot;new&quot;
+</I>&gt;<i>
+</I>&gt;&gt;<i> versions ;) )
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> I would prefer using updates over backports as well. If we use backports we
+</I>&gt;<i> would get more problems then benefit (like people not having backports
+</I>&gt;<i> enabled or people having backports enabled and thus getting problems they
+</I>&gt;<i> can't handle e.g. with new kernels, graphic drivers and so on).
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> Perhaps we could upload them to updates/testing for a really short qa before
+</I>&gt;<i> moving them to updates/ ?
+</I>&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> Oliver
+</I>
+If it's pushed to /updates then it should be imported to the stable
+release SVN tree; note that at some point Cauldron could get a newer
+version than the one in /updates, and maybe it's not backportable, new
+deps, regressions... etc. But now if there's a bug in the version in
+the stable */updates, and it needs a patch, what are you gonna base
+the patch on if you submit directly from the Cauldron SVN checkout to
+*/updates, and the Cauldron package has already changed?
+
+But if new package can go directly to updates.. that doesn't look
+right to me, because at which point will &quot;new&quot; packages stop going to
+a stable release */updates? if it goes on and on, then we're talking
+about a semi-cauldron-like repo.
+
+Also note that a new package in Cauldron gets tested for a while
+(depending at which point it was imported during the release cycle),
+but if gets pushed to /updates and not backports (which is &quot;not
+supported&quot;), that testing period is short-circuited.
+
+Just my 0.002&#8364;
+
+--
+Ahmad Samir
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="005278.html">[Mageia-dev] Missing packages in Mageia 1. How to backport?
+</A></li>
+ <LI>Next message: <A HREF="005322.html">[Mageia-dev] Missing packages in Mageia 1. How to backport?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5286">[ date ]</a>
+ <a href="thread.html#5286">[ thread ]</a>
+ <a href="subject.html#5286">[ subject ]</a>
+ <a href="author.html#5286">[ 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>