public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matt Thode" <prometheanfire@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/keystoneauth/
Date: Fri, 16 Feb 2018 06:08:11 +0000 (UTC)	[thread overview]
Message-ID: <1518752196.1665c1bc276c6c5cae9c4f38e55a4dff003eedcd.prometheanfire@gentoo> (raw)

commit:     1665c1bc276c6c5cae9c4f38e55a4dff003eedcd
Author:     Matthew Thode <prometheanfire <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 16 03:36:36 2018 +0000
Commit:     Matt Thode <prometheanfire <AT> gentoo <DOT> org>
CommitDate: Fri Feb 16 03:36:36 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1665c1bc

dev-python/keystoneauth: 3.4.0 bup

Package-Manager: Portage-2.3.19, Repoman-2.3.6

 dev-python/keystoneauth/Manifest                  |  1 +
 dev-python/keystoneauth/keystoneauth-3.4.0.ebuild | 27 +++++++++++++++++++++++
 2 files changed, 28 insertions(+)

diff --git a/dev-python/keystoneauth/Manifest b/dev-python/keystoneauth/Manifest
index 5a3ce513131..5bd6870f65b 100644
--- a/dev-python/keystoneauth/Manifest
+++ b/dev-python/keystoneauth/Manifest
@@ -4,3 +4,4 @@ DIST keystoneauth1-2.20.0.tar.gz 187746 BLAKE2B c47608115ce31bac39d7f410c9153feb
 DIST keystoneauth1-2.4.1.tar.gz 150586 BLAKE2B 78d3b5c99bf1d11573a7aba317aca669caee9b5a843eb7d25e3a51e315398617530c5beb9e067500d06922024cb9b5705cff1e9c9f25328e68d0e8155df26971 SHA512 f9e8fcea7b23001b907d643d5bf67fc4779c8729cca213b3240ef988eda9de1212b15c2031f6fd8b431aafac85e773346eda71e0b414fe967728611b6817fb05
 DIST keystoneauth1-2.4.2.tar.gz 151213 BLAKE2B aacdee83231982e919925aef9d305d517a00a4db323d407176296d8349d5afe01229429a00949ee2fc6adb49f655de840c90c1ab7d8b5dc5420a67f869522241 SHA512 dd3b0907c554606489081b970ad248efe52aa6593cb8584ac1d4e3b05075b6a60b8c5f159c00f5668eb0938dbed655e7135ac9b7d3d6017f2f280f69b9080122
 DIST keystoneauth1-3.1.0.tar.gz 217744 BLAKE2B 4e07c7f4dd6fc097c6838b2a18105656b16f8e45dd553d2908c55fa7aeb5c8dcd2968ca0c3954be0b66044880eec7c33fd9c42413a1ae6c93258a902666bb896 SHA512 3214e08cf449a0eff35eff0400542cbb9e46051095d7955593fec89c4ba31062677f434c70c40037db213fa0e0db15c66d1058e0eca35b1d214967f7fa3fcf14
+DIST keystoneauth1-3.4.0.tar.gz 227170 BLAKE2B 57f28ce5a36362f34fcfb2f456a19332df6851a4d372fe890286b4d48469ff69a3ad7281b55d4aa338f61d437f5e07908fc55210e2085a6d9a974cf0bf451c81 SHA512 aeaefb0e5b369e36e06adc1bada104dab2c2aed22bf96cc3e20a5dd4ce8ae10869eb73ce4802faef70f191c3bbd38e3b5c3dff3606c46956fb350c0875cb7a7d

diff --git a/dev-python/keystoneauth/keystoneauth-3.4.0.ebuild b/dev-python/keystoneauth/keystoneauth-3.4.0.ebuild
new file mode 100644
index 00000000000..e636a0e9f38
--- /dev/null
+++ b/dev-python/keystoneauth/keystoneauth-3.4.0.ebuild
@@ -0,0 +1,27 @@
+# Copyright 1999-2018 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+PYTHON_COMPAT=( python2_7 python3_4 python3_5 python3_6 )
+
+inherit distutils-r1
+
+DESCRIPTION="This package contains tools for authenticating to an OpenStack-based cloud."
+HOMEPAGE="https://github.com/openstack/keystoneauth"
+SRC_URI="mirror://pypi/${PN:0:1}/${PN}1/${PN}1-${PV}.tar.gz"
+S="${WORKDIR}/${PN}1-${PV}"
+
+LICENSE="Apache-2.0"
+SLOT="0"
+KEYWORDS="~amd64 ~arm64 ~x86"
+IUSE=""
+
+CDEPEND=">=dev-python/pbr-2.0.0[${PYTHON_USEDEP}]
+	!~dev-python/pbr-2.1.0"
+DEPEND="dev-python/setuptools[${PYTHON_USEDEP}]
+	${CDEPEND}"
+RDEPEND="${CDEPEND}
+	>=dev-python/iso8601-0.1.11[${PYTHON_USEDEP}]
+	>=dev-python/requests-2.14.2[${PYTHON_USEDEP}]
+	>=dev-python/six-1.10.0[${PYTHON_USEDEP}]
+	>=dev-python/stevedore-1.20.0[${PYTHON_USEDEP}]"


             reply	other threads:[~2018-02-16  6:08 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16  6:08 Matt Thode [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-14 16:24 [gentoo-commits] repo/gentoo:master commit in: dev-python/keystoneauth/ Michał Górny
2023-01-04 14:15 Michał Górny
2022-12-25 17:45 Michał Górny
2022-12-25 16:42 Sam James
2022-11-25  5:14 Michał Górny
2022-11-12 11:59 Arthur Zamarin
2022-08-17 19:31 Arthur Zamarin
2022-08-17 18:52 Arthur Zamarin
2022-07-15 18:30 Arthur Zamarin
2022-06-28 19:42 Michał Górny
2022-06-28 19:30 Arthur Zamarin
2022-05-28 21:12 Jakov Smolić
2022-05-21  6:47 Michał Górny
2022-04-01 18:45 Michał Górny
2022-04-01 17:33 Arthur Zamarin
2022-04-01 17:33 Arthur Zamarin
2022-04-01 17:32 Arthur Zamarin
2022-03-09 18:26 Arthur Zamarin
2022-02-24 18:08 Michał Górny
2021-12-17  9:15 Michał Górny
2021-10-24  5:13 Arthur Zamarin
2021-10-24  1:15 Sam James
2021-09-17 22:22 Michał Górny
2021-07-07  6:33 Michał Górny
2021-07-07  2:17 Sam James
2021-06-26  2:55 Sam James
2021-06-24 23:57 Sam James
2021-06-23 10:13 Michał Górny
2021-06-23 10:09 Michał Górny
2021-06-23 10:09 Michał Górny
2020-11-16  0:02 Michał Górny
2020-11-15 23:50 Sam James
2020-11-14 21:52 Michał Górny
2020-10-10 23:09 Matthew Thode
2020-10-10 20:34 Matthew Thode
2020-07-18 22:30 Matthew Thode
2020-07-17  1:52 Sam James
2020-07-01 16:27 Matthew Thode
2020-06-20 19:23 Matthew Thode
2020-05-30 17:52 Matthew Thode
2020-05-16 21:21 Matthew Thode
2020-03-25 16:17 Matthew Thode
2020-03-25 16:17 Matthew Thode
2020-02-25 17:52 Matthew Thode
2020-02-25 16:48 Matthew Thode
2019-11-19 18:36 Matthew Thode
2019-10-21  0:19 Matthew Thode
2019-05-11 18:17 Matthew Thode
2019-04-09  7:06 Matthew Thode
2018-08-30 21:34 Matt Thode
2018-02-16  6:08 Matt Thode
2017-08-28  0:47 Matt Thode
2017-08-28  0:47 Matt Thode
2017-06-04  7:30 Justin Lecher
2017-03-13  1:30 Zac Medico
2017-02-27  2:16 Matt Thode
2017-02-24 17:39 Matt Thode
2017-02-24 17:39 Matt Thode
2017-01-31 15:45 Matt Thode
2016-11-17 18:40 Matt Thode
2016-10-19  4:09 Matt Thode
2016-05-24 23:16 Matt Thode
2016-03-29 18:31 Matt Thode
2016-03-29 18:31 Matt Thode
2016-03-28  2:40 Matt Thode
2016-03-25  5:02 Matt Thode

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=1518752196.1665c1bc276c6c5cae9c4f38e55a4dff003eedcd.prometheanfire@gentoo \
    --to=prometheanfire@gentoo.org \
    --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