public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Rob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: Re: Location Database Update
Date: Sat, 11 Mar 2023 18:32:59 +0000	[thread overview]
Message-ID: <tuihgr$2ch8l$2@tuscan4.grantura.co.uk> (raw)
In-Reply-To: <ea7eccf8-b4c9-ea06-ac18-01000f983c57@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

On Sat, 11 Mar 2023 13:29:12 +0000, Peter Müller wrote:

> Hello *,
> 
> thanks for flagging this.
> 
> This is not an issue induced by Core Update 173, but on the server side,
> where the location database is generated. I'm at it and will keep you
> updated.
> 
> Thanks, and best regards,
> Peter Müller
>
 
Thanks Peter looks OK now.

location version
Sat, 11 Mar 2023 15:06:35 GMT

Rob



> 
>> On Fri, 10 Mar 2023 05:47:49 -0600, Charles Brown wrote:
>> 
>>> I thought perhaps there could be an issue since the location-database
>>> git repository stopped getting a daily update after Feb 24 See:
>>> https://git.ipfire.org/?p=location/location-database.git
>>>
>>> -cab
>>>
>>>
>> The lack of updates to the database is coincides with my last update
>> 
>> [root(a)ipfire-dev2 ~]# location version Sat, 25 Feb 2023 05:27:21 GMT
>> 
>> Hopefully someone is looking at reason why the database isn't updating.
>> 
>> The other problem of the high cpu usage also needs to be resolved.
>> 
>> 
>> Rob
>> 
>>


  reply	other threads:[~2023-03-11 18:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <95fe401f-d9b2-2a02-aafc-53a874822d5c.ref@yahoo.com>
2023-03-09 12:10 ` Charles Brown
2023-03-10 10:18   ` Rob Brewer
2023-03-10 11:47     ` Charles Brown
2023-03-11 10:05       ` Rob Brewer
2023-03-11 13:29         ` Peter Müller
2023-03-11 18:32           ` Rob Brewer [this message]
2023-03-12 11:43             ` Peter Müller
2023-03-12 12:24               ` Rob Brewer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='tuihgr$2ch8l$2@tuscan4.grantura.co.uk' \
    --to=ipfire-devel@grantura.co.uk \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox