Bug#768979: Thanks and geoipupdate for free GeoLite users
Thanks so much for packaging all of these! Although it is poorly advertised, geoipupdate can actually be used with the free GeoLite databases, e.g., with the GeoIP.conf file: UserId 99 LicenseKey ProductIds 506 533 I think it would be reasonable to use this as a default in a general package. The GeoLite2 databases should work too with the product IDs of GeoLite2-City and GeoLite2-Country, but there appears to be an issue with the deployment of them for geoipupdate currently. Hopefully in the future we will clean up that fake UserId/LicenseKey, but even as it stands, this is preferable for most people to using a homemade script for downloading as it only downloads if the file has changed, verifies the MD5s before deploy, and safely moves the verified files over the old files. Greg
Bug#768979: Thanks and geoipupdate for free GeoLite users
On Mon, Nov 10, 2014 at 4:58 PM, Faidon Liambotis parav...@debian.org wrote: Oh wow, that is indeed great (and indeed poorly advertised :). I wasn't aware of this at all. We could replace geoip-database-contrib with this entirely. Two questions: 1) Where can I find the product IDs for the rest of the GeoLite databases? Ideally we'd list all of them, at least commented-out. 506 - GeoLite Legacy Country 517 - GeoLite ASN 533 - GeoLite Legacy City GeoLite2-Country - GeoLite2 Country GeoLite2-City - GeoLite2 City It doesn't appear that we have any of the legacy IPv6 databases available through geoipupdate. I'll create an internal issue for that but work on the legacy products is generally a lower priority now that GeoIP2 is out. 2) Is there an ETA for fixing the GeoLite2 products on the server? I could wait for this before I make an upload. If the current build goes smoothly, this should be available tomorrow. Greg
Bug#768979: Thanks and geoipupdate for free GeoLite users
On 11/11/14 02:42, Gregory Oschwald wrote: Thanks so much for packaging all of these! You're very welcome :) FWIW, I've also submitted an ITP for the Python bindings, #768984. I don't have any plans for the rest of the language binaries for now. All three packages are essentially done (modulo your recommendations below) and in Debian's git: http://anonscm.debian.org/cgit/collab-maint/geoipupdate.git http://anonscm.debian.org/cgit/collab-maint/libmaxminddb.git http://anonscm.debian.org/cgit/collab-maint/python-maxminddb.git Although it is poorly advertised, geoipupdate can actually be used with the free GeoLite databases, e.g., with the GeoIP.conf file: UserId 99 LicenseKey ProductIds 506 533 I think it would be reasonable to use this as a default in a general package. The GeoLite2 databases should work too with the product IDs of GeoLite2-City and GeoLite2-Country, but there appears to be an issue with the deployment of them for geoipupdate currently. Hopefully in the future we will clean up that fake UserId/LicenseKey, but even as it stands, this is preferable for most people to using a homemade script for downloading as it only downloads if the file has changed, verifies the MD5s before deploy, and safely moves the verified files over the old files. Oh wow, that is indeed great (and indeed poorly advertised :). I wasn't aware of this at all. We could replace geoip-database-contrib with this entirely. Two questions: 1) Where can I find the product IDs for the rest of the GeoLite databases? Ideally we'd list all of them, at least commented-out. 2) Is there an ETA for fixing the GeoLite2 products on the server? I could wait for this before I make an upload. Thanks for the amazingly quick feedback :) Regards, Faidon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
