Port www/apache22 has mod_alias enabled by default. However for some reason the option framework always sets it as disabled. How-To-Repeat: cd /usr/ports/www/apache22 make rmconfig make config (verify Alias is enabled) make showconfig .. ALIAS=off: mod_alias .. make config (enable mod_alias) make showconfig .. ALIAS=off: mod_alias ..
Responsible Changed From-To: freebsd-ports-bugs->apache Over to maintainer (via the GNATS Auto Assign Tool)
Hi Remko, I don't see this issue on 8.4 and 9.1. Perhaps it is a setting in /etc/make.conf? Please try the following. $ mv /etc/make.conf /etc/make.conf.save $ make showconfig | grep ALIAS and $ make show-modules | grep ALIAS If mod_alias is still disabled set AUTHN_ALIAS, ALIAS, VHOST_ALIAS 'on' and test again. (Maybe it is an issue with the changes made for pkg during the last days) -- Regards, olli
State Changed From-To: open->feedback I'll take it
Responsible Changed From-To: apache->ohauer
> I don't think it has anything to do with any recent changes. I've had this > behaviour for quite some time. Possibly since the change to the new option > framework. Hm, any change you have the new bsdgrep installed?
Could you try with the old grep and move the bsdgrep out of the way (ie rename to bsdgrep). It has cost me already sleepless nights to debug this issue for the apache port. On 2013-06-18 11:01, SirDice wrote: > Ah, yes. I have. > > > > > On Tue, Jun 18, 2013 at 10:59 AM, olli hauer <ohauer@gmx.de> wrote: > >>> I don't think it has anything to do with any recent changes. I've had >> this >>> behaviour for quite some time. Possibly since the change to the new >> option >>> framework. >> >> >> Hm, any change you have the new bsdgrep installed? >> >
I don't know exactly why this happened. There is only one place where egrep is used and I guess here the bsdgrep strugles. Maybe I can find the bsdgrep related PR where I have added the finding as comment. On 2013-06-18 11:08, SirDice wrote: > I'll rebuild world without bsdgrep, I have to rebuild world anyway > (security advisory came out today). > > But why would that cause only the ALIAS module to be disabled? As far as I > can tell no other module is affected. > > > > On Tue, Jun 18, 2013 at 11:04 AM, olli hauer <ohauer@gmx.de> wrote: > >> Could you try with the old grep and move the bsdgrep out of the way (ie >> rename to bsdgrep). >> >> It has cost me already sleepless nights to debug this issue for the apache >> port. >> >> >> >> >> >> On 2013-06-18 11:01, SirDice wrote: >>> Ah, yes. I have. >>> >>> >>> >>> >>> On Tue, Jun 18, 2013 at 10:59 AM, olli hauer <ohauer@gmx.de> wrote: >>> >>>>> I don't think it has anything to do with any recent changes. I've had >>>> this >>>>> behaviour for quite some time. Possibly since the change to the new >>>> option >>>>> framework. >>>> >>>> >>>> Hm, any change you have the new bsdgrep installed? >>>> >>> >> >
On 2013-06-19 12:03, SirDice wrote: > Alright, I can confirm it was probably bsdgrep. After building world > without it the port now correctly enables mod_alias. > > Thank you for the support! > OK, Thanks for the feedback. I will close the PR.
State Changed From-To: feedback->closed Issue resolved by using the old grep instead of bsdgrep.