GNU bug report logs -
#36785
'sudo guix pull' failure in the profile migration code
Previous Next
Full log
View this message in rfc822 format
Hi Maxim,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -2387,8 +2387,8 @@ Success, you've now booted into Guix System! From then on, you can update the
> system whenever you want by running, say:
>
> @example
> -guix pull
> -sudo guix system reconfigure /etc/config.scm
> +sudo -i guix pull
> +sudo -i guix system reconfigure /etc/config.scm
> @end example
>
> @noindent
> @@ -2396,14 +2396,6 @@ This builds a new system generation with the latest packages and services
> (@pxref{Invoking guix system}). We recommend doing that regularly so that
> your system includes the latest security updates (@pxref{Security Updates}).
>
> -@c See <https://lists.gnu.org/archive/html/guix-devel/2019-01/msg00268.html>.
> -@quotation Note
> -@cindex sudo vs. @command{guix pull}
> -Note that @command{sudo guix} runs your user's @command{guix} command and
> -@emph{not} root's, because @command{sudo} leaves @code{PATH} unchanged. To
> -explicitly run root's @command{guix}, type @command{sudo -i guix @dots{}}.
> -@end quotation
I think these bits were correct.
That is, when running “sudo foo”, “foo” is looked up in the user’s
$PATH, not in root’s $PATH. That’s what led to this text in commit
796a4491fdaa4a0a3d669457b89356f9fbfc966e.
So this part is fine.
Perhaps we need another section for this? Or perhaps we can drop the
ball…
Thanks,
Ludo’.
This bug report was last modified 5 years and 235 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.