From: "Ludovic Courtès" <ludo@gnu.org>
To: "Noé Lopez" <noe@xn--no-cja.eu>
Cc: 73751@debbugs.gnu.org
Subject: bug#73751: [cuirass] channel-update-service fails trying to find key with accent in the name
Date: Thu, 28 Nov 2024 08:59:02 +0100 [thread overview]
Message-ID: <8734jb94c9.fsf@gnu.org> (raw)
In-Reply-To: <874j5iqthz.fsf@xn--no-cja.eu> ("Noé Lopez"'s message of "Fri, 11 Oct 2024 22:23:04 +0200")
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
Hi,
Noé Lopez <noe@noé.eu> skribis:
> Cuirass is failing to fetch the channel, because of something with the
> key file: « 2024-10-11 21:34:11 error: Git error while fetching channels
> from https://framagit.org/nll/bloup.git
> https://git.savannah.gnu.org/git/guix.git: the path 'No?? Lopez.key'
> does not exist in the given tree »
This error comes from libgit2, and I suspect the reason is that libgit2
interprets file names according to the current locale and ‘cuirass
register’ is not running in a UTF-8 locale.
Could you check with this patch:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 636 bytes --]
diff --git a/gnu/services/cuirass.scm b/gnu/services/cuirass.scm
index 187766bc99..f9f6355b98 100644
--- a/gnu/services/cuirass.scm
+++ b/gnu/services/cuirass.scm
@@ -184,7 +184,8 @@ (define (cuirass-shepherd-service config)
#$@extra-options)
#:environment-variables
- (list "GIT_SSL_CAINFO=/etc/ssl/certs/ca-certificates.crt"
+ (list "LC_ALL=C.UTF-8"
+ "GIT_SSL_CAINFO=/etc/ssl/certs/ca-certificates.crt"
(string-append "GIT_EXEC_PATH=" #$git
"/libexec/git-core"))
[-- Attachment #3: Type: text/plain, Size: 21 bytes --]
Thanks,
Ludo’.
prev parent reply other threads:[~2024-11-28 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 20:23 bug#73751: [cuirass] channel-update-service fails trying to find key with accent in the name Noé Lopez via Bug reports for GNU Guix
2024-11-28 7:59 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8734jb94c9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=73751@debbugs.gnu.org \
--cc=noe@xn--no-cja.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.