FS#53558 - [keepalived] Compiled against unreleased openssl

Attached to Project: Community Packages
Opened by ... (spider007) - Tuesday, 04 April 2017, 07:54 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Tuesday, 04 April 2017, 09:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

keepalived gets another completely broken release by the arch devs

/usr/bin/keepalived: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Tuesday, 04 April 2017, 09:02 GMT
Reason for closing:  Fixed
Comment by Jelle van der Waa (jelly) - Tuesday, 04 April 2017, 08:13 GMT
Which version of keepalived? Which repo's are enabled? It all works fine on my [testing]/[community-testing] machine.
Comment by Sébastien Luttringer (seblu) - Tuesday, 04 April 2017, 08:16 GMT
I guess it's because barth moved keepavlied from cty-testing to cty after the rebuild against iptables 1.6.1 without taking care of the pending rebuild of openssl 1.1 whih is still in testing.
Comment by Sébastien Luttringer (seblu) - Tuesday, 04 April 2017, 08:17 GMT
so, either we finally move openssl from testing or we have to repackage keepalived.
Comment by Jelle van der Waa (jelly) - Tuesday, 04 April 2017, 08:26 GMT
Shrug I wasn't up to date >_>. But yup seems that happened.
Comment by Bartłomiej Piotrowski (Barthalion) - Tuesday, 04 April 2017, 08:58 GMT
Sigh, I will rebuild it and push to respective repositories.
Comment by Bartłomiej Piotrowski (Barthalion) - Tuesday, 04 April 2017, 09:02 GMT
But while I can cry loud here, it makes me nuts that we don't rely on soname for dependencies. Pushed fixed packages.

Loading...