Bug#885441: Deprecate in favor of geoipupdate?

2018-04-13 Thread Patrick Matthäi
Am 27.12.2017 um 05:52 schrieb Faidon Liambotis:
> Package: geoip-database-contrib
> Version: 1.19
> Severity: normal
>
> Hi,

Hi,

sorry for my late answer. This is on my todo list since a long long time..

>
> libmaxminddb/geoipupdate/etc. maintainer here. This may be a bit of an
> odd request:
>
> Have you considered dropping this package in favor of geoipupdate?
> geoipupdate is shipped by MaxMind and is officially supported by them.
> It has a lot more code, and is capable for much more than the shell
> scripts that geoip-database-contrib ships.
>
> geoipupdate is capable of downloading both GeoIP Legacy and GeoIP2
> databases, as well as GeoLite and GeoLite2 databases at the same time,
> so it's a suitable replacement for geoip-database-contrib's
> functionality, that's also forward-looking. (GeoIP Legacy is deprecated
> and an increasing amount of software are switching to GeoIP2.)
>
> I just uploaded geoipupdate 2.5.0-1 that includes:
> * a configuration file, with only GeoLite2 enabled, but also with the
>   edition codes for GeoLite Legacy commented-out to ease a transition,
> * a weekly cronjob, at the request of a user and inspired from
>geoip-database-contrib's equivalent functionality.

Since Geoip v1 is deprecated now and geoipupdate has nearly the same
functionality I also would consider to remove it from sid+testing.

>
> All that said, a few caveats:
> - (Debian's) geoipupdate uses /var/lib/GeoIP for the download location,
>   instead of /usr/share/GeoIP, which is/would be an FHS violation.

But you could use a diversion/alternatives, if the user wants it, to
your package?

>   
> - Additionally, the actual filenames of the databases are going to be
>   different in some cases. geoipupdate names files according to what
>   MaxMind's servers instruct it to and has no option to rename.
>
> - Of the databases geoip-database-contrib ships, only one is not
>   available using geoipupdate: GeoLite ASN IPv6. I don't think it's
>   widely used, especially given that GeoLite IPv6 was and remained an
>   experiment (paid GeoIP IPv6 never existed). If you disagree, we can
>   always ask MaxMind to add it to their geoipupdate server and see what
>   they say.
>
> What do you think? Let me know if there are any ways I can help from the
> geoipupdate side :)
>

If you also don't mind I would fill a RoM and you could provide this
package after that.

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/



Bug#885441: Deprecate in favor of geoipupdate?

2018-02-08 Thread Faidon Liambotis
severity 885441 important
thanks

MaxMind announced that GeoLite Legacy is being discontinued:
https://support.maxmind.com/geolite-legacy-discontinuation-notice/

They gave an advance notice and there is still some time left (effective
date is January 2nd, 2019), but this is still significant for the buster
release.

Regards,
Faidon



Bug#885441: Deprecate in favor of geoipupdate?

2017-12-26 Thread Faidon Liambotis
Package: geoip-database-contrib
Version: 1.19
Severity: normal

Hi,

libmaxminddb/geoipupdate/etc. maintainer here. This may be a bit of an
odd request:

Have you considered dropping this package in favor of geoipupdate?
geoipupdate is shipped by MaxMind and is officially supported by them.
It has a lot more code, and is capable for much more than the shell
scripts that geoip-database-contrib ships.

geoipupdate is capable of downloading both GeoIP Legacy and GeoIP2
databases, as well as GeoLite and GeoLite2 databases at the same time,
so it's a suitable replacement for geoip-database-contrib's
functionality, that's also forward-looking. (GeoIP Legacy is deprecated
and an increasing amount of software are switching to GeoIP2.)

I just uploaded geoipupdate 2.5.0-1 that includes:
* a configuration file, with only GeoLite2 enabled, but also with the
  edition codes for GeoLite Legacy commented-out to ease a transition,
* a weekly cronjob, at the request of a user and inspired from
   geoip-database-contrib's equivalent functionality.

All that said, a few caveats:
- (Debian's) geoipupdate uses /var/lib/GeoIP for the download location,
  instead of /usr/share/GeoIP, which is/would be an FHS violation.
  
- Additionally, the actual filenames of the databases are going to be
  different in some cases. geoipupdate names files according to what
  MaxMind's servers instruct it to and has no option to rename.

- Of the databases geoip-database-contrib ships, only one is not
  available using geoipupdate: GeoLite ASN IPv6. I don't think it's
  widely used, especially given that GeoLite IPv6 was and remained an
  experiment (paid GeoIP IPv6 never existed). If you disagree, we can
  always ask MaxMind to add it to their geoipupdate server and see what
  they say.

What do you think? Let me know if there are any ways I can help from the
geoipupdate side :)

Regards,
Faidon