unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Wilko Meyer <w@wmeyer.eu>
To: Leo Famulari <leo@famulari.name>
Cc: 72123@debbugs.gnu.org
Subject: [bug#72123] [PATCH] gnu: Add linux-libre 6.10.
Date: Tue, 30 Jul 2024 22:31:49 +0200	[thread overview]
Message-ID: <87y15iei4q.fsf@wmeyer.eu> (raw)
In-Reply-To: <Zqhe0qJK_hxYlsxI@jasmine.lan> (Leo Famulari's message of "Mon, 29 Jul 2024 23:32:34 -0400")


Hi Leo,

Leo Famulari <leo@famulari.name> writes:
> Pushed as 93e19067b4428e41c281eebe19746ea253591aad

Thanks for reviewing & pushing the changes!

> The 6.9 series is now marked as end-of-life on kernel.org, so we can
> start moving to 6.10 soon.

Yes, I'll prepare the removal of 6.9 and the changes required to set
6.10 as our new default kernel. We could push these changes with the
next iteration of kernel updates.

We should also aim to solve #72119[0] rather sooner than later, as
packages like libbpf currently depend on linux-libre-headers-6.9 as a
specific version of the headers; there's a linux-libre-headers variable
but that currently points to an older kernel version for bootstrapping
purposes iirc. I'd suggest introducing linux-libre-headers-latest or
something along those lines, so we don't have to track wether we cause
breakages by removing end of life header packages. All packages that
depend on a specific headers package should imho depend on whatever
linux-libre-headers-latest points to. WDYT?

[0]: https://issues.guix.gnu.org/72119

-- 
Kind regards,
Wilko Meyer




      reply	other threads:[~2024-07-30 20:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 15:24 [bug#72123] [PATCH] gnu: Add linux-libre 6.10 Wilko Meyer
2024-07-17 14:57 ` Leo Famulari
2024-07-17 18:22 ` Leo Famulari
2024-07-30  3:32 ` bug#72123: " Leo Famulari
2024-07-30 20:31   ` Wilko Meyer [this message]

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=87y15iei4q.fsf@wmeyer.eu \
    --to=w@wmeyer.eu \
    --cc=72123@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).