Bug#970603: GeoIP database format

2020-09-28 Thread Antonio Terceiro
Control: severity -1 normal On Sat, Sep 19, 2020 at 07:33:39PM +0100, Dániel Fancsali wrote: > Confirmed: built from source with --enable-geoip=legacy and the issue is > gone. Yes, the legacy format is ... legacy. goacess in Debian is configured for the new format, on purpose. signature.asc

Bug#970603: GeoIP database format

2020-09-19 Thread Dániel Fancsali
Confirmed: built from source with --enable-geoip=legacy and the issue is gone. On Sat, 19 Sep 2020 at 18:36, Dániel Fancsali wrote: > Furthermore it seems to me, that all versions (buster, bullseye, > buster-backports) of the geoip-database and geoip-database-extra are using > the legacy

Bug#970603: GeoIP database format

2020-09-19 Thread Dániel Fancsali
Furthermore it seems to me, that all versions (buster, bullseye, buster-backports) of the geoip-database and geoip-database-extra are using the legacy format. On Sat, 19 Sep 2020 at 18:17, Dániel Fancsali wrote: > Hello, > > Just had an idea, and had another look, and it seems, I did spot

Bug#970603: GeoIP database format

2020-09-19 Thread Dániel Fancsali
Hello, Just had an idea, and had another look, and it seems, I did spot something: Both the 1.4 version from bullseye, and the 1.4 upstream (actually meant for buster seem to be built with --enable-geoip=mmdb; whereas the 1.2 official is using --enable-geoip=legacy. See