Hey Andreas!

No, thank you for keeping an eye on QA!

BTW, I am adding SilverlightningY to the loop, our newest audio team
member!

On Fri, Jun 12, 2026 at 01:14:56PM +0200, Andreas Enge wrote:
> Thanks for your reactivity!
> 
> Now alsa-plugins breaks:
>    
> https://bordeaux.guix.gnu.org/build/30c230be-582a-40bb-9e28-d49a707e2473/log
> and a few important packages such as webkitgtk:
>    
> https://qa.guix.gnu.org/branch/audio-team/package-changes?x86_64-linux-change=broken&x86_64-linux-change=still-failing&x86_64-linux-change=unknown-to-failing&x86_64-linux-change=new-failing
>    
> https://bordeaux.guix.gnu.org/build/9e28bc35-cc74-474e-9574-8f06d065b462/log
> 
> The first one is probably due to this commit:
> commit 55406d7a1e019949caca7f0f0c65ce1ec25d2e28
> Author: coopi <[email protected]>
> Date:   Thu Apr 16 11:13:29 2026 +0400
>     gnu: alsa-plugins: Update to 1.2.12.
>     * gnu/packages/linux.scm (alsa-plugins) [version]: Update to 1.2.12.
>     [source]: Switch to 'git-fetch'.
>     [description]: Reword.
> Where the switch to git-fetch probably required to add bootstrapping
> native-inputs. The package probably never built after this commit...

> It would be good to build the packages and if possible their direct
> dependents before adding a PR to a team branch.
I am sure I built the packages *before* pushing to the audio-team
branch.  Not sure about after, though

I'm running a `build -k -P1` job now locally for all the major packages.
It'd be great if we could figure out and fix all the issues with this QA
cycle instead of having to wait another bunch of months.


Andreas, are we in a particular rush?  Because from our (or at least my)
perspective we waited for QA to hint us towards everything we'd need to
resolve before pushing the audio-team changes to master.  I mean, like,
everything throughout the dependency tree.

But I somehow get the feeling that being on top of the QA build queue
means being in a rush and getting into a pushable state ASAP.

Is this some kind of misconception on my part?

Thanks for having an eye on this and helping us out!
g



Reply via email to