All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/python-flup: update dependency to python3
Date: Mon, 12 Apr 2021 22:39:11 +0200	[thread overview]
Message-ID: <20210412223911.1989281d@windsurf.home> (raw)
In-Reply-To: <20210412164405.16890-1-matthew.weber@rockwellcollins.com>

On Mon, 12 Apr 2021 11:44:05 -0500
Matt Weber <matthew.weber@rockwellcollins.com> wrote:

> From: Jared Bents <jared.bents@rockwellcollins.com>
> 
> Dependency incorrectly calls out python, should be python3
> 
> Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com>
> Signed-off-by: Ryan Barnett <ryan.barnett@rockwellcollins.com>
> Signed-off-by: Matt Weber <matthew.weber@rockwellcollins.com>
> ---
>  package/python-flup/Config.in | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/python-flup/Config.in b/package/python-flup/Config.in
> index 2c21323515..f40f250163 100644
> --- a/package/python-flup/Config.in
> +++ b/package/python-flup/Config.in
> @@ -1,6 +1,6 @@
>  config BR2_PACKAGE_PYTHON_FLUP
>  	bool "python-flup"
> -	depends on BR2_PACKAGE_PYTHON
> +	depends on BR2_PACKAGE_PYTHON3

Do we know since when this is the case? This package was introduced in
2014 as version 1.0.3.dev-20110405, and back then the commit log said
"Tested with ARM and Python 2.7.6". Then it was bumped to
1.0.3.dev20161029 by Adam in 2017, and again to 1.0.3 in 2019. Is it
this latest update that brought the python3 requirement ?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2021-04-12 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 16:44 [Buildroot] [PATCH] package/python-flup: update dependency to python3 Matt Weber
2021-04-12 20:39 ` Thomas Petazzoni [this message]
2021-04-13 13:22   ` Matthew Weber
2021-04-21 21:27 ` Thomas Petazzoni
2021-04-26 14:09 ` Peter Korsgaard

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=20210412223911.1989281d@windsurf.home \
    --to=thomas.petazzoni@bootlin.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.