public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: topazus <topazus@outlook.com>
To: git-commits@fedoraproject.org
Subject: [rpms/hardinfo2] epel10: 2.3.1
Date: Sat, 05 Sep 2026 16:43:57 GMT [thread overview]
Message-ID: <178862663784.1.115636544665581957.rpms-hardinfo2-624f62a76a0a@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/hardinfo2
Branch : epel10
Commit : 624f62a76a0a8d7cab523cbb4f497730bd584558
Author : topazus <topazus@outlook.com>
Date : 2026-09-06T00:39:49+08:00
Stats : +2/-4 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/hardinfo2/c/624f62a76a0a8d7cab523cbb4f497730bd584558?branch=epel10
Log:
2.3.1
---
diff --git a/hardinfo2.spec b/hardinfo2.spec
index 1fd5cb2..269a1dd 100644
--- a/hardinfo2.spec
+++ b/hardinfo2.spec
@@ -3,7 +3,7 @@
%endif
Name: hardinfo2
-Version: 2.2.16
+Version: 2.3.1
Release: %autorelease
Summary: System Information and Benchmark for Linux Systems
@@ -46,8 +46,6 @@ Summary: System Information and Benchmark for Linux Systems
License: GPL-2.0-or-later AND LGPL-2.1-or-later AND LGPL-2.0-or-later AND GPL-3.0-or-later AND LGPL-2.1-only
URL: https://github.com/hardinfo2/hardinfo2
Source0: %{url}/archive/release-%{version}/hardinfo2-release-%{version}.tar.gz
-# PACKAGE ELN and RHEL 11
-Patch0: %{url}/pull/294.patch
BuildRequires: gcc-c++
BuildRequires: cmake
diff --git a/sources b/sources
index eeddb24..f7b4f69 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (hardinfo2-release-2.2.16.tar.gz) = ad2a766599aa9df6ed0dbf6933ee306eddb2ae0f0f5ea3ceb9c4ef6ab67122e7e595bec58f93a5436a3dd594c2829f89a66bdb7252aa9bcabdbd1227a2af51d5
+SHA512 (hardinfo2-release-2.3.1.tar.gz) = 93ce0c80986f131c2f13d0ae14dec2011c82db4a0668f4c6eec62be6cde5fa426aef600046c70106fa40c781f4dbf3a368239dd228a2a7cb2adf68d9f7e4946b
reply other threads:[~2026-09-05 16:43 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=178862663784.1.115636544665581957.rpms-hardinfo2-624f62a76a0a@fedoraproject.org \
--to=topazus@outlook.com \
--cc=git-commits@fedoraproject.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