From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>
Cc: 51304@debbugs.gnu.org
Subject: bug#51304: guix upgrade fails on qutebrowser
Date: Wed, 20 Oct 2021 15:45:06 +0200 [thread overview]
Message-ID: <871r4fiz7f.fsf@nckx> (raw)
In-Reply-To: <CAEtmmezgeuvWPX1hmds8unSc62Vz_-BTnTYt+MHGRY5j7=eC=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
Rostislav,
Rostislav Svoboda 写道：
> Ehm, sorry. The file is attached.
Thanks! Hm. I might've oversold things with ‘useful’ in my
previous message…
The log just ends, without an error message as far as I can tell.
I can only guess: maybe you ran out of memory? Does dmesg (or
/var/log/messages, if you've since rebooted) contain any matches
for "Out of memory"?
One unsatisfying work-around for that is to build with
--{max-jobs,cores}=1 to limit the number of build & make jobs if
you were previously building in parallel. It will make the build
take even longer, though…
Sorry,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-10-20 13:49 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 [this message]
2021-10-20 14:06 ` Rostislav Svoboda
2021-10-21 20:00 ` Leo Famulari
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=871r4fiz7f.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=51304@debbugs.gnu.org \
--cc=me@tobias.gr \
--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).