GNU bug report logs - #36374
‘guix pull’ should not suggest running ‘guix pull’

Previous Next

To reply to this bug, email your comments to 36374 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: bug-Guix <at> gnu.org
Subject: ‘guix pull’ should not suggest running
 ‘guix pull’
Date: Tue, 25 Jun 2019 16:08:19 +0200

The article at
<https://distrowatch.com/weekly.php?issue=20190624#guixsd> has a
screenshot showing ‘guix pull’ suggesting to run ‘guix pull && guix
package -u’.  This is obviously wrong.

Ludo’.

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Julien Lepiller <julien <at> lepiller.eu>
To: bug-guix <at> gnu.org,Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#36374: ‘guix pull’ should not suggest running ‘guix pull’
Date: Wed, 26 Jun 2019 16:19:26 +0200

[Message part 1 (text/plain, inline)]

Le 25 juin 2019 16:08:19 GMT+02:00, "Ludovic Courtès" <ludo <at> gnu.org> a écrit :
>The article at
><https://distrowatch.com/weekly.php?issue=20190624#guixsd> has a
>screenshot showing ‘guix pull’ suggesting to run ‘guix pull && guix
>package -u’.  This is obviously wrong.
>
>Ludo’.

Here is a patch to address this issue on Guix System. It creates new files in /etc/skel: an initial profile (.config/guix/initial) tgat only contains a symlink to /run/current-system/profile/bin/guix and the current profile as a symlink to the initial profile.

At first boot, and for new users, guix well be found in the current profile, and stays there after guix pull, so we don't need to use hash guix anymore.

[0001-gnu-system-Symlink-guix-inside-an-initial-guix-pull-.patch (application/octet-stream, attachment)]

Message #11 received at 36374 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: 36374 <at> debbugs.gnu.org
Subject: Re: bug#36374: ‘guix pull’ should not suggest
 running ‘guix pull’
Date: Thu, 27 Jun 2019 11:55:36 +0200

Hello!

Julien Lepiller <julien <at> lepiller.eu> skribis:

> Here is a patch to address this issue on Guix System. It creates new
> files in /etc/skel: an initial profile (.config/guix/initial) tgat
> only contains a symlink to /run/current-system/profile/bin/guix and
> the current profile as a symlink to the initial profile.
>
> At first boot, and for new users, guix well be found in the current
> profile, and stays there after guix pull, so we don't need to use hash
> guix anymore.

I think this addresses the “hash guix” issue (this will no longer be
needed with this patch), but it only indirectly solves the “guix pull”
suggestion issue, right?

> From 89b5fa77af87e1a1537c10e929439a902806cc5c Mon Sep 17 00:00:00 2001
> From: Julien Lepiller <julien <at> lepiller.eu>
> Date: Wed, 26 Jun 2019 14:24:55 +0200
> Subject: [PATCH] gnu: system: Symlink guix inside an initial guix pull
>  profile.
>
> This patch adds an initial guix pull profile to the skeletons files used
> on Guix System.  This ensures that users don't have to type 'hash guix'
> after their first guix pull, and prevents 'guix pull' from suggesting to
> run 'guix pull' after it finished successfuly.

It prevents the suggestion, but only because the symlink appears to be
new.  If you change the mtime of the symlink, or if you run:

  GUIX_DISTRO_AGE_WARNING=1s guix pull

I think you still get the “guix pull” recommendation.

> * gnu/system/shadow.scm (skeleton-directory): Symlink guix inside an
> initial guix pull profile.

Perhaps we should add it to ‘default-skeletons’ instead of
special-casing it here?  WDYT?

Thanks for working on it!

Ludo’.

Message #16 received at 36374 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: 36374 <at> debbugs.gnu.org
Subject: Re: bug#36374: ‘guix pull’ should not suggest
 running ‘guix pull’
Date: Tue, 24 Mar 2020 18:18:17 +0100

Ping!  :-)

  https://issues.guix.gnu.org/issue/36374

Now’s a good time to fix this one!

Ludo’.

Ludovic Courtès <ludo <at> gnu.org> skribis:

> Hello!
>
> Julien Lepiller <julien <at> lepiller.eu> skribis:
>
>> Here is a patch to address this issue on Guix System. It creates new
>> files in /etc/skel: an initial profile (.config/guix/initial) tgat
>> only contains a symlink to /run/current-system/profile/bin/guix and
>> the current profile as a symlink to the initial profile.
>>
>> At first boot, and for new users, guix well be found in the current
>> profile, and stays there after guix pull, so we don't need to use hash
>> guix anymore.
>
> I think this addresses the “hash guix” issue (this will no longer be
> needed with this patch), but it only indirectly solves the “guix pull”
> suggestion issue, right?
>
>> From 89b5fa77af87e1a1537c10e929439a902806cc5c Mon Sep 17 00:00:00 2001
>> From: Julien Lepiller <julien <at> lepiller.eu>
>> Date: Wed, 26 Jun 2019 14:24:55 +0200
>> Subject: [PATCH] gnu: system: Symlink guix inside an initial guix pull
>>  profile.
>>
>> This patch adds an initial guix pull profile to the skeletons files used
>> on Guix System.  This ensures that users don't have to type 'hash guix'
>> after their first guix pull, and prevents 'guix pull' from suggesting to
>> run 'guix pull' after it finished successfuly.
>
> It prevents the suggestion, but only because the symlink appears to be
> new.  If you change the mtime of the symlink, or if you run:
>
>   GUIX_DISTRO_AGE_WARNING=1s guix pull
>
> I think you still get the “guix pull” recommendation.
>
>> * gnu/system/shadow.scm (skeleton-directory): Symlink guix inside an
>> initial guix pull profile.
>
> Perhaps we should add it to ‘default-skeletons’ instead of
> special-casing it here?  WDYT?
>
> Thanks for working on it!
>
> Ludo’.

Message #19 received at 36374 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: Julien Lepiller <julien <at> lepiller.eu>, 36374 <at> debbugs.gnu.org
Subject: Re: bug#36374: ‘guix pull’ should not suggest
 running ‘guix pull’
Date: Wed, 23 Mar 2022 12:23:19 +0100

Hi,

This old report and associated patch is uncommented since a while?

    <http://issues.guix.gnu.org/issue/36374>

What do we do?  Include the proposed patch?  Other ideas?


Cheers,
simon

Message #22 received at 36374 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: zimoun <zimon.toutoune <at> gmail.com>
Cc: Julien Lepiller <julien <at> lepiller.eu>, 36374 <at> debbugs.gnu.org
Subject: Re: bug#36374: ‘guix pull’ should not suggest
 running ‘guix pull’
Date: Thu, 24 Mar 2022 09:37:05 +0100

Hi,

zimoun <zimon.toutoune <at> gmail.com> skribis:

> This old report and associated patch is uncommented since a while?
>
>     <http://issues.guix.gnu.org/issue/36374>
>
> What do we do?  Include the proposed patch?  Other ideas?

I think the initial patch doesn’t work reliably, as I wrote back then,
but something like that might work.  Julien?

Ludo’.

Message #25 received at 36374 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: Julien Lepiller <julien <at> lepiller.eu>, 36374 <at> debbugs.gnu.org
Subject: Re: bug#36374: ‘guix pull’ should not suggest
 running ‘guix pull’
Date: Thu, 23 Jun 2022 11:30:28 +0200

Hi Julien,

On Thu, 24 Mar 2022 at 09:37, Ludovic Courtès <ludo <at> gnu.org> wrote:

>>     <http://issues.guix.gnu.org/issue/36374>
>>
>> What do we do?  Include the proposed patch?  Other ideas?
>
> I think the initial patch doesn’t work reliably, as I wrote back then,
> but something like that might work.  Julien?

Friendly ping. :-)

Cheers,
simon

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.