public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Troy Dawson <tdawson@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/kf5-kfilemetadata] epel9-next: Merge branch epel9-next into epel9
Date: Mon, 20 Jul 2026 17:57:23 GMT [thread overview]
Message-ID: <178457024314.1.7549053632580345472.rpms-kf5-kfilemetadata-dd6c237e0bae@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/kf5-kfilemetadata
Branch : epel9-next
Commit : dd6c237e0baec4ddf9a13d2262224919639971ba
Author : Troy Dawson <tdawson@redhat.com>
Date : 2023-10-20T12:50:12-07:00
Stats : +14/-2 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/kf5-kfilemetadata/c/dd6c237e0baec4ddf9a13d2262224919639971ba?branch=epel9-next
Log:
Merge branch epel9-next into epel9
---
diff --git a/.gitignore b/.gitignore
index 3645da3..5655382 100644
--- a/.gitignore
+++ b/.gitignore
@@ -56,3 +56,6 @@
/kfilemetadata-5.103.0.tar.xz
/kfilemetadata-5.104.0.tar.xz
/kfilemetadata-5.105.0.tar.xz
+/kfilemetadata-5.106.0.tar.xz
+/kfilemetadata-5.107.0.tar.xz
+/kfilemetadata-5.108.0.tar.xz
diff --git a/kf5-kfilemetadata.spec b/kf5-kfilemetadata.spec
index 8829ec9..3801dae 100644
--- a/kf5-kfilemetadata.spec
+++ b/kf5-kfilemetadata.spec
@@ -18,7 +18,7 @@
Name: kf5-%{framework}
Summary: A Tier 2 KDE Framework for extracting file metadata
-Version: 5.105.0
+Version: 5.108.0
Release: 1%{?dist}
# # KDE e.V. may determine that future LGPL versions are accepted
@@ -116,6 +116,15 @@ mkdir -p %{buildroot}%{_kf5_plugindir}/kfilemetadata/writers/
%changelog
+* Sun Jul 02 2023 Marc Deop i Argemí <marcdeop@fedoraproject.org> - 5.108.0-1
+- 5.108.0
+
+* Sat Jun 03 2023 Marc Deop i Argemí <marcdeop@fedoraproject.org> - 5.107.0-1
+- 5.107.0
+
+* Mon May 15 2023 Marc Deop i Argemí <marcdeop@fedoraproject.org> - 5.106.0-1
+- 5.106.0
+
* Sun Apr 02 2023 Marc Deop i Argemí <marcdeop@fedoraproject.org> - 5.105.0-1
- 5.105.0
diff --git a/sources b/sources
index ae749f3..f759aca 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (kfilemetadata-5.105.0.tar.xz) = 9ff836a857b6a670a0cdac6080b4598715d2f9270ea3a90c587c93943cc72c8984a2d933daeb909971a93c74b0409af1ab46ab8c2070e3475f54bc7c110c8fab
+SHA512 (kfilemetadata-5.108.0.tar.xz) = f1a8d20ae91809f736d0355a3fafb9be0e77482b8c7fd6a5ff66f0f6937f4ad61c26841d9bcee2574fdb55f6dcfc1670ec26fef70f3f2a0613ba6a30a7826489
next reply other threads:[~2026-07-20 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 17:57 Troy Dawson [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-20 17:57 [rpms/kf5-kfilemetadata] epel9-next: Merge branch epel9-next into epel9 Troy Dawson
2026-07-20 17:57 Troy Dawson
2026-07-20 17:57 Troy Dawson
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=178457024314.1.7549053632580345472.rpms-kf5-kfilemetadata-dd6c237e0bae@fedoraproject.org \
--to=tdawson@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