From: Asaf Kahlon <asafka7@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python-secretstorage: drop Python 2 support
Date: Sun, 20 Oct 2019 18:11:26 +0300 [thread overview]
Message-ID: <20191020151126.2468-2-asafka7@gmail.com> (raw)
In-Reply-To: <20191020151126.2468-1-asafka7@gmail.com>
Since version 3.0.0, secretstorage doesn't support Python 2 anymore.
Update its reverese dependency (python-keyring) as well.
Signed-off-by: Asaf Kahlon <asafka7@gmail.com>
---
package/python-keyring/Config.in | 1 +
package/python-secretstorage/Config.in | 1 +
2 files changed, 2 insertions(+)
diff --git a/package/python-keyring/Config.in b/package/python-keyring/Config.in
index 23d86a4822..3961ee8b81 100644
--- a/package/python-keyring/Config.in
+++ b/package/python-keyring/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_PYTHON_KEYRING
bool "python-keyring"
+ depends BR2_PACKAGE_PYTHON3 # python-secretstorage
depends on BR2_INSTALL_LIBSTDCPP # python-secretstorage
select BR2_PACKAGE_PYTHON_SECRETSTORAGE # runtime
help
diff --git a/package/python-secretstorage/Config.in b/package/python-secretstorage/Config.in
index 87aaf6a728..78a0a2ae15 100644
--- a/package/python-secretstorage/Config.in
+++ b/package/python-secretstorage/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_PYTHON_SECRETSTORAGE
bool "python-secretstorage"
+ depends on BR2_PACKAGE_PYTHON3
depends on BR2_INSTALL_LIBSTDCPP # python-cryptography
select BR2_PACKAGE_PYTHON_CRYPTOGRAPHY # runtime
help
--
2.20.1
next prev parent reply other threads:[~2019-10-20 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 15:11 [Buildroot] [PATCH 1/1] package/python-asgiref: drop Python 2 support Asaf Kahlon
2019-10-20 15:11 ` Asaf Kahlon [this message]
2019-10-21 18:46 ` [Buildroot] [PATCH 1/1] package/python-secretstorage: " Thomas Petazzoni
2019-10-21 18:46 ` [Buildroot] [PATCH 1/1] package/python-asgiref: " Thomas Petazzoni
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=20191020151126.2468-2-asafka7@gmail.com \
--to=asafka7@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.