unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Caleb Ristvedt <caleb.ristvedt@cune.org>
To: Giovanni Biscuolo <g@xelera.eu>, guix-devel@gnu.org
Subject: Re: ‘sudo’ leaves PATH unchanged… so what?
Date: Fri, 18 Jan 2019 19:03:18 +0000	[thread overview]
Message-ID: <CAELvotwLq8TZp+ieTtf-DAtZnGPcOSt6vQo4SzXtQe-a11aBXw@mail.gmail.com> (raw)
In-Reply-To: <87d0ouuro2.fsf@roquette.mug.biscuolo.net>

[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]

To be clear, it's not so much a real problem as an eyesore. 'sudo guix
package ...' and 'sudo guix pull' will operate on root's profile(s) as
expected, but that also means 'sudo guix system reconfigure' will look at
root's profile when deciding whether to say that it's out of date, even
though the guix actually used for reconfiguring may not be out of date. It
pretty much only ever comes up when reconfiguring, but for those like
myself who are worried by messages like that it can be confusing to try to
resolve.

On Fri, Jan 18, 2019 at 11:33 AM Giovanni Biscuolo <g@xelera.eu> wrote:

> Hi all,
>
> Caleb Ristvedt <caleb.ristvedt@cune.org> writes:
>
> > I'd just like to add that if a user has guix installed for root but only
> > really keeps their user's guix up to date (I imagine a fairly common
> > situation), they're in for a weird situation when using sudo: a
> > bleeding-edge guix will complain about being outdated, since sudo (even
> > with -E) sets $USER, which is used to determine which file's timestamp
> > should be used for deciding whether the installed guix is outdated.
> > Basically, your shiny new guix warns you that someone else's dirty old
> guix
> > is old.
>
> if this is true (root and user profiles using different versions of guix
> is a problem), should this be clearly stated in the manual?
>
> maybe I'm missing something, but I thought root and user profiles were
> isolated so I can have different binaries (guix included) and use them
> independently, am I wrong?
>
> Thanks!
> Giovanni
>
> [...]
>
> --
> Giovanni Biscuolo
>
> Xelera IT Infrastructures
>

[-- Attachment #2: Type: text/html, Size: 2164 bytes --]

  reply	other threads:[~2019-01-18 19:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 10:34 ‘sudo’ leaves PATH unchanged… so what? Ludovic Courtès
2019-01-17 11:03 ` Pierre Neidhardt
2019-01-17 11:14 ` Ricardo Wurmus
2019-01-17 12:35   ` Ludovic Courtès
2019-01-17 12:47     ` Pierre Neidhardt
2019-01-18  7:15     ` Giovanni Biscuolo
2019-01-18  7:30       ` Ricardo Wurmus
2019-01-18  8:06         ` Caleb Ristvedt
2019-01-18 11:33           ` Giovanni Biscuolo
2019-01-18 19:03             ` Caleb Ristvedt [this message]
2019-01-18 20:29               ` Danny Milosavljevic
2019-01-19  6:19                 ` swedebugia
2019-01-19 22:55                 ` Ludovic Courtès
2019-01-19 22:52           ` Ludovic Courtès
2019-01-20  2:12             ` Danny Milosavljevic
2019-01-18 10:39         ` Giovanni Biscuolo

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=CAELvotwLq8TZp+ieTtf-DAtZnGPcOSt6vQo4SzXtQe-a11aBXw@mail.gmail.com \
    --to=caleb.ristvedt@cune.org \
    --cc=g@xelera.eu \
    --cc=guix-devel@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.
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).