From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Fixing elasticsearch maintainer
Date: Thu, 18 May 2017 13:17:32 -0400 [thread overview]
Message-ID: <CAAr7Pr9t0cHkQVGWD1-_i5c109GQM7xLfYncNLHucDgya37VpQ@mail.gmail.com> (raw)
In-Reply-To: <58b21ad6-9ca5-170d-42c5-b4e5a5f8b0ef@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2171 bytes --]
On Wed, May 17, 2017 at 12:38 PM, Patrick Lauer <patrick@gentoo.org> wrote:
> 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 <bircoph@gentoo.org>
>
> That removed the versions I was using, so I better maintain the versions I
> use in an overlay. Well ok then.
>
I don't quite get this gripe. Gentoo is a rolling distro. Versions of
things "you are using" get removed and replaced with newer versions all the
time. Why is this a big deal now?
-A
>
> 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 ;)
>
>
[-- Attachment #2: Type: text/html, Size: 2912 bytes --]
next prev parent reply other threads:[~2017-05-18 17:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 16:38 [gentoo-dev] Fixing elasticsearch maintainer Patrick Lauer
2017-05-18 15:49 ` Mart Raudsepp
2017-05-18 16:50 ` Andrew Savchenko
2017-05-18 17:17 ` Alec Warner [this message]
2017-05-19 16:38 ` Patrick Lauer
2017-05-20 19:43 ` Tomas Mozes
2017-05-19 13:10 ` Michał Górny
2017-05-19 16:50 ` Patrick Lauer
2017-05-19 17:27 ` Kristian Fiskerstrand
2017-05-19 22:43 ` Kent Fredric
2017-05-19 22:58 ` Kristian Fiskerstrand
2017-05-20 19:57 ` Tomas Mozes
2017-05-20 20:46 ` Michał Górny
2017-05-20 20:51 ` Kristian Fiskerstrand
2017-05-20 21:06 ` Michał Górny
2017-05-20 21:16 ` Kristian Fiskerstrand
2017-05-22 4:10 ` Patrick Lauer
2017-05-22 19:27 ` Kent Fredric
2017-05-22 20:05 ` Matthias Maier
2017-05-22 21:05 ` M. J. Everitt
2017-05-20 21:24 ` Andreas K. Huettel
2017-05-20 19:35 ` Tomas Mozes
2017-05-22 1:52 ` Sam Jorna
2017-05-22 4:12 ` Patrick Lauer
2017-05-22 4:16 ` M. J. Everitt
2017-05-22 4:24 ` Sam Jorna
2017-05-22 19:31 ` Kent Fredric
2017-05-22 5:47 ` Michał Górny
2017-05-22 5:50 ` Sam Jorna
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAr7Pr9t0cHkQVGWD1-_i5c109GQM7xLfYncNLHucDgya37VpQ@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox