Apache 2.0.54-r31 went stable. The existing stable webalizer ebuild doesn't make use of the new layout. One of the ones that does make use of the new layout should probably go stable now right?
*** Bug 108762 has been marked as a duplicate of this bug. ***
The problem goes deeper than this. The ebuild output implies that the webalizer.conf file generated by the build should be Include'd by the apache config. In fact, webalizer.conf isn't a valid apache config file, and including it in the apache configuration file set will prevent apache from starting. Perhaps there's an option in the webalizer build that builds a true apache module which is capable of interpreting the directives in webalizer.conf, but otherwise this file belongs in /etc, not /etc/apache or /etc/apache2.
Anything new on this item? This bug prevents me from testing app-admin/ webalizer-2.01.10-r5 stable on x86.
Wouldn't a simple change of the einfo to edit and include /etc/apache{,2}/conf/ modules.d/55_webalizer.conf to the /etc/apache{,2}/httpd.conf be enough? As I look at /etc/apache{,2}/conf/modules.d/55_webalizer.conf, it looks like it could be included...
It's pretty easy to reconfigure this thing to work. It just seems ugly that we have quite a few ebuilds now that don't take advantage of the new apache layout.
Created attachment 71962 [details, diff] Diff made on webalizer-2.01.10-r5.ebuild This should help making webalizer work right after emerging webalizer and restarting apache. Out of the box.
From a quick review, it looks like Robert's patch got it right. The generation of stats files should take the Gentoo DocumentRoot into account. The config file, webalizer.conf, on the othere hand, has no relationship to the apache config files, and should not be in or under /etc/apache2.
I just committed -r11 which takes care of the new Apache layout issue by not installing an Apache config file at all. webalizer doesn't need Apache on the same machine at all, so we no longer assume that /etc/apache{2} is there. I'd rather wait another couple of weeks and stable -11, which also takes care of the new webapp-config. Arches, please start stabling in early Feb :)
A very wise decision, considering the fact that webalizer.conf does not, nor did it ever have any relationship to any apache configuration configuration file and uses a totally different syntax :-)
Arches - please test app-admin/webalizer-2.01.10-r12 and mark stable. -r4 and -r5 don't work with the new Apache layout and lack new functionality added in -12.
sparc stable.
x86 good to go... sorry for the delay
-r12 stable on ppc64
hppa done
Marked stable on ppc by hansmi, removing ppc from cc
get your amd64 cookie now!
(In reply to comment #16) > get your amd64 cookie now! > 2.01.10-r12 will not install on amd64: ... !!! ERROR: app-admin/webalizer-2.01.10-r12 failed. !!! Function pkg_setup, Line 52, Exitcode 0 !!! please either set LINGUAS or do not use nls Note: I do not have nls set.
on x86, USE="-nls" emerge =webalizer-2.01.10-r12 works fine.
stable on alpha. Closing since we are the last arch CC'd.
