public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Packit <hello@packit.dev>
To: git-commits@fedoraproject.org
Subject: [rpms/fedora-messaging] epel10.2: Update to 3.7.1 upstream release
Date: Thu, 13 Aug 2026 09:30:42 GMT [thread overview]
Message-ID: <178661344224.1.3102596189324580974.rpms-fedora-messaging-cb1bb02ceee1@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/fedora-messaging
Branch : epel10.2
Commit : cb1bb02ceee117e78ade101a2e4cded4380c42a7
Author : Packit <hello@packit.dev>
Date : 2025-04-22T14:04:43+02:00
Stats : +11/-7 in 4 file(s)
URL : https://src.fedoraproject.org/rpms/fedora-messaging/c/cb1bb02ceee117e78ade101a2e4cded4380c42a7?branch=epel10.2
Log:
Update to 3.7.1 upstream release
Upstream tag: v3.7.1
Upstream commit: b42b4b66
Commit authored by Packit automation (https://packit.dev/)
---
diff --git a/.gitignore b/.gitignore
index 633fb62..22adb87 100644
--- a/.gitignore
+++ b/.gitignore
@@ -23,3 +23,4 @@
/fedora_messaging-3.4.1.tar.gz
/fedora_messaging-3.5.0.tar.gz
/fedora_messaging-3.7.0.tar.gz
+/fedora_messaging-3.7.1.tar.gz
diff --git a/README.packit b/README.packit
index 3826605..807ffc6 100644
--- a/README.packit
+++ b/README.packit
@@ -1,3 +1,3 @@
This repository is maintained by packit.
https://packit.dev/
-The file was generated using packit 0.106.0.
+The file was generated using packit 1.6.0.post1.dev2+gd5a7662a.
diff --git a/fedora-messaging.spec b/fedora-messaging.spec
index 9391a90..2ce7153 100644
--- a/fedora-messaging.spec
+++ b/fedora-messaging.spec
@@ -7,8 +7,8 @@
%global srcname fedora_messaging
Name: %{pkgname}
-Version: 3.7.0
-Release: 2%{?dist}
+Version: 3.7.1
+Release: 1%{?dist}
Summary: Set of tools for using Fedora's messaging infrastructure
# Automatically converted from old format: GPLv2+ - review is highly recommended.
@@ -97,7 +97,7 @@ install -D -p -m 644 docs/_build/man/fedora-messaging.1 $RPM_BUILD_ROOT%{_mandir
%files
-%license LICENSE
+%license LICENSES/GPL-2.0-or-later.txt
%doc README.rst
%dir %{_sysconfdir}/fedora-messaging/
%config(noreplace) %{_sysconfdir}/fedora-messaging/config.toml
@@ -116,16 +116,19 @@ install -D -p -m 644 docs/_build/man/fedora-messaging.1 $RPM_BUILD_ROOT%{_mandir
%endif
%files -n python%{python3_pkgversion}-%{pkgname} -f %{pyproject_files}
-%license LICENSE
+%license LICENSES/GPL-2.0-or-later.txt
%if ! 0%{?rhel}
%files doc
-%license LICENSE
+%license LICENSES/GPL-2.0-or-later.txt
%doc README.rst docs/*.rst docs/_build/html docs/sample_schema_package
%endif
%changelog
+* Tue Apr 22 2025 Packit <hello@packit.dev> - 3.7.1-1
+- Update to version 3.7.1
+
* Thu Jan 16 2025 Fedora Release Engineering <releng@fedoraproject.org> - 3.7.0-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
diff --git a/sources b/sources
index c8d47ee..04354ac 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (fedora_messaging-3.7.0.tar.gz) = 3d385a754afc33da058375f2bb74b0550a4c13e4de1359c9f1f07c37b74ffdfc1f576aa1d2d3ff2e01fc96cf9a2b6f4c08e9353e8769ca5509c1a99a6db93fdb
+SHA512 (fedora_messaging-3.7.1.tar.gz) = fa5c7c802947929dd217004842a24112910e88f70a976bec07ea06367a2d0ee04df419de6b0ac704683b6c65d9ba4eac7e1c3af1f78179a07fc5d742a3886727
reply other threads:[~2026-08-13 9:30 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=178661344224.1.3102596189324580974.rpms-fedora-messaging-cb1bb02ceee1@fedoraproject.org \
--to=hello@packit.dev \
--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