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 [thread overview]
Message-ID: <9E9F8B83-42F6-4C98-B5DA-E9EEB88CE7C4@ipfire.org> (raw)
In-Reply-To: <3738a8b2-fbd9-9904-0bea-ba5e0f9c4204@starkstromkonsument.de>
[-- Attachment #1: Type: text/plain, Size: 2745 bytes --]
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> wrote:
>
> Hello Michael,
>
> 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.ipfire.org/patch/2086/) is ready to be merged and can still make it into it?
>
> Regards, Alex
>
> -------- 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
>
> Betreff: Re: Release planning for Core Update 127/128 and beyond...
>> Hi,
>>
>> Just a reminder for Core Update 129: I am planning to close this tomorrow.
>>
>> Please let me know if you have any last-minute changes.
>>
>> Otherwise we are ready to take patches for Core Update 130 from next week.
>>
>> Best,
>> -Michael
>>
>>> On 31 Jan 2019, at 18:29, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>
>>> Hi,
>>>
>>> On 31.01.2019 19:07, Michael Tremer wrote:
>>>> No worries, just wanted to coordinate and make sure that at least someone is working on it :)
>>>
>>> Yep - that's the way I read it. ;-)
>>>
>>> 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).
>>>
>>> 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.
>>>
>>> '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.
>>>
>>> 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.
>>>
>>> Besides that, Apache 2.4.38 is running here - patch follows...
>>>
>>> Best,
>>> Matthias
>>>
>>>>> On 31 Jan 2019, at 17:54, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> 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?
>>>>>
>>>>> Yes.
>>>>>
>>>>> I'm in the midst of testing - won't take long...
>>>>>
>>>>> Best,
>>>>> Matthias
>>>>
>>>>
>>>
>>
prev parent reply other threads:[~2019-03-08 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b70898bd-d9d3-fcfc-e4a0-373d495c7e51@ipfire.org>
2019-03-07 16:40 ` Michael Tremer
2019-03-08 8:04 ` Alexander Koch
2019-03-08 10:12 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9E9F8B83-42F6-4C98-B5DA-E9EEB88CE7C4@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox