patch to fix build failure

patch to fix build failure

[Andy Tai]

Hi, just observation on some aspect of current guix packages, as seen
from doing guix package -u

(I know all guix work is done by volunteers, so this is not a
complaint but just reporting on state of things)
after the core-update branch merge to main, there are some build
breakages, not unexpected.

I run into a build failure on python-pyopengl-accelerate which
prevents guix package -u from proceeding.  I posted a patch to upgrade
python-pyopengl to the next version, which is sufficient to fix this
build failure.   The patch is in the issue tracker waiting for Guix QA
to schedule it for build check...

but I don't know if there is a chicken and egg problem, that Guix QA
does not seem to schedule recent patches to the main branch for
builds, and then the committers may not look at the patches which have
not passed Guix QA, so things are not moving. (My observation, sorry
if not accurate description)

Again, thanks for all the people working on Guix, including the people
maintaining Guix QA, highly appreciated.

Just curious if there is any thing that is possible to improve the situation.

Re: patch to fix build failure

[Christopher Baines]

[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]


Andy Tai <atai@atai.org> writes:

> I run into a build failure on python-pyopengl-accelerate which
> prevents guix package -u from proceeding.  I posted a patch to upgrade
> python-pyopengl to the next version, which is sufficient to fix this
> build failure.   The patch is in the issue tracker waiting for Guix QA
> to schedule it for build check...
>
> but I don't know if there is a chicken and egg problem, that Guix QA
> does not seem to schedule recent patches to the main branch for
> builds, and then the committers may not look at the patches which have
> not passed Guix QA, so things are not moving. (My observation, sorry
> if not accurate description)
>
> Again, thanks for all the people working on Guix, including the people
> maintaining Guix QA, highly appreciated.
>
> Just curious if there is any thing that is possible to improve the situation.

Things are moving, but due to a lack of available hardware for doing
builds, things are moving quite slowly.

Currently QA submitting builds for patches is disabled [1] as the
bordeaux build farm is busy catching up after the merge of
core-updates.

1: https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=6343780896fcdfdeccfbaf9ef407ceb4641f33b7

You can see an overview of the substitute availability for the master
branch here [2] and currently things are looking good for x86_64-linux.
For powerpc64le-linux and aarch64-linux aren't many builds remaining,
but there are some failing builds leading to the low substitute
availability. For armhf-linux and i686-linux, there are still a lot of
builds to get through, and for i586-gnu, there are failing builds deep
in the graph, so there's fixes needed.

2: https://qa.guix.gnu.org/branch/master

I've got patches I want to see built soon as well, so at some point soon
it'll be the time to start submitting builds for patches again.

On improving the situation though, more hardware we can add to the
bordeaux build farm should help speed things up a lot.

Thanks,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]