unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>
Cc: 51304@debbugs.gnu.org
Subject: bug#51304: guix upgrade fails on qutebrowser
Date: Thu, 21 Oct 2021 16:00:26 -0400	[thread overview]
Message-ID: <YXHG2t5E3TMH3CMW@jasmine.lan> (raw)
In-Reply-To: <CAEtmmew=UpWzRY0EMAaotL59ns_tDq20g=XSoiQdrDK5bt_6OQ@mail.gmail.com>

On Wed, Oct 20, 2021 at 04:06:21PM +0200, Rostislav Svoboda wrote:
> which, in turn, surprises me, since I have 32GB of RAM. (And I thought
> already I bought too much, ugh :)

I think that should be enough, even for qtwebengine / Chromium!

But maybe you are building with a high level of parallelism. You could
try Tobias's suggestion to limit the number of cores used to 2 or 4.
That's a guess of what will work, based on your 32GB RAM.




  reply	other threads:[~2021-10-21 20:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <875ypw9c4w.fsf.ref@aol.com>
2021-10-20 11:37 ` bug#51304: guix upgrade fails on qutebrowser Rostislav Svoboda
2021-10-20 12:29   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-20 13:23     ` Rostislav Svoboda
2021-10-20 13:45       ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-20 14:06         ` Rostislav Svoboda
2021-10-21 20:00           ` Leo Famulari [this message]
2022-02-03 15:56   ` Adam Maleszka via Bug reports for GNU Guix
2022-02-03 16:16     ` Leo Famulari
2022-02-05 22:08   ` Adam Maleszka via Bug reports for GNU Guix

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=YXHG2t5E3TMH3CMW@jasmine.lan \
    --to=leo@famulari.name \
    --cc=51304@debbugs.gnu.org \
    --cc=rostislav.svoboda@gmail.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).