I’m interested in looking at this. Is this the script?

https://github.com/fedora-infra/geoip-city-wsgi/blob/master/geoip-city.wsgi

Assuming that’s the one, it looks like we need to replace GeoIP with geoip2 and wrap the geoip2 data in a structure to match what is currently being returned. Let me know if I’m missing anything.

-- kevin

On Dec 6, 2019, at 6:39 PM, Kevin Fenzi <kevin@scrye.com> wrote:

On Fri, Dec 06, 2019 at 04:49:15PM +0000, Tom Hughes wrote:
On 06/12/2019 16:41, Martin Kolman wrote:
On Fri, 2019-12-06 at 08:38 -0600, Chris Adams wrote:

I also installed the Fedora 31 GeoIP packages and ran the geoipupdate,
and that DB has the correct info.

IIRC the infra team mentioned some issues with the new geoip database
being incompatible with how the service is currently implemented,
resulting in being stuck with an outdated database until this is resolved.

Sounds like it maybe doesn't have support for GeoLite2 and is using the
old MaxMind GeoLite Legacy databases which haven't been updated since
the start of this year.

Yes, that is exactly the case.

We recently looked at this to see if we could retire the service, but it
looks like it's still needed, so we need to figure out how to get cycles
to update it.

If someone wants to work on this, let us know!

kevin
_______________________________________________
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org