Ohey,

as you might have noticed I've just corrected the metadata.xml of all elasticsearch-related packages. For some strange reason I was listed there as maintainer, but since no one wanted to listen to my ideas I guess I wasn't. So now last person who touched it gets stuck with it.

Since proxy-maint refuses to be removed from packages (especially since they were unconditionally added to all packages with a non-gentoo-dev maintainer in metadata) they are the de facto maintainers, and overrule everything else. I've tried multiple strategies including removing them from metadata, but ... see app-admin/elasticsearch, proxy-maint is like the toe fungus that always comes back (e.g. commit f0925c10834464e62ce7209f2afa7797b594d350 )

Sometimes it's almost absurdly funny, especially when you commit RESTRICT="test" because tests fail reliably just to have that reverted.
(See dev-python/elasticsearch-py )

Bonus mention:
bbdc5412061adf598ed935697441a7d6b05f7614
    app-admin/logstash-bin: drop old

    Signed-off-by: Andrew Savchenko <birc...@gentoo.org>

That removed the versions I was using, so I better maintain the versions I use in an overlay. Well ok then.

Since I, as maintainer, can't ... anything, well [CENSORED] this, now they are your packages. Don't try to reassign or drop them: You've demanded, insisted, to be maintainers ... wish granted.

So, err, well, is like ... wtf? I'm not sure how this all makes sense, but it's Not My Problem now. Take care now, bye bye then.

Oh, and Erki Ferenc was in metadata too, he's been inactive but told me that he wants to continue maintaining these packages in the near future. If he asks I'd recommend adding him back.

Patrick

P.S. If this sounds a bit incoherent, well ... the whole situation is, I have no idea what's going on or why I was in metadata ;)

Reply via email to