From: Dmitry Nikolaev <cameltheman@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix system disk-image broken?
Date: Wed, 22 Feb 2017 15:06:56 +0300 [thread overview]
Message-ID: <CAH3JXcG_gHebjz3+ZPPcSrMfB=rujE_U40mKC8NPD8BLgNTixw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
On 22 February 2017 at 13:36, Marius Bakke <mbakke@fastmail.com> wrote:
> Dmitry Nikolaev <cameltheman@gmail.com> writes:
>
> > On 22 February 2017 at 13:01, Marius Bakke <mbakke@fastmail.com> wrote:
> >
> >> Dmitry Nikolaev <cameltheman@gmail.com> writes:
> >> > $ git clone https://git.savannah.gnu.org/git/guix.git
> >> > ...
> >> > $ cd guix
> >> > $ guix system disk-image --image-size=1G gnu/system/install.scm
> >> > guix system: error: failed to load 'gnu/system/install.scm':
> >> > ice-9/boot-9.scm:2870:6: In procedure resolve-interface:
> >> > ice-9/boot-9.scm:2870:6: no code for module (gnu packages bootloaders)
> >>
> >> (gnu packages bootloaders) was recently moved. You will need to either
> >> update your guix package definitions with `guix pull`, or use
> >> `./pre-inst-env guix system ...`.
> >>
> >
> > I cloned guix repository moment before lanuching "guix system
> > disk-image...". Maybe install.scm should be updated to reflect new path
> to
> > bootloaders?
>
> The git repository is already up to date, but your installed Guix
> package definitions are not. Running `guix pull` should do the trick.
>
Running 'guix pull' does the trick. Thank you.
Dmitry Nikolaev
[-- Attachment #2: Type: text/html, Size: 2041 bytes --]
next reply other threads:[~2017-02-22 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 12:06 Dmitry Nikolaev [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-22 10:14 guix system disk-image broken? Dmitry Nikolaev
2017-02-22 10:36 ` Marius Bakke
2017-02-22 9:47 Dmitry Nikolaev
2017-02-22 10:01 ` Marius Bakke
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='CAH3JXcG_gHebjz3+ZPPcSrMfB=rujE_U40mKC8NPD8BLgNTixw@mail.gmail.com' \
--to=cameltheman@gmail.com \
--cc=help-guix@gnu.org \
--cc=mbakke@fastmail.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).