| 1 |
On Wed, May 17, 2017 at 6:38 PM, Patrick Lauer <patrick@g.o> wrote: |
| 2 |
|
| 3 |
> For some strange reason I was listed there as maintainer, but since no one |
| 4 |
> wanted to listen to my ideas I guess I wasn't. So now last person who |
| 5 |
> touched it gets stuck with it. |
| 6 |
> |
| 7 |
|
| 8 |
|
| 9 |
For elasticsearch, you added yourself to the maintainers, so why are you |
| 10 |
surprised to be there (e6175815b5792f09acd90627af5fe23f616ad245)? |
| 11 |
|
| 12 |
You also added yourself to other packages, for example elasticsearch-cutor |
| 13 |
(bd21ed1ef20cb2d27a87a4dadf780565236a72cd) without asking the maintainer |
| 14 |
(me at that time). |
| 15 |
|
| 16 |
And where exactly have you expressed your ideas? |
| 17 |
|
| 18 |
|
| 19 |
|
| 20 |
> |
| 21 |
> Since proxy-maint refuses to be removed from packages (especially since |
| 22 |
> they were unconditionally added to all packages with a non-gentoo-dev |
| 23 |
> maintainer in metadata) they are the de facto maintainers, and overrule |
| 24 |
> everything else. |
| 25 |
> I've tried multiple strategies including removing them from metadata, but |
| 26 |
> ... see app-admin/elasticsearch, proxy-maint is like the toe fungus that |
| 27 |
> always comes back (e.g. commit f0925c10834464e62ce7209f2afa7797b594d350 ) |
| 28 |
> |
| 29 |
|
| 30 |
|
| 31 |
Why did you add me as the maintainer of elasticsearch without asking and |
| 32 |
then removing proxy-maint so I cannot make any changes to elasticsearch at |
| 33 |
all? If you want to make all the changes, then I don't need to be there and |
| 34 |
I can just open regular bug reports and you merge them. |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
> |
| 39 |
> Sometimes it's almost absurdly funny, especially when you commit |
| 40 |
> RESTRICT="test" because tests fail reliably just to have that reverted. |
| 41 |
> (See dev-python/elasticsearch-py ) |
| 42 |
> |
| 43 |
|
| 44 |
Regarding RESTRICT="test", I was the one to revert your change because I |
| 45 |
thought it's a mistake as the tests passed for me. As soon as we discussed |
| 46 |
this via irc that it only happens in chroot, it got back. Now a few days |
| 47 |
ago @mrueg accidentally removed the restriction but after mailing him he |
| 48 |
reverted his change so it's as you made it. |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
> |
| 53 |
> Bonus mention: |
| 54 |
> bbdc5412061adf598ed935697441a7d6b05f7614 |
| 55 |
> app-admin/logstash-bin: drop old |
| 56 |
> |
| 57 |
> Signed-off-by: Andrew Savchenko <bircoph@g.o> |
| 58 |
> |
| 59 |
> That removed the versions I was using, so I better maintain the versions I |
| 60 |
> use in an overlay. Well ok then. |
| 61 |
> |
| 62 |
> |
| 63 |
Logstash is yet another package where you made yourself a maintainer |
| 64 |
without asking the maintainer (again, it was me). I don't remember you ever |
| 65 |
wanting to keep the old version of logstash in the repo. Plus, you don't |
| 66 |
need to update and you can mask the update. If you really want to use and |
| 67 |
old version (we already had multiple version of 5.x in the tree by that |
| 68 |
time), you can keep in your overlay. |
Archives