unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Ethan Blanton <elb@kb8ojh.net>, 56076@debbugs.gnu.org
Subject: bug#56076: guix shell -P behavior is surprising with persistent home
Date: Mon, 27 Jun 2022 09:55:14 +0200	[thread overview]
Message-ID: <878rpilevx.fsf@gnu.org> (raw)
In-Reply-To: <6c1c24fc001fe020895f9e85299c7049c1692a62.camel@telenet.be> (Maxime Devos's message of "Fri, 24 Jun 2022 23:18:16 +0200")

Hi,

Maxime Devos <maximedevos@telenet.be> skribis:

> Ludovic Courtès schreef op vr 24-06-2022 om 23:10 [+0200]:
>> That said, for this particular use case, you could do:
>> 
>>   guix shell syncthing nss-certs openssl -- syncthing
>> 
>> Adding ‘openssl’ to the mix is a trick to ensure that SSL_CERT_DIR is
>> defined, thanks to the search path mechanism:
>> 
>>   https://guix.gnu.org/manual/devel/en/html_node/Search-Paths.html
>> 
>> Thoughts?
>
> Having to add openssl looks like a bug,

It is, but it’s a reasonable solution for the problem at hand.

> so I'd go for something like <https://issues.guix.gnu.org/55297>
> instead, which resolves that.

That’s a bit of a hack to work around this venerable bug:

  https://issues.guix.gnu.org/22138

:-)

Ludo’.




  reply	other threads:[~2022-06-27  7:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18 21:41 bug#56076: guix shell -P behavior is surprising with persistent home Ethan Blanton via Bug reports for GNU Guix
2022-06-24 21:10 ` Ludovic Courtès
2022-06-24 21:18   ` Maxime Devos
2022-06-27  7:55     ` Ludovic Courtès [this message]
2022-06-27  8:37       ` Maxime Devos
2022-06-28  7:43         ` Ludovic Courtès
2022-06-28 10:50           ` Maxime Devos
2022-06-28 12:08           ` Maxime Devos

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=878rpilevx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=56076@debbugs.gnu.org \
    --cc=elb@kb8ojh.net \
    --cc=maximedevos@telenet.be \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).