Am 27.08.2019 um 16:30 schrieb Faidon Liambotis:
> Hi there,
>
> Thanks Colin for re-raising this! My intention for #885442 was to
> include the GeoLite2 *databases* (i.e. MMDB), rather than their data
> converted to the legacy GeoIP format. I'll avoid making a mess out of
> the BTS though, given we have this bug now :)
>
> On Thu, Aug 08, 2019 at 09:33:27AM +0200, Patrick Matthäi wrote:
>> Dont know. Patches would be welcome :)
> I'd be happy to help with that. Is the package in git somewhere? I don't
> see Vcs-* headers - perhaps you could import it to salsa?
I have got my own subversion system for my packages. If you want to
co-maintain geoip{-database} I could grant you access to it
>> Then also everything which is required to build the MMDB format has to
>> be in buster-backports and stretch-backports-sloppy. It was enough work
>> now to get everything to work again on both releases
> Could you elaborate a little bit more on why do you think that's a
> requirement? As I mentioned repeatedly in #885442, I don't share that
> view; I think we should be shipping MMDBs as-is and not building them
> out of CSVs. We have no reason to believe that MMDBs are generated out
> of CSVs and the most likely scenario is that the opposite holds true.
> Moreover, MMDB is openly and freely documented and with reader and
> writer implementations in all kinds of languages -- more than what we
> can say for most file formats out there.
For me building them from source was a requirement all the time, so that
the package could be in main and not non-free or contrib. So it would be
great if the MMDBs also could be in main.
--
/*
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
*/
