diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006003.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006003.html | 179 |
1 files changed, 179 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006003.html b/zarb-ml/mageia-dev/2011-June/006003.html new file mode 100644 index 000000000..ef8bc94d1 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006003.html @@ -0,0 +1,179 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Monitoring of new GNOME/upstream releases + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Monitoring%20of%20new%20GNOME/upstream%20releases&In-Reply-To=%3C1308990914.22020.191.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005991.html"> + <LINK REL="Next" HREF="005985.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Monitoring of new GNOME/upstream releases</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Monitoring%20of%20new%20GNOME/upstream%20releases&In-Reply-To=%3C1308990914.22020.191.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Monitoring of new GNOME/upstream releases">misc at zarb.org + </A><BR> + <I>Sat Jun 25 10:35:13 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005991.html">[Mageia-dev] Monitoring of new GNOME/upstream releases +</A></li> + <LI>Next message: <A HREF="005985.html">[Mageia-dev] Monitoring of new GNOME/upstream releases +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6003">[ date ]</a> + <a href="thread.html#6003">[ thread ]</a> + <a href="subject.html#6003">[ subject ]</a> + <a href="author.html#6003">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le vendredi 24 juin 2011 à 13:53 +0200, Olav Vitters a écrit : +><i> On Fri, Jun 24, 2011 at 11:46:59AM +0200, Michael Scherer wrote: +</I>><i> > Now, if you want to create a notification system for that, feel free. +</I>><i> > The software can be found on ouri.zarb.og, the documentation is minimal, +</I>><i> > this is perl. You can however get test result in txt format, html, or +</I>><i> > anything, and thus a tool to send notification ( and more important, a +</I>><i> > tool to configure notification ) can be constructed upon that. +</I>><i> +</I>><i> Thanks for the pointer. Already noticed a few things: +</I>><i> 1. It uses the LATEST-IS files and there was a bug with that and not +</I>><i> everything has been fixed atm (is fixed for new stuff) +</I> +The original setup do use others sources ( others distro, freshmeat, etc +), so I guess this bug would not affect us too much. + +But if I understood well, this is fixed so it would be ok in the long +term ? + +><i> 2. It uses <A HREF="http://fr2.rpmfind.net/linux/gnome.org/sources">http://fr2.rpmfind.net/linux/gnome.org/sources</A> instead of +</I>><i> either <A HREF="http://ftp.gnome.org/pub/GNOME/sources">http://ftp.gnome.org/pub/GNOME/sources</A> (primary mirror) or +</I>><i> <A HREF="http://download.gnome.org/">http://download.gnome.org/</A> (currently just redirects to primary mirror, +</I>><i> long term goal is having it redirect to closest mirror). +</I> +I guess that can be fixed quite quick. + +><i> Didn't fully analyse yet, but noticed it uses a database, so think I'll +</I>><i> need to make two things: +</I>><i> - script to process live update messages (ftp-release-list in case of +</I>><i> GNOME) +</I>><i> - script to notify people (either immediately or when youri runs from +</I>><i> cron) + setting in database which ensures the announce only goes out +</I>><i> once +</I>><i> +</I>><i> I'll try to work on this. +</I>><i> +</I>><i> How would the maintainer data be stored btw? Should it be a config file +</I>><i> that a script generates, LDAP? +</I> +It would be in a web software, with a json export. But the software is +not finished yet, Pascal Terjan said he would look at it. See +<A HREF="http://gitorious.org/mageia-maintainers-database-r2">http://gitorious.org/mageia-maintainers-database-r2</A> + +><i> Also: is a maintainer always the same for all branches? e.g. if someone +</I>><i> maintainers metacity, that person is responsible for Cauldron, stable +</I>><i> releases, backports, etc (some distributions differ on this)? +</I> +So far, yes. We discussed the concept of having more than one maintainer +however per package. +-- +Michael Scherer + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005991.html">[Mageia-dev] Monitoring of new GNOME/upstream releases +</A></li> + <LI>Next message: <A HREF="005985.html">[Mageia-dev] Monitoring of new GNOME/upstream releases +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6003">[ date ]</a> + <a href="thread.html#6003">[ thread ]</a> + <a href="subject.html#6003">[ subject ]</a> + <a href="author.html#6003">[ 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> |