From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Last call for Core Update 167 (was: Re: Core Updates 166 and 167)
Date: Sat, 02 Apr 2022 15:16:13 +0100
Message-ID: <07CA603C-23FA-494A-9944-7DA60F3B4F44@ipfire.org>
In-Reply-To: <74871d2b-d66a-315b-828c-ea1c813f7af8@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5224614197004430626=="
List-Id: <development.lists.ipfire.org>

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

Hello,

> On 2 Apr 2022, at 12:30, Peter M=C3=BCller <peter.mueller(a)ipfire.org> wro=
te:
>=20
> Hello Michael,
>=20
> thanks for your reply.
>=20
>> Hello Peter,
>>=20
>>> On 2 Apr 2022, at 08:42, Peter M=C3=BCller <peter.mueller(a)ipfire.org> w=
rote:
>>>=20
>>> Hello development folks,
>>>=20
>>> being responsible for upcoming Core Update 167, I would like to close this
>>> update roughly at the beginning of next week. This is because it contains
>>> several security-relevant updates (such as Apache, Bind [might need anoth=
er one?],
>>> zlib [again], OpenSSH, and so on) which I think should be available to our
>>> userbase as soon as possible.
>>=20
>> I don=E2=80=99t have anything left. Please await the conference call on Mo=
nday for a final decision.
>=20
> Yes, I was planning to do so. Just thought a preliminary notice would be in=
 order...

Good thinking :)

>>=20
>>> To have CVE-2022-1015 and CVE-2022-1016 covered, I will submit a patch for
>>> an updated kernel later this day, since we have enough space to ship one =
as
>>> the linux-firmware changes were reverted (see 8a4780de645a5b3ab42054eaf02=
2c57d6849ae9a).
>>=20
>> Please consult with Arne on this. There are lots of small details that nee=
d to be considered.
>>=20
>> And I am sure he has a branch with an updated kernel somewhere already.
>>=20
>> However, I really would like a new kernel in this release, even if that wi=
ll take us a few days longer.
>=20
> Oh, I overlooked your mail before submitting that Linux 5.15.32 patch. Sorr=
y.
>=20
> Arne working on a kernel was also my impression, but with a look at people/=
arne_f/kernel.git
> and people/arne_f/ipfire-2.x.git, I did not find anything I could pick up. =
So I thought I
> do a kernel update to once in a while, trying to reduce the bus factor on t=
his end. :-)

Please consult with him no matter what. Arne is not always pushing all change=
s to his repositories and you know how much he replies on the list.

>>=20
>>> Looking at Patchwork, it would be great if we could clarify the status of
>>> these patches and patch series, and whether they should go into Core Upda=
te
>>> 167 or not:
>>> - https://patchwork.ipfire.org/project/ipfire/list/?series=3D2684
>>=20
>> I will leave this for Stefan.
>>=20
>>> - https://patchwork.ipfire.org/project/ipfire/list/?series=3D2698
>>=20
>> I was awaiting some response from Anthony. I am not sure whether we can ta=
ke silence as approval but since he has approved the previous version of the =
patchset which has just been extended, I am sure this is okay to merge.
>=20
> I will wait until Monday for his reply then, and merge it if no negative fe=
edback arrives until then.

Silence is not an ack. We should not have this culture here.

If this is urgent, please get in touch with him. I am sure you have his phone=
 number :)

-Michael

> Thanks, and best regards,
> Peter M=C3=BCller
>=20
>>=20
>>> - https://patchwork.ipfire.org/project/ipfire/patch/66e4978d-6ba4-6c14-32=
9c-6f7ae99ed4b2(a)ipfire.org/
>>=20
>> This is something for Arne.
>>=20
>>> If there are any patches sitting around in your local/private repositories
>>> you want to have in Core Update 167, kindly post them. As always, drop me=
 a
>>> line in case of questions or comments.
>>>=20
>>> Thanks, and best regards,
>>> Peter M=C3=BCller
>>=20
>> -Michael


--===============5224614197004430626==--