From: Markus Heidelberg via ptxdist <ptxdist@pengutronix.de>
To: <ptxdist@pengutronix.de>
Cc: Markus Heidelberg <m.heidelberg@cab.de>
Subject: [ptxdist] [PATCH 3/5] python3-setuptools: version bump 71.1.0 -> 80.9.0
Date: Mon, 1 Dec 2025 18:43:45 +0100 [thread overview]
Message-ID: <20251201174347.129488-4-m.heidelberg@cab.de> (raw)
In-Reply-To: <20251201174347.129488-1-m.heidelberg@cab.de>
pydot needs setuptools >= 77.0.0
Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
---
rules/python3-setuptools.make | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rules/python3-setuptools.make b/rules/python3-setuptools.make
index 307196452..d514fa7c7 100644
--- a/rules/python3-setuptools.make
+++ b/rules/python3-setuptools.make
@@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_PYTHON3_SETUPTOOLS) += python3-setuptools
#
# Paths and names
#
-PYTHON3_SETUPTOOLS_VERSION := 71.1.0
-PYTHON3_SETUPTOOLS_MD5 := 2d7f698adca86005a771f8709686d5e4
+PYTHON3_SETUPTOOLS_VERSION := 80.9.0
+PYTHON3_SETUPTOOLS_MD5 := 82e1d67883b713f9493659b50d13b436
PYTHON3_SETUPTOOLS := setuptools-$(PYTHON3_SETUPTOOLS_VERSION)
PYTHON3_SETUPTOOLS_SUFFIX := tar.gz
PYTHON3_SETUPTOOLS_URL := $(call ptx/mirror-pypi, setuptools, $(PYTHON3_SETUPTOOLS).$(PYTHON3_SETUPTOOLS_SUFFIX))
--
2.43.0
next prev parent 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 [ptxdist] [PATCH 0/5] new python3-statemachine package + new/updated dependencies Markus Heidelberg via ptxdist
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 ` Markus Heidelberg via ptxdist [this message]
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-4-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