From: "Ludovic Courtès" <ludo@gnu.org>
To: Wayne Wallace <fr33d0m@agnuwayofthinking.com>
Cc: 38806@debbugs.gnu.org
Subject: bug#38806: Bug Report
Date: Mon, 30 Dec 2019 22:41:39 +0100 [thread overview]
Message-ID: <87blrp1ofg.fsf@gnu.org> (raw)
In-Reply-To: <75bc685a-62ee-52e4-64cf-10088c467086@agnuwayofthinking.com> (Wayne Wallace's message of "Sun, 29 Dec 2019 19:16:43 -0800")
Hello,
Wayne Wallace <fr33d0m@agnuwayofthinking.com> skribis:
> I was doing a guix pull on a new VM setup
Could it be that your VM ran out of memory during ‘guix pull’? (I’d
recommend ~2G of RAM at least.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-12-30 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 3:16 bug#38806: Bug Report Wayne Wallace
2019-12-30 21:41 ` Ludovic Courtès [this message]
2020-01-05 19:07 ` Gábor Boskovits
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=87blrp1ofg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38806@debbugs.gnu.org \
--cc=fr33d0m@agnuwayofthinking.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.
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).