unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Konrad Hinsen" <konrad.hinsen@fastmail.net>,
	"Wiktor Żelazny" <wz@freeshell.de>,
	help-guix@gnu.org
Subject: Re: Certificates in pure and containerized environments
Date: Mon, 04 Oct 2021 12:04:54 +0200	[thread overview]
Message-ID: <86fsthds1l.fsf@gmail.com> (raw)
In-Reply-To: <m135ph5dwy.fsf@fastmail.net>

Hi Konrad,

On Mon, 04 Oct 2021 at 11:37, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:

> thanks for shedding some light on this strange behavior. After some more
> exploration, the fundamental issue seems to be that many packages use
> certificates but only a very small number declare a dependence on
> nss-certs. In fact, nss-certs has only three direct dependents (icedtea,
> ldns, and pypy) and 115 additional indirect dependents.  That includes
> r-reqon from Simon's example, which depends on icedtea via r-rjava and
> openjdk.

Yeah, I found it using “guix graph -t reverse-package nss-certs”. :-)


> Python actually lists openssl as a dependency, but that is apparently
> not sufficient to propagate the environment variables.

I think it is the issue: correctly propagate the environment variables.
But I do not know how.

Cheers,
simon


  reply	other threads:[~2021-10-04 10:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 10:08 Certificates in pure and containerized environments Konrad Hinsen
2021-10-03 16:45 ` Wiktor Żelazny
2021-10-04  7:25   ` zimoun
2021-10-04  9:37     ` Konrad Hinsen
2021-10-04 10:04       ` zimoun [this message]
2021-10-10 15:42     ` Wiktor Żelazny
2021-10-11  6:27       ` Konrad Hinsen
2021-10-05 17:42   ` Maxim Cournoyer
2021-10-08  8:47     ` Konrad Hinsen
2021-10-11 15:05       ` Maxim Cournoyer
2021-10-13 11:51         ` Konrad Hinsen

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=86fsthds1l.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    --cc=wz@freeshell.de \
    /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).