public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ali Erdinc Koroglu <ali.koroglu@oss.qualcomm.com>
To: git-commits@fedoraproject.org
Subject: [rpms/libnitrokey] rawhide: Update to 3.8 (rhbz#2504287)
Date: Sat, 01 Aug 2026 18:53:10 GMT [thread overview]
Message-ID: <178561039071.1.15986330107220290526.rpms-libnitrokey-840937fe7021@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/libnitrokey
Branch : rawhide
Commit : 840937fe702186dd6973812baefef592218d6d76
Author : Ali Erdinc Koroglu <ali.koroglu@oss.qualcomm.com>
Date : 2026-08-01T21:52:53+03:00
Stats : +12/-5 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/libnitrokey/c/840937fe702186dd6973812baefef592218d6d76?branch=rawhide
Log:
Update to 3.8 (rhbz#2504287)
---
diff --git a/libnitrokey.spec b/libnitrokey.spec
index 27366f8..0b07c99 100644
--- a/libnitrokey.spec
+++ b/libnitrokey.spec
@@ -1,6 +1,6 @@
Name: libnitrokey
-Version: 3.7
-Release: 11%{?dist}
+Version: 3.8
+Release: 1%{?dist}
Summary: Communicate with Nitrokey stick devices in a clean and easy manner
License: LGPL-3.0-or-later
@@ -28,12 +28,16 @@ to develop using libnitrokey.
%autosetup
%build
-%cmake
+%cmake \
+ -DCMAKE_POLICY_VERSION_MINIMUM="3.5.0"
%cmake_build
%install
%cmake_install
+%check
+%ctest
+
%post
%udev_rules_update
@@ -44,7 +48,7 @@ to develop using libnitrokey.
%license LICENSE
%doc README.md
%{_libdir}/libnitrokey.so.*
-%{_udevrulesdir}/*-nitrokey.rules
+%{_udevrulesdir}/41-nitrokey.rules
%files devel
%{_libdir}/libnitrokey.so
@@ -52,6 +56,9 @@ to develop using libnitrokey.
%{_includedir}/libnitrokey/
%changelog
+* Sat Aug 01 2026 Ali Erdinc Koroglu <aekoroglu@fedoraproject.org> - 3.8-1
+- Update to 3.8 (rhbz#2504287)
+
* Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 3.7-11
- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
diff --git a/sources b/sources
index 6d045bf..35d6887 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (libnitrokey-3.7.tar.gz) = 000fb9addc59eff0346e61716de0948ab16415db39885349ba23f3e267623ec57175c63a127c8b3b51f0b2676e698ecfc7595e0b86a2eddf09f5934ab39a51a8
+SHA512 (libnitrokey-3.8.tar.gz) = 30f966eed77aa75057b096d18f8e88d6be28a376dfc1888e44aff80347e031a16755d30acf1bca196acc5b922778d90627ac71cba22f5cb002ba3ec058939c90
reply other threads:[~2026-08-01 18:53 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=178561039071.1.15986330107220290526.rpms-libnitrokey-840937fe7021@fedoraproject.org \
--to=ali.koroglu@oss.qualcomm.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