[Pkg-nginx-maintainers] Bug#921034: Depends on MaxMind GeoIP Legacy databases - superseded by GeoIP2

[Thomas Ward]

You're right, Upstream hasn't issued a response.  At least, not on that 
thread.  I reached out to NGINX directly and got a "We're not adjusting 
the GeoIP module" answer.

TO THAT END, however, downstream in Ubuntu we packaged the third party 
geoip2 module as its own independent of the core GeoIP module.

This was later absorbed at some point into the Debian packages and 
applied there, so there IS a libnginx-mod-http-geoip2 available in later 
versions of the packaging, at least in Unstable.


Thomas


On Thu, 29 Aug 2019 15:41:56 +0300 Faidon Liambotis wrote:

 > On Thu, Jan 31, 2019 at 04:36:45PM -0500, Thomas Ward wrote:
 > > The GeoIP module is a core module in NGINX upstream. Keeping this in
 > > mind, it's just packaged here as a dynamic module.
 > >
 > > For reference purposes, I have forwarded this bug report to nginx
 > > upstream's nginx-devel mailing list [1] for their response.
 > >
 > > (Note that this is just me adding information, not adding anything 
'new'
 > > to this discussion, as it is ultimately up to the maintainers to 
include
 > > a third party module or not here in Debian)
 >
 > Thanks Thomas! Looking at that thread, upstream doesn't seem to have
 > issued a response.
 >
 > That said, Debian is already shipping third-party modules in src:nginx,
 > under debian/modules. Would it perhaps be acceptable to the nginx
 > maintainers to include github:leev/ngx_http_geoip2_module in the source
 > package and include it as a separate binary package?
 >
 > Whether we should continue to ship the geoip (legacy) module is
 > orthogonal in a way -- both can be shipped at the same time, although
 > I'd argue that this is no longer very useful.
 >
 > Regards,
 > Faidon
 >
 >