unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Wilko Meyer <w@wmeyer.eu>
Cc: guix-devel@gnu.org
Subject: Re: Need people to help with kernel updates
Date: Thu, 12 Oct 2023 14:44:47 -0400	[thread overview]
Message-ID: <ZSg-nx2Ty_kgRbNo@jasmine.lan> (raw)
In-Reply-To: <87pm1kyqnv.fsf@wmeyer.eu>

On Thu, Oct 12, 2023 at 02:15:41PM +0200, Wilko Meyer wrote:
> seems to be good again at least, as in:
> 
> - it builds locally
> - QA[1] looks okayish as far as I can tell (no lint warnings, build
>   statuses look good on more common ISA)

I agree, this already counts as "good".

I pushed your patches as 06acda9715711c406f30b3a314387002244d8792

> even though we still seem to have partial build failures on some
> architectures:
> 
> - x86_64-linux and aarch64-linux build completely fine according to QA
> - without any failures or unknown status
> - i686-linux has mostly succeeding builds, 5 unknown
> - armhf-linux has one failing and 18 unknown

Things are even better since you wrote!

The only failure is of a quasi-obsolete wireguard package on i686.
Newer kernels don't require this package to provide an out-of-tree
Wireguard driver.

I see that ppc64le is still "unknown", which in this case means that the
builds are scheduled but haven't been performed yet.

Overall, the fact that qa.guix.gnu.org is successfully building across
so many architectures means that we have a strong foundation for the
future of building kernel packages in Guix.

Thanks you for taking the initiative to write the patches and manage QA
for this latest round of updates!

I'm curious, now that we've done a round, do you have any thoughts about
the work so far?


  reply	other threads:[~2023-10-12 18:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-07 18:04 Need people to help with kernel updates Leo Famulari
2023-10-07 18:31 ` Wilko Meyer
2023-10-08 18:12   ` Leo Famulari
2023-10-09 16:21     ` Wilko Meyer
2023-10-10 11:18       ` Leo Famulari
2023-10-10 14:13         ` wolf
2023-10-12 12:15         ` Wilko Meyer
2023-10-12 18:44           ` Leo Famulari [this message]
2023-10-15 19:58             ` Wilko Meyer
2023-10-28 20:17               ` Leo Famulari
2023-10-29 12:15                 ` Wilko Meyer
2023-10-09  1:22 ` John Kehayias
2023-10-09 13:22   ` Luis Felipe
2023-10-14 15:48     ` Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZSg-nx2Ty_kgRbNo@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=w@wmeyer.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).