From: Markus Heidelberg via ptxdist <ptxdist@pengutronix.de>
To: <ptxdist@pengutronix.de>
Cc: Markus Heidelberg <m.heidelberg@cab.de>
Subject: [ptxdist] [PATCH 0/5] new python3-statemachine package + new/updated dependencies
Date: Mon, 1 Dec 2025 18:43:42 +0100 [thread overview]
Message-ID: <20251201174347.129488-1-m.heidelberg@cab.de> (raw)
Markus Heidelberg (5):
python3-pyparsing: version bump 2.4.7 -> 3.2.5
python3-packaging: version bump 23.1 -> 25.0
python3-setuptools: version bump 71.1.0 -> 80.9.0
python3-pydot: new package
python3-statemachine: new package
rules/python3-packaging.make | 4 +--
rules/python3-pydot.in | 11 +++++++
rules/python3-pydot.make | 57 +++++++++++++++++++++++++++++++++
rules/python3-pyparsing.in | 1 +
rules/python3-pyparsing.make | 4 +--
rules/python3-setuptools.make | 4 +--
rules/python3-statemachine.in | 10 ++++++
rules/python3-statemachine.make | 55 +++++++++++++++++++++++++++++++
8 files changed, 140 insertions(+), 6 deletions(-)
create mode 100644 rules/python3-pydot.in
create mode 100644 rules/python3-pydot.make
create mode 100644 rules/python3-statemachine.in
create mode 100644 rules/python3-statemachine.make
--
2.43.0
next reply other threads:[~2025-12-01 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 17:43 Markus Heidelberg via ptxdist [this message]
2025-12-01 17:43 ` [ptxdist] [PATCH 1/5] python3-pyparsing: version bump 2.4.7 -> 3.2.5 Markus Heidelberg via ptxdist
2025-12-01 17:43 ` [ptxdist] [PATCH 2/5] python3-packaging: version bump 23.1 -> 25.0 Markus Heidelberg via ptxdist
2025-12-01 17:43 ` [ptxdist] [PATCH 3/5] python3-setuptools: version bump 71.1.0 -> 80.9.0 Markus Heidelberg via ptxdist
2025-12-01 17:43 ` [ptxdist] [PATCH 4/5] python3-pydot: new package Markus Heidelberg via ptxdist
2025-12-01 17:43 ` [ptxdist] [PATCH 5/5] python3-statemachine: " Markus Heidelberg via ptxdist
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=20251201174347.129488-1-m.heidelberg@cab.de \
--to=ptxdist@pengutronix.de \
--cc=m.heidelberg@cab.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