diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005324.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005324.html | 207 |
1 files changed, 207 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005324.html b/zarb-ml/mageia-dev/2011-June/005324.html new file mode 100644 index 000000000..a1909623b --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005324.html @@ -0,0 +1,207 @@ +<!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=%3C201106101152.51414.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005322.html"> + <LINK REL="Next" HREF="005326.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Missing packages in Mageia 1. How to backport?</H1> + <B>Samuel Verschelde</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=%3C201106101152.51414.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] Missing packages in Mageia 1. How to backport?">stormi at laposte.net + </A><BR> + <I>Fri Jun 10 11:52:51 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005322.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI>Next message: <A HREF="005326.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5324">[ date ]</a> + <a href="thread.html#5324">[ thread ]</a> + <a href="subject.html#5324">[ subject ]</a> + <a href="author.html#5324">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> +Le vendredi 10 juin 2011 10:56:35, Colin Guthrie a écrit : +><i> 'Twas brillig, and Ahmad Samir at 09/06/11 17:42 did gyre and gimble: +</I>><i> > On 9 June 2011 14:22, Oliver Burger <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">oliver.bgr at googlemail.com</A>> wrote: +</I>><i> >> Dexter Morgan <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dmorganec at gmail.com</A>> schrieb am 09.06.2011 +</I>><i> >> +</I>><i> >>> On Thu, Jun 9, 2011 at 11:54 AM, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> +</I>><i> >>> +</I>><i> >>> wrote: +</I>><i> >>>> I think updates would be the right place. +</I>><i> >>> +</I>><i> >>> Please no 3rd repo :) +</I>><i> >>> +</I>><i> >>> But i agree with you for updates for "new" packages ( no "new" +</I>><i> >>> +</I>><i> >>> versions ;) ) +</I>><i> >> +</I>><i> >> I would prefer using updates over backports as well. If we use backports +</I>><i> >> we would get more problems then benefit (like people not having +</I>><i> >> backports enabled or people having backports enabled and thus getting +</I>><i> >> problems they can't handle e.g. with new kernels, graphic drivers and +</I>><i> >> so on). +</I>><i> >> +</I>><i> >> +</I>><i> >> Perhaps we could upload them to updates/testing for a really short qa +</I>><i> >> before moving them to updates/ ? +</I>><i> >> +</I>><i> >> +</I>><i> >> Oliver +</I>><i> > +</I>><i> > If it's pushed to /updates then it should be imported to the stable +</I>><i> > release SVN tree; note that at some point Cauldron could get a newer +</I>><i> > version than the one in /updates, and maybe it's not backportable, new +</I>><i> > deps, regressions... etc. But now if there's a bug in the version in +</I>><i> > the stable */updates, and it needs a patch, what are you gonna base +</I>><i> > the patch on if you submit directly from the Cauldron SVN checkout to +</I>><i> > */updates, and the Cauldron package has already changed? +</I>><i> > +</I>><i> > But if new package can go directly to updates.. that doesn't look +</I>><i> > right to me, because at which point will "new" packages stop going to +</I>><i> > a stable release */updates? if it goes on and on, then we're talking +</I>><i> > about a semi-cauldron-like repo. +</I>><i> +</I>><i> So just svn cp it to the /1/updates tree in svn and job's a good 'un. +</I>><i> (well svn cp is no longer just one step due to source separation, but +</I>><i> the principle is the same!). +</I>><i> +</I>><i> > Also note that a new package in Cauldron gets tested for a while +</I>><i> > (depending at which point it was imported during the release cycle), +</I>><i> > but if gets pushed to /updates and not backports (which is "not +</I>><i> > supported"), that testing period is short-circuited. +</I>><i> +</I>><i> Yeah but then the examples I've got so far are: +</I>><i> +</I>><i> * trac +</I>><i> * supybot +</I>><i> * supybot-Meetbot +</I>><i> * passwd-gen +</I>><i> * dd_rescue +</I>><i> +</I>><i> In all these cases, these are packages I use. I will be testing them on +</I>><i> that version of the distro. And when I don't use them every day, (e.g. +</I>><i> passwd-gen, dd_rescue), they are pretty standard, stable and standalone +</I>><i> apps. +</I>><i> +</I>><i> IMO we can over-analyse the "risk" factor here massive to the detriment +</I>><i> of the overall offering. +</I>><i> +</I>><i> Col +</I> +I agree with Colin here. + +Samuel + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005322.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI>Next message: <A HREF="005326.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5324">[ date ]</a> + <a href="thread.html#5324">[ thread ]</a> + <a href="subject.html#5324">[ subject ]</a> + <a href="author.html#5324">[ 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> |