From: "Philip McGrath" <philip@philipmcgrath.com>
To: "Chris Keschnat" <chris@catsu.it>, "Guix Help" <help-guix@gnu.org>
Subject: How to find what grafts have been applied? [Was: Racket REPL not working]
Date: Wed, 05 Jul 2023 03:13:47 -0400 [thread overview]
Message-ID: <a243b336-6bd9-46b3-92d6-c2021045e51f@app.fastmail.com> (raw)
In-Reply-To: <874jmjngb4.fsf@catsu.it>
Can anyone offer advice on how to debug a potential grafting problem? (It seems like it might be something similar to <https://issues.guix.gnu.org/47064>.) Unfortunately I haven't been able to reproduce the crashes on my system.
Philip
On Wed, Jul 5, 2023, at 12:16 AM, Chris Keschnat wrote:
> Sorry, I would not know how to find that out.
>
> "Philip McGrath" <philip@philipmcgrath.com> writes:
>
>> On Sun, Jul 2, 2023, at 12:12 PM, Chris Keschnat wrote:
>>> This works
>>>
>>> ck@brak ~ $ guix shell --no-grafts racket -- racket
>>> --version
>>> Welcome to Racket v8.8 [cs].
>>>>
>>
>> That's very useful!
>>
>> I'm not exactly sure how to do this, but can we determine which grafts
>> are otherwise being applied to `racket` in your environment? Hopefully
>> knowing what is being grafted will help to narrow down how grafting
>> might be going wrong.
next prev parent reply other threads:[~2023-07-05 7:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 21:56 Racket REPL not working Zelphir Kaltstahl
2023-05-15 0:20 ` Felix Lechner via
2023-05-15 21:55 ` Zelphir Kaltstahl
2023-05-15 16:18 ` Efraim Flashner
2023-05-15 21:58 ` Zelphir Kaltstahl
2023-05-17 11:11 ` Giovanni Biscuolo
2023-06-30 4:52 ` Chris Keschnat
2023-06-30 12:08 ` Philip McGrath
2023-07-01 11:41 ` Chris Keschnat
2023-07-02 2:31 ` Philip McGrath
2023-07-02 15:34 ` Philip McGrath
2023-07-02 16:12 ` Chris Keschnat
2023-07-02 19:57 ` Philip McGrath
2023-07-05 4:16 ` Chris Keschnat
2023-07-05 7:13 ` Philip McGrath [this message]
2023-08-23 14:48 ` Simon Tournier
2023-08-23 17:54 ` Chris Keschnat
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=a243b336-6bd9-46b3-92d6-c2021045e51f@app.fastmail.com \
--to=philip@philipmcgrath.com \
--cc=chris@catsu.it \
--cc=help-guix@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.