[GeoNode-devel] New Issue #4153: GeoLite Legacy db discontinued so paver setup fails in Geonode 2.8 dev install

Jonathan Doig j.doig at unsw.edu.au
Fri Jan 11 00:14:29 PST 2019

Hi devs and Happy New Year

Maxmind has discontinued<https://blog.maxmind.com/2018/01/02/discontinuation-of-the-geolite-legacy-databases/> GeoLite Legacy database support as of Jan 2nd 2019.

That causes paver setup to fail when installing Geonode 2.8 dev in Finalize GeoNode Setup & Test<http://docs.geonode.org/en/master/tutorials/install_and_admin/geonode_install/create_geonode_db.html#finalize-geonode-setup-test>.

This is because updategeoip.py expects<https://github.com/GeoNode/geonode/blob/master/geonode/base/management/commands/updategeoip.py#L34> to use geoip2 to handle the new GeoLite2 database, but geoip2 is only available from Django 1.9, not in Django 1.8 as used by Geonode 2.8.
I've raised this as issue 4153<https://github.com/GeoNode/geonode/issues/4153>.

CityData<https://citydata.be.unsw.edu.au/>: Store, discover and share - data for city analytics and decision-making

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20190111/6c91a7bc/attachment.html>

More information about the geonode-devel mailing list