From: Lo Peter <peterloleungyau@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Problem installing Guix (through binary installation script) on AWS EC2
Date: Mon, 19 Jul 2021 21:22:10 +0800 [thread overview]
Message-ID: <CAEM+zmjTdrFUo6dCU36-J0F77Ry7SBUfTjVZgyX+=Z=GUmW-hA@mail.gmail.com> (raw)
In-Reply-To: <87fswa5yqq.fsf@elephly.net>
Sorry, I did not check the log files. I think it was probably the
installation (through the script) had not been completed, causing
subsequent problems.
On Mon, Jul 19, 2021 at 7:28 PM Ricardo Wurmus <rekado@elephly.net> wrote:
>
>
> Lo Peter <peterloleungyau@gmail.com> writes:
>
> > substitute: guix substitute: warning: ACL for archive imports
> > seems to
> > be uninitialized, substitutes may be unavailable
>
> Is this on purpose?
>
> > building
> > /gnu/store/hifim0h1p7nw81mg6rl00g9q0m6vr0qw-bzip2-mesboot-1.0.8.drv...
> >
> > \ 'build' phasebuilder for
> > `/gnu/store/hifim0h1p7nw81mg6rl00g9q0m6vr0qw-bzip2-mesboot-1.0.8.drv'
> > failed with exit code 1
> >
> > build of
> > /gnu/store/hifim0h1p7nw81mg6rl00g9q0m6vr0qw-bzip2-mesboot-1.0.8.drv
> > failed
> >
> > View build log at
> > '/var/log/guix/drvs/hi/fim0h1p7nw81mg6rl00g9q0m6vr0qw-bzip2-mesboot-1.0.8.drv.bz2'.
> […]
> > Any idea on what might be the problem? Thanks.
>
> What does the log file say?
>
> --
> Ricardo
prev parent reply other threads:[~2021-07-19 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 7:27 Problem installing Guix (through binary installation script) on AWS EC2 Lo Peter
2021-07-19 7:30 ` Lo Peter
2021-07-19 7:58 ` Lo Peter
2021-07-19 11:28 ` Ricardo Wurmus
2021-07-19 13:22 ` Lo Peter [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='CAEM+zmjTdrFUo6dCU36-J0F77Ry7SBUfTjVZgyX+=Z=GUmW-hA@mail.gmail.com' \
--to=peterloleungyau@gmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).