public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowi@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/fence-agents] eln: Update requirements-google.txt
Date: Wed, 15 Jul 2026 20:33:25 GMT [thread overview]
Message-ID: <178414760512.1.2915907243273065377.rpms-fence-agents-6c439ee36a3a@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/fence-agents
Branch : eln
Commit : 6c439ee36a3ad50cb244980208f733a80c681f85
Author : Yaakov Selkowitz <yselkowi@redhat.com>
Date : 2026-07-15T16:33:12-04:00
Stats : +1/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/fence-agents/c/6c439ee36a3ad50cb244980208f733a80c681f85?branch=eln
Log:
Update requirements-google.txt
---
diff --git a/sources b/sources
index 5c5612d..faa9992 100644
--- a/sources
+++ b/sources
@@ -3,7 +3,7 @@ SHA512 (requirements-common.txt) = 27efb8655b5cb949ddbdaa1ef8bb0787349ad3173ae46
SHA512 (requirements-aliyun.txt) = 74ae6b3f7bb0c25b532f606d7dea3cf4e3a0d1c1abdce78d01e2ab8e81c9f346162142679bad884b2fa110d4d6a8c4692b678017eb1fc7d092907c0c063b1c79
SHA512 (requirements-aws.txt) = ca39604d09f4b05589ddaa437be13b7f5d1868218745df107564d73a6c32efb7e4761436197a69653edc47a78f40dd7d5f0894935ec21b8f23b7c7bc71dfd0d1
SHA512 (requirements-azure.txt) = 8071c96bb3e2b82852b10fd68b77b69a7fce6153ab315298ceb07456fe66f3aca056d3273f11eb87ff30049759e8b4fddf62e39acb91953d36e933e44dce8c9b
-SHA512 (requirements-google.txt) = b71ef76f6f976b890666f264cbbb37909431d5c49b28aac5ec4abc19f11546e132051f8936561a94eb6b3790e23a07daf8aaf1eb46d147f36b56f0457d0abe59
+SHA512 (requirements-google.txt) = 160b7f78eb71968ed96326502b77a5fd24d90b4d10aab738212c3daf702541d5495c8f1ed6c631a315c45d697658349dab122faa6d546695aa29aedb4b66c1b2
SHA512 (pycurl-7.45.6.tar.gz) = 4eb53cbb3c8801950c76adb920b30919ca9f70e3f93dcef898d048244c475ec4a135590d173398efeb7642be33c11cb1742cb2519713088223870141e0cef8b3
SHA512 (suds_community-1.2.0.tar.gz) = 8955ad288fbd9d472b8aa4b4a016da66616436bb41b44d7935f4c14ae897c127e0d6c14457f2303ead671f92edc51454701c9658aec32f6af44882526ed86aeb
SHA512 (python-dateutil-2.9.0.post0.tar.gz) = f76522de0ff21547327eaf6966e80a15c57f8f92588d520eabd354a732e5c4b51d9c3ac5effd9eaa6dd451d1bce329a54a3f4c6bf4f1bd08ff06b0305c994e5a
reply other threads:[~2026-07-15 20:33 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=178414760512.1.2915907243273065377.rpms-fence-agents-6c439ee36a3a@fedoraproject.org \
--to=yselkowi@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