From: "Philip McGrath" <philip@philipmcgrath.com>
To: "Vagrant Cascadian" <vagrant@debian.org>,
"Guix Help" <help-guix@gnu.org>
Subject: Re: Failed to autoload read-substitute-urls in (guix scripts discover)
Date: Fri, 23 Jun 2023 00:53:29 -0400 [thread overview]
Message-ID: <a0625e18-53f2-4612-b10c-aec14c23064f@app.fastmail.com> (raw)
In-Reply-To: <87zg4r30qy.fsf@wireframe>
On Thu, Jun 22, 2023, at 12:44 PM, Vagrant Cascadian wrote:
> On 2023-06-21, Philip McGrath wrote:
>> On Fri, Jun 9, 2023, at 2:43 PM, Vagrant Cascadian wrote:
>>> On 2023-06-07, Philip McGrath wrote:
>> I forgot earlier that I had used `sudo systemctl edit
>> guix-daemon.service` to add `--discover` to the command line for
>> `/usr/bin/guix-daemon` on the broken machine, but not on the working
>> machine. Removing that option got things working again!
>
>> I think there is actually a Debian bug, though, because it looks like
>> the Debian package really doesn't have code for the module `(guix
>> scripts discover)`, and running with `--discover` ought to be
>> supported. Vagrant, I haven't come up with a minimum reproducible
>> example yet, but I can open a report now if you like, or feel free to
>> do it yourself.
>
> Yes, please file a bug at bugs.debian.org ... if this bug has been fixed
> in newer commits on upstream guix, that would be helpful information! :)
>
Reported as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038916
next prev parent reply other threads:[~2023-06-23 4:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 0:27 Failed to autoload read-substitute-urls in (guix scripts discover) Philip McGrath
2023-06-09 18:43 ` Vagrant Cascadian
2023-06-22 1:23 ` Philip McGrath
2023-06-22 16:44 ` Vagrant Cascadian
2023-06-23 4:53 ` Philip McGrath [this message]
2023-06-23 6:50 ` Vagrant Cascadian
2023-06-23 6:56 ` Philip McGrath
2023-06-23 18:44 ` Vagrant Cascadian
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=a0625e18-53f2-4612-b10c-aec14c23064f@app.fastmail.com \
--to=philip@philipmcgrath.com \
--cc=help-guix@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 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.