From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36469@debbugs.gnu.org
Subject: [bug#36469] [PATCH 0/2] 'guix pack' records environment variables
Date: Tue, 2 Jul 2019 18:46:02 +0200 [thread overview]
Message-ID: <CAJ3okZ3WT9ua6vQgVjLFnOnfb2LsvJYoLQTTrXYTyYmBzKnX4w@mail.gmail.com> (raw)
In-Reply-To: <20190702083731.10354-1-ludo@gnu.org>
Hi,
That's awesome !
I have not tried the patch yet because I am not able to `git pull`
(issue with gnu.org NS and the network of my University, whatever!)
and my current version seems too old.
> The change for Singularity is similar. I’ve tested it with an
> instance of Singularity 3.2.0. Unfortunately, we still have 2.x
> in Guix and that doesn’t quite support the environment file, so I’ve
> chosen to punt on this one.
In `docker.scm` you replace %bootstrap-guile by guile-2.2, that's you
are talking about?
And now both `docker.scm` and `singularity.scm` are consistent to
guile-2.2 and there were not. :-)
Thank you again for the patch
simon
next prev parent reply other threads:[~2019-07-02 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 8:37 [bug#36469] [PATCH 0/2] 'guix pack' records environment variables Ludovic Courtès
2019-07-02 8:56 ` [bug#36469] [PATCH 1/2] pack: 'docker' backend records the profile's search paths Ludovic Courtès
2019-07-02 8:56 ` [bug#36469] [PATCH 2/2] pack: 'squashfs' " Ludovic Courtès
2019-07-04 11:17 ` Ricardo Wurmus
2019-07-04 16:12 ` [bug#36469] Name of the Singularity/squashfs backend? Ludovic Courtès
2019-07-04 11:13 ` [bug#36469] [PATCH 1/2] pack: 'docker' backend records the profile's search paths Ricardo Wurmus
2019-07-04 15:06 ` Ludovic Courtès
2019-07-02 16:46 ` zimoun [this message]
2019-07-04 9:22 ` [bug#36469] [PATCH 0/2] 'guix pack' records environment variables Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ3WT9ua6vQgVjLFnOnfb2LsvJYoLQTTrXYTyYmBzKnX4w@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=36469@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.