public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michele Baldessari <michele@acksyn.org>
To: git-commits@fedoraproject.org
Subject: [rpms/google-api-python-client] epel10: New upstream
Date: Tue, 21 Jul 2026 20:26:54 GMT	[thread overview]
Message-ID: <178466561478.1.16798782898764048867.rpms-google-api-python-client-35b4aa0aa9fa@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/google-api-python-client
Branch : epel10
Commit : 35b4aa0aa9fab4a69875e5071db5b939306fbd70
Author : Michele Baldessari <michele@acksyn.org>
Date   : 2017-10-23T11:48:46+02:00
Stats  : +8/-4 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/google-api-python-client/c/35b4aa0aa9fab4a69875e5071db5b939306fbd70?branch=epel10

Log:
New upstream

---
diff --git a/.gitignore b/.gitignore
index f60ddb9..50735ea 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@
 /google-api-python-client-1.5.5.tar.gz
 /google-api-python-client-1.6.2.tar.gz
 /google-api-python-client-1.6.3.tar.gz
+/google-api-python-client-1.6.4.tar.gz

diff --git a/google-api-python-client.spec b/google-api-python-client.spec
index fac0aa4..7816027 100644
--- a/google-api-python-client.spec
+++ b/google-api-python-client.spec
@@ -9,12 +9,12 @@
 
 Name:           google-api-python-client
 Summary:        %{sum}
-Version:        1.6.3
-Release:        2%{?dist}
+Version:        1.6.4
+Release:        1%{?dist}
 
 License:        ASL 2.0
 URL:            http://github.com/google/%{name}/
-Source0:        https://pypi.python.org/packages/16/00/a6913a2e6eb3d5b1cc3538c3492ccd2b39a6d79367432d46cea1ec74170d/%{name}-%{version}.tar.gz
+Source0:        https://pypi.python.org/packages/b4/b3/f9be3f2ec31491c8f74e5c7905fabe890dedb4e1e8db5c951df3c167be41/%{name}-%{version}.tar.gz
 BuildArch:      noarch
 
 %description 
@@ -116,6 +116,9 @@ done
 %{python3_sitelib}/google_api_python_client-%{version}-py?.?.egg-info
 
 %changelog
+* Mon Oct 23 2017 Michele Baldessari <michele@acksyn.org> - 1.6.4-1
+- New upstream
+
 * Sun Sep 10 2017 Nick Bebout <nb@fedoraproject.org> - 1.6.3-2
 - Fix BuildRequires/Requires to use python2-* for Fedora
 

diff --git a/sources b/sources
index 3ee85de..fe28882 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (google-api-python-client-1.6.3.tar.gz) = 0e1d7a6528df5a9720ca7299320b32e4be98baa8a5aee877c1f09f1f30a70e4df80ffa3d35df9c09233e49d96d1d91521dbaffb09b520339059ecd593ecc47c9
+SHA512 (google-api-python-client-1.6.4.tar.gz) = a3d623c1802c00564f9b8e73c54ff9566e4e2efeb0d87ea3c22999a12e2ee0ef6c3e47f3054e06d6bf461977e02499422159ebc577c6455c7e060bcc6b1666a1

             reply	other threads:[~2026-07-21 20:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 20:26 Michele Baldessari [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-21 20:26 [rpms/google-api-python-client] epel10: New upstream Michele Baldessari
2026-07-21 20:26 Michele Baldessari
2026-07-21 20:26 Michele Baldessari
2026-07-21 20:26 Michele Baldessari
2026-07-21 20:26 Michele Baldessari
2026-07-21 20:26 Michele Baldessari

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=178466561478.1.16798782898764048867.rpms-google-api-python-client-35b4aa0aa9fa@fedoraproject.org \
    --to=michele@acksyn.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