public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jiri Kyjovsky <j1.kyjovsky@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-copr-common] epel8: Update python-copr-common to 1.9-1
Date: Tue, 22 Sep 2026 15:39:23 GMT [thread overview]
Message-ID: <179009156340.1.14490560351678902826.rpms-python-copr-common-013cfc7d57d9@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-copr-common
Branch : epel8
Commit : 013cfc7d57d99bab81911baab13c1ac4c1941820
Author : Jiri Kyjovsky <j1.kyjovsky@gmail.com>
Date : 2026-09-22T17:38:31+02:00
Stats : +5/-2 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/python-copr-common/c/013cfc7d57d99bab81911baab13c1ac4c1941820?branch=epel8
Log:
Update python-copr-common to 1.9-1
---
diff --git a/python-copr-common.spec b/python-copr-common.spec
index 52df965..20d864b 100644
--- a/python-copr-common.spec
+++ b/python-copr-common.spec
@@ -1,7 +1,7 @@
%global srcname copr-common
Name: python-copr-common
-Version: 1.8
+Version: 1.9
Release: 1%{?dist}
Summary: Python code used by Copr
@@ -80,6 +80,9 @@ version=%version %py3_install
%changelog
+* Tue Sep 22 2026 Jiri Kyjovsky <j1.kyjovsky@gmail.com> 1.9-1
+- uploadrpm: multiple RPMs, optional srpm/logs
+
* Wed Aug 12 2026 Jakub Kadlcik <frostyx@email.cz> 1.8-1
- Add direct RPM upload build type
- Efactor lock() function into Lock class
diff --git a/sources b/sources
index e54dc3f..5c6b8b4 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (python-copr-common-1.8.tar.gz) = ea7fd72a8928601b6a92e917879d17262320ec534e253716dac71ef39a46f4569eeed38e3b84d35785cd9d10780b8995c1adc64d78195202ff88743396377aa1
+SHA512 (python-copr-common-1.9.tar.gz) = 5e4aef5b69a3a453330b8ad73925600a7c16f06da436bdda634ed9b3666b998bff46a00d6e3d59a88d4c1c3da97ecfc610eed251ff0866516660992d3a390f7b
reply other threads:[~2026-09-22 15:39 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=179009156340.1.14490560351678902826.rpms-python-copr-common-013cfc7d57d9@fedoraproject.org \
--to=j1.kyjovsky@gmail.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