mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Markus Heidelberg <m.heidelberg@cab.de>
Subject: Re: [ptxdist] [APPLIED] python3-pyparsing: version bump 2.4.7 -> 3.2.5
Date: Fri, 12 Dec 2025 15:51:58 +0100	[thread overview]
Message-ID: <20251212145158.3023586-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251202141709.185914-2-m.heidelberg@cab.de>

Thanks, applied as 9967e3d2d909cc82f01c23134d58b072eb779665.

Michael

[sent from post-receive hook]

On Fri, 12 Dec 2025 15:51:58 +0100, Markus Heidelberg <m.heidelberg@cab.de> wrote:
> pydot needs pyparsing >= 3.1.0
> 
> Since 3.0.8 the build system is flit-core instead of setuptools.
> 
> Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
> Message-Id: <20251202141709.185914-2-m.heidelberg@cab.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/python3-pyparsing.in b/rules/python3-pyparsing.in
> index 5e59a09018dc..9c375a92f68d 100644
> --- a/rules/python3-pyparsing.in
> +++ b/rules/python3-pyparsing.in
> @@ -2,6 +2,7 @@
>  
>  config PYTHON3_PYPARSING
>  	tristate
> +	select HOST_PYTHON3_PYBUILD
>  	select PYTHON3
>  	prompt "pyparsing"
>  	help
> diff --git a/rules/python3-pyparsing.make b/rules/python3-pyparsing.make
> index 39ad2ab4b545..e12027ee1da9 100644
> --- a/rules/python3-pyparsing.make
> +++ b/rules/python3-pyparsing.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_PYTHON3_PYPARSING) += python3-pyparsing
>  #
>  # Paths and names
>  #
> -PYTHON3_PYPARSING_VERSION	:= 2.4.7
> -PYTHON3_PYPARSING_MD5		:= f0953e47a0112f7a65aec2305ffdf7b4
> +PYTHON3_PYPARSING_VERSION	:= 3.2.5
> +PYTHON3_PYPARSING_MD5		:= 49f6a72433130541fd92c56b110061d2
>  PYTHON3_PYPARSING		:= pyparsing-$(PYTHON3_PYPARSING_VERSION)
>  PYTHON3_PYPARSING_SUFFIX	:= tar.gz
>  PYTHON3_PYPARSING_URL		:= $(call ptx/mirror-pypi, pyparsing, $(PYTHON3_PYPARSING).$(PYTHON3_PYPARSING_SUFFIX))



  reply	other threads:[~2025-12-12 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 14:17 [ptxdist] [PATCH v2 0/5] new python3-statemachine package + new/updated dependencies Markus Heidelberg via ptxdist
2025-12-02 14:17 ` [ptxdist] [PATCH v2 1/5] python3-pyparsing: version bump 2.4.7 -> 3.2.5 Markus Heidelberg via ptxdist
2025-12-12 14:51   ` Michael Olbrich [this message]
2025-12-02 14:17 ` [ptxdist] [PATCH v2 2/5] python3-packaging: version bump 23.1 -> 25.0 Markus Heidelberg via ptxdist
2025-12-12 14:51   ` [ptxdist] [APPLIED] " Michael Olbrich
2025-12-02 14:17 ` [ptxdist] [PATCH v2 3/5] python3-setuptools: version bump 71.1.0 -> 80.9.0 Markus Heidelberg via ptxdist
2025-12-02 14:17 ` [ptxdist] [PATCH v2 4/5] python3-pydot: new package Markus Heidelberg via ptxdist
2025-12-02 14:17 ` [ptxdist] [PATCH v2 5/5] python3-statemachine: " Markus Heidelberg via ptxdist
2025-12-12 14:52   ` [ptxdist] [APPLIED] " Michael Olbrich

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=20251212145158.3023586-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