public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jirka Hladky <jhladky@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/haveged] epel10: Merge rawhide — add rpminspect.yaml
Date: Thu, 18 Jun 2026 02:09:23 GMT [thread overview]
Message-ID: <178174856341.1.12353842539765952766.rpms-haveged-478987ed8a1a@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/haveged
Branch : epel10
Commit : 478987ed8a1af79eb43b09b5a0ce3fbcd7de539c
Author : Jirka Hladky <jhladky@redhat.com>
Date : 2026-06-18T04:09:15+02:00
Stats : +9/-29 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/haveged/c/478987ed8a1af79eb43b09b5a0ce3fbcd7de539c?branch=epel10
Log:
Merge rawhide — add rpminspect.yaml
---
diff --git a/rpminspect.yaml b/rpminspect.yaml
new file mode 100644
index 0000000..5a2de30
--- /dev/null
+++ b/rpminspect.yaml
@@ -0,0 +1,7 @@
+---
+# The cpuid inline assembly in libhavege.so triggers an annocheck
+# "optimization level too low" false positive that has been present
+# since the library was first packaged. Waive the entire annocheck
+# inspection until upstream removes the bundled cpuid header.
+inspections:
+ annocheck: off
diff --git a/haveged.spec b/haveged.spec
index 14e4296..2054789 100644
--- a/haveged.spec
+++ b/haveged.spec
@@ -125,35 +125,8 @@ cp -p COPYING README ChangeLog AUTHORS contrib/build/havege_sample.c %{buildroot
- Fix semaphore error handling (SEM_FAILED vs NULL)
- Fix /dev/shm permissions (use 01777 with sticky bit)
-* Fri Jan 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 1.9.18-11
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
-
-* Thu Jul 24 2025 Fedora Release Engineering <releng@fedoraproject.org> - 1.9.18-10
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild
-
-* Fri Jan 17 2025 Fedora Release Engineering <releng@fedoraproject.org> - 1.9.18-9
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
-
-* Thu Jul 25 2024 Miroslav Suchý <msuchy@redhat.com> - 1.9.18-8
-- convert license to SPDX
-
-* Thu Jul 18 2024 Fedora Release Engineering <releng@fedoraproject.org> - 1.9.18-7
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild
-
-* Wed Jan 24 2024 Fedora Release Engineering <releng@fedoraproject.org> - 1.9.18-6
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
-
-* Sat Jan 20 2024 Fedora Release Engineering <releng@fedoraproject.org> - 1.9.18-5
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild
-
-* Thu Jul 20 2023 Fedora Release Engineering <releng@fedoraproject.org> - 1.9.18-4
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
-
-* Thu Jan 19 2023 Fedora Release Engineering <releng@fedoraproject.org> - 1.9.18-3
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
-
-* Thu Jul 21 2022 Fedora Release Engineering <releng@fedoraproject.org> - 1.9.18-2
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
+* Mon Jun 16 2025 Jirka Hladky <hladky.jiri@gmail.com> - 1.9.18-1
+- Initial build for EPEL 10
* Sat Apr 09 2022 Jirka Hladky <hladky.jiri@gmail.com> - 1.9.18-1
- Update to 1.9.18
reply other threads:[~2026-06-18 2:09 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=178174856341.1.12353842539765952766.rpms-haveged-478987ed8a1a@fedoraproject.org \
--to=jhladky@redhat.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