From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] squid 4.5: latest patches (01-09)
Date: Sun, 24 Feb 2019 11:20:18 +0100
Message-ID: <6c40b039-2a11-99d4-7212-cf633d2a09eb@ipfire.org>
In-Reply-To: <C108A447-8077-4CE4-8220-8046A8B1344D@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2742060622619642752=="
List-Id: <development.lists.ipfire.org>

--===============2742060622619642752==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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.
>=20
> Also just ignore the BCP 177 message.
>=20
> -Michael
>=20
>> On 5 Feb 2019, at 17:37, Matthias Fischer <matthias.fischer(a)ipfire.org> =
wrote:
>>=20
>> Hi,
>>=20
>> On 05.02.2019 13:02, Michael Tremer wrote:
>>> Hi,
>>>=20
>>>> On 4 Feb 2019, at 17:54, Matthias Fischer <matthias.fischer(a)ipfire.org=
> wrote:
>>>>=20
>>>> 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=3Daufs,diskd,ufs \
>>>=20
>>> Wait, didn=E2=80=99t the documentation say, that they are going to remove=
 this switch very soon?
>>=20
>> Ups. Yes. This is 'deprecated' since a long time:
>>=20
>> https://lists.ipfire.org/pipermail/development/2016-April/002046.html
>>=20
>> "The --disable-ipv6 build option is now deprecated.
>> ...
>> Squid-3.5.7 and later will perform IPv6 availability tests on startup in
>> all builds.
>>=20
>> - Where IPv6 is unavailable Squid will continue exactly as it would
>> have had the build option not been used.
>>=20
>> These Squid can have the build option removed now."
>>=20
>> (The error I described in the post above was not IPv6 related.)
>>=20
>> 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'.
>>=20
>>>> ...
>>=20
>> Best,
>> Matthias
>=20
>=20


--===============2742060622619642752==--