diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/20101201 | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/20101201')
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001565.html | 118 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001566.html | 130 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001567.html | 91 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001568.html | 162 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001569.html | 109 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001570.html | 72 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001571.html | 72 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001572.html | 88 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001573.html | 74 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001574.html | 122 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001575.html | 93 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001576.html | 349 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/001577.html | 70 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/author.html | 112 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/date.html | 112 | ||||
| l--------- | zarb-ml/mageia-dev/20101201/index.html | 1 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/subject.html | 112 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/20101201/thread.html | 135 |
18 files changed, 2022 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101201/001565.html b/zarb-ml/mageia-dev/20101201/001565.html new file mode 100644 index 000000000..30855b327 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001565.html @@ -0,0 +1,118 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Mirror layout, round two + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C201012010012.04846.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="001574.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout, round two</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C201012010012.04846.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Mirror layout, round two">maarten.vanraes at gmail.com + </A><BR> + <I>Wed Dec 1 00:12:04 CET 2010</I> + <P><UL> + + <LI>Next message: <A HREF="001574.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1565">[ date ]</a> + <a href="thread.html#1565">[ thread ]</a> + <a href="subject.html#1565">[ subject ]</a> + <a href="author.html#1565">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op dinsdag 30 november 2010 12:04:49 schreef Samuel Verschelde: +><i> Le mardi 30 novembre 2010 11:37:42, Thomas Backlund a écrit : +</I>><i> > So, after reading all different opinions here and discussing with +</I>><i> > founders, here is the idea: +</I>><i> > +</I>><i> > We start of with 3 medias: core, nonfree, tainted and 3 debug medias: +</I>><i> > debug_core, debug_nonfree, debug_tainted. In order to avoid confusion, +</I>><i> > we wont use the name "restricted" as it was used in MDV commercial +</I>><i> > products. +</I>><i> > +</I>><i> > Now all of theese medias will have their 5 submedias: release, updates, +</I>><i> > updates_testing, backports, backports_testing. +</I>><i> > +</I>><i> > That brings us to 30 medias in total :) +</I>><i> > +</I>><i> > The details of the media layout suggestion is also at the end of this +</I>><i> > mail, and at: <A HREF="http://mageia.org/wiki/doku.php?id=mirrors_policy">http://mageia.org/wiki/doku.php?id=mirrors_policy</A> +</I>><i> > +</I>><i> > +</I>><i> > Now... +</I>><i> > +</I>><i> > We wont blindly import every package from cooker, instead we'll +</I>><i> > start off the import with basesystem (as in bootable system with +</I>><i> > shell access), compiler and rpm tools (and of course their buildtime +</I>><i> > depencies). When all of that is imported and rebuilt, we have a working +</I>><i> > buildsystem / base to build from. +</I>><i> > +</I>><i> > Then we to go on with and start importing X, the different +</I>><i> > DE's and every other package needed to build a full distro. +</I>><i> > +</I>><i> > By doing it this way, we get a clean start, every package rebuilt, +</I>><i> > and no old/unmaintained stuff in the beginning. +</I>><i> > +</I>><i> > Then as more maintainers join, I guess more packages will be imported +</I>><i> > from cooker and other sources. And packages can always be requested. +</I>><i> > +</I>><i> > As for those that want the core/extra split: +</I>><i> > We already tried it with main/contrib split. And I know mdv is now +</I>><i> > trying to refine what belongs in main or not, but thats for mdv +</I>><i> > to work through the "problem" as it wont be an easy task. +</I>><i> > +</I>><i> > For us I think the best way for now is to start with this suggested +</I>><i> > layout, and see if it works well for us. Remember, as Michael pointed +</I>><i> > out, this is a community supported distro, and only time will tell how +</I>><i> > well the community actually will support their distro. +</I>><i> > +</I>><i> > Point is, if we later decide this is not working well, we can always +</I>><i> > review the decisions and if decided do the split. +</I>><i> > +</I>><i> > Can we reach an agreement that this is the way to start the distro? +</I>><i> +</I>><i> OK for me provided support policy matters are not discarded forever but +</I>><i> only delayed to allow things to start. +</I>><i> +</I>><i> It would be great to start QA Team's organization as soon as possible. I +</I>><i> don't think we need to wait for the BS and the packages to begin thinking +</I>><i> about those matters. +</I>><i> +</I>><i> Regards +</I>><i> +</I>><i> Samuel +</I> +i agree +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="001574.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1565">[ date ]</a> + <a href="thread.html#1565">[ thread ]</a> + <a href="subject.html#1565">[ subject ]</a> + <a href="author.html#1565">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001566.html b/zarb-ml/mageia-dev/20101201/001566.html new file mode 100644 index 000000000..e3db63425 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001566.html @@ -0,0 +1,130 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Support policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012010033.32924.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001574.html"> + <LINK REL="Next" HREF="001568.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Support policy</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012010033.32924.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Support policy">maarten.vanraes at gmail.com + </A><BR> + <I>Wed Dec 1 00:33:32 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001574.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001568.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1566">[ date ]</a> + <a href="thread.html#1566">[ thread ]</a> + <a href="subject.html#1566">[ subject ]</a> + <a href="author.html#1566">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op dinsdag 30 november 2010 13:31:08 schreef Samuel Verschelde: +><i> Hi, +</I>><i> +</I>><i> I would like to discuss the support policy for Mageia. +</I>><i> +</I>><i> It would be interesting to know (or decide) where Mageia is heading, given +</I>><i> our limited resources : 1) focus on stability and security : few very well +</I>><i> equally supported packages. Apparently, this is where we're going for now. +</I>><i> May be wise as a start, but I hope this is not our final destination, +</I>><i> because it means either very limited choice, or progressive diminution of +</I>><i> quality of support if the number of packages increases faster than the +</I>><i> dedicated resources. 2) focus on choice : many packages, but no support +</I>><i> policy. This would be really bad, I think we're not heading there, from +</I>><i> what I read. However, this is a danger if we start from option 1) and then +</I>><i> open wide the gates for importing packages, without setting a support +</I>><i> policy. 3) focus on both (this is my option). There would be 2 levels of +</I>><i> support : - top guaranteed support : those are the (few at start) packages +</I>><i> your can rely on almost blindly, they'll be updated in a timely manner, +</I>><i> and updates don't break things. Those are the packages the QA Team puts +</I>><i> its limited resources on (doesn't mean the QA Team provides the support +</I>><i> themselves, this is maintainer work, but they check that good support is +</I>><i> provided) : testing, helping the maintainers to watch for security +</I>><i> problems... The maintainers are responsible for their package, but the QA +</I>><i> Team double-checks updates for stable releases. - supported packages +</I>><i> (every other package) : those are maintained packages, however the QA Team +</I>><i> doesn't have to check them. It's up to the maintainer to check the package +</I>><i> and updates quality. - unsupported packages are dropped. +</I>><i> +</I>><i> Are we heading for 1), 2), 3), or any other option ? +</I>><i> +</I>><i> Of course, with unlimited resources, options 1 and 3 would be equivalent, +</I>><i> everything would have the "top guaranteed support" :) +</I>><i> +</I>><i> Best regards +</I>><i> +</I>><i> Samuel Verschelde +</I>><i> Packager/QA Team/User +</I> + +having read misc's lenghty and almost political proposal, i suggest a 4th +option (even though i'm not part of QAteam either): + +4) dynamically distributed focus: +- level 1: BuildSystem-required packages (all packages used for buildnodes) +- level 2: everything that is minimally required to boot and do stuff +- level 3: popular server packages +- level 4: release focus (everything that's defaultly installed by a release) +- level 4b: stage images +- level 5: the rest + +depending on resources and certain timings; focus should be spread according +to desires at that time. + +eg: +- i imagine that level 1 could be discussed between sysadm and qateam during +BS-updates +- i imagine that level 2 would be the primary focus +- i imagine that level 4 could be more important during release times +- i imagine that level 5 would probably not be focussed by QA unless unlimited +resources +- i imagine that level 3 would probably be good if resources would be growing, +and possibly level 4 if there's enough resources. + + +- i agree that testing should be open to anyone +- i agree that karma could not be a bad idea, but suggest that QAteam give +more karma (perhaps even on the karmic state of that person) +- i also would suggest that at the time of alpha release, we should do a +contest on testing and bugfinding; so that we could gather enough testers; and +possibly even extra packagers or qateam people. + +WDYT? +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001574.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001568.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1566">[ date ]</a> + <a href="thread.html#1566">[ thread ]</a> + <a href="subject.html#1566">[ subject ]</a> + <a href="author.html#1566">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001567.html b/zarb-ml/mageia-dev/20101201/001567.html new file mode 100644 index 000000000..4416a9059 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001567.html @@ -0,0 +1,91 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Support policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012010935.53000.bgmilne%40multilinks.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001573.html"> + <LINK REL="Next" HREF="001569.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Support policy</H1> + <B>Buchan Milne</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012010935.53000.bgmilne%40multilinks.com%3E" + TITLE="[Mageia-dev] Support policy">bgmilne at multilinks.com + </A><BR> + <I>Wed Dec 1 09:35:52 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001573.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001569.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1567">[ date ]</a> + <a href="thread.html#1567">[ thread ]</a> + <a href="subject.html#1567">[ subject ]</a> + <a href="author.html#1567">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Tuesday, 30 November 2010 18:09:38 Michael Scherer wrote: +><i> Le mardi 30 novembre 2010 à 16:36 +0100, Samuel Verschelde a écrit : +</I> +><i> > +</I>><i> > Well, I can't because as you already told me we don't know what our +</I>><i> > resources will be. What I can guess is that they are limited because I +</I>><i> > know no free software project where there's too much resources. +</I>><i> +</I>><i> Well, from a physical point of view, everything is limited, so saying +</I>><i> "limited ressources" didn't indeed told much. +</I> +[...] + +><i> But still, having community enabled QA is a great way to have every grow +</I>><i> properly. +</I>><i> And in fact, that's exactly one of the feature of your project +</I>><i> mageia-app-db. So we could indeed have a better QAteam by easing the +</I>><i> work of community, using mageia-app-db. Ie, take regular user, and turn +</I>><i> them in QA team member. +</I> +BTW., this is one reason why I would prefer a Mageia user or contributor to +have one account, for everything. It reduces the obstacles becoming a +contributor. A user who post on the forum has a bugzilla account and a wiki +account and should be able to provide feedback on packages etc. + +Only when the user needs to be able to push changes somewhere without +authorization of another contributor, does the user need to request privileged +access (but, on the same account). + +Regards, +Buchan +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001573.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001569.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1567">[ date ]</a> + <a href="thread.html#1567">[ thread ]</a> + <a href="subject.html#1567">[ subject ]</a> + <a href="author.html#1567">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001568.html b/zarb-ml/mageia-dev/20101201/001568.html new file mode 100644 index 000000000..a47627e90 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001568.html @@ -0,0 +1,162 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Support policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3CAANLkTi%3DNvoNwDLN4M1aMgUO9d9AstBNauV5boBZa6j43%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="001566.html"> + <LINK REL="Next" HREF="001570.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Support policy</H1> + <B>Daniel Kreuter</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3CAANLkTi%3DNvoNwDLN4M1aMgUO9d9AstBNauV5boBZa6j43%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Support policy">daniel.kreuter85 at googlemail.com + </A><BR> + <I>Wed Dec 1 09:42:18 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001566.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001570.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1568">[ date ]</a> + <a href="thread.html#1568">[ thread ]</a> + <a href="subject.html#1568">[ subject ]</a> + <a href="author.html#1568">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>2010/12/1 Maarten Vanraes <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">maarten.vanraes at gmail.com</A>> + +><i> Op dinsdag 30 november 2010 13:31:08 schreef Samuel Verschelde: +</I>><i> > Hi, +</I>><i> > +</I>><i> > I would like to discuss the support policy for Mageia. +</I>><i> > +</I>><i> > It would be interesting to know (or decide) where Mageia is heading, +</I>><i> given +</I>><i> > our limited resources : 1) focus on stability and security : few very +</I>><i> well +</I>><i> > equally supported packages. Apparently, this is where we're going for +</I>><i> now. +</I>><i> > May be wise as a start, but I hope this is not our final destination, +</I>><i> > because it means either very limited choice, or progressive diminution of +</I>><i> > quality of support if the number of packages increases faster than the +</I>><i> > dedicated resources. 2) focus on choice : many packages, but no support +</I>><i> > policy. This would be really bad, I think we're not heading there, from +</I>><i> > what I read. However, this is a danger if we start from option 1) and +</I>><i> then +</I>><i> > open wide the gates for importing packages, without setting a support +</I>><i> > policy. 3) focus on both (this is my option). There would be 2 levels of +</I>><i> > support : - top guaranteed support : those are the (few at start) +</I>><i> packages +</I>><i> > your can rely on almost blindly, they'll be updated in a timely manner, +</I>><i> > and updates don't break things. Those are the packages the QA Team puts +</I>><i> > its limited resources on (doesn't mean the QA Team provides the support +</I>><i> > themselves, this is maintainer work, but they check that good support is +</I>><i> > provided) : testing, helping the maintainers to watch for security +</I>><i> > problems... The maintainers are responsible for their package, but the QA +</I>><i> > Team double-checks updates for stable releases. - supported packages +</I>><i> > (every other package) : those are maintained packages, however the QA +</I>><i> Team +</I>><i> > doesn't have to check them. It's up to the maintainer to check the +</I>><i> package +</I>><i> > and updates quality. - unsupported packages are dropped. +</I>><i> > +</I>><i> > Are we heading for 1), 2), 3), or any other option ? +</I>><i> > +</I>><i> > Of course, with unlimited resources, options 1 and 3 would be equivalent, +</I>><i> > everything would have the "top guaranteed support" :) +</I>><i> > +</I>><i> > Best regards +</I>><i> > +</I>><i> > Samuel Verschelde +</I>><i> > Packager/QA Team/User +</I>><i> +</I>><i> +</I>><i> having read misc's lenghty and almost political proposal, i suggest a 4th +</I>><i> option (even though i'm not part of QAteam either): +</I>><i> +</I>><i> 4) dynamically distributed focus: +</I>><i> - level 1: BuildSystem-required packages (all packages used for buildnodes) +</I>><i> - level 2: everything that is minimally required to boot and do stuff +</I>><i> - level 3: popular server packages +</I>><i> - level 4: release focus (everything that's defaultly installed by a +</I>><i> release) +</I>><i> - level 4b: stage images +</I>><i> - level 5: the rest +</I>><i> +</I>><i> depending on resources and certain timings; focus should be spread +</I>><i> according +</I>><i> to desires at that time. +</I>><i> +</I>><i> eg: +</I>><i> - i imagine that level 1 could be discussed between sysadm and qateam +</I>><i> during +</I>><i> BS-updates +</I>><i> - i imagine that level 2 would be the primary focus +</I>><i> - i imagine that level 4 could be more important during release times +</I>><i> - i imagine that level 5 would probably not be focussed by QA unless +</I>><i> unlimited +</I>><i> resources +</I>><i> - i imagine that level 3 would probably be good if resources would be +</I>><i> growing, +</I>><i> and possibly level 4 if there's enough resources. +</I>><i> +</I>><i> +</I>><i> - i agree that testing should be open to anyone +</I>><i> - i agree that karma could not be a bad idea, but suggest that QAteam give +</I>><i> more karma (perhaps even on the karmic state of that person) +</I>><i> - i also would suggest that at the time of alpha release, we should do a +</I>><i> contest on testing and bugfinding; so that we could gather enough testers; +</I>><i> and +</I>><i> possibly even extra packagers or qateam people. +</I>><i> +</I>><i> WDYT? +</I>><i> +</I> + +Option 4 sounds good, it also shows a little bit the responsibilities of +each team. +I would like to add a level 3b which differs between server-only and +desktop. + + +-- +Mit freundlichen Grüßen + +Greetings + +Daniel Kreuter +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-dev/attachments/20101201/1604e755/attachment-0001.html> +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001566.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001570.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1568">[ date ]</a> + <a href="thread.html#1568">[ thread ]</a> + <a href="subject.html#1568">[ subject ]</a> + <a href="author.html#1568">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001569.html b/zarb-ml/mageia-dev/20101201/001569.html new file mode 100644 index 000000000..027228024 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001569.html @@ -0,0 +1,109 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Support policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3CAANLkTi%3DgvqqqAa_C6poqcvJvgqYWaRZpCXsQyH-NeHww%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="001567.html"> + <LINK REL="Next" HREF="001572.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Support policy</H1> + <B>Daniel Kreuter</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3CAANLkTi%3DgvqqqAa_C6poqcvJvgqYWaRZpCXsQyH-NeHww%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Support policy">daniel.kreuter85 at googlemail.com + </A><BR> + <I>Wed Dec 1 09:45:44 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001567.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001572.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1569">[ date ]</a> + <a href="thread.html#1569">[ thread ]</a> + <a href="subject.html#1569">[ subject ]</a> + <a href="author.html#1569">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>2010/12/1 Buchan Milne <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bgmilne at multilinks.com</A>> + +><i> On Tuesday, 30 November 2010 18:09:38 Michael Scherer wrote: +</I>><i> > Le mardi 30 novembre 2010 à 16:36 +0100, Samuel Verschelde a écrit : +</I>><i> +</I>><i> > > +</I>><i> > > Well, I can't because as you already told me we don't know what our +</I>><i> > > resources will be. What I can guess is that they are limited because I +</I>><i> > > know no free software project where there's too much resources. +</I>><i> > +</I>><i> > Well, from a physical point of view, everything is limited, so saying +</I>><i> > "limited ressources" didn't indeed told much. +</I>><i> +</I>><i> [...] +</I>><i> +</I>><i> > But still, having community enabled QA is a great way to have every grow +</I>><i> > properly. +</I>><i> > And in fact, that's exactly one of the feature of your project +</I>><i> > mageia-app-db. So we could indeed have a better QAteam by easing the +</I>><i> > work of community, using mageia-app-db. Ie, take regular user, and turn +</I>><i> > them in QA team member. +</I>><i> +</I>><i> BTW., this is one reason why I would prefer a Mageia user or contributor to +</I>><i> have one account, for everything. It reduces the obstacles becoming a +</I>><i> contributor. A user who post on the forum has a bugzilla account and a wiki +</I>><i> account and should be able to provide feedback on packages etc. +</I>><i> +</I>><i> Only when the user needs to be able to push changes somewhere without +</I>><i> authorization of another contributor, does the user need to request +</I>><i> privileged +</I>><i> access (but, on the same account). +</I>><i> +</I>><i> Regards, +</I>><i> Buchan +</I>><i> +</I> +Nice idea, something like that would be a nice thing. Who wants to register +for 5 pages only to become a full member of a community? Nobody. + + +-- +Mit freundlichen Grüßen + +Greetings + +Daniel Kreuter +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-dev/attachments/20101201/9aa255f5/attachment.html> +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001567.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001572.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1569">[ date ]</a> + <a href="thread.html#1569">[ thread ]</a> + <a href="subject.html#1569">[ subject ]</a> + <a href="author.html#1569">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001570.html b/zarb-ml/mageia-dev/20101201/001570.html new file mode 100644 index 000000000..351be8338 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001570.html @@ -0,0 +1,72 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Support policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012011012.59252.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="001568.html"> + <LINK REL="Next" HREF="001573.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Support policy</H1> + <B>Samuel Verschelde</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012011012.59252.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] Support policy">stormi at laposte.net + </A><BR> + <I>Wed Dec 1 10:12:59 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001568.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001573.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1570">[ date ]</a> + <a href="thread.html#1570">[ thread ]</a> + <a href="subject.html#1570">[ subject ]</a> + <a href="author.html#1570">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> +Le mercredi 1 décembre 2010 00:33:32, Maarten Vanraes a écrit : +><i> +</I>><i> Op dinsdag 30 november 2010 13:31:08 schreef Samuel Verschelde: +</I>><i> > Samuel Verschelde +</I>><i> > Packager/QA Team/User +</I>><i> +</I>><i> having read misc's lenghty and almost political proposal, i suggest a 4th +</I>><i> option (even though i'm not part of QAteam either): +</I> + +My signing "Packager/Qa Team/User" wasn't meant to make any difference between those who are in the team and those who aren't. I just tried to stress that I feel concerned equally by packaging issues, QA issues and that by end-user usage :) + +Samuel + +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001568.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001573.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1570">[ date ]</a> + <a href="thread.html#1570">[ thread ]</a> + <a href="subject.html#1570">[ subject ]</a> + <a href="author.html#1570">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001571.html b/zarb-ml/mageia-dev/20101201/001571.html new file mode 100644 index 000000000..23f87db74 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001571.html @@ -0,0 +1,72 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Support policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012010944.57917.bgmilne%40multilinks.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001572.html"> + <LINK REL="Next" HREF="001575.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Support policy</H1> + <B>Buchan Milne</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012010944.57917.bgmilne%40multilinks.com%3E" + TITLE="[Mageia-dev] Support policy">bgmilne at multilinks.com + </A><BR> + <I>Wed Dec 1 09:44:57 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001572.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001575.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1571">[ date ]</a> + <a href="thread.html#1571">[ thread ]</a> + <a href="subject.html#1571">[ subject ]</a> + <a href="author.html#1571">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Tuesday, 30 November 2010 18:09:38 Michael Scherer wrote: + +><i> Of course, the system is not perfect and will not solve everything. For +</I>><i> example, last week, openldap update broke server functionality : +</I>><i> ( <A HREF="http://lists.fedoraproject.org/pipermail/devel/2010-November/146097.html">http://lists.fedoraproject.org/pipermail/devel/2010-November/146097.html</A> +</I>><i> ) +</I> +Hahahaha. + +Hint to fedora, always run the correct db_recover in %pre ... + +Regards, +Buchan +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001572.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001575.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1571">[ date ]</a> + <a href="thread.html#1571">[ thread ]</a> + <a href="subject.html#1571">[ subject ]</a> + <a href="author.html#1571">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001572.html b/zarb-ml/mageia-dev/20101201/001572.html new file mode 100644 index 000000000..4589c9a43 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001572.html @@ -0,0 +1,88 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Support policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012010935.59105.bgmilne%40multilinks.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001569.html"> + <LINK REL="Next" HREF="001571.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Support policy</H1> + <B>Buchan Milne</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012010935.59105.bgmilne%40multilinks.com%3E" + TITLE="[Mageia-dev] Support policy">bgmilne at multilinks.com + </A><BR> + <I>Wed Dec 1 09:35:58 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001569.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001571.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1572">[ date ]</a> + <a href="thread.html#1572">[ thread ]</a> + <a href="subject.html#1572">[ subject ]</a> + <a href="author.html#1572">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Tuesday, 30 November 2010 18:09:38 Michael Scherer wrote: +><i> Le mardi 30 novembre 2010 à 16:36 +0100, Samuel Verschelde a écrit : +</I> +><i> > +</I>><i> > Well, I can't because as you already told me we don't know what our +</I>><i> > resources will be. What I can guess is that they are limited because I +</I>><i> > know no free software project where there's too much resources. +</I>><i> +</I>><i> Well, from a physical point of view, everything is limited, so saying +</I>><i> "limited ressources" didn't indeed told much. +</I> +[...] + +><i> But still, having community enabled QA is a great way to have every grow +</I>><i> properly. +</I>><i> And in fact, that's exactly one of the feature of your project +</I>><i> mageia-app-db. So we could indeed have a better QAteam by easing the +</I>><i> work of community, using mageia-app-db. Ie, take regular user, and turn +</I>><i> them in QA team member. +</I> +BTW., this is one reason why I would prefer a Mageia user or contributor to +have one account, for everything. It reduces the obstacles becoming a +contributor. A user who post on the forum has a bugzilla account and a wiki +account and should be able to provide feedback on packages etc. + +Only when the user needs to be able to push changes somewhere without +authorization of another contributor, does the user need to request privileged +access (but, on the same account). + +Regards, +Buchan +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001569.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001571.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1572">[ date ]</a> + <a href="thread.html#1572">[ thread ]</a> + <a href="subject.html#1572">[ subject ]</a> + <a href="author.html#1572">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001573.html b/zarb-ml/mageia-dev/20101201/001573.html new file mode 100644 index 000000000..a06a3db82 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001573.html @@ -0,0 +1,74 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Support policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012011736.59465.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001570.html"> + <LINK REL="Next" HREF="001567.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Support policy</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Support%20policy&In-Reply-To=%3C201012011736.59465.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Support policy">maarten.vanraes at gmail.com + </A><BR> + <I>Wed Dec 1 17:36:59 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001570.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001567.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1573">[ date ]</a> + <a href="thread.html#1573">[ thread ]</a> + <a href="subject.html#1573">[ subject ]</a> + <a href="author.html#1573">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op woensdag 01 december 2010 10:12:59 schreef Samuel Verschelde: +><i> Le mercredi 1 décembre 2010 00:33:32, Maarten Vanraes a écrit : +</I>><i> > Op dinsdag 30 november 2010 13:31:08 schreef Samuel Verschelde: +</I>><i> > > Samuel Verschelde +</I>><i> > > Packager/QA Team/User +</I>><i> > +</I>><i> > having read misc's lenghty and almost political proposal, i suggest a 4th +</I>><i> +</I>><i> > option (even though i'm not part of QAteam either): +</I>><i> My signing "Packager/Qa Team/User" wasn't meant to make any difference +</I>><i> between those who are in the team and those who aren't. I just tried to +</I>><i> stress that I feel concerned equally by packaging issues, QA issues and +</I>><i> that by end-user usage :) +</I>><i> +</I>><i> Samuel +</I> +my reply was more to suggest stuff, even though i feel the responsibility +belongs to QAteam +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001570.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001567.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1573">[ date ]</a> + <a href="thread.html#1573">[ thread ]</a> + <a href="subject.html#1573">[ subject ]</a> + <a href="author.html#1573">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001574.html b/zarb-ml/mageia-dev/20101201/001574.html new file mode 100644 index 000000000..06bf04290 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001574.html @@ -0,0 +1,122 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Mirror layout, round two + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF68030.7010309%40googlemail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001565.html"> + <LINK REL="Next" HREF="001566.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout, round two</H1> + <B>Daniel Kreuter</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF68030.7010309%40googlemail.com%3E" + TITLE="[Mageia-dev] Mirror layout, round two">daniel.kreuter85 at googlemail.com + </A><BR> + <I>Wed Dec 1 18:04:48 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001565.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001566.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1574">[ date ]</a> + <a href="thread.html#1574">[ thread ]</a> + <a href="subject.html#1574">[ subject ]</a> + <a href="author.html#1574">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 01.12.2010 00:12, Maarten Vanraes wrote: +><i> Le mardi 30 novembre 2010 11:37:42, Thomas Backlund a écrit : +</I>>>><i> So, after reading all different opinions here and discussing with +</I>>>><i> founders, here is the idea: +</I>>>><i> +</I>>>><i> We start of with 3 medias: core, nonfree, tainted and 3 debug medias: +</I>>>><i> debug_core, debug_nonfree, debug_tainted. In order to avoid confusion, +</I>>>><i> we wont use the name "restricted" as it was used in MDV commercial +</I>>>><i> products. +</I>>>><i> +</I>>>><i> Now all of theese medias will have their 5 submedias: release, updates, +</I>>>><i> updates_testing, backports, backports_testing. +</I>>>><i> +</I>>>><i> That brings us to 30 medias in total :) +</I>>>><i> +</I>>>><i> The details of the media layout suggestion is also at the end of this +</I>>>><i> mail, and at: <A HREF="http://mageia.org/wiki/doku.php?id=mirrors_policy">http://mageia.org/wiki/doku.php?id=mirrors_policy</A> +</I>>>><i> +</I>>>><i> +</I>>>><i> Now... +</I>>>><i> +</I>>>><i> We wont blindly import every package from cooker, instead we'll +</I>>>><i> start off the import with basesystem (as in bootable system with +</I>>>><i> shell access), compiler and rpm tools (and of course their buildtime +</I>>>><i> depencies). When all of that is imported and rebuilt, we have a working +</I>>>><i> buildsystem / base to build from. +</I>>>><i> +</I>>>><i> Then we to go on with and start importing X, the different +</I>>>><i> DE's and every other package needed to build a full distro. +</I>>>><i> +</I>>>><i> By doing it this way, we get a clean start, every package rebuilt, +</I>>>><i> and no old/unmaintained stuff in the beginning. +</I>>>><i> +</I>>>><i> Then as more maintainers join, I guess more packages will be imported +</I>>>><i> from cooker and other sources. And packages can always be requested. +</I>>>><i> +</I>>>><i> As for those that want the core/extra split: +</I>>>><i> We already tried it with main/contrib split. And I know mdv is now +</I>>>><i> trying to refine what belongs in main or not, but thats for mdv +</I>>>><i> to work through the "problem" as it wont be an easy task. +</I>>>><i> +</I>>>><i> For us I think the best way for now is to start with this suggested +</I>>>><i> layout, and see if it works well for us. Remember, as Michael pointed +</I>>>><i> out, this is a community supported distro, and only time will tell how +</I>>>><i> well the community actually will support their distro. +</I>>>><i> +</I>>>><i> Point is, if we later decide this is not working well, we can always +</I>>>><i> review the decisions and if decided do the split. +</I>>>><i> +</I>>>><i> Can we reach an agreement that this is the way to start the distro? +</I>>><i> +</I>I have one question at your suggestion Thomas. +Mandriva has editions like Mandriva One or Mandriva Free. Will there be +something different or will Mageia use this as a base? + +I would prefer that some proprietary firmware will be available such as +the WIFI drivers of Intel (iwlwifi) , which is needed by my wireless +card, without choosing the correct version of Mageia. +These drivers are also available in the kernel right now, so it would be +a possibility to activate them there by default so newer hardware will +work correctly. + +Daniel + +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-dev/attachments/20101201/7249ee28/attachment.html> +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001565.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001566.html">[Mageia-dev] Support policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1574">[ date ]</a> + <a href="thread.html#1574">[ thread ]</a> + <a href="subject.html#1574">[ subject ]</a> + <a href="author.html#1574">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001575.html b/zarb-ml/mageia-dev/20101201/001575.html new file mode 100644 index 000000000..ddddcc831 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001575.html @@ -0,0 +1,93 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Mirror layout, round two + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF6B034.8080203%40iki.fi%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001571.html"> + <LINK REL="Next" HREF="001576.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout, round two</H1> + <B>Anssi Hannula</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF6B034.8080203%40iki.fi%3E" + TITLE="[Mageia-dev] Mirror layout, round two">anssi.hannula at iki.fi + </A><BR> + <I>Wed Dec 1 21:29:40 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001571.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001576.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1575">[ date ]</a> + <a href="thread.html#1575">[ thread ]</a> + <a href="subject.html#1575">[ subject ]</a> + <a href="author.html#1575">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 30.11.2010 12:37, Thomas Backlund wrote: +[...] +><i> Can we reach an agreement that this is the way to start the distro? +</I> +Yes. + +><i> +</I>><i> and for refernece: The suggested layout for is: +</I>><i> +</I>><i> * core +</I>><i> * nonfree +</I>><i> * tainted +</I>><i> * debug_core +</I>><i> * debug_nonfree +</I>><i> * debug_tainted +</I>><i> +</I>><i> +</I>><i> Every media contains the same layout: +</I>><i> +</I>><i> * backports +</I>><i> * backports_testing +</I>><i> * release +</I>><i> * updates +</I>><i> * updates_testing +</I> +I wonder which 32bit ones we should add on 64bit, and which ones of +those should be enabled and which ones disabled. + +On MDV, main+main_updates were added and enabled. + +But for example wine backports are commonly wanted by 64bit users, and +those are in main/backports (core/backports for us). + +Or is there an alternative approach that I can't think of? + +-- +Anssi Hannula +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001571.html">[Mageia-dev] Support policy +</A></li> + <LI>Next message: <A HREF="001576.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1575">[ date ]</a> + <a href="thread.html#1575">[ thread ]</a> + <a href="subject.html#1575">[ subject ]</a> + <a href="author.html#1575">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001576.html b/zarb-ml/mageia-dev/20101201/001576.html new file mode 100644 index 000000000..105805d84 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001576.html @@ -0,0 +1,349 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Mirror layout, round two + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF6B618.907%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001575.html"> + <LINK REL="Next" HREF="001577.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout, round two</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF6B618.907%40laposte.net%3E" + TITLE="[Mageia-dev] Mirror layout, round two">andr55 at laposte.net + </A><BR> + <I>Wed Dec 1 21:54:48 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001575.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001577.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1576">[ date ]</a> + <a href="thread.html#1576">[ thread ]</a> + <a href="subject.html#1576">[ subject ]</a> + <a href="author.html#1576">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> +Ahmad Samir a écrit : +><i> +</I>><i> On 30 November 2010 07:29, andre999<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">andr55 at laposte.net</A>> wrote: +</I>>><i> Michael Scherer a écrit : +</I>>>><i> +</I>>>><i> Le lundi 29 novembre 2010 à 20:54 -0500, andre999 a écrit : +</I>>>><i> +</I>>>>><i> Yann Ciret a écrit : +</I>>>>><i> +</I>>>>>><i> I dislike the main/contrib separation in some case. +</I>>>>>><i> The first example is with Mozilla Thunderbird packages. Some extension +</I>>>>>><i> packages are in contrib. So each time thunderbird received security +</I>>>>>><i> update, the update cannot be installed because of non automatically +</I>>>>>><i> rebuild of his contrib package. And each time I see a bug report of user +</I>>>>>><i> asking a manual rebuilt. With only one core media, this situation will +</I>>>>>><i> disapear (I hope). +</I>>>>><i> +</I>>>>><i> Unlikely. This problem is not at all related to separate repositories. +</I>>>><i> +</I>>>><i> It is. It is exactly related to the fact that thunderbird is supported, +</I>>>><i> and that extension are not despites depending on it. +</I>>><i> +</I>>><i> In this case it is evident that you don't understand how extensions work +</I>>><i> with mozilla products. +</I>>><i> Thunderbird will function correctly with no extensions installed. +</I>>><i> So why should any extension block the update of Thunderbird ? +</I>><i> +</I>><i> So the user can simply uninstall that extension and update to new +</I>><i> thunderbird? the user can do this only if he doesn't need that +</I>><i> extension, only if it doesn't offer features he wants to use. That's +</I>><i> an invalid argument, if he doesn't need that extension why does he +</I>><i> have it on his system?? +</I> +You're missing some points here : +1) There is no need to remove an extension. It will continue to work, +as long as there hasn't been some error in packaging. In other words, +on a generic Mozilla installation, it would continue to work. The only +exceptions in the past are when Mozilla changed the version of XML used +to code extensions. (Which has happened twice since the beginning of +Mozilla, if I recall correctly.) But that would not happen on an update. + +2) If by chance the extension does not work properly, it can always be +updated directly by the update function inside Thunderbird. Unless the +distro packaging has somehow disabled this function. Which would be an +error in packaging. + +3) There is no reason to package Mozilla extensions in the distro, +except for base localisation modules, which are already in main. + +4) If an optional module of any application stops working, that can only +affect the application in question. And should not stop the application +from working. That does not in itself justify such an extension being +considered (logically) core. +><i> +</I>><i> The rationale is/was that mozilla code breaks/broke ABI, so it was +</I>><i> agreed that extensions are rebuilt for both firefox and thunderbird +</I>><i> respective new versions. +</I>See above. +><i> +</I>><i> We will look into that with upstream, so that if a rebuild isn't +</I>><i> needed, then all the better for us (packagers). But until that +</I>><i> happens, they will be rebuilt. A 1-2 day delay isn't too much for +</I>><i> users. +</I>Good. Check with upstream. It can be done quickly, and will help clean +the system. +By the way, if you install Thunderbird, you can confirm the critical +elements yourself. (Installation/update of Extensions and other +optional modules fully managable from inside Thunderbird. As well, by +default there are automatic alerts when updates become available.) +><i> +</I>><i> The more pressing issue is, what does this have to do with the topic +</I>><i> at hand "Mirrors layout, round two" ?? this discussion is deviating +</I>><i> too much, to the extent it's becoming bloated... +</I> +Everything. +Removing the distinction between core and non-core packages removes an +important control, useful to give greater assurance that (logically) +core packages are not broken, thus breaking users' systems. +In my mind, alternative controls are likely to be more complex to +maintain, and probably less reliable. +It is interesting that the names "core" and "extra" were chosen to +replace "main" and "contrib". +Especially since "main" was originally meant to be core packages. But +not enforced, as some packagers themselves have pointed out. +(One would prefer that I don't mention his name.) +><i> +</I>>><i> Additionally, modules installed will continue to work as long as the major +</I>>><i> version doesn't change. (Actually slightly more complicated.) +</I>>><i> In some cases one won't be able to newly install a module because a config +</I>>><i> file inside the module - equivalent to the spec file in rpm packages - +</I>>><i> hasn't been updated for compatible versions. (In fact, the versions were +</I>>><i> probably improperly specified.) But installed modules will continue to +</I>>><i> function. +</I>>><i> It is possible that the packager did not realise this - or for whatever +</I>>><i> reason did not properly set up a spec file - but this issue has nothing at +</I>>><i> all to do with separate sets of repositories. +</I>><i> +</I>><i> Speaking abstractly without examples in this case is just that, +</I>><i> "speaking". Give us an example of such a case (if any) in a spec file +</I>><i> so that it can be fixed. +</I>More precise details added above. +><i> +</I>>>><i> That precisely because we tell "security and bugfixes occurs only on +</I>>>><i> main" that contribs got broken, since the security team do not care to +</I>>>><i> not break contribs packages +</I>>><i> +</I>>><i> The crux of this problem is that core (in the general sense) packages are +</I>>><i> dependant on packages that are not recognized as core. +</I>>><i> That again has nothing to do with repositories as such. +</I>I should have said "packages in core", since many such packages aren't +really logically core to the system. +><i> +</I>><i> I agree with Michael here, doing sec fixes isn't hard (once one gets +</I>><i> used to it), just time consuming, and it should be done for all +</I>><i> packages in the "official" repos; it's true that GPL gives no +</I>><i> guarantees what so ever, just it's a moral obligation for people +</I>><i> involved in the FOSS world to support users as best they can. +</I>I agree that security fixes should be done for all packages in +"officiel" repos. (Meaning "core" and "extra".) +But +1) My main point is that priority should be given to truly core +packages, because, as you mention, it is time consuming. If core is +mixed with non-core, that priority is (at least more) difficult to follow. + +2) An important part of my proposals has been to remove non-core +packages from the core repo, to assist in this. +To do that, we have to define clearly what is core and non-core. +(This will have to be done anyway if we wish to give priority to core +packages.) +I think that this would be a *very* useful discussion in this thread. +And I'm very willing to actively contribute. (As you might guess:) ) +I have to admit, I'm a bit surprised at the opposition to my proposals +by many (but not all) packagers. +><i> +</I>><i> Users do not differentiate between main/contrib, there's a package +</I>><i> they install it, I don't think they look from which repo it comes +</I>><i> from. +</I> +With this I disagree. Not only due to my own habit to leave contrib +disabled most of the time. And activate it only to find packages not in +main. (Often after searching elsewhere - but being a programmer, I'm +used to compiling/ extra configuring if necessary.) +Many users have expressed on this list a preference to install packages +from main, rather than contrib. +On the other hand, it is true that many users don't care. +><i> +</I>>>>><i> Rather that one package was updated, and an optional installed module +</I>>>>><i> was not. +</I>>>>><i> The fact that the module is optional is the key point. +</I>>>>><i> The installer should be flexible enough to give a warning in this case, +</I>>>>><i> and ask if you wish to continue the installation. +</I>>>><i> +</I>>>><i> So basically, you want a --nodeps ? +</I>>>><i> If there is a requires, there is usually a good reason. Engineering is +</I>>>><i> not randomly adding line to a file until it work. +</I>>><i> +</I>>><i> How about better configured spec files ? +</I>>><i> A better definition (in general) of core packages ? +</I>>><i> A focus on ensuring that core packages are maintained ? +</I>>><i> Basically my idea behind a core sandbox. +</I>>><i> But if you have a better idea ... +</I>><i> +</I>><i> Again, give us an example of a spec file that needs "better" +</I>><i> configuration, otherwise you're theorising. +</I> +(Firstly, of course I'm theorising. And so are those that propose +eliminating a separate core set of repos. But you could argue that it +wasn't clear.) +Sorry, I thought my point was obvious in the context. +If a package is optional, the spec file contents should never block the +upgrade of the package to which it is an option. +(Which is not necessarily the case if the package is one of several +required alternatives.) +It might be useful to warn the user that the optional module might not +work, but to refuse to update the main package just creates an +unnecessary blockage. +><i> +</I>>><i> Just remember, eliminating a supported core breaks the sandbox. +</I>>><i> So removing repositories does have secondary effects. +</I>>><i> And they should be seriously considered and discussed by those proposing to +</I>>><i> remove the repositories. +</I>>><i> +</I>>>>><i> As well, in the case of Thunderbird, it is almost certain that the +</I>>>>><i> installed module was in fact compatible with newer version of +</I>>>>><i> Thunderbird. (A security problem may directly impact Thunderbird or the +</I>>>>><i> module, but highly unlikely both packages.) +</I>>>>><i> Rpm tags should have been set so that Thunderbird would recognize that +</I>>>>><i> the module was appropriate in the newer version. +</I>>>><i> +</I>>>><i> No. If there is stricter dependency, it is precisely because there is no +</I>>>><i> guarantee of any kind of ABI between thunderbird versions. The same goes +</I>>>><i> for firefox. +</I>>><i> +</I>>><i> Overly restrictive compatibility specification is a very a common error in +</I>>><i> Mozilla extension packaging. (It's mentioned in their development guides.) +</I>>><i> But the rpm packager should be knowledgable enough to recognize it. +</I>>><i> But such errors do happen. +</I>><i> +</I>><i> Read above. +</I>I think that this statement stands on its own. +(Note that I said *Mozilla* extension packaging.) +Or read added comments above. +><i> +</I>>>>><i> So in sum, this was probably only a packaging problem. Whatever the +</I>>>>><i> repository. +</I>In fact, *necessarily* a packaging *error*, to be totally clear. + +>>><i> +</I>>>><i> No. Not at all. +</I>>>><i> The problem is linked to the difference of support between main and +</I>>>><i> contribs. +</I>>><i> +</I>>><i> In this case, it is inappropriate packaging. +</I>>><i> Other cases could be a difference of support. +</I>>><i> +</I>>><i> There is no reason that extensions should ever block the upgrade of +</I>>><i> Thunderbird, unless when one passes from one major version to another. +</I>>><i> In that case, the extension will have to be rewritten, a development +</I>>><i> function. +</I>>><i> (That has only happened a few times since the beginning of Mozilla.) +</I>><i> +</I>><i> See above (again). +</I> +See above (again) +Or think about this. The thai localisation is "required" in Mandriva. +Even if one doesn't have any knowledge thai, and thus is totally useless. +Just as logical as an optional Mozilla module blocking the update of +Thunderbird. +They are both packaging errors. +><i> +</I>>><i> The essence of our disagreement seems to be how to ensure that core packages +</I>>><i> are properly supported. +</I>><i> +</I>><i> Define "core". For KDE users who want to change GTK themes gtk-chtheme +</I>><i> (a very small and really old package) is core (i.e. important). The +</I>><i> point is, a package is offered in the repos it should be as supported +</I>><i> as possible, main/contrib/non-free doesn't/shouldn't matter. +</I> +Earlier in this thread, I defined core as necessary for a typical +desktop or server or development installation. Adding that certain +widely useful packages, such as Openoffice/LibreOffice and Firefox could +be added, due to their general utility. +This was to include complete desktops, such as Gnome, KDE, and LXDE. + +By this definition, the old GTK theme would probably not be considered +core, but that doesn't prevent it from being supported. I would expect +that the majority of non-core packages would be well supported. +The fact that the theme is important to the individual user is not key : +The question is more, would problems with it block or significantly +impair the user's system ? Considering that there are a number of +widely used alternatives, it would probably be decided to be non-core. + +Which brings up another important point. Exactly what constitutes core +and non-core should always be a collective decision. Meaning that +borderline cases are never decided by one individual, and decisions +should follow core guidelines. + +In general, this definition of core follows ideas proposed on Mandriva +cooker recently, although I have long had this view. I would guess that +at least a third of "main", if not more, is non-core. + +Examples ? I have installed (and use) poedit and gtranslator, packages +which facilitate translating .po files. They came from "main". +In my mind they are non-core, and never should have been in main. +As although they are used in the development process, they are not +central to it, and no other package would depend on them. +However, collective decisions could say that one of them is core (on the +basis of being widely used), and I, as a packager, would follow that. + +BTW, although I am interested in starting as a new Mageia packager, I +have decades of programming/development experience, with complex +systems. So my comments/suggestions come from considerable experience. +><i> +</I>>><i> My point is that a sandbox will facilitate proper support. Which would be +</I>>><i> facilitated by keeping the 2 sets of free repositories. And restricting +</I>>><i> what should be considered core. +</I>>><i> We both know that Mandriva is moving in that direction. Evidently +</I>>><i> recognising that they weren't restrictive enough in the past. +</I>><i> +</I>><i> Contrib _is_not_ a sandbox, unless you're implying packagers are using +</I>><i> users as lab rats.... which isn't true. +</I>Earlier in this thread, it was "main" and "core" that I qualified as +sandboxes. +In terms of isolating core packages into a repository on which all +packages could depend. +Obviously, "main" strayed from the concept. + +regards + +- André + + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001575.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001577.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1576">[ date ]</a> + <a href="thread.html#1576">[ thread ]</a> + <a href="subject.html#1576">[ subject ]</a> + <a href="author.html#1576">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/001577.html b/zarb-ml/mageia-dev/20101201/001577.html new file mode 100644 index 000000000..602ce7395 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/001577.html @@ -0,0 +1,70 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Mirror layout, round two + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C201012012250.26448.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001576.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout, round two</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C201012012250.26448.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Mirror layout, round two">maarten.vanraes at gmail.com + </A><BR> + <I>Wed Dec 1 22:50:26 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001576.html">[Mageia-dev] Mirror layout, round two +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1577">[ date ]</a> + <a href="thread.html#1577">[ thread ]</a> + <a href="subject.html#1577">[ subject ]</a> + <a href="author.html#1577">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op woensdag 01 december 2010 21:54:48 schreef andre999: +[...] + +allthough interesting, this thread is about mirror layout; and is not about +removing the distinction between supported packages and not. (this wasn't all +that clear to me at first.) + +i do understand that you think other methods of having the distinction might +not work; i have reservations myself that way. (i do feel the disctinction is +important.) + +i also see that mirror layout should be as easy as possible for mirror admins. + +however, looking at the big picture, i think that logically it's sounds to +have one purpose to one thing; and thus for the mirror layout; only the mirror +admins should be looked at; the viewpoint of a user _should_ not really +matter. +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001576.html">[Mageia-dev] Mirror layout, round two +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1577">[ date ]</a> + <a href="thread.html#1577">[ thread ]</a> + <a href="subject.html#1577">[ subject ]</a> + <a href="author.html#1577">[ 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> diff --git a/zarb-ml/mageia-dev/20101201/author.html b/zarb-ml/mageia-dev/20101201/author.html new file mode 100644 index 000000000..b823e4265 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/author.html @@ -0,0 +1,112 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 1 December 2010 Archive by author</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>1 December 2010 Archives by author</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Wed Dec 1 00:12:04 CET 2010</i><br> + <b>Ending:</b> <i>Wed Dec 1 22:50:26 CET 2010</i><br> + <b>Messages:</b> 13<p> + <ul> + +<LI><A HREF="001575.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1575"> </A> +<I>Anssi Hannula +</I> + +<LI><A HREF="001568.html">[Mageia-dev] Support policy +</A><A NAME="1568"> </A> +<I>Daniel Kreuter +</I> + +<LI><A HREF="001569.html">[Mageia-dev] Support policy +</A><A NAME="1569"> </A> +<I>Daniel Kreuter +</I> + +<LI><A HREF="001574.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1574"> </A> +<I>Daniel Kreuter +</I> + +<LI><A HREF="001567.html">[Mageia-dev] Support policy +</A><A NAME="1567"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001572.html">[Mageia-dev] Support policy +</A><A NAME="1572"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001571.html">[Mageia-dev] Support policy +</A><A NAME="1571"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001565.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1565"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001566.html">[Mageia-dev] Support policy +</A><A NAME="1566"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001573.html">[Mageia-dev] Support policy +</A><A NAME="1573"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001577.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1577"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001570.html">[Mageia-dev] Support policy +</A><A NAME="1570"> </A> +<I>Samuel Verschelde +</I> + +<LI><A HREF="001576.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1576"> </A> +<I>andre999 +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Wed Dec 1 22:50:26 CET 2010</i><br> + <b>Archived on:</b> <i>Wed Dec 1 22:50:32 CET 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101201/date.html b/zarb-ml/mageia-dev/20101201/date.html new file mode 100644 index 000000000..efc16fffb --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/date.html @@ -0,0 +1,112 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 1 December 2010 Archive by date</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>1 December 2010 Archives by date</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Wed Dec 1 00:12:04 CET 2010</i><br> + <b>Ending:</b> <i>Wed Dec 1 22:50:26 CET 2010</i><br> + <b>Messages:</b> 13<p> + <ul> + +<LI><A HREF="001565.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1565"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001566.html">[Mageia-dev] Support policy +</A><A NAME="1566"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001567.html">[Mageia-dev] Support policy +</A><A NAME="1567"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001572.html">[Mageia-dev] Support policy +</A><A NAME="1572"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001568.html">[Mageia-dev] Support policy +</A><A NAME="1568"> </A> +<I>Daniel Kreuter +</I> + +<LI><A HREF="001571.html">[Mageia-dev] Support policy +</A><A NAME="1571"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001569.html">[Mageia-dev] Support policy +</A><A NAME="1569"> </A> +<I>Daniel Kreuter +</I> + +<LI><A HREF="001570.html">[Mageia-dev] Support policy +</A><A NAME="1570"> </A> +<I>Samuel Verschelde +</I> + +<LI><A HREF="001573.html">[Mageia-dev] Support policy +</A><A NAME="1573"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001574.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1574"> </A> +<I>Daniel Kreuter +</I> + +<LI><A HREF="001575.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1575"> </A> +<I>Anssi Hannula +</I> + +<LI><A HREF="001576.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1576"> </A> +<I>andre999 +</I> + +<LI><A HREF="001577.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1577"> </A> +<I>Maarten Vanraes +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Wed Dec 1 22:50:26 CET 2010</i><br> + <b>Archived on:</b> <i>Wed Dec 1 22:50:32 CET 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101201/index.html b/zarb-ml/mageia-dev/20101201/index.html new file mode 120000 index 000000000..db4b46f72 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/index.html @@ -0,0 +1 @@ +thread.html
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/20101201/subject.html b/zarb-ml/mageia-dev/20101201/subject.html new file mode 100644 index 000000000..b812ad196 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/subject.html @@ -0,0 +1,112 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 1 December 2010 Archive by subject</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>1 December 2010 Archives by subject</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Wed Dec 1 00:12:04 CET 2010</i><br> + <b>Ending:</b> <i>Wed Dec 1 22:50:26 CET 2010</i><br> + <b>Messages:</b> 13<p> + <ul> + +<LI><A HREF="001565.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1565"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001574.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1574"> </A> +<I>Daniel Kreuter +</I> + +<LI><A HREF="001575.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1575"> </A> +<I>Anssi Hannula +</I> + +<LI><A HREF="001576.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1576"> </A> +<I>andre999 +</I> + +<LI><A HREF="001577.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1577"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001566.html">[Mageia-dev] Support policy +</A><A NAME="1566"> </A> +<I>Maarten Vanraes +</I> + +<LI><A HREF="001567.html">[Mageia-dev] Support policy +</A><A NAME="1567"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001572.html">[Mageia-dev] Support policy +</A><A NAME="1572"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001568.html">[Mageia-dev] Support policy +</A><A NAME="1568"> </A> +<I>Daniel Kreuter +</I> + +<LI><A HREF="001571.html">[Mageia-dev] Support policy +</A><A NAME="1571"> </A> +<I>Buchan Milne +</I> + +<LI><A HREF="001569.html">[Mageia-dev] Support policy +</A><A NAME="1569"> </A> +<I>Daniel Kreuter +</I> + +<LI><A HREF="001570.html">[Mageia-dev] Support policy +</A><A NAME="1570"> </A> +<I>Samuel Verschelde +</I> + +<LI><A HREF="001573.html">[Mageia-dev] Support policy +</A><A NAME="1573"> </A> +<I>Maarten Vanraes +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Wed Dec 1 22:50:26 CET 2010</i><br> + <b>Archived on:</b> <i>Wed Dec 1 22:50:32 CET 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101201/thread.html b/zarb-ml/mageia-dev/20101201/thread.html new file mode 100644 index 000000000..7e0ba5c59 --- /dev/null +++ b/zarb-ml/mageia-dev/20101201/thread.html @@ -0,0 +1,135 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 1 December 2010 Archive by thread</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>1 December 2010 Archives by thread</h1> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Wed Dec 1 00:12:04 CET 2010</i><br> + <b>Ending:</b> <i>Wed Dec 1 22:50:26 CET 2010</i><br> + <b>Messages:</b> 13<p> + <ul> + +<!--0 01291158724- --> +<LI><A HREF="001565.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1565"> </A> +<I>Maarten Vanraes +</I> + +<UL> +<!--1 01291158724-01291223088- --> +<LI><A HREF="001574.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1574"> </A> +<I>Daniel Kreuter +</I> + +</UL> +<!--0 01291160012- --> +<LI><A HREF="001566.html">[Mageia-dev] Support policy +</A><A NAME="1566"> </A> +<I>Maarten Vanraes +</I> + +<UL> +<!--1 01291160012-01291192938- --> +<LI><A HREF="001568.html">[Mageia-dev] Support policy +</A><A NAME="1568"> </A> +<I>Daniel Kreuter +</I> + +<!--1 01291160012-01291194779- --> +<LI><A HREF="001570.html">[Mageia-dev] Support policy +</A><A NAME="1570"> </A> +<I>Samuel Verschelde +</I> + +<UL> +<!--2 01291160012-01291194779-01291221419- --> +<LI><A HREF="001573.html">[Mageia-dev] Support policy +</A><A NAME="1573"> </A> +<I>Maarten Vanraes +</I> + +</UL> +</UL> +<!--0 01291192552- --> +<LI><A HREF="001567.html">[Mageia-dev] Support policy +</A><A NAME="1567"> </A> +<I>Buchan Milne +</I> + +<UL> +<!--1 01291192552-01291193144- --> +<LI><A HREF="001569.html">[Mageia-dev] Support policy +</A><A NAME="1569"> </A> +<I>Daniel Kreuter +</I> + +</UL> +<!--0 01291192558- --> +<LI><A HREF="001572.html">[Mageia-dev] Support policy +</A><A NAME="1572"> </A> +<I>Buchan Milne +</I> + +<!--0 01291193097- --> +<LI><A HREF="001571.html">[Mageia-dev] Support policy +</A><A NAME="1571"> </A> +<I>Buchan Milne +</I> + +<!--0 01291235380- --> +<LI><A HREF="001575.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1575"> </A> +<I>Anssi Hannula +</I> + +<!--0 01291236888- --> +<LI><A HREF="001576.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1576"> </A> +<I>andre999 +</I> + +<UL> +<!--1 01291236888-01291240226- --> +<LI><A HREF="001577.html">[Mageia-dev] Mirror layout, round two +</A><A NAME="1577"> </A> +<I>Maarten Vanraes +</I> + +</UL> + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Wed Dec 1 22:50:26 CET 2010</i><br> + <b>Archived on:</b> <i>Wed Dec 1 22:50:32 CET 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + |