public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/fido2/
Date: Fri, 18 May 2018 23:19:47 +0000 (UTC)	[thread overview]
Message-ID: <1526685566.34e75a68871fafd25322b36abc43fe75e6ca8517.gokturk@gentoo> (raw)

commit:     34e75a68871fafd25322b36abc43fe75e6ca8517
Author:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
AuthorDate: Fri May 18 22:47:17 2018 +0000
Commit:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Fri May 18 23:19:26 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=34e75a68

dev-python/fido2: initial commit with version 0.3.0

This is a dependency for >=app-crypt/yubikey-manager-0.7.0.

Package-Manager: Portage-2.3.27, Repoman-2.3.9

 dev-python/fido2/Manifest           |  1 +
 dev-python/fido2/fido2-0.3.0.ebuild | 35 +++++++++++++++++++++++++++++++++++
 dev-python/fido2/metadata.xml       | 16 ++++++++++++++++
 3 files changed, 52 insertions(+)

diff --git a/dev-python/fido2/Manifest b/dev-python/fido2/Manifest
new file mode 100644
index 00000000000..ef3b3d41a76
--- /dev/null
+++ b/dev-python/fido2/Manifest
@@ -0,0 +1 @@
+DIST fido2-0.3.0.tar.gz 125907 BLAKE2B 95054f258c775ac3b4f65608fd3b62ec4165a568c237064ebb66da1ca6ae899a3d88b5613e9dd4be87c05068ebd698be452dd3467800317e5894092216196e12 SHA512 c6ea83e104d77350413156eba4c1aa2635b77ae00d157dce61e5a8539c65aca4dd1dfc5303f9d408359582eeb98ae558aa1e2043a9b1dfcb23415eb8bc9c6a09

diff --git a/dev-python/fido2/fido2-0.3.0.ebuild b/dev-python/fido2/fido2-0.3.0.ebuild
new file mode 100644
index 00000000000..80c22c109c0
--- /dev/null
+++ b/dev-python/fido2/fido2-0.3.0.ebuild
@@ -0,0 +1,35 @@
+# Copyright 1999-2018 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+
+PYTHON_COMPAT=( python{2_7,3_{4,5,6}} )
+inherit distutils-r1
+
+DESCRIPTION="Python based FIDO 2.0 library"
+HOMEPAGE="https://github.com/Yubico/python-fido2"
+SRC_URI="https://github.com/Yubico/python-fido2/releases/download/${PV}/${P}.tar.gz"
+
+LICENSE="Apache-2.0 BSD-2 MPL-2.0"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE="test"
+
+RDEPEND="
+	dev-python/six[${PYTHON_USEDEP}]
+	dev-python/cryptography[${PYTHON_USEDEP}]
+	$(python_gen_cond_dep 'dev-python/enum34[${PYTHON_USEDEP}]' python2_7)
+"
+DEPEND="
+	dev-python/setuptools[${PYTHON_USEDEP}]
+	test? (
+		${RDEPEND}
+		dev-python/mock[${PYTHON_USEDEP}]
+		dev-python/pyfakefs[${PYTHON_USEDEP}]
+	)
+"
+
+python_test() {
+	touch "${S}"/test/__init__.py || die
+	esetup.py test
+}

diff --git a/dev-python/fido2/metadata.xml b/dev-python/fido2/metadata.xml
new file mode 100644
index 00000000000..b0754694d80
--- /dev/null
+++ b/dev-python/fido2/metadata.xml
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+<maintainer type="person">
+  <email>gokturk@gentoo.org</email>
+  <name>Göktürk Yüksek</name>
+</maintainer>
+<longdescription>
+  fido2 provides library functionality for communicating with a FIDO
+  device over USB as well as verifying attestation and assertion
+  signatures.
+</longdescription>
+<upstream>
+  <remote-id type="github">Yubico/python-fido2</remote-id>
+</upstream>
+</pkgmetadata>


             reply	other threads:[~2018-05-18 23:19 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 23:19 Göktürk Yüksek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-07 22:47 [gentoo-commits] repo/gentoo:master commit in: dev-python/fido2/ Göktürk Yüksek
2019-01-24 20:18 Göktürk Yüksek
2019-03-11  8:40 Mikle Kolyada
2019-03-19 15:38 Rick Farina
2019-05-21 17:18 Göktürk Yüksek
2019-06-18 20:40 Göktürk Yüksek
2019-09-20 13:19 Göktürk Yüksek
2019-10-24 15:27 Göktürk Yüksek
2019-11-25 20:18 Göktürk Yüksek
2019-11-25 20:44 Göktürk Yüksek
2019-11-26 10:18 Thomas Deutschmann
2019-11-26 12:27 Agostino Sarubbo
2019-11-29  4:32 Göktürk Yüksek
2020-03-17  7:23 Michał Górny
2020-03-19  2:11 Rick Farina
2020-03-19  2:11 Rick Farina
2020-07-08 20:16 Michał Górny
2020-07-08 20:16 Michał Górny
2020-12-03 16:53 Marek Szuba
2021-02-15  2:19 Rick Farina
2021-03-14 19:55 Göktürk Yüksek
2021-03-14 19:55 Göktürk Yüksek
2021-04-18  1:41 Sam James
2021-05-27 15:37 Marek Szuba
2021-08-01 22:07 Marek Szuba
2021-08-10  0:22 Göktürk Yüksek
2021-09-13 16:26 Marek Szuba
2021-11-17 13:03 Marek Szuba
2021-11-17 13:03 Marek Szuba
2021-12-17 18:30 Jakov Smolić
2021-12-17 18:57 Michał Górny
2021-12-31  1:15 Georgy Yakovlev
2022-01-11  2:23 Georgy Yakovlev
2022-06-08 23:11 Marek Szuba
2022-06-20 15:40 Marek Szuba
2022-07-24 19:13 Sam James
2022-10-18  6:36 Michał Górny
2022-11-19 16:40 Sam James
2022-11-19 16:52 Michał Górny
2023-02-26 23:32 Marek Szuba
2023-04-06  3:07 Michał Górny
2023-05-01  0:09 Sam James
2023-05-01 17:14 Sam James
2023-05-02  3:14 Michał Górny
2023-07-07  3:15 Michał Górny
2023-08-19 15:51 Michał Górny
2023-08-23 23:37 Marek Szuba
2023-11-24 16:55 Sam James
2023-11-24 17:04 Arthur Zamarin
2024-03-09 11:25 Marek Szuba
2024-03-14 11:44 Michał Górny
2024-03-30 14:53 Michał Górny
2024-06-17 16:27 Michał Górny
2024-06-28 11:38 Michał Górny

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=1526685566.34e75a68871fafd25322b36abc43fe75e6ca8517.gokturk@gentoo \
    --to=gokturk@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