Bug 2091875 - EPEL 9 missing GeoIP
Summary: EPEL 9 missing GeoIP
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: GeoIP
Version: epel9
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Thomas Andrejak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-31 08:42 UTC by Istiak Ferdous
Modified: 2022-08-01 08:44 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-06-08 09:01:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Istiak Ferdous 2022-05-31 08:42:49 UTC
Description of problem:
EPEL9 missing GeoIP-devel which is required to build ModSecurity and other packages that depends on development headers from GeoIP package. Can there be a EPEL9 branch for this package?


Additional info:
I am willing to adopt the package if current maintainer @totol don't have any time for this package.

Comment 1 Paul Howarth 2022-05-31 09:29:01 UTC
I'm no longer the maintainer of this package but I used to be: I gave it up because it's no longer supported upstream. It's possible that the current maintainer won't want to maintain it for the EPEL-9 lifetime. Is it not possible for ModSecurity and the other packages to migrate to or use libmaxminddb instead?

Comment 2 Istiak Ferdous 2022-05-31 13:19:18 UTC
I can use libmaxminddb but on appstream and codereadybuilder that is older version(1.5.2) and EPEL8, EPEL9 have no branch. I wanted to use the latest one like Fedora. I am not sure about EPEL policy about version overlapping. Maybe that's why there is no EPEL8, EPEL9 branch. I guess I would have to build libmaxmind too.

Comment 3 Paul Howarth 2022-05-31 13:36:47 UTC
EPEL has a non-replacement policy so if a package is available in RHEL base/appstream/codereadybuilder then it can't be in EPEL. If you really need a later version then I guess you'd have to build it yourself. Or perhaps you might ask the libmaxinddb maintainer to build it in a COPR. Or if you're a RHEL customer, you could try requesting RedHat to update libmaxminddb in the next point release?

Comment 4 Istiak Ferdous 2022-06-08 09:01:10 UTC
RHEL probably won't upgrade it because of their updates policy. I managed to compile it myself. I am closing this bug.

Comment 5 Petr Pisar 2022-08-01 08:44:40 UTC
I think that EPEL allows packaging concurrent versions as nondefault module streams. A downside is that user would need to manually enable a stream with the new libmaxminddb before installing it. And that would have ramifications into packages which hard-require the new version. They would need to become modules too.


Note You need to log in before you can comment on or make changes to this bug.