Re: [PATCH] squid 4.5: latest patches (01-09)

[Michael Tremer <michael.tremer@ipfire.org>]

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

Hey,

I think it is best to only follow the releases from upstream.

I am sure that they will release a new version when there were important changes and that will save us from doing some extra work with the patches.

Best,
-Michael

> On 24 Feb 2019, at 10:20, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> Please note:
> 
> This patch is superseded - I'm working/testing with 'squid 4.6'.
> 
> So please don't merge this one. ;-)
> 
> Best,
> Matthias
> 
> On 05.02.2019 21:58, Michael Tremer wrote:
>> Okay, so we should not use that switch then.
>> 
>> Also just ignore the BCP 177 message.
>> 
>> -Michael
>> 
>>> On 5 Feb 2019, at 17:37, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>> 
>>> Hi,
>>> 
>>> On 05.02.2019 13:02, Michael Tremer wrote:
>>>> Hi,
>>>> 
>>>>> On 4 Feb 2019, at 17:54, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>>> 
>>>>> For details see:
>>>>> http://www.squid-cache.org/Versions/v4/changesets/
>>>>> ...
>>>>> 	cd $(DIR_APP) && autoreconf -vfi
>>>>> @@ -91,7 +100,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
>>>>> 		--disable-kqueue \
>>>>> 		--disable-esi \
>>>>> 		--disable-arch-native \
>>>>> -		--enable-ipv6 \
>>>>> +		--disable-ipv6 \
>>>>> 		--enable-poll \
>>>>> 		--enable-ident-lookups \
>>>>> 		--enable-storeio=aufs,diskd,ufs \
>>>> 
>>>> Wait, didn’t the documentation say, that they are going to remove this switch very soon?
>>> 
>>> Ups. Yes. This is 'deprecated' since a long time:
>>> 
>>> https://lists.ipfire.org/pipermail/development/2016-April/002046.html
>>> 
>>> "The --disable-ipv6 build option is now deprecated.
>>> ...
>>> Squid-3.5.7 and later will perform IPv6 availability tests on startup in
>>> all builds.
>>> 
>>> - Where IPv6 is unavailable Squid will continue exactly as it would
>>> have had the build option not been used.
>>> 
>>> These Squid can have the build option removed now."
>>> 
>>> (The error I described in the post above was not IPv6 related.)
>>> 
>>> For my part we could either leave this enabled (default) or remove this
>>> option. The warning message concerning the "BCP 177 violation" while
>>> starting 'squid' stays the same - no matter if IPv6 was disabled or
>>> enabled in 'configure'.
>>> 
>>>>> ...
>>> 
>>> Best,
>>> Matthias
>> 
>> 
>