Bug 2164055
Summary: | Please branch and build GeoIP in epel9 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | farrotin |
Component: | GeoIP | Assignee: | Thomas Andrejak <thomas.andrejak> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel9 | CC: | anon.amish, paul, philipp, 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: | 2023-03-23 11:41:42 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
farrotin
2023-01-24 15:38:37 UTC
Just worth adding that just rebuilding the epel8 one for el9 works fine : https://cbs.centos.org/koji/taskinfo?taskID=3188687 (needed for our own infra tags for centos stream infra) Are you sure you really need this legacy library? See also previous requests for this: https://bugzilla.redhat.com/show_bug.cgi?id=2066787 https://bugzilla.redhat.com/show_bug.cgi?id=2089333 https://bugzilla.redhat.com/show_bug.cgi?id=2091875 https://bugzilla.redhat.com/show_bug.cgi?id=2112527 I just had a quick look at reason why it was needed and it was because of some ansible roles, imported for other ones. But it's true that we switched to python-geoip2 to interact with the .mmdb format anyway, so the GeoIP pkg itself is probably not needed anymore (and geoiplookup tool should be coming from something else, understanding correctly .mmdb format) There is an mmdblookup tool shipped in the libmaxminddb package that can probably be used in place of geoiplookup. *** This bug has been marked as a duplicate of bug 2066787 *** |