From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] linux-headers: update to 5.19.
Date: Tue, 23 Aug 2022 12:23:28 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38854@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
There is a new pull request by dataCobra against master on the void-packages repository
https://github.com/dataCobra/void-packages linux-headers-update-5.19
https://github.com/void-linux/void-packages/pull/38854
linux-headers: update to 5.19.
#### Testing the changes
- I tested the changes in this PR: **YES**
Packages that depend on `linux-headers` still want the 5.18 kernel header files. Since the new
mainline kernel for void is 5.19 I consider this a bug.
A patch file from https://github.com/void-linux/void-packages/pull/38854.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-linux-headers-update-5.19-38854.patch --]
[-- Type: text/x-diff, Size: 596 bytes --]
From d4d625a1b8d0a434d9edb23129dd70ac6c3d2aa5 Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Tue, 23 Aug 2022 12:19:59 +0200
Subject: [PATCH] linux-headers: update to 5.19.
---
srcpkgs/linux/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/linux/template b/srcpkgs/linux/template
index 965a96997a33..1d4a5d35eeea 100644
--- a/srcpkgs/linux/template
+++ b/srcpkgs/linux/template
@@ -1,6 +1,6 @@
# Template file for 'linux'
pkgname=linux
-version=5.18
+version=5.19
revision=1
build_style=meta
depends="linux${version} linux-base"
next reply other threads:[~2022-08-23 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 10:23 dataCobra [this message]
2022-08-23 10:36 ` paper42
2022-08-23 10:45 ` dataCobra
2022-08-23 10:45 ` [PR PATCH] [Closed]: " dataCobra
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-38854@inbox.vuxu.org \
--to=datacobra@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).