From: "Simen Endsjø" <simendsjo@gmail.com>
To: "(" <paren@disroot.org>
Cc: Julien Lepiller <julien@lepiller.eu>, help-guix@gnu.org
Subject: Re: Additional channels pulled, but cannot install/update software
Date: Sat, 25 Jun 2022 22:49:49 +0200 [thread overview]
Message-ID: <CAHkVV6GPrj3VzeCJk1W2TA-qHRcoKgdMtF7YaX6jqsp_i9JHNg@mail.gmail.com> (raw)
In-Reply-To: <CKZHMQ8P7QKZ.28K1L5LONGTXR@guix-aspire>
> Try `~/.config/guix/current/bin/guix describe --format=channels`. If it
> prints the correct channels, that Guix binary is at fault.
Thank, that solved it! I guess my PATH has changed recently so that
/usr/local/bin has a higher priority than before.
But I should remove the one in /usr/local/bin..? The documentation states
to add
it, but that's only to allow other users to run the first command? Looks
like my
problem is the PATH priority rather than the location of guix
The documentation states (ref
https://guix.gnu.org/en/manual/devel/en/html_node/Binary-Installation.html#Binary-Installation
)
6. Make the guix command available to other users on the machine, for
instance with:
# mkdir -p /usr/local/bin
# cd /usr/local/bin
# ln -s /var/guix/profiles/per-user/root/current-guix/bin/guix
On Sat, Jun 25, 2022 at 10:12 PM ( <paren@disroot.org> wrote:
> On Sat Jun 25, 2022 at 9:05 PM BST, Simen Endsjø wrote:
> > No, I have the manual binary installation on a Manjaro host system.
>
> Once you pull for the first time, you should remove Guixen that you've
> installed through other means (like the debian package and binary
> installation). /usr/local/bin/guix is probably overriding the pulled
> Guix.
>
> Try `~/.config/guix/current/bin/guix describe --format=channels`. If it
> prints the correct channels, that Guix binary is at fault.
>
> -- (
>
next prev parent reply other threads:[~2022-06-25 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 18:49 Additional channels pulled, but cannot install/update software Simen Endsjø
2022-06-25 19:40 ` Julien Lepiller
2022-06-25 19:48 ` (
2022-06-25 19:49 ` Simen Endsjø
2022-06-25 20:00 ` (
2022-06-25 20:05 ` Simen Endsjø
2022-06-25 20:12 ` (
2022-06-25 20:49 ` Simen Endsjø [this message]
2022-06-25 20:57 ` (
2022-06-25 20:50 ` Vagrant Cascadian
2022-06-25 20:55 ` (
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=CAHkVV6GPrj3VzeCJk1W2TA-qHRcoKgdMtF7YaX6jqsp_i9JHNg@mail.gmail.com \
--to=simendsjo@gmail.com \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=paren@disroot.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).