From: "Jens Mølgaard" <jens@zete.tk>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Nextcloud-client gets the wrong version of OpenSSL
Date: Fri, 28 Jun 2019 23:06:50 +1200 [thread overview]
Message-ID: <87r27ej7ed.fsf@zete.tk> (raw)
In-Reply-To: <87v9wrw714.fsf@elephly.net>
Hi Ricardo,
> It might be used by some other dependency. Have you tried to located
> the different openssl variants in the output of “guix graph”?
Thanks, I forgot about graph! I can see openssl@1.0.2p seems to be a
dependency of 7 packages in the graph of owncloud-client, and 10
packages for nextcloud-client.
They are: python, python2, python-minimal, python-pyopenssl,
python-cryptography, qtbase, ruby, mariadb, postgresql, w3m
Candidates I can see:
- qtbase: But I would expect the website to mention if qtbase needs
built with OpenSSL 1.1.x
- mariadb: Propagates openssl for some reason, but is not a direct
dependency.
Is there any way to explore this without changing the openssl version
for each of those packages in turn?
Thanks,
Jens M
prev parent reply other threads:[~2019-06-28 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 11:55 Nextcloud-client gets the wrong version of OpenSSL Jens Mølgaard
2019-06-27 11:08 ` Jens Mølgaard
2019-06-27 12:24 ` Ricardo Wurmus
2019-06-28 11:06 ` Jens Mølgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r27ej7ed.fsf@zete.tk \
--to=jens@zete.tk \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).