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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] new mgarepo version
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20new%20mgarepo%20version&In-Reply-To=%3C4E2259A5.9090800%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006769.html">
<LINK REL="Next" HREF="007084.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] new mgarepo version</H1>
<B>andre999</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20new%20mgarepo%20version&In-Reply-To=%3C4E2259A5.9090800%40laposte.net%3E"
TITLE="[Mageia-dev] new mgarepo version">andr55 at laposte.net
</A><BR>
<I>Sun Jul 17 05:40:21 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006769.html">[Mageia-dev] new mgarepo version
</A></li>
<LI>Next message: <A HREF="007084.html">[Mageia-dev] new mgarepo version
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6811">[ date ]</a>
<a href="thread.html#6811">[ thread ]</a>
<a href="subject.html#6811">[ subject ]</a>
<a href="author.html#6811">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Michael Scherer a écrit :
><i>
</I>><i> Le samedi 16 juillet 2011 à 14:31 +0300, Ahmad Samir a écrit :
</I>>><i> On 16 July 2011 03:02, Michael Scherer<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote:
</I>>>><i> Le mercredi 13 juillet 2011 à 12:11 +0200, nicolas vigier a écrit :
</I>>>>><i> On Wed, 13 Jul 2011, Samuel Verschelde wrote:
</I>>>>><i>
</I>>>>>><i> Le mercredi 13 juillet 2011 00:30:41, nicolas vigier a écrit :
</I>>>>>>><i> Hello.
</I>>>>>>><i>
</I>>>>>>><i> mgarepo version 1.9.11 adds maintdb command :
</I>>>>>>><i>
</I>>>>>>><i> $ mgarepo maintdb --help
</I>>>>>>><i> Usage:
</I>>>>>>><i> Take maintainership of one package :
</I>>>>>>><i> mgarepo maintdb set [package] [login]
</I>>>>>>><i>
</I>>>>>>><i> Remove yourself from maintainer of a package :
</I>>>>>>><i> mgarepo maintdb set [package] nobody
</I>>>>>>><i>
</I>>>>>>><i> See who is maintainer of a package :
</I>>>>>>><i> mgarepo maintdb get [package]
</I>>>>>>><i>
</I>>>>>>><i> See the list of all packages with their maintainer :
</I>>>>>>><i> mgarepo maintdb get
</I>>>>>><i>
</I>>>>>><i> I used in in Mageia 1 using the package in updates_testing and it works well.
</I>>>>><i>
</I>>>>><i> Ok, it's moved to updates now.
</I>>>><i>
</I>>>><i> Wasn't it against the policy ( ie, this is neither a bugfix, this is a
</I>>>><i> version update, providing feature ) ?
</I>>>><i>
</I>>><i>
</I>>><i> That is a bug fix; is there any other way a Mageia packager running
</I>>><i> mga1 can set/unset himself as a maintainer of a package in the
</I>>><i> official Mageia repos?
</I>><i>
</I>><i> Yes :
</I>><i> - using cauldron in a vm, a chroot
</I>><i> - backporting by himself the package
</I>><i>
</I>><i> Packagers convenience do not seems a reason to bypass our policies.
</I>><i>
</I>>><i> That is not a "feature", that's a "basic requirement" in repository
</I>>><i> access and management tool for a distro, that was missing and is now
</I>>><i> available, that warrants an official update, IMHO...
</I>><i>
</I>><i> Everybody has a different vision of what is a basic requirement, and the
</I>><i> problem with such reasoning is that we first start to say "this is not a
</I>><i> new feature", and then, someone say "I need to have this in stable and
</I>><i> like $FOO, I think that's a basic requirement, so we should
</I>><i> backport/upgrade".
</I>
+1
I think it's better to follow policy as much as possible. And try to avoid a
lot of ad hoc exceptions. If we come to a concensus on an exception, that
would effectively revise our policy. But it is better to revise policy first.
A new feature, however essential it may seem, is still a new feature.
And nothing is wrong with using the occasional backport for specific reasons.
Although I installed the mgarepo update, I would have looked for it in
backports if it hadn't been in updates.
><i> All packagers should have a cauldron installed somewhere, or that mean
</I>><i> they cannot test any packages or try to reproduce any bugs on it ( ie,
</I>><i> do the job of a package maintainer ).
</I>
Good point. Have to do that soon. That should be documented for apprentices.
(If not already.)
><i> And so if they do not have, I do not think we should encourage them to
</I>><i> do so.
</I>
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006769.html">[Mageia-dev] new mgarepo version
</A></li>
<LI>Next message: <A HREF="007084.html">[Mageia-dev] new mgarepo version
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6811">[ date ]</a>
<a href="thread.html#6811">[ thread ]</a>
<a href="subject.html#6811">[ subject ]</a>
<a href="author.html#6811">[ 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>
|
