Re: [PATCH] apache: Update to 2.4.38

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]

Did you overwrite the library file while it was in use maybe (by the OpenSSH server)?

> On 1 Feb 2019, at 18:07, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> 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