From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Markus Heidelberg <m.heidelberg@cab.de>
Subject: Re: [ptxdist] [APPLIED] python3-statemachine: version bump 2.5.0 -> 3.1.2
Date: Thu, 25 Jun 2026 21:23:34 +0200 [thread overview]
Message-ID: <20260625192334.832557-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260619082226.578174-1-m.heidelberg@cab.de>
Thanks, applied as 167081ba6c0418b3cab753eebb3e01ff084e72aa.
Michael
[sent from post-receive hook]
On Thu, 25 Jun 2026 21:23:34 +0200, Markus Heidelberg <m.heidelberg@cab.de> wrote:
> There is a newer version 3.2.0 out since two days, but we tested with
> this now one month old release from May.
>
> Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
> Message-Id: <20260619082226.578174-1-m.heidelberg@cab.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/python3-statemachine.make b/rules/python3-statemachine.make
> index a29dca7de43e..dc2a4321b897 100644
> --- a/rules/python3-statemachine.make
> +++ b/rules/python3-statemachine.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_PYTHON3_STATEMACHINE) += python3-statemachine
> #
> # Paths and names
> #
> -PYTHON3_STATEMACHINE_VERSION := 2.5.0
> -PYTHON3_STATEMACHINE_SHA256 := ae88cd22e47930b92b983a2176e61d811e571b69897be2568ec812c2885fb93a
> +PYTHON3_STATEMACHINE_VERSION := 3.1.2
> +PYTHON3_STATEMACHINE_SHA256 := 3a64c4ae91d628eb256580f328c68b16e472f25794d2c478e91f2f1dfb8b0668
> PYTHON3_STATEMACHINE := python_statemachine-$(PYTHON3_STATEMACHINE_VERSION)
> PYTHON3_STATEMACHINE_SUFFIX := tar.gz
> PYTHON3_STATEMACHINE_URL := $(call ptx/mirror-pypi, python-statemachine, $(PYTHON3_STATEMACHINE).$(PYTHON3_STATEMACHINE_SUFFIX))
prev parent reply other threads:[~2026-06-25 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 8:22 [ptxdist] [PATCH] " Markus Heidelberg via ptxdist
2026-06-25 19:23 ` Michael Olbrich [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=20260625192334.832557-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=m.heidelberg@cab.de \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox