From: Vagrant Cascadian <vagrant@debian.org>
To: Thom Harmon <trharmon@proton.me>, help-guix@gnu.org
Subject: Re: glibc-locales package problems (again)
Date: Fri, 27 Dec 2024 11:22:47 -0800 [thread overview]
Message-ID: <871pxtkk1k.fsf@wireframe> (raw)
In-Reply-To: <2b53ccefc851531698e7d2e90e3f2b25e7c30a62.camel@proton.me>
On 2024-12-27, Thom Harmon via wrote:
> I've been through the list archives and have not found a solution. I
> repeatedly get into a state where package updates are failing with the
> following messsage(s):
>
>> guix install: error: package glibc-locales@2.37 does not support
> x86_64-linux
>
> This is a binary install on Debian 12. I've seen some indication that
> there might just be a problem with the package definitions guix-side
> and so I tried to manually upgrade past 2.37 like so:
>
>> guix install glibc-locales@2.39
>
> but then I end up with something like this:
>
>> error: #{ %make-platform-procedure/abi-check}#: unbound variable
>> hint: Did you forget a `use-modules' form?
>>
>> The following packages will be downgraded:
>> glibc-locales 2.39 → 2.37
>> guix 1.4.0-16.aeb4943 → 1.4.0-15.e0885fc
>
> The only solution I have found is to manually uninstall and re-install
> guix every couple of weeks. This has been happening for more than a
> year and, well, let's just say its getting annoying. ;)
Based on the "guix" package downgrade, my hunch is you have "guix"
installed in your profile, so you will continually downgrade to an older
and older version of guix... as well as other packages in your profile
will get older and older as well...
If that is the case, remove guix from your profile, and make sure the
guix produced by "guix pull" is in your path,
e.g. $HOME/.config/guix/current/bin/guix.
live well,
vagrant
prev parent reply other threads:[~2024-12-27 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 17:28 glibc-locales package problems (again) Thom Harmon via
2024-12-27 19:22 ` Vagrant Cascadian [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=871pxtkk1k.fsf@wireframe \
--to=vagrant@debian.org \
--cc=help-guix@gnu.org \
--cc=trharmon@proton.me \
/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.
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).