Yea, distro standards are generally a mess. Each distro has "their way" and if you deviate you're in for a world of hurt.
Fedora's "way" in this case is simply they expect you to rely on their system packages, bundling everything separate is anathame (in their eyes). Of course they are so slow at pushing updates to calibre that we want a separately bundled app anyways. I might start building calibre from the src rpm and just updating it myself.
Anyways if you're interested in a workaround:
1. Replacing the bundled libs with symlinks
On Fedora 21 the ABIs are compatible, for now. In /opt/calibre/lib symlinked as follows.
Code:
libcrypto.so.1.0.0 -> /usr/lib64/libcrypto.so
libssl.so.1.0.0 -> /usr/lib64/libssl.so.10
2. Setting env vars
Launching calibre manually with "env SSL_CERT_FILE=/etc/ssl/certs/ca-bundle.crt calibre" works, or you can edit the .desktop files (/usr/local/share/applications/calibre-*desktop) to set the variable yourself.
Option one is easiest for me, and I'll be doing that until I take the time to roll my own RPM of calibre.
Kovid, any chance calibre could detect the location? According to the article below, the best solution is
Code:
1. Check if /etc/pki/tls/certs/ca-bundle.crt exists, if so use with SSL_CERT_FILE [Fedora, Redhat, Arch etc]
2. Check if /etc/ssl/certs exists, if so use with SSL_CERT_DIR [Debian, Ubuntu, etc]
3. Fall back on default settings
Here is a fascinating read on the origin and evolution of the /etc/ssl/ slash /etc/pki mess:
A note about SSL/TLS trusted certificate stores, and platforms (OpenSSL and GnuTLS) -
https://www.happyassassin.net/2015/01/12/a-note-about-ssltls-trusted-certificate-stores-and-platforms/