Gentoo Archives: gentoo-dev

From: Andrew Savchenko <bircoph@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Fixing elasticsearch maintainer
Date: Thu, 18 May 2017 16:51:35
Message-Id: 20170518195056.265420d89de89bdb1d20e157@gentoo.org
In Reply to: [gentoo-dev] Fixing elasticsearch maintainer by Patrick Lauer
1 On Wed, 17 May 2017 18:38:28 +0200 Patrick Lauer wrote:
2 > Ohey,
3 >
4 > as you might have noticed I've just corrected the metadata.xml of all
5 > elasticsearch-related packages.
6 > For some strange reason I was listed there as maintainer, but since no
7 > one wanted to listen to my ideas I guess I wasn't. So now last person
8 > who touched it gets stuck with it.
9 >
10 > Since proxy-maint refuses to be removed from packages (especially since
11 > they were unconditionally added to all packages with a non-gentoo-dev
12 > maintainer in metadata) they are the de facto maintainers, and overrule
13 > everything else.
14 > I've tried multiple strategies including removing them from metadata,
15 > but ... see app-admin/elasticsearch, proxy-maint is like the toe fungus
16 > that always comes back (e.g. commit
17 > f0925c10834464e62ce7209f2afa7797b594d350 )
18 >
19 > Sometimes it's almost absurdly funny, especially when you commit
20 > RESTRICT="test" because tests fail reliably just to have that reverted.
21 > (See dev-python/elasticsearch-py )
22 >
23 > Bonus mention:
24 > bbdc5412061adf598ed935697441a7d6b05f7614
25 > app-admin/logstash-bin: drop old
26 >
27 > Signed-off-by: Andrew Savchenko <bircoph@g.o>
28
29 Use the full quote please:
30
31 commit bbdc5412061adf598ed935697441a7d6b05f7614
32 Author: Tomas Mozes <tmozes@×××××.com>
33 Date: Mon Feb 13 14:02:21 2017 +0100
34
35 app-admin/logstash-bin: drop old
36
37 Signed-off-by: Andrew Savchenko <bircoph@g.o>
38
39 I applied the commit made by the proxied maintainer as a part of
40 his pull request https://github.com/gentoo/gentoo/pull/3948
41 required to fix bug 609132. (By the way you ignored that bug.)
42
43 Since the proxied maintainer doesn't have the direct access to the
44 tree, I facilitated him and I see nothing wrong with this.
45
46 > That removed the versions I was using, so I better maintain the versions
47 > I use in an overlay. Well ok then.
48
49 Discuss this with your co-maintainers. I see nothing wrong in
50 removing old packages from the tree if this doesn't break any deps
51 and don't result in keywords being dropped.
52
53 > Since I, as maintainer, can't ... anything, well [CENSORED] this, now
54 > they are your packages. Don't try to reassign or drop them: You've
55 > demanded, insisted, to be maintainers ... wish granted.
56
57 Commit from any listed maintainer either direct or proxied is OK.
58
59 Best regards,
60 Andrew Savchenko