Re: New port: textproc/elasticsearch6

[Kurt Jaeger]

Hi!

> I don't think I makes sense to put it back to pool or tj@ is resetted 
> for elasticsearch ports. So someone other can take all elasticsearch
> 
> port. As I wrote in my first answer: it is better one maintainer make 
> all elasticsearch ports. So please but tj@ for the moment back as
> 
> maintainer.

While adding a port with maintainer, then dropping that maintainer
looks like it's according to the ports handbook, it at least violates
the spirit.

Giving the port to someone who's not very active right now, without him
activily approving it was my mistake.

I'll work on a solution (this evening CET).

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: New port: textproc/elasticsearch6

[Walter Schwarzenfeld]

I don't think I makes sense to put it back to pool or tj@ is resetted 
for elasticsearch ports. So someone other can take all elasticsearch


port. As I wrote in my first answer: it is better one maintainer make 
all elasticsearch ports. So please but tj@ for the moment back as


maintainer.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: New port: textproc/elasticsearch6

[Romain Tartière]

On Thu, Feb 15, 2018 at 09:49:24AM +0100, Walter Schwarzenfeld wrote:
> No, that's a misunderstood. Let the maintainer for the port (I don't 
> really want the port). It is better one maintainer make all elastisearch
> 
> ports. It was a request on FreeBSD Forum for elasticsearch6. First I 
> updated elasticsearch5 and as I was "in work" I make the PR for
> 
> elasticsearch6. It was committed very quick. But I never wanted to 
> override or overrule a maintainer.

Ooops, ETOOLATE :-)  BTW, assigning maintainership to someone is not a
great idea, and as noted in the previous e-mail, tj@ has not committed
to the ports repository in the last 6 month.

You can request to drop maintainership, but in this case, maybe it
wasn't worth doing a port?

-- 
Romain Tartière   http://people.FreeBSD.org/~romain/
pgp: 8234 9A78 E7C0 B807 0B59  80FF BA4D 1D95 5112 336F (ID: 0x5112336F)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)


signature.asc
Description: PGP signature

Re: New port: textproc/elasticsearch6

[Walter Schwarzenfeld]

No, that's a misunderstood. Let the maintainer for the port (I don't 
really want the port). It is better one maintainer make all elastisearch


ports. It was a request on FreeBSD Forum for elasticsearch6. First I 
updated elasticsearch5 and as I was "in work" I make the PR for


elasticsearch6. It was committed very quick. But I never wanted to 
override or overrule a maintainer.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: New port: textproc/elasticsearch6

[Romain Tartière]

Adding concerned people in the loop.

On Wed, Feb 14, 2018 at 07:25:35PM -0500, John W. O'Brien wrote:
> I'm glad to see this in the tree and appreciate the work pi@ and
> w.schwarzenfeld have done.
> 
> I'm puzzled about why tj@, who is AWOL, ended up as maintainer. Could
> somebody help me understand this?
> 
> $ svn log -c 461559 /usr/ports | egrep "^r[0-9]|Submitted"
> r461559 | pi | 2018-02-12 01:49:48 -0500 (Mon, 12 Feb 2018) | 10 lines
> Submitted by:   w.schwarzenf...@utanet.at
> $ svn diff -c 461559 /usr/ports | grep MAINTAINER
> +MAINTAINER=t...@freebsd.org
> 
> Nothing against tj@, by the way.

I guess the submitter of the PR used a previous version of elasticsearch
(textproc/elasticsearch5) as a base and forgot to update the MAINTAINER
line:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225836

Thanks for catching this, I will:
  - Update the port so that it is copied from textproc/elasticsearch5
(in order to preserve history);
  - Assign it to Walter as it should have:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#makefile-maintainer

Regards,
Romain

-- 
Romain Tartière   http://people.FreeBSD.org/~romain/
pgp: 8234 9A78 E7C0 B807 0B59  80FF BA4D 1D95 5112 336F (ID: 0x5112336F)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)


signature.asc
Description: PGP signature

New port: textproc/elasticsearch6

[John W. O'Brien]

I'm glad to see this in the tree and appreciate the work pi@ and
w.schwarzenfeld have done.

I'm puzzled about why tj@, who is AWOL, ended up as maintainer. Could
somebody help me understand this?

$ svn log -c 461559 /usr/ports | egrep "^r[0-9]|Submitted"
r461559 | pi | 2018-02-12 01:49:48 -0500 (Mon, 12 Feb 2018) | 10 lines
Submitted by:   w.schwarzenf...@utanet.at
$ svn diff -c 461559 /usr/ports | grep MAINTAINER
+MAINTAINER=t...@freebsd.org

Nothing against tj@, by the way.

-- 
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
0x474ABD3C1A7B3F70 (expires 2018-03-14)



signature.asc
Description: OpenPGP digital signature