The port options set by default for www/apache24 are broken. See following transcript: Script started on Sun Sep 1 00:55:45 2013 root@nucleus:/usr/ports/www/apache24 # make rmconfig ===> No user-specified options configured for apache24-2.4.6 root@nucleus:/usr/ports/www/apache24 # make -V PORT_DBDIR /var/db/ports root@nucleus:/usr/ports/www/apache24 # ls /var/db/ports | grep apache root@nucleus:/usr/ports/www/apache24 # make PORT_DBDIR= BATCH=1 ===> apache24-2.4.6 AUTHN_DBD requires DBD. *** Error code 1 Stop. make: stopped in /usr/ports/www/apache24 root@nucleus:/usr/ports/www/apache24 # ^D Script done on Sun Sep 1 00:56:01 2013 root@nucleus:/usr/ports/www/apache24 # make showconfig | grep DBD AUTHN_DBD=on: SQL-based authentication control AUTHZ_DBD=on: SQL based authorization and Login/Session support DBD=on: Apache DBD Framework SESSION_DBD=off: Session dbd module
Responsible Changed From-To: freebsd-ports-bugs->apache Over to maintainer (via the GNATS Auto Assign Tool)
Responsible Changed From-To: apache->ohauer I'll take it
I cannot reproduce this issue on 9.1 only if I switch from gnugrep to bsdgrep. Can you check if you have bsdgrep enabled and if yes change to the old gnugrep.
olli hauer <ohauer@gmx.de> wrote: >I cannot reproduce this issue on 9.1 only if I switch from gnugrep to >bsdgrep. > >Can you check if you have bsdgrep enabled and if yes change to the old >gnugrep. Yes, I use bsdgrep. I will revert to gnugrep and retest as soon as possible. Glen
On Sun, Sep 01, 2013 at 02:20:56PM -0400, Glen Barber wrote: > olli hauer <ohauer@gmx.de> wrote: > >I cannot reproduce this issue on 9.1 only if I switch from gnugrep to > >bsdgrep. > > > >Can you check if you have bsdgrep enabled and if yes change to the old > >gnugrep. > > Yes, I use bsdgrep. I will revert to gnugrep and retest as soon as possible. > I see this behavior with both gnugrep and bsdgrep. Installing grep(1) with both WITH_BSD_GREP=1 and WITHOUT_BSD_GREP=1 set exhibit the same result. Glen
On 2013-09-04 14:05, Glen Barber wrote: > On Sun, Sep 01, 2013 at 02:20:56PM -0400, Glen Barber wrote: >> olli hauer <ohauer@gmx.de> wrote: >>> I cannot reproduce this issue on 9.1 only if I switch from gnugrep to >>> bsdgrep. >>> >>> Can you check if you have bsdgrep enabled and if yes change to the old >>> gnugrep. >> >> Yes, I use bsdgrep. I will revert to gnugrep and retest as soon as possible. >> > > I see this behavior with both gnugrep and bsdgrep. Installing grep(1) > with both WITH_BSD_GREP=1 and WITHOUT_BSD_GREP=1 set exhibit the same > result. > > Glen > Hm, now it get really strange ... I've created a simple test port, no issue on 8.4 and 9.1 with default grep but as soon I switch to bsdgrep on my 9.1 system the port fails (once saved) Can you do a test with this simple test port? Create an empty directory and place the following Makefile there. http://people.freebsd.org/~ohauer/diffs/PR_181717/ > make config (keep everything default) > make showconfig > make -- Regards, olli
On Wed, Sep 04, 2013 at 11:32:50PM +0200, olli hauer wrote: > On 2013-09-04 14:05, Glen Barber wrote: > > On Sun, Sep 01, 2013 at 02:20:56PM -0400, Glen Barber wrote: > >> olli hauer <ohauer@gmx.de> wrote: > >>> I cannot reproduce this issue on 9.1 only if I switch from gnugrep to > >>> bsdgrep. > >>> > >>> Can you check if you have bsdgrep enabled and if yes change to the old > >>> gnugrep. > >> > >> Yes, I use bsdgrep. I will revert to gnugrep and retest as soon as possible. > >> > > > > I see this behavior with both gnugrep and bsdgrep. Installing grep(1) > > with both WITH_BSD_GREP=1 and WITHOUT_BSD_GREP=1 set exhibit the same > > result. > > > > Glen > > > > Hm, > > now it get really strange ... > > I've created a simple test port, no issue on 8.4 and 9.1 with default grep > but as soon I switch to bsdgrep on my 9.1 system the port fails (once saved) > What happens with gnugrep when you do not save the config? In my original script, setting PORT_DBDIR="" is as if a user has selected 'Cancel' to avoid saving the (otherwise unchanged) configuration in /var/db/ports (or wherever PORT_DBDIR really is). > Can you do a test with this simple test port? > > Create an empty directory and place the following Makefile there. > http://people.freebsd.org/~ohauer/diffs/PR_181717/ > > > make config (keep everything default) > > make showconfig > > make > Sure. root@nucleus:/home/gjb/tmp/porttest # make PORT_DBDIR= BATCH=1 ===> pr181717-1.0 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by pr181717-1.0 for building ===> Extracting for pr181717-1.0 ===> Patching for pr181717-1.0 ===> Configuring for pr181717-1.0 root@nucleus:/home/gjb/tmp/porttest # make showconfig ===> The following configuration options are available for pr181717-1.0: AUTHN_DBD=on AUTHZ_DBD=on DBD=on SESSION_DBD=off root@nucleus:/home/gjb/tmp/porttest # make rmconfig ===> No user-specified options configured for pr181717-1.0 Now if I manually switch DBD and SESSION_DBD, I get the same errors as www/apache24. root@nucleus:/home/gjb/tmp/porttest # make showconfig ===> The following configuration options are available for pr181717-1.0: AUTHN_DBD=on AUTHZ_DBD=on DBD=off SESSION_DBD=on ===> Use 'make config' to modify these settings root@nucleus:/home/gjb/tmp/porttest # make ===> pr181717-1.0 AUTHN_DBD requires DBD. *** Error code 1 Stop. make: stopped in /usr/home/gjb/tmp/porttest Glen
State Changed From-To: open->feedback Hi Glen, can you test the patch from PR ports/181973 ?
On Sat, Apr 05, 2014 at 08:40:06PM +0000, ohauer@FreeBSD.org wrote: > Synopsis: www/apache24: default PORT_OPTIONS are broken > > State-Changed-From-To: open->feedback > State-Changed-By: ohauer > State-Changed-When: Sat Apr 5 20:38:36 UTC 2014 > State-Changed-Why: > Hi Glen, > > can you test the patch from PR ports/181973 ? > Hi, This does seem to fix the issue. Glen
Fixed by gjb@ by committing the patch from PR 181973