From: Adolf Belka <ahb.ipfire@gmail.com>
To: development@lists.ipfire.org
Subject: Re: [PATCH] sqlite: Update to 3.34.0
Date: Fri, 18 Dec 2020 12:14:28 +0100 [thread overview]
Message-ID: <48bff0b2-e20c-8f75-a6f0-b6eca0ce2de1@gmail.com> (raw)
In-Reply-To: <3A0F70FD-5B4C-4384-81C4-8BFE9729C08B@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1485 bytes --]
Hi Michael,
On 18/12/2020 10:44, Michael Tremer wrote:
> Him,
>
>> On 16 Dec 2020, at 19:28, Adolf Belka <ahb.ipfire(a)gmail.com> wrote:
>>
>> -Update sqlite from 3.26.0 to 3.34.0
>> See https://sqlite[.]org/chronology[.]html for history between
>
> Is there any reason you had to escape this URL like this?
>
My first sending of the patch got bounced due to the url showing up as a spam source. I remembered that Erik or Matthias had also had problems in the past like that so hence I escaped the url and it was then successfully sent.
Regards,
Adolf.
>> these releases.
>> -Have reviewed all release notes between these two releases and there
>> are no deprecations.
>> -No change to rootfile.
>
> Very good. Merged.
>
> -Michael
>
>> Signed-off-by: Adolf Belka <ahb.ipfire(a)gmail.com>
>> ---
>> lfs/sqlite | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/lfs/sqlite b/lfs/sqlite
>> index 8f02634cd..b2e1b6d3b 100644
>> --- a/lfs/sqlite
>> +++ b/lfs/sqlite
>> @@ -24,7 +24,7 @@
>>
>> include Config
>>
>> -VER = 3260000
>> +VER = 3340000
>>
>> THISAPP = sqlite-autoconf-$(VER)
>> DL_FILE = $(THISAPP).tar.gz
>> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>>
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>
>> -$(DL_FILE)_MD5 = ac2b3b8cd3a97600e36fb8e756e8dda1
>> +$(DL_FILE)_MD5 = 7f33c9db7b713957fcb9271fe9049fef
>>
>> install : $(TARGET)
>>
>> --
>> 2.29.2
>>
>
next prev parent reply other threads:[~2020-12-18 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 18:28 Adolf Belka
2020-12-18 9:44 ` Michael Tremer
2020-12-18 11:14 ` Adolf Belka [this message]
2020-12-18 11:47 ` 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=48bff0b2-e20c-8f75-a6f0-b6eca0ce2de1@gmail.com \
--to=ahb.ipfire@gmail.com \
--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