From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, Andy Tai <atai@atai.org>
Subject: Re: guix on a foreign distribution: how to upgrade to new release
Date: Fri, 28 Jun 2019 16:36:24 +0200 [thread overview]
Message-ID: <CA282F67-81C5-4862-84CC-EA7DF8D16BE1@lepiller.eu> (raw)
In-Reply-To: <CAJsg1E-N9mbom=NvqbkyxKByt7-A4H5x8tv8_fzTn7Qt-eUK4Q@mail.gmail.com>
Le 28 juin 2019 09:30:58 GMT+02:00, Andy Tai <atai@atai.org> a écrit :
>Hi, sorry if this is some question with obvious answer that I might
>have
>missed:
>
>I installed Guix on a Fedora system as a "foreign" distribution after
>the
>1.0.0 release. Things work (except trouble with SELinux, but that is
>off
>topic).
>
>Of course later Guix 1.0.1 was released. I did not do anything except
>to
>continue to do
>
>guix pull && guix package -u
>
>periodically.
>
>Now
>guix --version
>
>continues to show it is at version 1.0.0. I wonder if this is as
>expected
>or I missed something that I should do after a new guix release, to
>upgrade
>to the new version?
>
>Thanks
Hi!
You should check that you have ~/.config/guix/current/bin at the beginning of your $PATH. If this is already the case, run "hash guix" to update the binary cache of bash. Make sure you run guix from "current" and not /usr/local/bin or some other global location.
next prev parent reply other threads:[~2019-06-28 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 7:30 guix on a foreign distribution: how to upgrade to new release Andy Tai
2019-06-28 14:36 ` Julien Lepiller [this message]
2019-06-28 14:46 ` zimoun
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=CA282F67-81C5-4862-84CC-EA7DF8D16BE1@lepiller.eu \
--to=julien@lepiller.eu \
--cc=atai@atai.org \
--cc=help-guix@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.
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).