public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Fedora Release Engineering <releng@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/python-azure-keyvault-secrets] epel10: Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
Date: Mon, 01 Jun 2026 12:55:31 GMT [thread overview]
Message-ID: <178031853104.1.18284099051505860277.rpms-python-azure-keyvault-secrets-5421e0afe406@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-azure-keyvault-secrets
Branch : epel10
Commit : 5421e0afe406fec6f5ac6c2f26ac358909d6f5c1
Author : Fedora Release Engineering <releng@fedoraproject.org>
Date : 2023-01-20T11:28:09+00:00
Stats : +4/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-azure-keyvault-secrets/c/5421e0afe406fec6f5ac6c2f26ac358909d6f5c1?branch=epel10
Log:
Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
Signed-off-by: Fedora Release Engineering <releng@fedoraproject.org>
---
diff --git a/python-azure-keyvault-secrets.spec b/python-azure-keyvault-secrets.spec
index 611e75e..f0e4dde 100644
--- a/python-azure-keyvault-secrets.spec
+++ b/python-azure-keyvault-secrets.spec
@@ -2,7 +2,7 @@
Name: python-%{srcname}
Version: 4.3.0
-Release: 7%{?dist}
+Release: 8%{?dist}
Summary: Microsoft Azure Key Vault Secrets Client Library for Python
License: MIT
URL: https://pypi.org/project/%{srcname}/
@@ -50,6 +50,9 @@ Obsoletes: python3-azure-sdk < 5.0.1
%changelog
+* Fri Jan 20 2023 Fedora Release Engineering <releng@fedoraproject.org> - 4.3.0-8
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
+
* Fri Jul 22 2022 Fedora Release Engineering <releng@fedoraproject.org> - 4.3.0-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
reply other threads:[~2026-06-01 12:55 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=178031853104.1.18284099051505860277.rpms-python-azure-keyvault-secrets-5421e0afe406@fedoraproject.org \
--to=releng@fedoraproject.org \
--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