GNU bug report logs - #53434
Patches to unbreak many i686 packages

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#53434: closed (Patches to unbreak many i686 packages)
Date: Thu, 28 Apr 2022 21:36:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 28 Apr 2022 23:35:34 +0200
with message-id <878rroc2mx.fsf <at> gnu.org>
and subject line Re: bug#53434: Patches to unbreak many i686 packages
has caused the debbugs.gnu.org bug report #53434,
regarding Patches to unbreak many i686 packages
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
53434: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53434
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Denis 'GNUtoo' Carikli <GNUtoo <at> cyberdimension.org>
To: guix-patches <at> gnu.org
Subject: Patches to unbreak many i686 packages
Date: Sat, 22 Jan 2022 03:54:11 +0100

[Message part 3 (text/plain, inline)]

Hi,

This is a patch serie to unbreak many i686 packages.

In it, there is a patch to disable tests for Guix. This is necessary
until the bug #52752 [1] is fixed. Part of it was fixed, but then some
new tests failed and I'm unsure if I've managed to re-open the
bug, or if I should bugreport in a new bug.

I've tested this patch serie by building a system (I've attached the
system.scm) with the following command:
> ./pre-inst-env guix system build -M 1 -c 1 --save-provenance \
> system.scm

I use that system.scm as it worked before as my guix system
installation used that (with gdm enabled and without (debug? #t) and
(wayland? #t) in the gdm configuration).

The big issue I had when doing that work is that at the time I managed
to verify that everything was ok with guix system build, but at that
point new commits are merged into the Guix repository, and after
rebasing, the build takes ages again (usually one day or more) due to
missing substitutes but also because building Guix also hangs with
messages like that:
> GC Warning: Failed to expand heap by 1335296 bytes
> GC Warning: Out of Memory! Heap size: 2617 MiB. Returning NULL!
> Warning: Unwind-only out of memory exception; skipping pre-unwind
> handler.
> Warning: Unwind-only out of memory exception; skipping pre-unwind
> handler.
That is not an issue when building it with 'make' as you restart at the
same point, but when running guix system build you need to restart from
scratch.

So I've tested all that on top of commit
4d7a997ee147acf82c8ca510c0ecd3f520ea74f4 (gnu: Add nhooks.), and right
now I'm still in the process of testing the rebase on top of commit
cadcbbaf655953b28df9466c07b4b5c63d29b00b (gnu: r-bigmelon: Add r-knitr.

I've sent patches for the rebased version.

References:
-----------
[1]http://debbugs.gnu.org/cgi/bugreport.cgi?bug=52752

Denis.

[system.scm (text/x-scheme, attachment)]

[Message part 5 (application/pgp-signature, inline)]

[Message part 6 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: Denis 'GNUtoo' Carikli <GNUtoo <at> cyberdimension.org>
Cc: 53434-done <at> debbugs.gnu.org, Maxime Devos <maximedevos <at> telenet.be>
Subject: Re: bug#53434: Patches to unbreak many i686 packages
Date: Thu, 28 Apr 2022 23:35:34 +0200

Hi,

Denis 'GNUtoo' Carikli <GNUtoo <at> cyberdimension.org> skribis:

> On Wed, 16 Feb 2022 14:53:53 +0100
> Ludovic Courtès <ludo <at> gnu.org> wrote:
>
>> Did the problem sort itself?
> I think so. Beside gdm that started to really depend on rust, all the
> other packages I mentioned now build fine.
>
> Should I send a mail to close the bug?

Doing it right now.  :-)

Thanks!

Ludo’.

Previous Next

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