From: Maxime Devos <maximedevos@telenet.be>
To: Grigory Shepelev <shegeley@gmail.com>, 52559@debbugs.gnu.org
Subject: bug#52559: guix pull fails with `Unknown command: nix fish: nix show-derivation "~/.fr-sqOEpp/....-module-import-compiled.drv"
Date: Thu, 16 Dec 2021 21:13:44 +0000 [thread overview]
Message-ID: <1abf81878c1a434869407b1ba7bfb95cc969f624.camel@telenet.be> (raw)
In-Reply-To: <CAGJuR-4WYF8iWQJfC7ZiprF5eLVMHaj3SqfORx-1vEMS-9dB6A@mail.gmail.com>
Grigory Shepelev schreef op do 16-12-2021 om 23:49 [+0300]:
> > fish: Unknown command: nix
> > fish:
> > nix show-derivation "/home/shegeley/.cache/.fr-
> > sqOEpp/273vsd5gv1ch73ayih504s5wcxvysq-module-import-compiled.drv"
>
> IS in fact the contents of
> /var/log/guix/drvs/6r/273vsd5gv1ch73ayih504s5wcxvysq-module-import-
> compiled.drv.bz2.
This is very weird, because:
1. what's a derivation doing in $HOME?
2. This would mean that, while compiling some guile modules, fish is
invoked and fish is calling nix. But nix and fish are not involved at
all when compiling guile modules. (The only mention of 'fish' in the
source code is in shell completions.)
3. How did $HOME get leaked to the builder?
4. How did 'show-derivation' appear in the builder? There's no mention
of 'show-derivation' anywhere in guix' source code.
Greetings,
Maxime.
next prev parent reply other threads:[~2021-12-16 22:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 17:46 bug#52559: guix pull fails with `Unknown command: nix fish: nix show-derivation "~/.fr-sqOEpp/....-module-import-compiled.drv" Grigory Shepelev
2021-12-16 18:29 ` Maxime Devos
2021-12-16 19:15 ` Grigory Shepelev
2021-12-16 19:29 ` Grigory Shepelev
2021-12-16 19:32 ` Grigory Shepelev
2021-12-16 19:52 ` Grigory Shepelev
[not found] ` <CAGJuR-64F703LMjNeN=UfmzBcBPA1qVTY8bz-1umoxDaB+qcGQ@mail.gmail.com>
2021-12-16 20:26 ` Maxime Devos
2021-12-16 20:49 ` Grigory Shepelev
2021-12-16 20:54 ` Grigory Shepelev
2021-12-16 21:12 ` Grigory Shepelev
[not found] ` <d96e92826149aed480f5a9dc3a1f3bc891bc0a83.camel@telenet.be>
[not found] ` <CAGJuR-7E9Oztcig0_vzFGETXU6fXakh+wQzpxe0wcrw-n=8hhg@mail.gmail.com>
2021-12-16 21:24 ` bug#52559: Fwd: " Grigory Shepelev
2021-12-16 21:32 ` Maxime Devos
2021-12-16 21:50 ` Maxime Devos
2021-12-17 5:50 ` Grigory Shepelev
2021-12-17 6:21 ` Grigory Shepelev
2021-12-17 6:59 ` Maxime Devos
2021-12-17 9:07 ` Grigory Shepelev
2021-12-27 14:27 ` Grigory Shepelev
2021-12-27 15:53 ` Maxime Devos
2021-12-27 18:01 ` Grigory Shepelev
2021-12-27 20:08 ` Maxime Devos
2022-01-17 19:02 ` Grigory Shepelev
2022-01-17 19:31 ` Maxime Devos
2022-01-17 19:37 ` Grigory Shepelev
2021-12-17 6:53 ` Maxime Devos
2021-12-16 21:13 ` Maxime Devos [this message]
2021-12-16 18:30 ` Maxime Devos
2021-12-16 18:32 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1abf81878c1a434869407b1ba7bfb95cc969f624.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=52559@debbugs.gnu.org \
--cc=shegeley@gmail.com \
/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.