From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] squid: Update to 6.6
Date: Mon, 11 Dec 2023 19:41:00 +0000 [thread overview]
Message-ID: <A29913E1-7F5C-4F78-9D55-44CD2C715893@ipfire.org> (raw)
In-Reply-To: <e90b0723-66ed-49cb-bcb2-7773925b165c@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
Thank you for the patch and review.
Is there any urgency here to include this in the update that is currently in testing? Considering that latest history of vulnerabilities in squid, I am happy to ship any fixes as soon as possible.
-Michael
> On 9 Dec 2023, at 22:05, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>
>
> On 09/12/2023 08:56, Matthias Fischer wrote:
>> For details see:
>> https://github.com/squid-cache/squid/commits/v6
>>
>> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
>> ---
>> lfs/squid | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/lfs/squid b/lfs/squid
>> index d92341794..c0f465c16 100644
>> --- a/lfs/squid
>> +++ b/lfs/squid
>> @@ -24,7 +24,7 @@
>> include Config
>> -VER = 6.5
>> +VER = 6.6
>> THISAPP = squid-$(VER)
>> DL_FILE = $(THISAPP).tar.xz
>> @@ -46,7 +46,7 @@ objects = $(DL_FILE)
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>> -$(DL_FILE)_BLAKE2 = 91ed91f9b0f56f440a7f15a63bbc3e19537b60bc8b31b5bf7e16884367d0da060c5490e1721dbd7c5fce7f4a4e958fb3554d6bdc5b55f568598f907722b651de
>> +$(DL_FILE)_BLAKE2 = 7c3c96f5cd5f819f6f020fb3e63ee8d9bb26b7fb4ff4405d7963a643c6766344e6492505bc1b33f3040ad800b3d7a3ad6a4b067b031ac4d178ddcac04c6e74dc
>> install : $(TARGET)
>>
next prev parent reply other threads:[~2023-12-11 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 7:56 Matthias Fischer
2023-12-09 22:05 ` Adolf Belka
2023-12-11 19:41 ` Michael Tremer [this message]
2023-12-19 18:20 ` Matthias Fischer
2023-12-20 10:59 ` 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=A29913E1-7F5C-4F78-9D55-44CD2C715893@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