unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: itd <itd@net.in.tum.de>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Janneke Nieuwenhuizen" <janneke@gnu.org>,
	"Christopher Baines" <guix@cbaines.net>
Cc: 67507@debbugs.gnu.org
Subject: [bug#67507] [PATCH v2 0/2] Using the right locales on GNU/Hurd
Date: Mon, 04 Dec 2023 20:34:47 +0100	[thread overview]
Message-ID: <87h6kxvk14.fsf@localhost> (raw)
In-Reply-To: <87o7f8g7ed.fsf@gnu.org>

Dear all,

Ludovic Courtès <ludo@gnu.org> writes:

> Let’s do some more testing from here and see how it goes.

there was some discussion on IRC which, I think, is related to this
issue:
- https://logs.guix.gnu.org/guix/2023-12-03.log#104632
- https://logs.guix.gnu.org/guix/2023-12-04.log#165604

In short, people observe issues such as: "package glibc-locales@2.37
does not support x86_64-linux".  There is also #67586 describing this.

I am sharing it in case it is related and with the hope that it helps.

Best regards
itd




  parent reply	other threads:[~2023-12-04 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 11:33 [bug#67507] [PATCH] packages: Use glibc-utf8-locales/hurd in %standard-patch-inputs Christopher Baines
2023-11-29 15:44 ` [bug#67507] [PATCH v2 0/2] Using the right locales on GNU/Hurd Ludovic Courtès
2023-11-29 17:39   ` Janneke Nieuwenhuizen
2023-11-30 21:43     ` Ludovic Courtès
2023-12-01 19:49       ` Janneke Nieuwenhuizen
2023-12-02 11:39         ` bug#67507: " Ludovic Courtès
2023-12-02 14:38           ` [bug#67507] " Janneke Nieuwenhuizen
2023-12-04 19:34           ` itd [this message]
2023-12-01 18:42   ` Christopher Baines
2023-11-29 15:44 ` [bug#67507] [PATCH v2 1/2] gnu: Add ‘libc-locales-for-target’ and related Ludovic Courtès
2023-11-29 15:44 ` [bug#67507] [PATCH v2 2/2] gnu: Use ‘libc-utf8-locales-for-target’ 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=87h6kxvk14.fsf@localhost \
    --to=itd@net.in.tum.de \
    --cc=67507@debbugs.gnu.org \
    --cc=guix@cbaines.net \
    --cc=janneke@gnu.org \
    --cc=ludo@gnu.org \
    /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).