"Version 2.20-01 has been released. This is a drop in replacement for sites running v2.01 with no additional changes required, and all users are encouraged to upgrade when possible. Many new and exciting features have been added in this release. See the CHANGES file for a list of what's been changed/added/fixed. Go to the download page to obtain a copy in your preferred format." Fixes list is a decently long one: ftp://ftp.mrunix.net/pub/webalizer/CHANGES Reproducible: Always
Reassign to primary maintainer.
Ping: 2 months since opened.
Created attachment 172445 [details] webalizer-2.20.01.ebuild Compared to 2.01.10-r16 this one doesn't include default configuration file into /etc and apache configuration. I didn't include those as the old configuration file comes directly from mirror://gentoo. Otherwise this is a direct replacement.
Created attachment 172447 [details, diff] configure.in.patch webalizer's configure.in is broken! Again the very same mistake, that i already fixed in Bug 228137. A patch is attached. Unless that patch is attached, "--disable-geoip" has the same meaning as "--enable-geoip".
Created attachment 172450 [details, diff] configure.in.patch new version with {}
Patch has been sent upstream, by the way.
> Patch has been sent upstream, by the way. Thanks, Sven!
*** Bug 250584 has been marked as a duplicate of this bug. ***
2.21-02 has been released. I haven't tried installing it yet.
*** Bug 258567 has been marked as a duplicate of this bug. ***
Is there a reason Tero & Sven's work on this bug haven't been added to the tree?
Oh, and Sven's configure.in.patch looks like it's integrated with 2.20.02.
I tried to install 2.21-02 using the here supplied ebuild. I only changed this: --- webalizer-2.20.01.ebuild 2009-06-28 14:07:15.000000000 +0200 +++ webalizer-2.21.02.ebuild 2009-06-28 14:11:34.000000000 +0200 @@ -4,7 +4,7 @@ WEBAPP_MANUAL_SLOT="yes" -MY_PV=${PV/.01/-01} +MY_PV=${PV/.02/-02} MY_P=${PN}-${MY_PV} DESCRIPTION="Webserver log file analyzer" As far as I can see it works fine. Can I help in any way to make this become public?
bump any reason, why this takes a year to get done?
(In reply to comment #14) > any reason, why this takes a year to get done? The webalizer ebuild has use flags for popular patches: - geolizer (flag "geoip") - webalizer xtended (flag "xtended") Both patches have not been updated beyond 2.01.10 upstream so far. In this situation it's not trivial to know what's best to do: - Drop use flags "geoip" and "xtended"? - Wait for new releases on these patches? - Bump, keep flags in, throw error when either flag is actually used? - Split off geolizer and webalizer xtended to their own ebuilds? I have not checked in detail, which of these are actually doable, yet. I hope it mnakes the problem a bit more clear.
(In reply to comment #15) > (In reply to comment #14) > > any reason, why this takes a year to get done? > > The webalizer ebuild has use flags for popular patches: > - geolizer (flag "geoip") > - webalizer xtended (flag "xtended") > > Both patches have not been updated beyond 2.01.10 upstream so far. I know for sure, that geoip-support has been merged upstream and is included in versions recently released. AFAIK, the geolizer patch is not needed anymore. Instead, the use-flag could be used to turn that feature on/off.
(In reply to comment #16) > I know for sure, that geoip-support has been merged upstream and is included in > versions recently released. AFAIK, the geolizer patch is not needed anymore. > Instead, the use-flag could be used to turn that feature on/off. See ftp://ftp.mrunix.net/pub/webalizer/CHANGES It's the first item in "Changes/Additions"
Right, there is --enable-geoip upstream now. However, that doesn't resolve the problem yet. Merging geolizer with the latest webalizer gives conflicts, too much for me to say what they mean quickly. While the main point of geolizer might be the gioip feature it offers more. In-depth analysis is required in my eyes.
(In reply to comment #18) > Right, there is --enable-geoip upstream now. > However, that doesn't resolve the problem yet. Merging geolizer with the > latest webalizer gives conflicts, too much for me to say what they mean > quickly. While the main point of geolizer might be the gioip feature it offers > more. In-depth analysis is required in my eyes. Can you ask, whether new patches are going to be released? The projects may be dead. This bug has been open for about 1.5 years. That they haven't released anything might be evidence, that the projects are really dead or that slow, that you might not want to include their patches anymore.
I'm happy to finally have some news here: +*webalizer-2.21.02 (10 Mar 2010) + + 10 Mar 2010; Sebastian Pipping <sping@gentoo.org> + +webalizer-2.21.02.ebuild: + Bump to 2.21.02 (bug #231859) + geolizer and webalizer xtended now have dedicated packages + Bumped, please test and report bugs. Please note geolizer and webalizer xtended have been split off to dedicated ebuilds now: - app-admin/geolizer - app-admin/webalizer-xtended
