From: Vagrant Cascadian <vagrant@debian.org>
To: Philip McGrath <philip@philipmcgrath.com>, Guix Help <help-guix@gnu.org>
Subject: Re: Failed to autoload read-substitute-urls in (guix scripts discover)
Date: Fri, 23 Jun 2023 11:44:43 -0700 [thread overview]
Message-ID: <87h6qy2f38.fsf@wireframe> (raw)
In-Reply-To: <35458c9f-578a-4d22-8346-5077690df29a@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
On 2023-06-23, Philip McGrath wrote:
> On Fri, Jun 23, 2023, at 2:50 AM, Vagrant Cascadian wrote:
>> On 2023-06-23, Philip McGrath wrote:
>>> 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
>>
>> Well, that got me looking in the right place!
>>
>> guile-avahi is not packaged for Debian and somewhere along the way was
>> added as a dependency for guix, presumably for this (and possibly other)
>> feature(s).
>>
>> At least, that is my working theory :)
>>
>
> On the Guix side, it seems like either guile-avahi should be a mandatory dependency or guix-daemon should fail much more gracefully without it.
Sounds like a bug report for upstream too! :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2023-06-23 18:45 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
2023-06-23 6:50 ` Vagrant Cascadian
2023-06-23 6:56 ` Philip McGrath
2023-06-23 18:44 ` Vagrant Cascadian [this message]
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=87h6qy2f38.fsf@wireframe \
--to=vagrant@debian.org \
--cc=help-guix@gnu.org \
--cc=philip@philipmcgrath.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.
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).