From: Leo Famulari <leo@famulari.name>
To: 74843@debbugs.gnu.org
Cc: Leo Famulari <leo@famulari.name>, Wilko Meyer <w@wmeyer.eu>
Subject: [bug#74843] [PATCH] gnu: linux-libre 6.6: Update to 6.6.65.
Date: Thu, 12 Dec 2024 18:21:06 -0500 [thread overview]
Message-ID: <288a83c89d50463625b8437f7782dce3a39c4077.1734045666.git.leo@famulari.name> (raw)
* gnu/packages/linux.scm (linux-libre-6.6-version): Update to 6.6.65.
(linux-libre-6.6-pristine-source): Update hash.
Change-Id: I48f65a614f2ba5cc7ada038d0fad5f345f5d857f
---
gnu/packages/linux.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index 0fc2c4428a..36354cc2f7 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -532,7 +532,7 @@ (define-public linux-libre-6.11-pristine-source
;; Here are the support timelines:
;; <https://www.kernel.org/category/releases.html>
-(define-public linux-libre-6.6-version "6.6.64")
+(define-public linux-libre-6.6-version "6.6.65")
(define-public linux-libre-6.6-gnu-revision "gnu")
(define deblob-scripts-6.6
(linux-libre-deblob-scripts
@@ -542,7 +542,7 @@ (define deblob-scripts-6.6
(base32 "1x3455v7sfzakq99ydifh65yzvjzrw06p2lchwb6902yzqbnh786")))
(define-public linux-libre-6.6-pristine-source
(let ((version linux-libre-6.6-version)
- (hash (base32 "1cbag4wzv5fpjdcl0rpp158ch1q17rfz2qxm1xjjyhnblqzxjpq6")))
+ (hash (base32 "1q53xiwnszchl9c4g4yfxyzk4nffzgb4a7aq9rsyg1jcidp4gqbs")))
(make-linux-libre-source version
(%upstream-linux-source version hash)
deblob-scripts-6.6)))
base-commit: 98aca7a2b6250e7f6a2ff3a93b29d0dea896ad21
--
2.46.0
next reply other threads:[~2024-12-12 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 23:21 Leo Famulari [this message]
2024-12-16 19:16 ` bug#74843: [PATCH] gnu: linux-libre 6.6: Update to 6.6.65 Leo Famulari
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=288a83c89d50463625b8437f7782dce3a39c4077.1734045666.git.leo@famulari.name \
--to=leo@famulari.name \
--cc=74843@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.