From: Joshua Branson via Guix-patches via <guix-patches@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 58357@debbugs.gnu.org
Subject: [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations'
Date: Sat, 19 Nov 2022 09:06:47 -0500 [thread overview]
Message-ID: <87iljbujgo.fsf@dismail.de> (raw)
In-Reply-To: <87wn7tk0nv.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Thu, 17 Nov 2022 17:26:12 +0100")
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> jbranso@dismail.de writes:
>> I can submit a patch in the guix manual to recommend hardware with at least
>> 1 or 2GB. Which is better? 1 or 2?
>
> Come to think of it, there recently was a commit about Guix System (not
> about but because of the Guix package manager):
>
> commit 98a8b48a69b8208475c9a1e40d09517f8643b8cb
> Author: Ludovic Courtès <ludo@gnu.org>
> Date: Thu Sep 1 14:45:45 2022 +0200
>
> doc: Suggest more RAM for "Running Guix in a VM".
>
> Fixes <https://issues.guix.gnu.org/57474>.
> Reported by Michael F. Lamb <mike@orbital.rodeo>.
>
> Running 'guix pull' to target current revisions would lead to memory
> exhaustion. Bumping the memory size works around that.
>
> * doc/guix.texi (Running Guix in a VM): Change "-m 1024" to "-m 2048".
>
>
> However, to quote Ludo from that bug#57474:
>> It looks like the memory requirements to build the latest revisions of
>> Guix have increased (and this is a bit ridiculous).
>
> Nevertheless the docs should mention 2GB, I guess.
>
Sounds good. I'll create a patch soon.
>
> Regards,
> Florian
next prev parent reply other threads:[~2022-11-19 14:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Yz/FHD608HeU6iIM@3900XT>
2022-10-07 14:24 ` [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations' Joshua Branson via Guix-patches via
2022-10-08 9:55 ` pelzflorian (Florian Pelz)
2022-10-08 15:33 ` jbranso--- via Guix-patches via
2022-10-10 10:07 ` pelzflorian (Florian Pelz)
2022-10-14 15:12 ` Ludovic Courtès
2022-10-14 15:47 ` kiasoc5 via Guix-patches via
2022-10-15 9:47 ` pelzflorian (Florian Pelz)
2022-10-16 11:53 ` pelzflorian (Florian Pelz)
2022-10-14 17:09 ` pelzflorian (Florian Pelz)
2022-10-15 15:51 ` pelzflorian (Florian Pelz)
2022-10-17 16:35 ` Ludovic Courtès
2022-10-14 19:28 ` jbranso--- via Guix-patches via
2022-11-03 19:21 ` Ludovic Courtès
2022-11-16 0:22 ` pelzflorian (Florian Pelz)
2022-11-16 23:16 ` jbranso--- via Guix-patches via
2022-11-17 16:26 ` pelzflorian (Florian Pelz)
2022-11-19 14:06 ` Joshua Branson via Guix-patches via [this message]
2022-12-08 17:02 ` pelzflorian (Florian Pelz)
2023-03-09 21:06 ` pelzflorian (Florian Pelz)
2023-08-20 17:44 ` pelzflorian (Florian Pelz)
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=87iljbujgo.fsf@dismail.de \
--to=guix-patches@gnu.org \
--cc=58357@debbugs.gnu.org \
--cc=jbranso@dismail.de \
--cc=pelzflorian@pelzflorian.de \
/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).