public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/uranium/
Date: Tue, 25 May 2021 11:55:00 +0000 (UTC)	[thread overview]
Message-ID: <1621943687.65b9df2e535a6476e6685a7674ca2d388becf3b8.sam@gentoo> (raw)

commit:     65b9df2e535a6476e6685a7674ca2d388becf3b8
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue May 25 11:51:51 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue May 25 11:54:47 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=65b9df2e

dev-python/uranium: add dev-python/cryptography dependency

Closes: https://bugs.gentoo.org/783465
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-python/uranium/{uranium-4.8.0.ebuild => uranium-4.8.0-r1.ebuild} | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/dev-python/uranium/uranium-4.8.0.ebuild b/dev-python/uranium/uranium-4.8.0-r1.ebuild
similarity index 96%
rename from dev-python/uranium/uranium-4.8.0.ebuild
rename to dev-python/uranium/uranium-4.8.0-r1.ebuild
index ec44ffc1c0b..d2fbe4c6054 100644
--- a/dev-python/uranium/uranium-4.8.0.ebuild
+++ b/dev-python/uranium/uranium-4.8.0-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2020 Gentoo Authors
+# Copyright 1999-2021 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=7
@@ -32,6 +32,7 @@ BDEPEND="${PYTHON_DEPS}
 DEPEND="${PYTHON_DEPS}
 	~dev-libs/libarcus-${PV}:=[python,${PYTHON_SINGLE_USEDEP}]
 	$(python_gen_cond_dep '
+		dev-python/cryptography[${PYTHON_USEDEP}]
 		dev-python/PyQt5[${PYTHON_USEDEP},declarative,network,svg]
 		dev-python/numpy[${PYTHON_USEDEP}]
 		>=dev-python/scipy-1.1[${PYTHON_USEDEP}]


             reply	other threads:[~2021-05-25 11:55 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 11:55 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-09 10:52 [gentoo-commits] repo/gentoo:master commit in: dev-python/uranium/ Matthew Smith
2022-05-09  7:00 Michał Górny
2022-04-07 20:58 Jakov Smolić
2022-03-10 21:21 Jakov Smolić
2022-03-05 16:15 Matthew Smith
2022-02-28 19:43 Matthew Smith
2022-02-10 17:35 Marek Szuba
2021-11-02  8:38 Arthur Zamarin
2021-06-14 17:02 Dennis Lamm
2021-06-10 17:41 Dennis Lamm
2021-02-07 23:57 Dennis Lamm
2021-02-07 23:57 Dennis Lamm
2021-02-07 21:30 Dennis Lamm
2020-11-30 18:37 Dennis Lamm
2020-10-07  0:59 Sam James
2020-09-19 16:34 Sam James
2020-09-18 15:53 Michał Górny
2020-09-12 20:24 Dennis Lamm
2020-03-29 10:30 Michał Górny
2020-02-09 16:18 Michał Górny
2019-10-16  5:22 Joonas Niilola
2019-08-25 17:59 Joonas Niilola
2019-04-30 12:46 Michael Palimaka
2019-01-03 17:28 Amy Liffey
2019-01-02 22:05 Amy Liffey
2019-01-02 21:52 Amy Liffey
2018-12-22 19:28 Davide Pesavento
2018-12-16 11:04 Andreas Sturmlechner
2018-11-18 17:19 Amy Liffey
2018-07-16 17:29 Amy Liffey
2018-06-14 20:14 Alexey Shvetsov
2018-04-03 15:28 Jonas Stein
2018-01-06 13:39 Michał Górny
2017-11-25 21:44 David Seifert
2017-07-23 11:05 Alexey Shvetsov
2017-05-22 14:43 Michał Górny
2016-05-22 17:05 Göktürk Yüksek
2016-05-14  9:47 Patrice Clement
2016-04-29  5:46 Ian Delaney

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=1621943687.65b9df2e535a6476e6685a7674ca2d388becf3b8.sam@gentoo \
    --to=sam@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