bug#65456: [PATCH 0/2] Split guix build into more steps for 32bit hosts.

2023-09-17 Thread Janneke Nieuwenhuizen
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 split without (gc), it failed 5
consecutive times building guix-packages-base.  Because the initial
patch worked pretty well and had the (gc) call (and yes, also used the
26-way split), I re-added (gc), and now the fourth attempt succeeded.
After `guix-packages-base' built, `guix-packages' then built right away.

I seem to remember guix-packages was the main problem when I wrote the
first version of this patch some four months ago, but that one split the
list of packages 26-way of course.  That suggests that the (combined)
compilation of certain files is especially problematic, or that it has
since become more problematic ().

On the other hand, we may be able to use more than 4GiB of memory on the
Hurd some time soon (and after we upgrade and compile using
--enable-pae)
.

Pushed to master as 658de25e990a56265e2398a3737e9cf1eb57af68

Greetings,
Janneke

-- 
Janneke Nieuwenhuizen   | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com





bug#66059: [cuirass] [feature] Mention which builder machine was used

2023-09-17 Thread Maxim Cournoyer
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
interface and not mentioned either in the build log.

We should add it to both places, ideally.

-- 
Thanks,
Maxim





bug#64653: stopping ntp and dnsmasq

2023-09-17 Thread Matt Wette

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 that.   Still no working ntpd.





bug#64653: stopping ntp and dnsmasq

2023-09-17 Thread Matt Wette
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






bug#66053: Childhurd fails to run inside ‘guix system vm’

2023-09-17 Thread Ludovic Courtès
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, ret: -1 
Sep 17 17:03:37 localhost shepherd[1]: [qemu-system-i386] qemu-system-i386: 
Slirp: Failed to send packet, ret: -1 
Sep 17 17:03:43 localhost shepherd[1]: [qemu-system-i386] qemu-system-i386: Bad 
ram pointer 0x7f739ac0001e 
Sep 17 17:03:43 localhost shepherd[1]: secret service: invalid handshake # 
Sep 17 17:03:43 localhost shepherd[1]: Service hurd-vm could not be started. 
Sep 17 17:03:43 localhost shepherd[1]: Service hurd-vm failed to start. 
--8<---cut here---end--->8---

When I run it by hand with KVM on my bare-metal GNU/Linux machine, it’s
all good: 

--8<---cut here---start->8---
$ 
"/gnu/store/1rg1fb9mj65rh82467vwlrkmi12p4v89-qemu-minimal-8.1.0/bin/qemu-system-i386"
 "-m" 2048 "--device" "rtl8139,netdev=net0" "--netdev" 
"user,id=net0,hostfwd=tcp:127.0.0.1:11004-:1004,hostfwd=tcp:127.0.0.1:10022-:,hostfwd=tcp:127.0.0.1:15900-:5900"
 "--snapshot" "--hda" "/gnu/store/iqacww23byvw9c5ssja9fkx6m4s057b0-disk-image" 
"--no-reboot" --enable-kvm
VNC server running on 127.0.0.1:5900
--8<---cut here---end--->8---

However, the same thing *without* KVM (as happens within ‘guix system
vm’) reproduces the “Bad ram pointer” issue:

--8<---cut here---start->8---
$ 
"/gnu/store/1rg1fb9mj65rh82467vwlrkmi12p4v89-qemu-minimal-8.1.0/bin/qemu-system-i386"
 "-m" 2048 "--device" "rtl8139,netdev=net0" "--netdev" 
"user,id=net0,hostfwd=tcp:127.0.0.1:11004-:1004,hostfwd=tcp:127.0.0.1:10022-:,hostfwd=tcp:127.0.0.1:15900-:5900"
 "--snapshot" "--hda" "/gnu/store/iqacww23byvw9c5ssja9fkx6m4s057b0-disk-image" 
"--no-reboot" 
VNC server running on 127.0.0.1:5900
qemu-system-i386: Bad ram pointer 0x7fa930e0001e
Aborted
--8<---cut here---end--->8---

Good news: I found a workaround!  Just use the x86_64 emulator:

--8<---cut here---start->8---
$ 
"/gnu/store/1rg1fb9mj65rh82467vwlrkmi12p4v89-qemu-minimal-8.1.0/bin/qemu-system-x86_64"
 "-m" 2048 "--device" "rtl8139,netdev=net0" "--netdev" 
"user,id=net0,hostfwd=tcp:127.0.0.1:11004-:1004,hostfwd=tcp:127.0.0.1:10022-:,hostfwd=tcp:127.0.0.1:15900-:5900"
 "--snapshot" "--hda" "/gnu/store/iqacww23byvw9c5ssja9fkx6m4s057b0-disk-image" 
"--no-reboot" 
VNC server running on 127.0.0.1:5900
--8<---cut here---end--->8---

Obviously, I have no clue why that works, but who cares, right?  :-)

Thoughts?

Ludo’.





bug#65809: mumi: Add msg number and subject in search results when searching for subject:

2023-09-17 Thread Arun Isaac


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 of the way we index issues as
Xapian "documents".

First, a quick Xapian primer. Xapian has a bunch of documents each
associated with a set of terms. When a search query comes in, Xapian
decomposes the query into a list of terms and retrieves documents that
match those terms.

In our case, we index entire issues as Xapian documents; we don't index
each individual email message as its own Xapian document. This means
that an issue is the smallest unit we can address. We cannot address
each individual email message. So, localizing a subject to a specific
email message is difficult.

Maybe what you are looking for is some context in the search results to
know why that particular search result was produced. This can be done by
displaying a snippet of text from the issue with the search terms
highlighted. For a working demo of what I mean, see for example,
https://issues.genenetwork.org/search?query=database=all . Notice
how the search term "database" is highlighted in the search
results. This is relatively easy to do with Xapian, and indeed I do plan
to implement this at some point.

WDYT? Would this meet your needs?

Regards,
Arun