From: Vagrant Cascadian <vagrant@debian.org>
To: "(" <paren@disroot.org>, "Simen Endsjø" <simendsjo@gmail.com>
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 13:50:00 -0700 [thread overview]
Message-ID: <877d54cvt3.fsf@contorta> (raw)
In-Reply-To: <CKZHMQ8P7QKZ.28K1L5LONGTXR@guix-aspire>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On 2022-06-25, ( 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.
I'm not sure this is the best advice; other installations of guix should
not interfere with the pulled "guix" command as long as your PATH is set
up correctly. If PATH is not set up correctly, other things could be
wrong too...
There are cases where it may be fine to remove, but I don't think it is
good generalized troubleshooting advice, as it may hide other problems
with the installation.
By removing it a packaged or binary installation of guix from the
system, you also prevent other users on the same system from running
guix pull for themselves... or at least make it non-obvious or
otherwise more difficult than it needs to be.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-06-25 20:53 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ø
2022-06-25 20:57 ` (
2022-06-25 20:50 ` Vagrant Cascadian [this message]
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=877d54cvt3.fsf@contorta \
--to=vagrant@debian.org \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=paren@disroot.org \
--cc=simendsjo@gmail.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).