From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] squid: Update to 4.5
Date: Wed, 02 Jan 2019 19:11:48 +0000 [thread overview]
Message-ID: <FB428539-35D0-4D4D-B53C-386BF0BB53C5@ipfire.org> (raw)
In-Reply-To: <22bf4c01-6f16-eecf-c0db-2fb5550562fc@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
> On 2 Jan 2019, at 19:10, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> On 02.01.2019 20:01, Michael Tremer wrote:
>>
>>
>>> On 2 Jan 2019, at 18:55, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>
>>> Hi,
>>>
>>> On 02.01.2019 18:27, Michael Tremer wrote:
>>>> Hello,
>>>>
>>>> This is quite good that we finally have a stable release of this (am I right that 4.4 wasn’t considered to be stable?).
>>>
>>> 'squid 4.4' was "stable", too:
>>>
>>> In July 2018, 'squid 4' was "released for production use", see:
>>> https://wiki.squid-cache.org/Squid-4
>>
>> Why do they compare everything to squid 3.5 then?
>
> No idea. Perhaps to make upgrading easier for people running
> (huge/complex) 3.x-installations? They even still list "missing
> squid.conf options available in Squid-2.7"! ;-)
>
> But as I read it, 3.x will not be continued, see:
>
> https://wiki.squid-cache.org/RoadMap/Squid3
>
> "We are no longer releasing new Squid series with 3.x numbers.”
No, it is indeed time to migrate!
>
> Best,
> Matthias
>
>>>
>>>> This however removes support for the SMB_LM helper which we still use and I will have to remove that from the CGI. We will have to announce that properly, but I do not think that it is a huge problem because this is Windows 2000 era. Hopefully nobody is using that any more.
>>>
>>> I'm not an expert for this - never used it -, but I found this on the
>>> above website:
>>>
>>> "Major UI changes:
>>> ...
>>> basic_msnt_multi_domain_auth: Superceeded by basic_smb_lm_auth
>>> …"
>>
>> The latter is not being compiled any more. You removed it from the rootfiles.
>>
>>>
>>> Best,
>>> Matthias
>>>
>>>> Apart from that, I hope that we can now stay on the releases in this series until there is a new one.>
>>>> Best,
>>>> -Michael
>>>>
>>>>> On 1 Jan 2019, at 17:39, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>>>
>>>>> For details see:
>>>>> http://www.squid-cache.org/Versions/v4/changesets/
>>>>> ...
>>>
>>
>>
>
next prev parent reply other threads:[~2019-01-02 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 17:39 Matthias Fischer
2019-01-02 17:27 ` Michael Tremer
2019-01-02 18:55 ` Matthias Fischer
2019-01-02 19:01 ` Michael Tremer
2019-01-02 19:10 ` Matthias Fischer
2019-01-02 19:11 ` Michael Tremer [this message]
2019-01-04 18:02 ` Matthias Fischer
2019-01-04 18:07 ` 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=FB428539-35D0-4D4D-B53C-386BF0BB53C5@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