From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/2] package/python-colorzero: bump version to 2.0
Date: Thu, 22 Apr 2021 21:36:27 +0200 [thread overview]
Message-ID: <20210422213627.0670eb2b@windsurf> (raw)
In-Reply-To: <20210409211258.32652-1-ps.report@gmx.net>
Hello,
On Fri, 9 Apr 2021 23:12:57 +0200
Peter Seiderer <ps.report@gmx.net> wrote:
> - change to python3 only
>
> - update license file hash:
> @@ -1,4 +1,4 @@
> -Copyright 2016-2018 Dave Jones <dave@waveform.org.uk>
> +SPDX-License-Identifier: BSD-3-Clause
>
> Changelog ([1]):
>
> - Dropped Python 2.x support. Current Python support level is 3.5 and above.
>
> - Added html and css format specifications to the :class:`Color` class'
> string-formatting capabilities.
>
> [1] https://github.com/waveform80/colorzero/blob/master/docs/changelog.rst
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
I have applied, with one change. See below.
> config BR2_PACKAGE_PYTHON_COLORZERO
> bool "python-colorzero"
> + depends on BR2_PACKAGE_PYTHON3
This should have been propagated to python-gpiozero, in that same
patch. I know you did it in PATCH 2/2, but that breaks bisectability,
and logically speaking, after this PATCH 1/2, python-gpiozero is no
longer usable with python2.
Again: applied with that change. Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2021-04-22 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 21:12 [Buildroot] [PATCH v1 1/2] package/python-colorzero: bump version to 2.0 Peter Seiderer
2021-04-09 21:12 ` [Buildroot] [PATCH v1 2/2] package/python-gpiozero: bump version to 1.6.2 Peter Seiderer
2021-04-22 19:36 ` Thomas Petazzoni
2021-04-22 19:36 ` 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=20210422213627.0670eb2b@windsurf \
--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.