From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-paramiko: bump to version 2.2.0
Date: Tue, 13 Jun 2017 10:16:04 +0200 [thread overview]
Message-ID: <20170613101604.50b79b4d@windsurf.lan> (raw)
In-Reply-To: <20170613071317.7112-1-yegorslists@googlemail.com>
Hello,
On Tue, 13 Jun 2017 09:13:17 +0200, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> Add new runtime dependencies bcrypt and pynacl.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Applied, thanks. However, one request below.
> ---
> package/python-paramiko/Config.in | 2 ++
> package/python-paramiko/python-paramiko.hash | 4 ++--
> package/python-paramiko/python-paramiko.mk | 4 ++--
> 3 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/package/python-paramiko/Config.in b/package/python-paramiko/Config.in
> index aad85cb13..7d20d04d2 100644
> --- a/package/python-paramiko/Config.in
> +++ b/package/python-paramiko/Config.in
> @@ -5,6 +5,8 @@ config BR2_PACKAGE_PYTHON_PARAMIKO
> select BR2_PACKAGE_PYTHON3_ZLIB if BR2_PACKAGE_PYTHON3 # runtime
> select BR2_PACKAGE_PYTHON_CRYPTOGRAPHY # runtime
> select BR2_PACKAGE_PYTHON_PYASN # runtime
> + select BR2_PACKAGE_PYTHON_PYNACL # runtime
> + select BR2_PACKAGE_PYTHON_BCRYPT # runtime
Alphabetic sorting would be better. However, alphabetic sorting was
already not good (with the zlib selects), so it can be fixed in a
follow-up commit.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-06-13 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 7:13 [Buildroot] [PATCH] python-paramiko: bump to version 2.2.0 yegorslists at googlemail.com
2017-06-13 8:16 ` Thomas Petazzoni [this message]
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=20170613101604.50b79b4d@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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