Bug 1224705

Summary:	geoip is deprecated upstream what is the plan after it is gone?
Product:	Red Hat Enterprise Linux 7	Reporter:	Nikos Mavrogiannopoulos <nmavrogi>
Component:	GeoIP	Assignee:	Michal Ruprich <mruprich>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	carl, thozza
Target Milestone:	rc	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-26 14:12:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nikos Mavrogiannopoulos 2015-05-25 12:02:43 UTC

According to the discussion in:
https://bugzilla.redhat.com/show_bug.cgi?id=1220698

upstream has marked the geoip libraries and apps as legacy and plans no update on them. Unfortunately it has deprecated them using a totally different and incompatible set of libraries and tools.

What is the plan for RHEL? What should we do if there will not be an updated on the geoip data accessed by these libraries?

Comment 6 Carl George 2018-05-29 19:28:51 UTC

Until Red Hat determines their official solution to this, there are a few EPEL packages that may be of assistance.  geolite2-city and geolite2-country contain the new format databases from MaxMind.  golang-github-oschwald-maxminddb-golang-devel is a golang interface to read the new databases.  libmaxminddb contains the C library to read the new databases.  libmaxminddb-devel also contains the mmdblookup CLI lookup tool.  Applications still need work to use these new libraries and databases, but it's a start.

Comment 7 Tomáš Hozza 2018-10-26 14:12:07 UTC


*** This bug has been marked as a duplicate of bug 1607876 ***

Comment 8 Carl George 2018-10-26 14:18:08 UTC

Closing a pubic bug as a duplicate of a private bug is not cool.  Can bug 1607876 be made public?

Comment 9 Tomáš Hozza 2018-10-26 14:52:26 UTC

(In reply to Carl George from comment #8)
> Closing a pubic bug as a duplicate of a private bug is not cool.  Can bug
> 1607876 be made public?

Sorry for that. I made the bug public. However the description of the bug can not be made public for now.

Comment 10 Carl George 2018-10-26 14:59:58 UTC

Thanks Tomáš.  If geolite2-city and geolite2-country get added to RHEL I'll be happy to retire them from EPEL to comply with policy.