From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 51466@debbugs.gnu.org
Subject: bug#51466: guix shell --check reports missing PKG_CONFIG_PATH on Debian bookworm
Date: Fri, 29 Oct 2021 21:06:26 +0200 [thread overview]
Message-ID: <87o877y7kd.fsf@gnu.org> (raw)
In-Reply-To: <87r1c5c6gk.fsf@ponder> (Vagrant Cascadian's message of "Thu, 28 Oct 2021 12:08:59 -0700")
Hi!
Vagrant Cascadian <vagrant@debian.org> skribis:
> Most things seem to work fine, but noticed an oddity with guix shell:
>
> vagrant@vagranttdgxbookworm:~$ guix shell --pure --check --development guix guix git less
>
> guix shell: checking the environment variables visible from shell
> '/bin/bash'...
> guix shell: warning: variable 'PKG_CONFIG_PATH' is missing from shell
[...]
> vagrant@vagranttdgxbookworm:~$ guix shell --pure --development guix guix git less
>
> vagrant@vagranttdgxbookworm:~$ echo $PKG_CONFIG_PATH
> /gnu/store/9vk59alg27y0cp1za91nfdjiy718cn1f-profile/lib/pkgconfig
Notice that it doesn’t complain about any of the other environment
variables (there are 10 of them according to ‘guix shell -D guix
--search-paths|wc -l’).
If you look at ‘child-shell-environment’ in (guix scripts environment),
it runs this in the child shell:
env || /usr/bin/env || set; echo GUIX-CHECK-DONE; read x; exit
If the shell prints non-newline-terminated stuff before the output of
‘env’, the first line of ‘env’ would be swallowed by the parser below.
Could you run:
strace -o log -s 500 guix shell --check -D guix
to see exactly what ‘guix shell’ reads?
If there’s nothing obvious, you know the story: we can always add ‘pk’
calls in ‘child-shell-environment’. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-10-29 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 19:08 bug#51466: guix shell --check reports missing PKG_CONFIG_PATH on Debian bookworm Vagrant Cascadian
2021-10-29 19:06 ` Ludovic Courtès [this message]
2021-10-30 6:35 ` Vagrant Cascadian
2021-10-30 14:21 ` Ludovic Courtès
2022-03-27 17:01 ` bug#51466: [PATCH 0/1] environment: properly parse environment variables during --check Kevin Boulain
2022-03-27 17:01 ` bug#51466: [PATCH 1/1] " Kevin Boulain
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=87o877y7kd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=51466@debbugs.gnu.org \
--cc=vagrant@debian.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 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).