We have moved to a new Sailfish OS Forum. Please start new discussions there.
1

SDK Update broken on debian buster

asked 2019-08-01 20:13:05 +0200

JulienBlanc gravatar image

The current sdk (2.1) fails to update using debian buster. 2.2 fails as well.

The error is openssl related : it seems that the binaries were built against a version of openssl that is no longer present in debian buster:

qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: QSslSocket: cannot call unresolved function SSLeay
qt.network.ssl: Incompatible version of OpenSSL

Strangely enough, the same errors do exist at install but they do not prevent installation.

To work around it, it is possible to set up the repositories manually as temporary repositories, replacing the https protocol by http.

But still, it fails at the next launch. Is there another way to fix this in a more permanent way ?

edit retag flag offensive close delete

Comments

Add an older libssl1.0 package. if you don't want it in system libraries directory just copy libssl and libcrypto .so-files to the sdk directory, this is what has been needed with Fedora for a while too. See general qt documentation and comments.

ljo ( 2019-08-01 21:47:08 +0200 )edit

1 Answer

Sort by » oldest newest most voted
1

answered 2020-01-14 21:18:41 +0200

michfu gravatar image

As @ljo pointed out there needs to be openssl-1.0 installed. On Arch this can be done by

# pacman -S openssl-1.0

This resolves the problems with the updater (Maintenance Tool).

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
3 followers

Stats

Asked: 2019-08-01 20:13:05 +0200

Seen: 245 times

Last updated: Jan 14 '20