GNU bug report logs - #59485
'guix system list-generations' identifies wrong generation as current

Previous Next

Package: guix;

Reported by: Felix Lechner <felix.lechner <at> lease-up.com>

Date: Tue, 22 Nov 2022 17:08:02 UTC

Severity: normal

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

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#59485; Package guix. (Tue, 22 Nov 2022 17:08:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Felix Lechner <felix.lechner <at> lease-up.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 22 Nov 2022 17:08:02 GMT) Full text and rfc822 format available.

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

From: Felix Lechner <felix.lechner <at> lease-up.com>
To: bug-guix <at> gnu.org
Subject: 'guix system list-generations' identifies wrong generation as current
Date: Tue, 22 Nov 2022 09:06:19 -0800
Hi,

On my equipment the command 'guix system list-generations' identifies
the most recent system generation as "(current)" even though I booted
a different, past generation via Grub.

The information is most certainly wrong because my latest generation
does not boot successfully.

I don't know if it matters, but I used 'guix deploy' on my local system.

Kind regards,
Felix Lechner




Information forwarded to bug-guix <at> gnu.org:
bug#59485; Package guix. (Tue, 22 Nov 2022 17:23:02 GMT) Full text and rfc822 format available.

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

From: Julien Lepiller <julien <at> lepiller.eu>
To: Felix Lechner <felix.lechner <at> lease-up.com>, 59485 <at> debbugs.gnu.org
Subject: Re: bug#59485: 'guix system list-generations' identifies wrong generation as current
Date: Tue, 22 Nov 2022 18:22:06 +0100
[Message part 1 (text/plain, inline)]
Current system generation identifies the one that would boot by default. Basically, booted ≠ current. Maybe guix system could show that information.

Le 22 novembre 2022 18:06:19 GMT+01:00, Felix Lechner via Bug reports for GNU Guix <bug-guix <at> gnu.org> a écrit :
>Hi,
>
>On my equipment the command 'guix system list-generations' identifies
>the most recent system generation as "(current)" even though I booted
>a different, past generation via Grub.
>
>The information is most certainly wrong because my latest generation
>does not boot successfully.
>
>I don't know if it matters, but I used 'guix deploy' on my local system.
>
>Kind regards,
>Felix Lechner
>
>
>
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#59485; Package guix. (Tue, 22 Nov 2022 18:17:01 GMT) Full text and rfc822 format available.

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

From: Felix Lechner <felix.lechner <at> lease-up.com>
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: 59485 <at> debbugs.gnu.org
Subject: Re: bug#59485: 'guix system list-generations' identifies wrong
 generation as current
Date: Tue, 22 Nov 2022 10:15:55 -0800
Hi,

On Tue, Nov 22, 2022 at 9:22 AM Julien Lepiller <julien <at> lepiller.eu> wrote:
>
> Current system generation identifies the one that would boot by default. Basically, booted ≠ current.

Okay, thanks for the explanation!

I was confused since 'guix system delete-generations' also refused to
drop the defective generation. A kind user on IRC suggested the use of
'roll-back'. I see how that is consistent, but still think the
labeling is imprecise. Maybe we could instead offer the designations
"(default)" and maybe also "(booted)"?

Kind regards
Felix Lechner




This bug report was last modified 1 year and 153 days ago.

Previous Next


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