Subject: bug#73181: closed (Re: bug#73181: guix-daemon fails when invoking‘guix authenticate’ on the Hurd)

From: [email-masked] (GNU bug Tracking System)
Date: Tue, 10 Dec 2024 17:01:03 +0000

Your bug report

#73181: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
73181: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=73181
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#73181: guix-daemon fails when invoking‘guix authenticate’ on the Hurd
From: Janneke Nieuwenhuizen <[email-masked]>
To: Ludovic Courtès <[email-masked]>
Cc: [email-masked]
Date: Tue, 10 Dec 2024 18:00:42 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

Ludovic Courtès writes:

> Janneke Nieuwenhuizen <[email-masked]> skribis:
>
>> Yeah, so I'm proposing the attached patch -- tested and works for me --
>> well, apart from having to set overload-threshold.  I asked on #hurd and
>> hopefully one of Damien's patch series
>>
>> <https://lists.gnu.org/archive/html/bug-hurd/2024-12/msg00100.html>
>> <https://lists.gnu.org/archive/html/bug-hurd/2024-12/msg00114.html>
>
> We could also set that field in ‘hurd-vm-guix-extension’, if that helps.

Nice; done.

>> From 832ef198f7e423e0fdff7fe7c5558ff13d1f20c1 Mon Sep 17 00:00:00 2001
>> Message-ID: <[email-masked]>
>> From: Janneke Nieuwenhuizen <[email-masked]>
>> Date: Tue, 10 Dec 2024 10:16:05 +0100
>> Subject: [PATCH] guile: Silence GC warnings on the Hurd, part II.
>>
>> This is a follow-up to commit
>>     b0416b8503e38746717a2d1167f9d1410634981e
>>     guile: Silence GC warnings on the Hurd.
>>
>> This should work around <https://issues.guix.gnu.org/73181>, resurrecting
>> offloading to the Hurd.
>>
>> * gnu/packages/aux-files/guile-launcher.c: (main)[__GNU__]: Move code to
>> silence warnings to...
>> (inner_main)[__GNU__]: ...here.
>>
>> Change-Id: I408201f7f4072c9a33837e6020ac63270b33702e
>
> LGTM!  (We’ll have to update the ‘guix’ package, right?)

Also done, pushed to master as 8966bd6c06df58316e01941577de1a7b1147ccbd.

With some luck, we have offloading again!  With more luck, we can
configure 64bit offloading!

Greetings,
Janneke

-- 
Janneke Nieuwenhuizen <[email-masked]>  | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com

Subject: guix-daemon fails when invoking ‘guix authenticate’ on the Hurd
From: Ludovic Courtès <[email-masked]>
To: [email-masked]
Date: Wed, 11 Sep 2024 17:40:13 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

As reported by yelninei on IRC, Guix on the Hurd is in half-broken state
following the recent ‘core-updates’ merge.

Specifically, sending store items over SSH (and thus breaks offloading
too):

--8<---------------cut here---------------start------------->8---
$ guix copy --to=localhost:10022 idutils
guix copy: sending 1 store item (1 MiB) to 'localhost'...
guix copy: error: unknown error while sending files over SSH
--8<---------------cut here---------------end--------------->8---

(Here localhost:10022 is a childhurd.)

Inside the childhurd, we get:

--8<---------------cut here---------------start------------->8---
root@childhurd ~# tail -1 /var/log/guix-daemon.log 
2024-09-09 21:09:03 unexpected build daemon error: stoi
--8<---------------cut here---------------end--------------->8---

Last time we got that error was in commit
21deb89e287b5821975544118bf137562a91d4e1: guix-daemon was running with
incorrect locale data, and thus ‘std::stoi’ would throw (‘std::stoi’ in
guix-daemon is used for the communication with the ‘guix authenticate’
process, see ‘readAuthenticateReply’).

When running guix-daemon by hand instead of via the Shepherd service,
with the same environment variables, everything works, unless we set one
of the LC_* variables.

Ludo’.