Bug 2066787

Summary: Please branch and build GeoIP in epel9
Product: [Fedora] Fedora EPEL Reporter: Jaroslav Škarvada <jskarvad>
Component: GeoIPAssignee: Jonathan Wright <jonathan>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: anon.amish, carl, cmdr, farrotin, jonathan, paul, peljasz, philipp, plautrba, redhat-bugzilla, sergio, thomas.andrejak
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Bug Depends On:    
Bug Blocks: 2142695, 2066610, 2109779    

Description Jaroslav Škarvada 2022-03-22 13:44:59 UTC
Description of problem:
It's prereq for netsniff-ng (bug 2066610).

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Check the EPEL-9 repo
2.
3.

Actual results:
There are NO GeoIP, GeoIP-devel packages

Expected results:
There are GeoIP, GeoIP-devel packages

Additional info:

Comment 1 Paul Howarth 2022-03-22 14:01:25 UTC
GeoIP is a legacy library, can't it use libmaxminddb instead?

Comment 2 Jaroslav Škarvada 2022-03-22 14:40:30 UTC
(In reply to Paul Howarth from comment #1)
> GeoIP is a legacy library, can't it use libmaxminddb instead?

It seems there is no support upstream for libmaxminddb.

I could build netsniff-ng without GeoIP support, but as EPEL-8 version supported it, I opened this request.

Comment 3 Paul Howarth 2022-03-22 14:57:47 UTC
Somebody raised this upstream in 2019 but nothing seems to have happened:
https://github.com/netsniff-ng/netsniff-ng/issues/212

I used to maintain GeoIP but dropped it about a year after upstream stopped support for it. The current maintainer is keeping it in Fedora for the few things that still need it but I'm not sure if they'll be willing to maintain it in EPEL-9. We'll have to see. But it's definitely worth considering building without GeoIP support. That's what I did for proftpd.

Comment 4 Carl George 🤠 2022-07-15 21:23:56 UTC
*** Bug 2089333 has been marked as a duplicate of this bug. ***

Comment 5 Robert Scheck 2022-07-17 20:02:16 UTC
Please do NOT branch GeoIP for EPEL 9, because MaxMind, the GeoIP upstream, has clearly declared the end of life for GeoIP at https://github.com/maxmind/geoip-api-c/ - and personally, I would somehow question the health and further development of a project currently still depending on GeoIP two years after the deprecation notice (and 7.5 years after libmaxminddb v1.0.0 as first stable release, or even 9 years after the introduction of libmaxminddb in general).

Comment 6 Petr Pisar 2022-08-01 08:46:56 UTC
*** Bug 2112527 has been marked as a duplicate of this bug. ***

Comment 7 Sergio Basto 2023-03-23 11:41:42 UTC
*** Bug 2164055 has been marked as a duplicate of this bug. ***

Comment 8 Fedora Admin user for bugzilla script actions 2025-05-07 02:59:58 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 9 Fedora Admin user for bugzilla script actions 2025-05-07 16:28:22 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 10 Simon de Vlieger 2025-05-10 07:30:18 UTC
*** Bug 2365370 has been marked as a duplicate of this bug. ***