Bug 2142695

Will you be able to branch and build webalizer in epel9?

Hi, sorry for the quick message 

opensuse removed libGeoIP-devel [1]

Maybe we can try https://github.com/StoneStepsInc/StoneStepsWebalizer which already supports "MaxMindDB v1.2 or newer" 

what do you suggest ? 

[1]
https://build.opensuse.org/request/show/783487#tab-pane-changes

forgot to mention, because we don't have libGeoIP in epel 9

I would be ok using StoneStepsWebalizer as long as it is 100% backwards compatible with webalizer (and is committed to remaining so). I manage many systems that have pre-build configurations for running webalizer, and any changes in config or command-line options in a new version might break everything. 

If StoneStepsWebalizer has different usage, it should probably be included as a separate package than webalizer (I see the binary already has a different name, `webalizer-stonesteps`).

*** Bug 2262319 has been marked as a duplicate of this bug. ***

@comsec , you want build webalizer without GeoIP ? don't we have alternatives ? awstats vs webalizer vs analog https://www.c-amie.co.uk/software/analog/

(In reply to Sergio Basto from comment #6)
> @comsec , you want build webalizer without GeoIP ? don't we have
> alternatives ? awstats vs webalizer vs analog
> https://www.c-amie.co.uk/software/analog/

Well, as said GeoIP is still available for rhel9 from old offline Remi packages, but as reported in 2066787 it was retired in 2022.
https://blog.maxmind.com/2020/06/retirement-of-geoip-legacy-downloadable-databases-in-may-2022/

I'm not able to find GeoIP2 in Fedora or other main repistories, and don't even know if v2 libraries are compatible with v1 and usable without changes in client code.

So I think that in the meantime better a no geoip webalizer that no webalizer at all, since it's still very fast and useful.

By the way epel8 binaries seem to work on rhel9, but it's obviously not a clean solution in the long term, since databases are no more updated an will shortly contain a lot of errors.

(In reply to Sergio Basto from comment #6)
> @comsec , you want build webalizer without GeoIP ? don't we have
> alternatives ? awstats vs webalizer vs analog
> https://www.c-amie.co.uk/software/analog/

Also old webalizer included with rhel6 seems to be build with it's internal IP database, but since it's 10 years old it's for sure largely wrong, much more than geoip v1.

Regards

(In reply to Sergio Basto from comment #6)
> @comsec , you want build webalizer without GeoIP ? don't we have
> alternatives ? awstats vs webalizer vs analog
> https://www.c-amie.co.uk/software/analog/

I also use awstats where I need more flexibility than webalizer, but since it's interpreted code, not binary, it's n times slower.

webalizer is damn simple and fast.

It seems that you can quite easily update the internal DB to at least 2021 from here:

https://github.com/earnolmartin/EHCP-Force-Edition/raw/master/ehcp/fixes/webalizer/webalizer-geodb-latest.tgz


It should also be possible to use the last 2022 DB from maxmind but it seems that some unknown adaption in file format is needed:

https://stackoverflow.com/questions/75583887/webalizer-geoip-dat-updates-mrunix-net-offline

I found https://github.com/zone-eu/webalizer/commits/master/ 

can you test replace of old GeoIP library with libmaxminddb ?


dnf copr enable sergiomb/webalizer
dnf install webalizer


references 
https://copr.fedorainfracloud.org/coprs/sergiomb/webalizer/

have anyone test the version on copr ? I don't have a great way to test it yet

new version available for tests 


dnf copr enable sergiomb/webalizer
dnf update webalizer

I've taken over the maintainership from Sergio and I've requested for GeoIP to be branched for EPEL9 so we can build in the current state. Let's see what the outcome is of that before doing a build without it :)