Subject: bug#64369: closed (Re: bug#64369: Request for merging "mesa-updates" branch)

From: [email-masked] (GNU bug Tracking System)
Date: Mon, 31 Jul 2023 15:26:02 +0000

Your bug report

#64369: Request for merging "mesa-updates" branch

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
64369: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64369
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#64369: Request for merging "mesa-updates" branch
From: John Kehayias <[email-masked]>
To: [email-masked]
Cc: Christopher Baines <[email-masked]>
Date: Mon, 31 Jul 2023 15:24:40 +0000
List-Id: <debbugs-submit.debbugs.gnu.org>

On Fri, Jul 28, 2023 at 03:29 PM, John Kehayias wrote:

> Hello,
>
> On Mon, Jul 24, 2023 at 03:14 PM, John Kehayias wrote:
>
>> I'm not sure what is going on with the CI and QA.
>> <https://ci.guix.gnu.org/> hasn't shown any new evaluations in several
>> days (the workers were stuck at some point too, but nckx gave it a
>> poke and now I don't see any builds left). But when I check with guix
>> weather I do get substitutes. Any ideas what the actual status is?
>>
>
> Things got unstuck recently at ci.guix.gnu.org was churning away. I saw
> some failed builds due to what looks like some build farm download
> issue, e.g. <https://ci.guix.gnu.org/build/1671444/details> which build
> fine locally. I think this is what blocked a bunch of KDE-related
> packages as well. A bunch of java packages also failed but the ones I
> tried also built locally (some had long build logs but I didn't see the
> cause).
>
> So I think x86 is okay, while e.g. aarch64 is slowly chipping away.
>
> If that's okay then I'll cherry pick the commits to master today or
> tomorrow.
>
> Thanks for your help Chris!

Pushed to master with 4f0ce65b74a3d28bf6ecbe4c15052dd0de22b284 the final
commit from that branch.

Thanks!

(I'll delete the remote branch for now, until needed again.)

Subject: Request for merging "mesa-updates" branch
From: John Kehayias <[email-masked]>
To: [email-masked]
Date: Fri, 30 Jun 2023 15:53:28 +0000
List-Id: <debbugs-submit.debbugs.gnu.org>

Hello all,

This is a request to merge the recently created "mesa-updates" branch. Currently there are just 2 patches on there, fixing/updating mesa only. The main thing to see is how substitute building goes in case anything breaks, but I'm hoping there isn't anything caused by this update.

I believe the "ruby-team" and "tex-team-next" [1] are ahead in the queue, not sure the timing of where those are. In addition/alternatively, would it make sense to have this branch as a separate build job on Cuirass directly as the "kernel-updates" branch? This would need a build roughly every month or so when mesa puts out a new update, we check for breakages, and then merge to master with substitutes available already.

I wasn't sure if this needs formal blockers in debbugs for the other branch merge requests, let me know!

Thanks,
John

[0] <https://issues.guix.gnu.org/63713>

[1] <https://issues.guix.gnu.org/64324>