From: "Virgil Dupras" <vdupras@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/fabric/
Date: Fri, 27 Jul 2018 18:27:26 +0000 (UTC) [thread overview]
Message-ID: <1532715160.83d00a6d2dada40cad5133971079ea0a71984824.vdupras@gentoo> (raw)
commit: 83d00a6d2dada40cad5133971079ea0a71984824
Author: Virgil Dupras <vdupras <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 27 18:12:40 2018 +0000
Commit: Virgil Dupras <vdupras <AT> gentoo <DOT> org>
CommitDate: Fri Jul 27 18:12:40 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=83d00a6d
dev-python/fabric: add paramiko dep upper guard
Bug 623496 happened because we forgot that guard for v2.0. Let's not
repeat the mistake.
Package-Manager: Portage-2.3.43, Repoman-2.3.10
dev-python/fabric/fabric-1.14.0.ebuild | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/dev-python/fabric/fabric-1.14.0.ebuild b/dev-python/fabric/fabric-1.14.0.ebuild
index 4b345890112..2b202fef3ee 100644
--- a/dev-python/fabric/fabric-1.14.0.ebuild
+++ b/dev-python/fabric/fabric-1.14.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -24,7 +24,8 @@ KEYWORDS="~amd64 ~arm64 ~x86"
IUSE="doc test"
RDEPEND="
- >=dev-python/paramiko-1.10[${PYTHON_USEDEP}]"
+ >=dev-python/paramiko-1.10[${PYTHON_USEDEP}]
+ <dev-python/paramiko-3.0[${PYTHON_USEDEP}]"
DEPEND="${RDEPEND}
dev-python/setuptools[${PYTHON_USEDEP}]
doc? (
next reply other threads:[~2018-07-27 18:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 18:27 Virgil Dupras [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-05 1:29 [gentoo-commits] repo/gentoo:master commit in: dev-python/fabric/ Aaron Bauman
2019-12-05 1:29 Aaron Bauman
2019-05-14 13:10 Virgil Dupras
2019-05-10 18:06 Virgil Dupras
2019-04-08 18:31 Aaron Bauman
2019-03-01 0:26 Aaron Bauman
2018-08-22 14:52 Virgil Dupras
2018-08-02 12:36 Virgil Dupras
2018-08-01 12:11 Virgil Dupras
2018-07-31 14:27 Virgil Dupras
2018-07-31 2:25 Virgil Dupras
2018-07-30 23:41 Virgil Dupras
2018-07-30 20:59 Mikle Kolyada
2018-07-28 13:24 Thomas Deutschmann
2017-11-08 16:34 Patrick Lauer
2017-07-08 14:19 Alexis Ballier
2017-05-03 7:37 Michał Górny
2016-09-25 5:03 Alice Ferrazzi
2016-05-11 14:09 Patrick Lauer
2016-02-09 12:19 Justin Lecher
2015-10-22 11:09 Justin Lecher
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=1532715160.83d00a6d2dada40cad5133971079ea0a71984824.vdupras@gentoo \
--to=vdupras@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