unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: 50978-done@debbugs.gnu.org
Subject: bug#50978: "guix home describe" backtraces if "guix home" hasn't been used
Date: Tue, 11 Jan 2022 11:37:57 +0100	[thread overview]
Message-ID: <87sftuwoai.fsf@gnu.org> (raw)
In-Reply-To: <8735pjnoel.fsf@yoctocell.xyz> (Xinglu Chen's message of "Sat, 02 Oct 2021 22:48:50 +0200")

Hi,

Xinglu Chen <public@yoctocell.xyz> skribis:

> On Sat, Oct 02 2021, Maxime Devos wrote:
>
>> Hi,
>>
>> When running "guix home describe" before "guix home import"
>> and before "guix build":
>>
>> $ guix home  describe
>> Backtrace:
>>            7 (primitive-load "/home/[...]/.config/guix/current/b…")
>> In guix/ui.scm:
>>    2185:7  6 (run-guix . _)
>>   2148:10  5 (run-guix-command _ . _)
>> In ice-9/boot-9.scm:
>>   1752:10  4 (with-exception-handler _ _ #:unwind? _ # _)
>> In guix/status.scm:
>>     820:3  3 (_)
>>     800:4  2 (call-with-status-report _ _)
>> In guix/scripts/home.scm:
>>     263:8  1 (_)
>> In ice-9/boot-9.scm:
>>   1685:16  0 (raise-exception _ #:continuable? _)
>>
>> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
>> no home environment generation, nothing to describe~%
>>
>> I don't think a backtrace is needed here.
>
> This seems to be the case for ‘guix system describe’ too
>
> $ guix system describe
> Backtrace:
>            7 (primitive-load "/home/yoctocell/.config/guix/current/bin/guix")
> In guix/ui.scm:
>    2185:7  6 (run-guix . _)
>   2148:10  5 (run-guix-command _ . _)
> In ice-9/boot-9.scm:
>   1752:10  4 (with-exception-handler _ _ #:unwind? _ #:unwind-for-type _)
> In guix/status.scm:
>     820:3  3 (_)
>     800:4  2 (call-with-status-report _ _)
> In guix/scripts/system.scm:
>    1310:8  1 (_)
> In ice-9/boot-9.scm:
>   1685:16  0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> no system generation, nothing to describe~%

Fixed in a9268216e4f38189d7948cf2ecb51ad2eac7e586, thanks!

Ludo'.




      reply	other threads:[~2022-01-11 10:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02 19:51 bug#50978: "guix home describe" backtraces if "guix home" hasn't been used Maxime Devos
2021-10-02 20:48 ` Xinglu Chen
2022-01-11 10:37   ` Ludovic Courtès [this message]

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=87sftuwoai.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=50978-done@debbugs.gnu.org \
    --cc=public@yoctocell.xyz \
    /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).