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: Mon, 25 Feb 2019 19:17:58 +0100
Message-ID: <698edfe9-bc63-b233-6bf2-e39c6d20a627@ipfire.org>
In-Reply-To: <C6BBD54A-56E6-4F0B-ADB6-6FB918E23264@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7833472861230287239=="
List-Id: <development.lists.ipfire.org>

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

Hi,

On 25.02.2019 11:34, Michael Tremer wrote:
> Hey,
>=20
> I think it is best to only follow the releases from upstream.

Besides, I'm closely watching
http://www.squid-cache.org/Versions/v4/changesets/ (daily) and I never
read of problems in IPFire forum related to the (bug) patches published
there.

I'll stick with the major releases. Less work, less noise here. ;-)

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

ACK.

FYI:

In the testing queue (running here):

squid 4.6
bind 9.11.5-P4
tar 1.32
mc 4.8.22

So if anyone is working on these - I got them already running. Will
probably push them on weekend.

Best,
Matthias

> Best,
> -Michael
>=20
>> On 24 Feb 2019, at 10:20, Matthias Fischer <matthias.fischer(a)ipfire.org>=
 wrote:
>>=20
>> Hi,
>>=20
>> Please note:
>>=20
>> This patch is superseded - I'm working/testing with 'squid 4.6'.
>>=20
>> So please don't merge this one. ;-)
>>=20
>> Best,
>> Matthias
>>=20
>> 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.o=
rg> 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 remo=
ve 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
>>=20
>=20
>=20


--===============7833472861230287239==--