From: zimoun <zimon.toutoune@gmail.com>
To: me@tobias.gr, 45632@debbugs.gnu.org
Cc: kuba@kadziolka.net
Subject: [bug#45632] [PATCH] guix package: Warn if uses has 'guix' package in profile.
Date: Thu, 7 Jan 2021 18:56:36 +0100 [thread overview]
Message-ID: <CAJ3okZ0bQ4ruVpqv96Ah_rhTBbYOOEt9WyEtfdAW+dMcNvvhCg@mail.gmail.com> (raw)
In-Reply-To: <87eeiwllbn.fsf@nckx>
Hi Tobias,
On Thu, 7 Jan 2021 at 18:23, Tobias Geerinckx-Rice via Guix-patches
via <guix-patches@gnu.org> wrote:
> How about warning on pull instead? That should address the ‘halp,
> me Guix be Benjamin Buttonin'’ support calls that I assume
> inspired this.
Wait, does someone install packages in the profile
"~/.config/guix/current"? And does they install the package 'guix' in
this profile? Nan...
> Simon, would that reduce the noise in your case?
I am not sure to understand what the problem is; I should miss
something. My config is simply '~/.config/guix/current/bin' first in
my PATH and I am doing it manually with ~/.bash_profile. And I have a
lot of profiles that are sourced with a for-loop, some of them contain
the package 'guix'. And I have never hit an issue but I do not use
'upgrade'. Howver, I am mainly using Guix on Debian. Is the issue
Guix System specific?
Well, if the conflict is between the package 'guix' and the 'upgrade'
command, then the warning should be there, IMHO.
All the best,
simon
next prev parent reply other threads:[~2021-01-07 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 18:32 [bug#45632] [PATCH] guix package: Warn if uses has 'guix' package in profile Jakub Kądziołka
2021-01-07 16:39 ` zimoun
2021-01-07 17:11 ` Jakub Kądziołka
2021-01-07 17:46 ` zimoun
2021-01-07 20:31 ` Ricardo Wurmus
2021-01-07 17:15 ` Tobias Geerinckx-Rice via Guix-patches via
2021-01-07 17:56 ` zimoun [this message]
2021-01-07 17:58 ` Jakub Kądziołka
2021-01-07 19:25 ` 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=CAJ3okZ0bQ4ruVpqv96Ah_rhTBbYOOEt9WyEtfdAW+dMcNvvhCg@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=45632@debbugs.gnu.org \
--cc=kuba@kadziolka.net \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).