If you follow the link above you will see:
"As a result you will need to install the OpenFusion repo to install the updated contrib"
Read here as well.
https://wiki.contribs.org/GeoIPYou can either continue using the old contrib with the exclude line but note you will most likely get update errors from the geoipupdate tool when the old DBs are pulled, or add the OpenFusion repo to use the new version. If you use geoip with mail then this is really the best route in the absence of a better solution..
There has been some discussion about how best to do this and there is no easy solution.
The DBs can sit alongside each other, but the updater tool will be overwritten in the new version. The old DBs stopped being maintained in April, and by then were pretty poor (I first noticed issues nearly 2 years ago, and with the shortage of IPv4 IPs, the remaining ones are being swapped around a lot leading to location issues). The v1 DBs will disappear entirely on 2nd Jan 2019.
The only core package that relies on the old GeoIP is Proftd which has the geoip module built in by upstream, even though it is never used. Regrettably no one has bothered to attend to this issue upstream, either at RH or Proftpd, despite knowing about it for nearly 2 years, so we can't deprecate/remove the old geoIP packages currently.
Note current spamassassin 3.4.1 can use geoip v1 if enabled, but it is not a install dependency.
Spamassassin 3.4.2 can use geoip v2 if enabled, but again geoip is not an install dependency. I was intending at looking if I can add some keys to enable it in spamassassin.
All in all it is messy and I wish there was a better way. But I haven't found one yet.