From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] [RFC] note the kernel series each metapackage follows
Date: Tue, 19 Nov 2024 04:35:52 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53137@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
There is a new pull request by classabbyamp against master on the void-packages repository
https://github.com/classabbyamp/void-packages linux-meta
https://github.com/void-linux/void-packages/pull/53137
[RFC] note the kernel series each metapackage follows
The current kernel metapackage policy is:
- `linux-mainline`: follows the latest available kernel
- `linux`: follows the latest available kernel that supports popular dkms modules, like `zfs` and `nvidia`
- `linux-lts`: follows an LTS release and is behind `linux`
In recent times, kernels have been released and gone EOL faster than `zfs` can release build fixes, and `nvidia` in particular has had trouble with recent kernels, holding us back from bumping `linux` to 6.10 or 6.11. In the recent past, we've had `linux` point to a kernel that was already EOL (6.3 or 6.5), so we risked not getting backports for important fixes.
I propose the following changes:
- `linux-mainline`: no change
- `linux`: follows the latest LTS release
- `linux-lts`: follows the second-latest LTS release
This should help us keep `linux` on a supported kernel and provide a more reliable indicator for when we can update the default kernel series, I think.
@void-linux/pkg-committers, thoughts?
A patch file from https://github.com/void-linux/void-packages/pull/53137.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-linux-meta-53137.patch --]
[-- Type: text/x-diff, Size: 1975 bytes --]
From d7b85d3d4203c7626ca700b7dd7add3fc392e020 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:22:28 -0500
Subject: [PATCH 1/3] linux: note that it follows the latest LTS release
---
srcpkgs/linux/template | 1 +
1 file changed, 1 insertion(+)
diff --git a/srcpkgs/linux/template b/srcpkgs/linux/template
index b42a1f00cdf7fb..0b51c561d73d31 100644
--- a/srcpkgs/linux/template
+++ b/srcpkgs/linux/template
@@ -1,4 +1,5 @@
# Template file for 'linux'
+# this package should follow the latest LTS kernel listed on kernel.org
pkgname=linux
version=6.6
revision=1
From 4f47d80faf36a4881f983de7f12065dc8c87ea52 Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:22:52 -0500
Subject: [PATCH 2/3] linux-lts: note that it follows the second-latest LTS
release
---
srcpkgs/linux-lts/template | 1 +
1 file changed, 1 insertion(+)
diff --git a/srcpkgs/linux-lts/template b/srcpkgs/linux-lts/template
index 638ad8aa7af01f..e9f2653b4c7683 100644
--- a/srcpkgs/linux-lts/template
+++ b/srcpkgs/linux-lts/template
@@ -1,4 +1,5 @@
# Template file for 'linux-lts'
+# this package should follow the second-latest LTS kernel listed on kernel.org
pkgname=linux-lts
version=6.1
revision=1
From 2bbbcc3d03f03cf9e6c100abd80e3df2962019ef Mon Sep 17 00:00:00 2001
From: classabbyamp <void@placeviolette.net>
Date: Mon, 18 Nov 2024 22:23:10 -0500
Subject: [PATCH 3/3] linux-mainline: note that it follows the latest mainline
release
---
srcpkgs/linux-mainline/template | 1 +
1 file changed, 1 insertion(+)
diff --git a/srcpkgs/linux-mainline/template b/srcpkgs/linux-mainline/template
index 7a07d69df76ef3..01597eec076d58 100644
--- a/srcpkgs/linux-mainline/template
+++ b/srcpkgs/linux-mainline/template
@@ -1,4 +1,5 @@
# Template file for 'linux-mainline'
+# this package should follow the latest mainline kernel listed on kernel.org
pkgname=linux-mainline
version=6.11
revision=1
next reply other threads:[~2024-11-19 3:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 3:35 classabbyamp [this message]
2024-11-19 3:54 ` [RFC] adjust and " Calandracas606
2024-11-19 4:18 ` lemmi
2024-11-19 10:35 ` leahneukirchen
2024-11-19 11:10 ` ahesford
2024-11-19 11:10 ` ahesford
2024-11-19 11:59 ` leahneukirchen
2024-11-19 12:44 ` Calandracas606
2024-11-19 12:50 ` Calandracas606
2024-11-19 12:50 ` Calandracas606
2024-11-19 12:53 ` ahesford
2024-11-19 14:17 ` [PR PATCH] [Updated] " classabbyamp
2024-11-19 14:18 ` classabbyamp
2024-11-19 14:21 ` [PR PATCH] [Updated] " classabbyamp
2024-11-19 14:27 ` classabbyamp
2024-11-19 14:27 ` classabbyamp
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53137@inbox.vuxu.org \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).