Janneke Nieuwenhuizen writes:
Hi!
> Janneke Nieuwenhuizen writes:
>
>> Ludovic Courtès writes:
> If there are no objections I'll go forward and install this patch by the
> end of the weekend.
So, I've been running guix pull from hurd-team on the Hurd all day.
Starting with the max-25 files spli
Hello,
When investigating a build failure, it can be useful to see the logs of
the machine that built the package (to determine whether it ran out of
memory, say), but currently the build logs or even the derivation page
on Cuirass doesn't track such information: it's not visible in the web
interf
On 9/17/23 9:42 AM, Matt Wette wrote:
Are there any workarounds for this. I've been digging into anything
to help.
I'm dead in the water trying to get ntpd and tftpd (dnsmasq) working.
They require this.
Or, is there a way to get dnsmasq working itself?
I see there is atftp, so I'll try th
Are there any workarounds for this. I've been digging into anything to
help.
I'm dead in the water trying to get ntpd and tftpd (dnsmasq) working.
They require this.
Or, is there a way to get dnsmasq working itself?
Matt
Hello!
I’m failing to run a childhurd inside a ‘guix system vm’ GNU/Linux VM as
of fc3a53525ab3dcaf7c22eec8d62294017f9760fe.
--8<---cut here---start->8---
Sep 17 17:03:25 localhost shepherd[1]: [qemu-system-i386] qemu-system-i386:
Slirp: Failed to send packet,
Hi Gio,
Sorry for my late reply. I have been travelling the last week and am
just catching up on all my email.
> When searching for "subject:" it would be useful to have a speficic
> message number and subject along with (or in place of) the bug title.
This is actually difficult to do because
