From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens =?utf-8?Q?M=C3=B8lgaard?= Subject: Nextcloud-client gets the wrong version of OpenSSL Date: Wed, 26 Jun 2019 23:55:07 +1200 Message-ID: <877e98lfxg.fsf@zete.tk> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:45633) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hg6WI-0001ZX-Tr for help-guix@gnu.org; Wed, 26 Jun 2019 07:55:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hg6WH-00034a-3A for help-guix@gnu.org; Wed, 26 Jun 2019 07:55:22 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21281) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hg6WF-0002gL-Ko for help-guix@gnu.org; Wed, 26 Jun 2019 07:55:20 -0400 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Guix Help --=-=-= Content-Type: text/plain Hello Guix, I've been trying to package the nextcloud-client for a while and am stuck at a weird issue. Since it is a fork of owncloud-client, I have just adapted the package definition. With the addition of a patch from Parabola to strip out the need for qtwebengine, I've gotten it to build. However, it immediately segfaults on launch. Running it in gdb I see the following: > ssl3_cleanup_key_block () from >/gnu/store/m9ngbfyi8wrwiwyr7dkfnhn5fyfalq3r-openssl-1.0.2p/lib/libssl.so.1.0.0 And running 'nextcloud --version' gets me: > Using 'OpenSSL 1.0.2p 14 Aug 2018' But it is supposed to have been built with openssl-next, i.e. version 1.1.1c, and it requires 1.1.x at least. Adding openssl-next to native-inputs vs inputs does not make a difference. Turns out this is also the case for the existing owncloud-client package, which even though it depends on openssl-next also returns 'Using OpenSSL 1.0.2p'. So I'm stumped. Where is it getting this version of OpenSSL from? The build environment has the right version. It's not explicitly installed in any profile. Is it propagated from somewhere? Is there something obvious I'm missing? Or any idea what to try? Thanks, Jens M --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE/VzWzPUn4Rzyui0RiZ866GcCScAFAl0TXRsACgkQiZ866GcC ScBHgw/9GaUnYm12QNkasy5bNEaVsvD7K0qfyFQkhbZ7eEUrBVWm9T1r7/iSxpU5 JR/Zj8VlWsVm2JUJHuz+STp5CxZht7476xVo2Bw6kHU+GRRbVe6bt464mC406Zwi ZYzKQDz3h5hleYJWX/sfXQ/7Vct7VZ7OOK478rZ3nR1+g6168R9+saxSzWwDrR6H CcAPf4ovzVDZ67aM54Dumv7mPW29L9rmKp9rAYEIACo3VPeneCjazQNSP7RxtO9m SWcNbSQyZkXVfh64QH93ajrfWomKjoy8bSHo4rW8UJQi50OFM35hZ9ATf8o1tddd FvV3rK7Dn8OA/X0zo4U7WEB15npYU7tJ3thV6Bpbr4Bxa6uwv009BJFvKBs+Tva0 N0MUOyTM7kOtOgTvMSauM11b63iUR7z2GSwlmFQnSn+tl+8du0Mh6TpqERXG2ZMk TF3BxK38ASnsQbtssIupwjJfPO3YxxQW7LLVlFLsH9aMkP4+9lk/x6YmfnFlLA8X sZtsdG35xNaR3tc6FjI+PkTKIao7pVjbX9IYc3FunwcGgs5f6ryJCq1wgi7lxEn0 N8VHrbYO9kPJitv+bcsrvMQ0UpeE0vKOSW79or/buv6i4KoIEQv+FVb8Fy5QIglS S0qn2M/rlSEDtzJJc1sR3vz6Y9clxunAWUFE0FQxnQbMsbTx7Eg= =be1n -----END PGP SIGNATURE----- --=-=-=--