Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] intel-ucode: update to 20230808 [CVE-2022-40982]
Date: Tue, 08 Aug 2023 21:28:51 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45498@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

There is a new pull request by icp1994 against master on the void-packages repository

https://github.com/icp1994/void-packages intel-ucode
https://github.com/void-linux/void-packages/pull/45498

intel-ucode: update to 20230808 [CVE-2022-40982]
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture: **x86_64**

cc @mhmdanas 

A patch file from https://github.com/void-linux/void-packages/pull/45498.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-intel-ucode-45498.patch --]
[-- Type: text/x-diff, Size: 1266 bytes --]

From 9495a186d3ba76a2a059c3cd7c7ebc184037aeac Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Wed, 9 Aug 2023 00:55:54 +0530
Subject: [PATCH] intel-ucode: update to 20230808.

---
 srcpkgs/intel-ucode/template | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/intel-ucode/template b/srcpkgs/intel-ucode/template
index 090c0c57a1ff1..f3dac4ae8da26 100644
--- a/srcpkgs/intel-ucode/template
+++ b/srcpkgs/intel-ucode/template
@@ -1,14 +1,15 @@
 # Template file for 'intel-ucode'
 pkgname=intel-ucode
-version=20230613
+version=20230808
 revision=1
 archs="i686* x86_64*"
 short_desc="Microcode update files for Intel CPUs"
 maintainer="Mohammed Anas <triallax@tutanota.com>"
 license="custom: Proprietary"
 homepage="https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files"
+changelog="https://raw.githubusercontent.com/intel/Intel-Linux-Processor-Microcode-Data-Files/microcode-20230808/releasenote.md"
 distfiles="https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/archive/microcode-${version}.tar.gz"
-checksum=894d822d2347222a2595d4fc47d358e01d35a54780123100c317dfc31b1b0cc9
+checksum=fe49bb719441f20335ed6004090ab38cdc374134d36d4f5d30be7ed93b820313
 repository=nonfree
 
 do_install() {

             reply	other threads:[~2023-08-08 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08 19:28 icp1994 [this message]
2023-08-08 19:37 ` [PR PATCH] [Updated] " icp1994
2023-08-09 15:07 ` [PR PATCH] [Merged]: " ahesford

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-45498@inbox.vuxu.org \
    --to=icp1994@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).