From: Joshua Branson <jbranso@dismail.de>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Getting the Guix Build Coordinator agent working on the Hurd
Date: Mon, 15 Feb 2021 10:12:39 -0500 [thread overview]
Message-ID: <87a6s5mkk8.fsf@dismail.de> (raw)
In-Reply-To: <87tuqekheb.fsf@cbaines.net> (Christopher Baines's message of "Sun, 14 Feb 2021 11:39:24 +0000")
Christopher Baines <mail@cbaines.net> writes:
> Hey,
>
> This has been on my todo list ever since the childhurd service came in
> to existence. I spent some more time looking at it yesterday, and did
> manage to get the agent working in a childhurd VM, at least somewhat.
Firstly awesome!
> There's also one problem probably within the Guix Build Coordinator
> itself, after doing a few builds, it will just stop. I've only seen this
> behaviour on the Hurd, but I'm unsure how to debug it, any suggestions?
> My only idea is add more logging.
You could always email bug-hurd@gnu.org or hang out in the #hurd
channel. Samuel is pretty quick to reply. He's about as responsive as
Ludo!
--
Joshua Branson (joshuaBPMan in #guix)
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
https://propernaming.org
"You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar
next prev parent reply other threads:[~2021-02-15 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 11:39 Getting the Guix Build Coordinator agent working on the Hurd Christopher Baines
2021-02-15 15:12 ` Joshua Branson [this message]
2021-02-16 8:58 ` Christopher Baines
2021-02-16 8:57 ` Christopher Baines
2021-02-18 9:25 ` Christopher Baines
2021-02-18 17:35 ` Ludovic Courtès
2021-02-23 20:58 ` Christopher Baines
2021-03-10 10:10 ` Ludovic Courtès
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=87a6s5mkk8.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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).