All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/2] package/python-gpiozero: bump version to 1.6.2
Date: Thu, 22 Apr 2021 21:36:32 +0200	[thread overview]
Message-ID: <20210422213632.0f526b35@windsurf> (raw)
In-Reply-To: <20210409211258.32652-2-ps.report@gmx.net>

On Fri,  9 Apr 2021 23:12:58 +0200
Peter Seiderer <ps.report@gmx.net> wrote:

> - change to python3 only (runtime dependency python-colorzero)
> 
> - update license file hash:
>   @@ -1,3 +1,5 @@
>   +SPDX-License-Identifier: BSD-3-Clause
>   +
> 
> - add setuptools runtime dependency, fixes:
> 
> 	$ pinout -r a020d3 -m
> 	Traceback (most recent call last):
> 	  File "/usr/bin/pinout", line 6, in <module>
> 	    from pkg_resources import load_entry_point
> 	ModuleNotFoundError: No module named 'pkg_resources'
> 
> For details see [1].
> 
> [1] https://gpiozero.readthedocs.io/en/stable/changelog.html
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
>  package/python-gpiozero/Config.in            | 2 ++
>  package/python-gpiozero/python-gpiozero.hash | 4 ++--
>  package/python-gpiozero/python-gpiozero.mk   | 2 +-
>  3 files changed, 5 insertions(+), 3 deletions(-)

Applied to master, thanks.

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

  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 [this message]
2021-04-22 19:36 ` [Buildroot] [PATCH v1 1/2] package/python-colorzero: bump version to 2.0 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=20210422213632.0f526b35@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.