GNU bug report logs - #35108
ungoogled-chromium fails to install

Previous Next

Package: guix;

Reported by: Blackbeard <barbanegra <at> posteo.mx>

Date: Tue, 2 Apr 2019 19:17:01 UTC

Severity: normal

Done: Marius Bakke <mbakke <at> fastmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Marius Bakke <mbakke <at> fastmail.com>
To: Jeff Bauer <jbauer <at> rubic.com>
Cc: 35108 <at> debbugs.gnu.org
Subject: bug#35108: ungoogled-chromium fails to install
Date: Sat, 25 May 2019 13:06:58 +0200
[Message part 1 (text/plain, inline)]
Jeff Bauer <jbauer <at> rubic.com> writes:

> On Thu, May 16, 2019 at 04:52:14PM +0200, Marius Bakke wrote:
>> The problem with Ungoogled-Chromium is that it (at some point) uses
>> 6-8GiB of memory *per core* during the build.
>>
>> It would be great to codify this constraint in the package definition,
>> but I can't think of an easy way short of parsing /proc/meminfo.
>>
>> For now we can disable parallel building, which will arguably provide
>> a better user experience than thrashing and crashing systems...
>>
>> Thoughts?
>
> Interesting.  If I ran the following command, the installation
> might succeed?
>
>   guix package -i ungoogled-chromium --cores=1

Errh, sorry for the belated response.  The above command should indeed
work around this issue.
[signature.asc (application/pgp-signature, inline)]

This bug report was last modified 5 years and 67 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.