From: "Andrew Ammerlaan" <andrewammerlaan@riseup.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/spotipy/
Date: Thu, 19 Mar 2020 08:10:42 +0000 (UTC) [thread overview]
Message-ID: <1584605415.d8c71fadc8f1ac53ea86c4322eb84177a2eef983.andrewammerlaan@gentoo> (raw)
commit: d8c71fadc8f1ac53ea86c4322eb84177a2eef983
Author: Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
AuthorDate: Thu Mar 19 08:10:15 2020 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> riseup <DOT> net>
CommitDate: Thu Mar 19 08:10:15 2020 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=d8c71fad
dev-python/spotipy: version bump 2.10.0
Package-Manager: Portage-2.3.94, Repoman-2.3.21
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> riseup.net>
dev-python/spotipy/Manifest | 2 +-
dev-python/spotipy/{spotipy-2.9.0.ebuild => spotipy-2.10.0.ebuild} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/spotipy/Manifest b/dev-python/spotipy/Manifest
index d1e2b17..7b13792 100644
--- a/dev-python/spotipy/Manifest
+++ b/dev-python/spotipy/Manifest
@@ -1 +1 @@
-DIST spotipy-2.9.0.tar.gz 81689 BLAKE2B 909e615c4dad90571c7aa4c1ce4512effffab34505b1193eca8694290fa937143bc4e90d69779f4e899fe0556626591078fcbc175c8d52427553de1b0dbcdd0e SHA512 ebfe8e4b31cb741fe5ddd5fae52d269e6e311d04aa6edc9d727d56bc32963b253db22ae3b43b0db10d1c55bd045439b0e74e0cfefab386e895730ac5cd10b110
+DIST spotipy-2.10.0.tar.gz 82414 BLAKE2B 06915b6e910ab69853ee8e54503da050733e138dc27fbb3c27049c2277231c97659fcbc3f3205aa252f89b738f5863851751de253efce970f31617046a6e8de5 SHA512 00e9a05ce4321c889a4586ae504b4399753701a6fc08ecc4775099b74d82087551c81329242c395ff9d0497f45c9aa4c9a261132295117be310cd6f33ca1811a
diff --git a/dev-python/spotipy/spotipy-2.9.0.ebuild b/dev-python/spotipy/spotipy-2.10.0.ebuild
similarity index 100%
rename from dev-python/spotipy/spotipy-2.9.0.ebuild
rename to dev-python/spotipy/spotipy-2.10.0.ebuild
next reply other threads:[~2020-03-19 8:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 8:10 Andrew Ammerlaan [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-05 13:16 [gentoo-commits] repo/proj/guru:dev commit in: dev-python/spotipy/ Maciej Barć
2022-02-07 9:52 Nicola Smaniotto
2021-05-24 11:06 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-05-24 10:01 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2021-02-28 17:35 Andrew Ammerlaan
2020-11-04 9:57 Andrew Ammerlaan
2020-09-16 20:30 Andrew Ammerlaan
2020-09-08 10:30 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-09-08 10:30 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-08-29 14:14 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-08-29 14:14 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-08-14 18:20 Andrew Ammerlaan
2020-06-26 8:23 Andrew Ammerlaan
2020-06-09 16:27 Andrew Ammerlaan
2020-04-27 7:10 Andrew Ammerlaan
2020-04-20 9:48 Andrew Ammerlaan
2020-04-11 20:34 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2020-04-11 19:23 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2020-02-15 21:19 Andrew Ammerlaan
2020-02-13 10:21 Andrew Ammerlaan
2020-02-10 14:19 Andrew Ammerlaan
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=1584605415.d8c71fadc8f1ac53ea86c4322eb84177a2eef983.andrewammerlaan@gentoo \
--to=andrewammerlaan@riseup.net \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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