From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libloc: ship a more recent database by default
Date: Wed, 27 Jan 2021 22:11:11 +0000 [thread overview]
Message-ID: <9EFFD7F0-9B77-4694-89EA-270A95191A50@ipfire.org> (raw)
In-Reply-To: <004c2db5-8c17-d095-ab09-289830c87e6c@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
Hello,
Good idea, but you will need to change the MD5 checksum of that file too just like any other source file.
-Michael
> On 27 Jan 2021, at 21:24, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> The database we ship by default is meanwhile four weeks old, and since
> the merge window for Core Update 154 is still open, there is no need to
> ship data being more outdated than they have to be. :-)
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> lfs/libloc | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/libloc b/lfs/libloc
> index 279840535..170261e42 100644
> --- a/lfs/libloc
> +++ b/lfs/libloc
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2020 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2021 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -25,7 +25,7 @@
> include Config
>
> VER = 0.9.5
> -DB_DATE = 2020-12-23
> +DB_DATE = 2021-01-27
>
> THISAPP = libloc-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> --
> 2.26.2
next prev parent reply other threads:[~2021-01-27 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 21:24 Peter Müller
2021-01-27 22:11 ` Michael Tremer [this message]
2021-01-28 16:00 ` [PATCH v2] " Peter Müller
2021-01-29 11:35 ` Michael Tremer
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=9EFFD7F0-9B77-4694-89EA-270A95191A50@ipfire.org \
--to=michael.tremer@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