Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
Opened by ... (spider007) - Tuesday, 04 April 2017, 07:54 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Tuesday, 04 April 2017, 09:02 GMT
|
Detailskeepalived 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
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.