From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Release planning for Core Update 127/128 and beyond...
Date: Fri, 08 Mar 2019 10:12:07 +0000
Message-ID: <9E9F8B83-42F6-4C98-B5DA-E9EEB88CE7C4@ipfire.org>
In-Reply-To: <3738a8b2-fbd9-9904-0bea-ba5e0f9c4204@starkstromkonsument.de>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4672865231223565962=="
List-Id: <development.lists.ipfire.org>

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

Hey Alex,

Thanks for the reminder. I will reply on email with the patch.

-Michael

> On 8 Mar 2019, at 08:04, Alexander Koch <ipfire(a)starkstromkonsument.de> w=
rote:
>=20
> Hello Michael,
>=20
> I just read your call for last minute changes for Core Update 129 and want =
to ask whether my revised patch for the zabbix_agentd (https://patchwork.ipfi=
re.org/patch/2086/) is ready to be merged and can still make it into it?
>=20
> Regards, Alex
>=20
> -------- Original-Nachricht --------
> Von: michael.tremer(a)ipfire.org
> Gesendet: Thu, 7 Mar 2019 16:40:55 +0000
> An: matthias.fischer(a)ipfire.org
> CC: development(a)lists.ipfire.org
>=20
> Betreff: Re: Release planning for Core Update 127/128 and beyond...
>> Hi,
>>=20
>> Just a reminder for Core Update 129: I am planning to close this tomorrow.
>>=20
>> Please let me know if you have any last-minute changes.
>>=20
>> Otherwise we are ready to take patches for Core Update 130 from next week.
>>=20
>> Best,
>> -Michael
>>=20
>>> On 31 Jan 2019, at 18:29, Matthias Fischer <matthias.fischer(a)ipfire.org=
> wrote:
>>>=20
>>> Hi,
>>>=20
>>> On 31.01.2019 19:07, Michael Tremer wrote:
>>>> No worries, just wanted to coordinate and make sure that at least someon=
e is working on it :)
>>>=20
>>> Yep - that's the way I read it. ;-)
>>>=20
>>> Testing took some time because of the problems that arouse here with the
>>> missing sse2 version of '/usr/lib/sse2/libcrypto.so.1.1' (running on an
>>> i586 system).
>>>=20
>>> Problem:
>>> Despite all efforts I can't update this file without running into an
>>> openssl "Bus error". System is dead as a dodo after the update.
>>>=20
>>> 'openssl version' still gives me "OpenSSL *1.1.0j*  20 Nov 2018
>>> (Library: OpenSSL *1.1.0i*  14 Aug 2018)" with 'libcrypto.so.1.1' being
>>> the culprit for the 1.1.0*i* version, IMHO.
>>>=20
>>> Do you have any hints how to update this file without breaking the
>>> system? I tried recompiling Core 126 and just copying it but this
>>> doesn't work. All connections die almost immediately. Each time. Copying
>>> the old file back and rebooting makes the machine working again.
>>>=20
>>> Besides that, Apache 2.4.38 is running here - patch follows...
>>>=20
>>> Best,
>>> Matthias
>>>=20
>>>>> On 31 Jan 2019, at 17:54, Matthias Fischer <matthias.fischer(a)ipfire.o=
rg> wrote:
>>>>>=20
>>>>> Hi,
>>>>>=20
>>>>> On 31.01.2019 13:06, Michael Tremer wrote:
>>>>>> For TLSv1.3 to work on the web UI, we still need the latest version of=
 Apache and as far as I am aware of it Matthias is supposed to submit a patch=
 for that, am I right?
>>>>>=20
>>>>> Yes.
>>>>>=20
>>>>> I'm in the midst of testing - won't take long...
>>>>>=20
>>>>> Best,
>>>>> Matthias
>>>>=20
>>>>=20
>>>=20
>>=20


--===============4672865231223565962==--