From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] spectre-meltdown-checker: Update to 0.46
Date: Fri, 15 Sep 2023 15:07:18 +0000 [thread overview]
Message-ID: <20230915150718.693162-1-peter.mueller@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1994 bytes --]
See https://github.com/speed47/spectre-meltdown-checker/releases/tag/v0.46
for this version's release notes.
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
lfs/spectre-meltdown-checker | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lfs/spectre-meltdown-checker b/lfs/spectre-meltdown-checker
index bfb429363..4bfe5274f 100644
--- a/lfs/spectre-meltdown-checker
+++ b/lfs/spectre-meltdown-checker
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2022 IPFire Team <info(a)ipfire.org> #
+# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -26,7 +26,7 @@ include Config
SUMMARY = Spectre & Meltdown Vulnerability Checker
-VER = 0.45
+VER = 0.46
THISAPP = spectre-meltdown-checker-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = spectre-meltdown-checker
-PAK_VER = 6
+PAK_VER = 7
DEPS =
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 14d49f40458167ab9af04cc31c9a0b9f8cb5f1e9417f5ac0bab0290be01cf14a737c716d8d28873fee1870535c0b36a56dac2d39f2cc7a000d27f0643a94cff7
+$(DL_FILE)_BLAKE2 = 355469c2176fffa8fb40695b47174959c9112e66cd870545ed424ef7b6ef4c10a5aa94bfbc6912510c979e16b0f8a18c0b822200eb69e9ded8300305d779fa79
install : $(TARGET)
--
2.39.2
reply other threads:[~2023-09-15 15:07 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=20230915150718.693162-1-peter.mueller@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@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