unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Nils Landt <nils@landt.email>
Cc: 67586@debbugs.gnu.org
Subject: bug#67586: guix package: error: package glibc-locales@2.37 does not support x86_64-linux
Date: Thu, 14 Dec 2023 19:11:36 +0100	[thread overview]
Message-ID: <87a5qcvelj.fsf@gnu.org> (raw)
In-Reply-To: <688533078.370112.1701936055582@office.mailbox.org> (Nils Landt's message of "Thu, 7 Dec 2023 09:00:55 +0100 (CET)")

Hi,

Nils Landt <nils@landt.email> skribis:

>> Ludovic Courtès <ludo@gnu.org> hat am 06.12.2023 23:58 CET geschrieben:
>> 
>>  
>> Hi,
>> 
>> Nils Landt <nils@landt.email> skribis:
>> 
>> > I use guix home for almost everything, but I have installed glibc-locales in my "regular" guix (just by running guix package install glibc-locales).
>> > Now, running guix package --upgrade fails with:
>> > guix package: error: package glibc-locales@2.37 does not support x86_64-linux
>> 
>> Fixed with 4a6cef9d66ff26e96d63f2f1f886b8212154ca00.
>> 
>> The problem was that glibc-locales@2.37 is marked as supported for
>> i586-gnu only (that’s GNU/Hurd).
>
> Thank you for the quick fix! 
> But isn't the the real bug that guix package (--install, --upgrade) consider an unsupported package as the version to install / upgrade to? Expected behaviour for me would be that it checks for the newest version that can actually be installed on the architecture.

Yes, you’re right, we should fix this.

Thanks,
Ludo’.




      reply	other threads:[~2023-12-14 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-02 17:03 bug#67586: guix package: error: package glibc-locales@2.37 does not support x86_64-linux Nils Landt
2023-12-03 22:11 ` TakeV via Bug reports for GNU Guix
2023-12-06 22:58 ` Ludovic Courtès
2023-12-07  8:00   ` Nils Landt
2023-12-14 18:11     ` 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

  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=87a5qcvelj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=67586@debbugs.gnu.org \
    --cc=nils@landt.email \
    /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).