1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
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>
|
