From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Matt Weber <matthew.weber@collins.com>,
Asaf Kahlon <asafka7@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/python-pysftp: add missing C++ dependency from paramiko
Date: Thu, 05 Aug 2021 12:06:29 +0200 [thread overview]
Message-ID: <87pmuskxy2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210720100828.421187-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni's message of "Tue, 20 Jul 2021 12:08:28 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> python-paramiko has a dependency on C++ support, which was added in
> commit 2d7b73cf75daedd4a198a75546308fedae7c9467 in 2016.
> When python-pysftp was added in commit
> 3b920487bad119abf5bfb10a237cedd3b5278c10 in 2020, this C++ dependency
> was not propagated, even though python-pysftp selects python-paramiko.
> This commit fixes this issue by propagating the dependency, which
> fixes this warning:
> WARNING: unmet direct dependencies detected for BR2_PACKAGE_PYTHON_PARAMIKO
> Depends on [n]: (BR2_PACKAGE_PYTHON [=n] || BR2_PACKAGE_PYTHON3 [=y]) && BR2_PACKAGE_PYTHON3 [=y] && BR2_INSTALL_LIBSTDCPP [=n]
> Selected by [y]:
> - BR2_PACKAGE_PYTHON_PYSFTP [=y] && (BR2_PACKAGE_PYTHON [=n] || BR2_PACKAGE_PYTHON3 [=y]) && BR2_PACKAGE_PYTHON3 [=y]
> That occurs with configuration with C++ disabled, but python-pysftp
> enabled.
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to 2021.02.x and 2021.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-08-05 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 10:08 [Buildroot] [PATCH] package/python-pysftp: add missing C++ dependency from paramiko Thomas Petazzoni
2021-07-25 13:37 ` Thomas Petazzoni
2021-08-05 10:06 ` Peter Korsgaard [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=87pmuskxy2.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--cc=matthew.weber@collins.com \
--cc=thomas.petazzoni@bootlin.com \
/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.