From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org, "olivier.dion@polymtl.ca" <olivier.dion@polymtl.ca>
Subject: Re: guix: workflow: command not found
Date: Tue, 26 Apr 2022 20:03:07 +0000 [thread overview]
Message-ID: <PWn3H2oAP-vGYjaJYF2S7g96svHBkX98ZxrPuTmiFnInfxox82AscmkBU1URjWabybw5tOD7RVgF1BnwcpaNKtc2iLeLarCRjClIvJidoDE=@protonmail.com> (raw)
In-Reply-To: <87mtg767ja.fsf@elephly.net>
[-- Attachment #1.1: Type: text/plain, Size: 614 bytes --]
> Hi Luis,
>
> > I'm following the tutorial in the website
> > (https://www.guixwl.org/tutorial), but I get this message when trying
> > to the workflow command:
>
> The tutorial fails to mention GUIX_EXTENSIONS_PATH, which needs to be
> set to share/guix/extensions, e.g.:
>
> export GUIX_EXTENSIONS_PATH=$HOME/.guix-profile/share/guix/extensions
>
> Originally I had hoped it would be set automatically due to a search
> path specification on the “guix” package, but this doesn’t work as
> intended, so it must be set manually.
Okay, now it works :)
Thanks, Ricardo, Olivier.
[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]
next prev parent reply other threads:[~2022-04-26 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 16:17 guix: workflow: command not found Luis Felipe
2022-04-26 17:59 ` Olivier Dion via
2022-04-26 18:07 ` Ricardo Wurmus
2022-04-26 20:03 ` Luis Felipe [this message]
2022-04-29 9:11 ` zimoun
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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='PWn3H2oAP-vGYjaJYF2S7g96svHBkX98ZxrPuTmiFnInfxox82AscmkBU1URjWabybw5tOD7RVgF1BnwcpaNKtc2iLeLarCRjClIvJidoDE=@protonmail.com' \
--to=luis.felipe.la@protonmail.com \
--cc=gwl-devel@gnu.org \
--cc=olivier.dion@polymtl.ca \
--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).