public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] squid: Update to 4.4 (stable)
Date: Mon, 17 Dec 2018 17:19:08 +0000	[thread overview]
Message-ID: <9ef693781aaf68a722482c4588cdad39@ipfire.org> (raw)
In-Reply-To: <20181213173224.11553-1-matthias.fischer@ipfire.org>

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

Hey,

this patch has a binary blob in it. That is why it is so large.

I guess you want to resend that?!

-Michael

On 13/12/2018 05:32 PM, Matthias Fischer wrote:
> For details see:
> http://www.squid-cache.org/Versions/v4/changesets/
> 
> In July 2018, 'squid 4' was "released for production use", see:
> https://wiki.squid-cache.org/Squid-4
> 
> "The features have been set and large code changes are reserved for
> later versions."
> 
> I've tested almost all 4.x-versions and patch series before with good 
> results.
> Right now, 4.4 is running here with no seen problems together with
> 'squidclamav', 'squidguard' and 'privoxy'.
> 
> I too would declare this version stable.
> 
> Best,
> Matthias
> 
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
>  config/rootfiles/common/squid                 |  64 ++++++++-
>  lfs/squid                                     |  15 +-
>  squid-4.4-for-ipfire.tar.gz                   | Bin 0 -> 3213220 bytes
>  ...via_D_in_ERR_SECURE_CONNECT_FAIL_306.patch |  72 ----------
>  ...b_exchange_with_a_TLS_cache_peer_307.patch |  91 ++++++++++++
>  ...ry_leak_when_parsing_SNMP_packet_313.patch |  22 ---
>  ...all_format_formally_to_make_dist_325.patch |  22 +++
>  .../03_The_handshake_logformat_code_331.patch | 132 ++++++++++++++++++
>  ... squid-4.4-fix-max-file-descriptors.patch} |   4 +-
>  9 files changed, 314 insertions(+), 108 deletions(-)
>  create mode 100644 squid-4.4-for-ipfire.tar.gz
>  delete mode 100644
> src/patches/squid/01_Certificate_fields_injection_via_D_in_ERR_SECURE_CONNECT_FAIL_306.patch
>  create mode 100644
> src/patches/squid/01_Fix_netdb_exchange_with_a_TLS_cache_peer_307.patch
>  delete mode 100644
> src/patches/squid/02_Fix_memory_leak_when_parsing_SNMP_packet_313.patch
>  create mode 100644
> src/patches/squid/02_Maintenance_add_xz_tarball_format_formally_to_make_dist_325.patch
>  create mode 100644 
> src/patches/squid/03_The_handshake_logformat_code_331.patch
>  rename src/patches/squid/{squid-3.5.28-fix-max-file-descriptors.patch
> => squid-4.4-fix-max-file-descriptors.patch} (92%)

...

       reply	other threads:[~2018-12-17 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181213173224.11553-1-matthias.fischer@ipfire.org>
2018-12-17 17:19 ` Michael Tremer [this message]
2018-12-17 18:52   ` Matthias Fischer
2018-12-19 16:10     ` Michael Tremer
     [not found] <36903BA6-7CA8-46E0-9670-304583696FA1@ipfire.org>
2018-12-19 17:54 ` Matthias Fischer
2018-12-20 20:05   ` Matthias Fischer
2018-12-21 14:28     ` Michael Tremer
2018-12-13 17:40 Matthias Fischer
  -- strict thread matches above, loose matches on Subject: below --
2018-11-04  7:09 Matthias Fischer
2018-11-09 15:22 ` Michael Tremer
2018-11-09 18:56   ` Matthias Fischer

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=9ef693781aaf68a722482c4588cdad39@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