From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] apache: Update to 2.4.38
Date: Fri, 01 Feb 2019 19:07:14 +0100 [thread overview]
Message-ID: <fc3d15e1-938e-2251-ba9e-1e69a3419975@ipfire.org> (raw)
In-Reply-To: <6A16C532-07D6-460D-915E-B4F07C438AE9@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Hi,
On 01.02.2019 18:47, Michael Tremer wrote:
>> Right now, '2.4.38' is running here under Core 126. No seen problems
>> with GUI or anything else so far. Log is clean. My only glitch is the
>> d*** 'libcrypto.so.1.1'-lib from sse2. As I wrote, all of my update
>> efforts ended in breaking the system.
>>
>> One last thing I could do - would take some time - is to build under
>> current 'next' and make a test installation on my testmachine (offline).
> Hmm, I am slightly confused.
Understandable.
> So in Core 128, we are going to ship apache together with OpenSSL 1.1.1. So that should be fine because the runtime version is the same as the built version. All older SSL libraries should be removed then.
Yes - that's what I'm assuming too.
In commit
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=f8d407e5f7ff0812beaa6b45eae18b57475aa3d8
Arne added the missing '/usr/lib/sse2/libcrypto.so.1.1' for i586 which
seems to be the culprit of my problems. They should be solved with this
update.
> So I suppose if the nightly build works, then the update should work, too.
>
> Right?
Yes. What I still don't understand: why the manual updates always failed
with "openssl bus error". :-((
Best,
Matthias
next prev parent reply other threads:[~2019-02-01 18:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 17:06 Matthias Fischer
2019-02-01 17:13 ` Michael Tremer
2019-02-01 17:44 ` Matthias Fischer
2019-02-01 17:47 ` Michael Tremer
2019-02-01 18:07 ` Matthias Fischer [this message]
2019-02-04 22:20 ` Michael Tremer
2019-02-05 17:24 ` Matthias Fischer
2019-02-05 17:30 ` Michael Tremer
2019-02-05 17:45 ` Matthias Fischer
2019-02-05 20:57 ` Michael Tremer
2019-02-06 17:32 ` Matthias Fischer
2019-02-06 17:45 ` Michael Tremer
2019-02-06 17:53 ` Matthias Fischer
2019-02-09 20:04 ` Matthias Fischer
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=fc3d15e1-938e-2251-ba9e-1e69a3419975@ipfire.org \
--to=matthias.fischer@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