public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [Fwd: [squid-announce] Squid 4.1 is available]
Date: Wed, 04 Jul 2018 17:04:35 +0200	[thread overview]
Message-ID: <bc76867f-9876-1650-4df3-84efed2ec8dc@ipfire.org> (raw)
In-Reply-To: <dab11da4f7181d039c49a3e22ef0cbd8df8b12f0.camel@ipfire.org>

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

On 04.07.2018 16:57, Michael Tremer wrote:
> On Wed, 2018-07-04 at 16:54 +0200, Matthias Fischer wrote:
>> Hi,
>> 
>> On 04.07.2018 11:12, Michael Tremer wrote:
>> > Squid 4.1 has been released.
>> 
>> Yep.
>> 
>> > @Matthias: As far as I remember, you have been working on updating squid
>> > before.
>> > Will you have a look at this?
>> 
>> I'm "looking at it" right now. ;-)
>> 
>> When I came home, Devel was ready.
>> 
>> First compiled version (32bit) is running here. No seen problems.
>> 
>> But today they released the first patch
>> (http://www.squid-cache.org/Versions/v4/changesets/squid-4-01fd74072310c3b018f
>> 4b6a5b5c6be4816f72166.patch).
>> Great...
>> 
>> I think we're not affected ("There is a Segfault when opening long URLs
>> if Bump is enabled and the on_unsupported_protocol option is set. Proxy
>> mode is transparent.") but to be complete, I'd like to include this one.
>> 
>> This requires a clean build (~5:30 hours). Patched version will be ready
>> tomorrow. Ok?
> 
> No hurry at all. I guess this already shows us that we should not migrate to
> squid 4, yet. There are still many bugs in it. But what we need to do is to
> review the proxy.cgi and see if the configuration file is valid and make changes
> if required.

Im testing the squid4-branch since ~4.0.22, 'squid -k parse' hasn't
shown an error since then, except this one - and I can't find the reason:

"WARNING: Ignoring error setting default trusted CA : An unimplemented
or disabled feature has been requested."

For me, its running stable - but I keep my eyes on this.

Best,
Matthias

  reply	other threads:[~2018-07-04 15:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c8f9202f-47b1-c34e-5480-8191d57f8a2b@treenet.co.nz>
2018-07-04  9:12 ` Michael Tremer
2018-07-04 14:54   ` Matthias Fischer
2018-07-04 14:57     ` Michael Tremer
2018-07-04 15:04       ` Matthias Fischer [this message]
2018-07-04 16:43         ` Michael Tremer
2018-07-04 18:52           ` Matthias Fischer
2018-07-05 14:55             ` Matthias Fischer
2018-07-05 16:57   ` 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=bc76867f-9876-1650-4df3-84efed2ec8dc@ipfire.org \
    --to=matthias.fischer@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