From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] core177: Do not ship location database extracted in ipset format
Date: Thu, 13 Jul 2023 14:23:00 +0000 [thread overview]
Message-ID: <8c1e32f1-187f-5159-ba00-ffd0e6a3e536@ipfire.org> (raw)
In-Reply-To: <20230711093726.771964-1-michael.tremer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
Thank you for raising this, I'll pay attention to it for future Core Updates.
Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> Since the update is not built on the day when people install it, we will
> ship an outdated database. For updates, where the firewall is being
> reloaded or rebooted, we will have an old database in place until the
> next database update job runs.
>
> Secondly, the data is 33 MiB in size, which is useless data shipped as
> every system will already have a database that is very likely to be more
> recent.
>
> In this update, we are not shipping the location database again, but I
> wanted to add this change so it does not get lost next time.
>
> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
> ---
> config/rootfiles/core/177/exclude | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/config/rootfiles/core/177/exclude b/config/rootfiles/core/177/exclude
> index 378c2d563..8ee1c3c2f 100644
> --- a/config/rootfiles/core/177/exclude
> +++ b/config/rootfiles/core/177/exclude
> @@ -27,6 +27,7 @@ var/ipfire/urlfilter/blacklist
> var/ipfire/urlfilter/settings
> var/lib/alternatives
> var/lib/location/database.db
> +var/lib/location/ipset
> var/log/cache
> var/log/dhcpcd.log
> var/log/messages
prev parent reply other threads:[~2023-07-13 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 9:37 Michael Tremer
2023-07-13 14:23 ` Peter Müller [this message]
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=8c1e32f1-187f-5159-ba00-ffd0e6a3e536@ipfire.org \
--to=peter.mueller@ipfire.org \
--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