From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 45591-done@debbugs.gnu.org, guy fleury iteriteka <gfleury@disroot.org>
Subject: bug#45591: environment: gracefully handle unsupported system.
Date: Mon, 16 Jan 2023 13:10:24 -0500 [thread overview]
Message-ID: <87tu0q4agf.fsf_-_@gmail.com> (raw)
In-Reply-To: <87lfcwaon2.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 13 Jan 2021 15:37:53 +0100")
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> guy fleury iteriteka <gfleury@disroot.org> skribis:
>
>> diff --git a/guix/scripts/environment.scm b/guix/scripts/environment.scm
>> index e435bf0..40af012 100644
>> --- a/guix/scripts/environment.scm
>> +++ b/guix/scripts/environment.scm
>> @@ -719,6 +719,10 @@ message if any test fails."
>> (mappings (pick-all opts 'file-system-mapping))
>> (white-list (pick-all opts 'inherit-regexp)))
>>
>> + (when (not (member system '("armhf-linux" "aarch64-linux"
>> + "i686-linux" "x86_64-linux" "i586-gnu")))
>> + (leave (G_ "guix does not support ~A system~%") system))
>
> The system list should not be hardcoded (there’s already such a list in
> (guix packages)).
>
> Currently the error one gets is:
>
> $ guix environment -s does-not-exist --ad-hoc coreutils
> guix environment: error: could not find bootstrap binary 'tar' for system 'does-not-exist'
>
> I suppose that’s what you intended to improve, right?
Thanks to the recent work of Mathieu, we now get:
guix environment: error: 'does-not-exist' is not a supported system
hint: Try `--list-systems' to view available system types.
Closing.
--
Thanks,
Maxim
prev parent reply other threads:[~2023-01-16 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 10:53 [bug#45591] environment: gracefully handle unsupported system guy fleury iteriteka via Guix-patches via
2021-01-13 14:37 ` Ludovic Courtès
2023-01-16 18:10 ` Maxim Cournoyer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tu0q4agf.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=45591-done@debbugs.gnu.org \
--cc=gfleury@disroot.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.