From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 4e69701332f4cee583752ed3ff3e4d44b129931d
Date: Sat, 22 Jun 2019 20:05:37 +0100 [thread overview]
Message-ID: <20190622190538.6CD7180F69A@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3284 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 4e69701332f4cee583752ed3ff3e4d44b129931d (commit)
from b10365c832420b09be9cb62161fa21aef89e4017 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 4e69701332f4cee583752ed3ff3e4d44b129931d
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Jun 22 20:59:32 2019 +0200
intel-microcode: update to 20190618
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
.../{common => core/134/filelists}/i586/intel-microcode | 0
.../{oldcore/121 => core/134}/filelists/x86_64/intel-microcode | 0
lfs/intel-microcode | 9 ++++-----
3 files changed, 4 insertions(+), 5 deletions(-)
copy config/rootfiles/{common => core/134/filelists}/i586/intel-microcode (100%)
copy config/rootfiles/{oldcore/121 => core/134}/filelists/x86_64/intel-microcode (100%)
Difference in files:
diff --git a/config/rootfiles/core/134/filelists/i586/intel-microcode b/config/rootfiles/core/134/filelists/i586/intel-microcode
new file mode 120000
index 000000000..1c5bc5743
--- /dev/null
+++ b/config/rootfiles/core/134/filelists/i586/intel-microcode
@@ -0,0 +1 @@
+../x86_64/intel-microcode
\ No newline at end of file
diff --git a/config/rootfiles/core/134/filelists/x86_64/intel-microcode b/config/rootfiles/core/134/filelists/x86_64/intel-microcode
new file mode 120000
index 000000000..d5ac074e2
--- /dev/null
+++ b/config/rootfiles/core/134/filelists/x86_64/intel-microcode
@@ -0,0 +1 @@
+../../../../common/x86_64/intel-microcode
\ No newline at end of file
diff --git a/lfs/intel-microcode b/lfs/intel-microcode
index f2223148f..e01ea9934 100644
--- a/lfs/intel-microcode
+++ b/lfs/intel-microcode
@@ -24,10 +24,10 @@
include Config
-VER = 20190514
+VER = 20190618
THISAPP = Intel-Linux-Processor-Microcode-Data-Files-microcode-$(VER)
-DL_FILE = $(THISAPP).tar.gz
+DL_FILE = $(THISAPP).tar.xz
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
@@ -41,8 +41,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = ad5fe712f54387c0737caef8131b4770
-
+$(DL_FILE)_MD5 = 18af9bd8b6c7164f0cd917080a387244
install : $(TARGET)
@@ -74,7 +73,7 @@ $(subst %,%_MD5,$(objects)) :
$(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
- @rm -rf $(DIR_APP) && cd $(DIR_SRC) && mkdir -p $(DIR_APP) && tar zxf $(DIR_DL)/$(DL_FILE)
+ @rm -rf $(DIR_APP) && cd $(DIR_SRC) && mkdir -p $(DIR_APP) && tar axf $(DIR_DL)/$(DL_FILE)
# Copy the firmware files into the right position
cd $(DIR_APP) && cp -R intel-ucode /lib/firmware/
@rm -rf $(DIR_APP)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-06-22 19:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190622190538.6CD7180F69A@people01.i.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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