guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Merging ‘core-updates’ real soon


From: Kaelyn
Subject: Re: Merging ‘core-updates’ real soon
Date: Wed, 21 Aug 2024 22:07:08 +0000

On Wednesday, August 21st, 2024 at 1:43 PM, Ludovic Courtès <ludo@gnu.org> 
wrote:

> 
> 
> Hello Guix!
> 
> I’d like to propose merging ‘core-updates’ real soon, say by next week,
> Friday 30th.

Woohoo! I look forward to it. My thanks and congratulations to all who helped 
with 'core-updates'! :)

> 
> 
> But first, this branch started about a year ago (!), and it’s hard for
> someone who’s not following IRC 7 days a week to figure out what the
> status is—something we should definitely improve on.
> 
> An overview in terms of package coverage can be found here:
> 
> https://qa.guix.gnu.org/branch/core-updates
> 
> To view “blocking builds” (packages that fail to build and thus “block”
> all those that depend on it), say for i686-linux, see:
> 
> https://data.qa.guix.gnu.org/revision/aab1fe98574e1cd4c7911c1e5571b3733fb71d67/blocking-builds?system=i686-linux&target=none&limit_results=50
> 
> or run:
> 
> ./pre-inst-env guix weather -s i686-linux -c 200
> 
> from a ‘core-updates’ checkout. This gives an idea where to focus our
> efforts. You can also browse individual ci.guix builds at:
> 
> https://ci.guix.gnu.org/eval/latest/dashboard?spec=core-updates
> 
> Currently, we’re at ~95% on x86_64-linux, 80–90% on the other *-linux
> systems, and ~2% on i586-gnu (GNU/Hurd; that’s more or less where we
> were before.) Note that ci.guix is still struggling with aarch64-linux
> build and hasn’t even attempted armhf-linux builds, but bordeaux.guix is
> doing well.
> 
> I’m aware of at least one important issue that prevents use of Guix
> System on i686-linux:
> 
> https://issues.guix.gnu.org/72725
> 
> To me, that’s the last blocker, even though there’s room for improvement
> here and there (for instance, FFmpeg currently fails to build on
> i686-linux).

My three 'core-updates' patches (which thank you for sprucing the remaining two 
up and committing them!) were from me addressing the main build failures I 
encountered while building my system and home configs against core-updates: 
wine64 and wine64-staging not building due to their dependence on the 32-bit 
(i686-linux) wine and wine-staging packages--the three patches fixed the wine64 
build for me, although building wine-staging (for wine64-staging) hit the 
FFmpeg build failure. After two weeks of bisecting, I tracked it down to commit 
8025d419db which updates binutils from 2.38 to 2.41. I haven't figured out how 
to address the bug but it seems to be from a change between 2.38 and 2.39, as I 
also found a Gentoo bug report hitting the same FFmpeg build error 
(https://bugs.gentoo.org/893118) and downgraded binutils to 2.39 to confirm the 
error is present with that version.

Otherwise, IIRC I didn't encounter any other build failures for x86_64-linux.

Cheers,
Kaelyn

> 
> Anything else?
> 
> 
> A number of people already provided feedback informally after
> reconfiguring their systems on ‘core-updates’. Please share your
> experience, positive or negative, here!
> 
> Ludo’.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]