From mboxrd@z Thu Jan 1 00:00:00 1970 From: Caleb Ristvedt Subject: =?UTF-8?B?UmU6IOKAmHN1ZG/igJkgbGVhdmVzIFBBVEggdW5jaGFuZ2Vk4oCmIHNvIHdoYXQ/?= Date: Fri, 18 Jan 2019 19:03:18 +0000 Message-ID: References: <87y37jwp1p.fsf@gnu.org> <87h8e7h6yd.fsf@elephly.net> <87r2dbv4w0.fsf@gnu.org> <87zhryv3l5.fsf@roquette.mug.biscuolo.net> <87fttqfmnm.fsf@elephly.net> <87d0ouuro2.fsf@roquette.mug.biscuolo.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000aa0b02057fc02a3a" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:50432) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gkZQX-0005pm-Lx for guix-devel@gnu.org; Fri, 18 Jan 2019 14:03:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gkZQV-000830-PH for guix-devel@gnu.org; Fri, 18 Jan 2019 14:03:37 -0500 Received: from mail-oi1-x22a.google.com ([2607:f8b0:4864:20::22a]:41938) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gkZQT-0007tc-T9 for guix-devel@gnu.org; Fri, 18 Jan 2019 14:03:34 -0500 Received: by mail-oi1-x22a.google.com with SMTP id j21so9761430oii.8 for ; Fri, 18 Jan 2019 11:03:30 -0800 (PST) In-Reply-To: <87d0ouuro2.fsf@roquette.mug.biscuolo.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Giovanni Biscuolo , guix-devel@gnu.org --000000000000aa0b02057fc02a3a Content-Type: text/plain; charset="UTF-8" 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 wrote: > Hi all, > > Caleb Ristvedt 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 > --000000000000aa0b02057fc02a3a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
To be clear, it's not so much a real problem as an eye= sore. 'sudo guix package ...' and 'sudo guix pull' will ope= rate on root's profile(s) as expected, but that also means 'sudo gu= ix system reconfigure' will look at root's profile when deciding wh= ether 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 bu= t only
> really keeps their user's guix up to date (I imagine a fairly comm= on
> situation), they're in for a weird situation when using sudo: a > bleeding-edge guix will complain about being outdated, since sudo (eve= n
> with -E) sets $USER, which is used to determine which file's times= tamp
> 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<= br> isolated so I can have different binaries (guix included) and use them
independently, am I wrong?

Thanks!
Giovanni

[...]

--
Giovanni Biscuolo

Xelera IT Infrastructures
--000000000000aa0b02057fc02a3a--