Paul Howarth

The free legacy databases won't be updated after 1st April 2018, and the paid legacy databases on 2nd January 2019: https://blog.maxmind.com/2018/01/02/discontinuation-of-the-geolite-legacy-databases/

Ah, just looked at Bug#4053 and you knew that already; sorry!

Is there any point in supporting mod_geoip at all in 1.3.8? Is there any current support for the format it uses from any GeoIP database source?

I may not be updating to `libmaxminddb` and `mod_geoip2` myself actually, since Maxmind's database license is no longer acceptable for Fedora. I'll probably just drop GeoIP support altogether unless a...

The license issue is with the Maxmind databases, not the library (https://bugzilla.redhat.com/show_bug.cgi?id=1786211). However, there may be an alternative database source: https://db-ip.com/db/lite.php, which has Creative Commons Attributions 4 International License and...

They do need to be kept up to date, yes, but it's convenient for users that database updates come along the same path that regular package updates do.

Just built 1.3.7 on Fedora and found that `PR_RUN_DIR` was empty so `proftpd` tried to create sockets, PID files etc. directly in the root directory. I tried rebuilding with `configure...

@Castaglia, here's the `configure` command that ends up getting run after rpm macro expansion: ``` ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var...

@Castaglia please go ahead and raise it yourself.

As detailed in the links I added, many (most?) Linux distributions have moved from aspell to hunspell several years ago. Red Hat Enterprise Linux 7 (and clones thereof) ship the...