From: sirgazil <sirgazil@zoho.com>
To: sirgazil <sirgazil@zoho.com>
Cc: Marius Bakke <mbakke@fastmail.com>,
guix-devel <guix-devel@gnu.org>, help-guix <help-guix@gnu.org>
Subject: Re: core-updates call for testing
Date: Fri, 24 Apr 2020 18:46:28 +0000 [thread overview]
Message-ID: <171ad833007.1179f27834719.8540473356595291204@zoho.com> (raw)
In-Reply-To: <171aa339c16.dea1952b12162.1876835440526368620@zoho.com>
---- On Fri, 24 Apr 2020 03:20:41 +0000 sirgazil <sirgazil@zoho.com> wrote ----
> ---- On Thu, 23 Apr 2020 23:24:23 +0000 Marius Bakke <mbakke@fastmail.com> wrote ----
> > Hello Guix!
> >
> > The "core-updates" branch is ready for testing! According to 'guix
> > weather', the substitute coverage is slightly better than on "master"
> > for x86_64. You can get it by running:
> >
> > guix pull --branch=core-updates
> >
> > Please try upgrading your profiles and systems and file bugs for
> > anything that does not work for you. GNOME users in particular are
> > encouraged to try the new GNOME 3.34 and report any regressions.
>
> I pulled from core-updates without problems, but "guix upgrade" failed.
>
> First, when running "guix upgrade", I got the following message, which I think is confusing because I use GNU, not Guix on a foreign distro:
>
> $ guix upgrade
> guile: warning: failed to install locale
> hint: Consider installing the `glibc-utf8-locales' or `glibc-locales' package and defining `GUIX_LOCPATH', along these lines:
>
> guix package -i glibc-utf8-locales
> export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"
>
> See the "Application Setup" section in the manual, for more info.
I filed a bug about this: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40826
next prev parent reply other threads:[~2020-04-24 18:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 23:24 core-updates call for testing Marius Bakke
2020-04-24 3:20 ` sirgazil
2020-04-24 12:58 ` sirgazil
2020-04-24 16:25 ` Marius Bakke
2020-04-24 16:54 ` Gábor Boskovits
2020-04-24 19:29 ` sirgazil
2020-04-24 18:08 ` sirgazil
2020-04-24 21:52 ` Marius Bakke
2020-04-24 22:42 ` sirgazil
2020-04-24 18:46 ` sirgazil [this message]
2020-04-24 14:40 ` Jack Hill
2020-04-24 20:06 ` Jack Hill
2020-04-25 3:02 ` Jack Hill
2020-04-25 13:24 ` sirgazil
2020-04-25 18:13 ` sirgazil
2020-04-29 11:31 ` Ricardo Wurmus
2020-04-25 18:36 ` sirgazil
2020-04-25 21:19 ` Jack Hill
2020-04-25 21:54 ` sirgazil
2020-04-27 22:09 ` Jack Hill
2020-04-29 6:17 ` Ricardo Wurmus
2020-04-25 18:06 ` Leo Famulari
2020-04-28 13:17 ` Marius Bakke
2020-04-28 12:46 ` Efraim Flashner
2020-04-28 13:12 ` Marius Bakke
2020-05-04 14:51 ` Timothy Sample
2020-05-04 15:32 ` Marius Bakke
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=171ad833007.1179f27834719.8540473356595291204@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=mbakke@fastmail.com \
/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).