CentOS 7: geoipupdate conflicts GeoIP #76
Comments
|
I confirm this behaviour, but I think it could be easily bypassed. The directory /usr/share/GeoIP is in conflict with the one contained in GeoIP: but why geoipupdate wants to create /usr/share/GeoIP folder? it doesn't put any file in it. |
|
I agree that this is an issue, but not creating the directory would be less than ideal. |
|
Same issue here, with CentOS 7.
Any ideas for a workaround?? I've also tried to install |
|
In the meantime, I would recommend using the non-RPM binary. I suppose you could also try installing the RPM with |
|
On CentOS 8 there are conflicts with: geolite2-country-20180605-1.el8.noarch |
|
The problem as I see it is with the GeoIP package providing both data and the library. That means that removing it leave you without a library. In an ideal situation either these would be separate packages or there would be a package providing both lib and data to replace it. Is the GeoIP package using a legacy format? I also can't find a lib package for latest lib geoip. I suspect if more thought out it might end up with its own namespace, IE, geoip2 or geolite. The geolite and geoip packages look like two different things, one with mmdb and one with dat. The GeoIP package is legacy. libmaxminddb looks like the replacement package which also differs from the geoip package as it's pure lib with out the utils (such as geoiplookup). For my use case I think it's enough to remove GeoIP and the geolite packages then just go with libmaxminddb and geoipupdate (which also provides geoiplookup according to above list). For people who need both at the same time it might be a problem. geoiplookup appears to only be in maxmind/geoip-api-c which is legacy. |
|
It appears this issue was being caused by goreleaser/nfpm#117. It should be fixed on the next release. |
4.2.0 * The major version of the module is now included at the end of the module path. Previously, it was not possible to import the module in projects that were using Go modules. Reported by Roman Glushko. GitHub #81. * The minimum Go version is now 1.13. * A valid account ID and license key combination is now required for database downloads, so those configuration options are now required. * The error handling when closing a local database file would previously ignore errors and, upon upgrading to `github.com/pkg/errors` 0.9.0, would fail to ignore expected errors. Reported by Ilya Skrypitsa and pgnd. GitHub #69 and #70. * The RPM release was previously lacking the correct owner and group on files and directories. Among other things, this caused the package to conflict with the `GeoIP` package in CentOS 7 and `GeoIP-GeoLite-data` in CentOS 8. The files are now owned by `root`. Reported by neonknight. GitHub #76.
|
this is still broken for me. using |
|
@lotashah, please upgrade |
|
quick question : we have java based code written for geoipupdate-4.1.4 .. (our code queries the generated mmdb file) if we completely switch to geoip 1.5.0-14 will all operations work well?? (the db file format is different right? and will we be able to update this weekly via a cron job?) |
|
@sh-darshan, my comment about was for the C-based |
|
@oschwald thanks for the super quick response.. so we will upgrade on the instance, we will remove all of which apologies in advance if the question seems trivial but couldn't find a straightforward answer to this online. trying GeoIP-1.5.0.11 (installed as dependency by bind-utils) along with GeoIP-update-1.5.0.11 doesn't seem to work. Thanks |
|
All versions of |
It is not possible to install geoipupdate-4.1.5 on CentOS7 as it conflicts with GeoIP - which is a dependency of crucial core networking tools such as bind-utils:
The text was updated successfully, but these errors were encountered: