unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Fredrik Salomonsson <plattfot@posteo.net>
To: Jelle Licht <jlicht@fsfe.org>,
	Roland Everaert <r.everaert@protonmail.com>,
	"help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: i18n guix module error when opening shell after guix home reconfigure
Date: Mon, 17 Jan 2022 06:55:17 +0000	[thread overview]
Message-ID: <87fspmx356.fsf@posteo.net> (raw)
In-Reply-To: <86lezr8bvp.fsf@fsfe.org>

Hi,

Jelle Licht <jlicht@fsfe.org> writes:

> Hello Roland,
>
> Sad prefix: I don't have a solution for you, nor am I a guix home
> expert, but I can confirm that I also run into the issue. 
>
> On my VM, I actually used an almost-default bash configuration, but run
> into the very same issue.
>
> Roland Everaert via <help-guix@gnu.org> writes:
>
>> Hello,
>>
>> First, happy new year and best wishes for this year.
>>
>> I have updated my guix home configuration to use my zsh config instead of a blank bash configuration.
>>
>> Unfortunatelly, when I logout and login again, I face the following errors:
>> -----------------------------------------------------------------------------------------
>> Backtrace:
>> 9 (primitive-load "/home/roland/.guix-home/on-first-login")
>> In ice-9/eval.scm:
>> 721:20 8 (primitive-eval (begin (use-modules (guix i18n)) (# …) …))
>> In ice-9/psyntax.scm:
>> 1230:36 7 (expand-top-sequence ((begin (use-modules (guix …)) …)) …)
>> 1090:25 6 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …)
>> 1222:19 5 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …)
>> 259:10 4 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) …)
>> In ice-9/boot-9.scm:
>> 3927:20 3 (process-use-modules _)
>> 222:17 2 (map1 (((guix i18n))))
>> 3928:31 1 (_ ((guix i18n)))
>> 3329:6 0 (resolve-interface (guix i18n) #:select _ #:hide _ # _ # …)
>>
>> ice-9/boot-9.scm:3329:6: In procedure resolve-interface:
>> no code for module (guix i18n)
>
> It seems that my $HOME/.guix-home/on-first-login assumes that guix's
> guile modules are available to the guile interpreter that is listed in
> the shebang;
>
>> Any idea what might cause such trouble?
>
> If you are not worried about temporarily running some older software,
> could you try and see if running:
>
> --8<---------------cut here---------------start------------->8---
> guix time-machine --commit=2719dfa631 -- home reconfigure your-home-config.scm
> --8<---------------cut here---------------end--------------->8---
>
> works for you? This will get guix to use an older copy of itself to
> build and 'install' your home environment.

I'm also encountering this issue running guix on a foreign distro. Not
sure which commit it stopped working, but it's broken in:

172bd0b5cde2609389fd16d18862b5b612c4b000

works when I use the guix time-machine command above.

-- 
s/Fred[re]+i[ck]+/Fredrik/g


  reply	other threads:[~2022-01-17  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 10:00 i18n guix module error when opening shell after guix home reconfigure Roland Everaert via
2022-01-07 21:38 ` Jelle Licht
2022-01-17  6:55   ` Fredrik Salomonsson [this message]
2022-01-20 23:21   ` Holger Peters

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=87fspmx356.fsf@posteo.net \
    --to=plattfot@posteo.net \
    --cc=help-guix@gnu.org \
    --cc=jlicht@fsfe.org \
    --cc=r.everaert@protonmail.com \
    /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.
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).