Re: Issue with Fedora GeoIP service

2019-12-07 Thread Chris Adams
Once upon a time, Kevin Fenzi said: > On Fri, Dec 06, 2019 at 04:49:15PM +, Tom Hughes wrote: > > On 06/12/2019 16:41, Martin Kolman wrote: > > > On Fri, 2019-12-06 at 08:38 -0600, Chris Adams wrote: > > > > > > > I also installed the Fedora 31 GeoIP packages and ran the geoipupdate, > > > >

Re: Issue with Fedora GeoIP service

2019-12-06 Thread Kevin Fenzi
On Fri, Dec 06, 2019 at 04:49:15PM +, Tom Hughes wrote: > On 06/12/2019 16:41, Martin Kolman wrote: > > On Fri, 2019-12-06 at 08:38 -0600, Chris Adams wrote: > > > > > I also installed the Fedora 31 GeoIP packages and ran the geoipupdate, > > > and that DB has the correct info. > > > > IIRC

Re: Issue with Fedora GeoIP service

2019-12-06 Thread Tom Hughes
On 06/12/2019 16:41, Martin Kolman wrote: On Fri, 2019-12-06 at 08:38 -0600, Chris Adams wrote: I also installed the Fedora 31 GeoIP packages and ran the geoipupdate, and that DB has the correct info. > IIRC the infra team mentioned some issues with the new geoip database being incompatible

Re: Issue with Fedora GeoIP service

2019-12-06 Thread Martin Kolman
On Fri, 2019-12-06 at 08:38 -0600, Chris Adams wrote: > When installing Fedora 31 on a system, I noticed that anaconda defaulted > to US/Pacific for the time zone, rather than the correct US/Central. > I'm on a Google Fiber connection, and when I check Fedora's service at >

Issue with Fedora GeoIP service

2019-12-06 Thread Chris Adams
When installing Fedora 31 on a system, I noticed that anaconda defaulted to US/Pacific for the time zone, rather than the correct US/Central. I'm on a Google Fiber connection, and when I check Fedora's service at https://geoip.fedoraproject.org/city I get the info for their HQ in Mountain View.