Re: New port: textproc/elasticsearch6

2018-02-15 Thread 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 unders

Re: New port: textproc/elasticsearch6

2018-02-15 Thread 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

Re: New port: textproc/elasticsearch6

2018-02-15 Thread 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 > updat

Re: New port: textproc/elasticsearch6

2018-02-15 Thread 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. _

Re: New port: textproc/elasticsearch6

2018-02-15 Thread 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 > > m

Re: apache24 and pkg check --recompute

2018-02-15 Thread Rafal Lukawiecki
> On 14 Feb 2018, at 23:18, Dave Horsfall wrote: > > On Wed, 14 Feb 2018, Rafal Lukawiecki wrote: > >> apache24-2.4.29: missing file /usr/local/www/apache24/cgi-bin/printenv >> apache24-2.4.29: missing file /usr/local/www/apache24/cgi-bin/test-cgi >> apache24-2.4.29: missing file >> /usr/lo

undefined symbol "php7_module" in libphp7.so?

2018-02-15 Thread scratch65535
I upgraded to 11.1, and installed php72. But I'm getting a httpd.conf error saying that "php7_module" is an undefined symbol in the .so It was okay in 7.1 -- did it change? Php.net doesn't seem to have anything to say about it. ___ freebsd-ports@free

Re: undefined symbol "php7_module" in libphp7.so?

2018-02-15 Thread Jochen Neumeister
Am 15.02.2018 um 17:35 schrieb scratch65...@att.net: I upgraded to 11.1, and installed php72. But I'm getting a httpd.conf error saying that "php7_module" is an undefined symbol in the .so It was okay in 7.1 -- did it change? Php.net doesn't seem to have anything to say about it. rebuild a

Re: undefined symbol "php7_module" in libphp7.so?

2018-02-15 Thread scratch65535
[Default] On Thu, 15 Feb 2018 18:54:33 +0100, Jochen Neumeister wrote: > > >Am 15.02.2018 um 17:35 schrieb scratch65...@att.net: >> I upgraded to 11.1, and installed php72. But I'm getting a >> httpd.conf error saying that "php7_module" is an undefined symbol >> in the .so >> >> It was okay in 7

Re: undefined symbol "php7_module" in libphp7.so?

2018-02-15 Thread scratch65535
Did 11.1 break something in PHP? I just reverted to PHP 7.1, but the problem with the .so remains. Who builds libphp7.so? It seems to be a bit of a mess. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-p

Re: undefined symbol "php7_module" in libphp7.so?

2018-02-15 Thread Walter Schwarzenfeld
what said grep php /usr/local/etc/apache24/httpd.conf ___ 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"

synth "--:--:-- check-sanity accessibility/at-spi2-atk" - what/why?

2018-02-15 Thread Bob Willcox
When I run synth 'upgrade-system' lately I always get a port build stuck in the "check-sanity" phase. Seems to never progress or complete (left one attempt over night w/o any obvious progress. So, can anyone tell me what might cause a port to get stuck in the check-sanity phase? Thanks, Bob --