[Bug 1186889] Review Request: geoipupdate - Update GeoIP2 and GeoIP Legacy binary databases from MaxMind

bugzilla at redhat.com bugzilla at redhat.com
Fri Jan 30 17:34:42 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1186889



--- Comment #14 from Paul Howarth <paul at city-fan.org> ---
(In reply to Philip Prindeville from comment #12)
> (In reply to Paul Howarth from comment #11)
> 
> > Yes, this should be:
> > 
> > Provides: GeoIP-update = 1.6.0
> > Obsoletes: GeoIP-update < 1.6.0
> > 
> > You could arguably use %{version} in the Provides: line but I think it's
> > safer to stick with 1.6.0 as geoipupdate looks to have a different numbering
> > scheme to GeoIP.
> 
> Fixed.

We must make sure that anyone updating from GeoIP 1.5.x to 1.6.x gets the GeoIP
+ geoipupdate combination, as must anyone with GeoIP updating from F-21 to
F-22. People doing fresh installs on F-22 can install the two packages
independently. It can be tricky to get the provides/obsoletes/requires correct
for all of these cases, so they should be tested.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component


More information about the package-review mailing list