@@ -1,4 +1,4 @@
-From e4e1fed9f8e3ff3e04467699f36599f76caa9487 Mon Sep 17 00:00:00 2001
+From ea75b7fc017f7a1a3a47e9e2bef21209f0f36a04 Mon Sep 17 00:00:00 2001
From: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Wed, 23 Feb 2022 12:27:06 +0000
Subject: [PATCH] python3-pip: Don't change shebang
@@ -13,10 +13,10 @@ Upstream-Status: Inappropriate [OE specific config]
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/pip/_vendor/distlib/scripts.py b/src/pip/_vendor/distlib/scripts.py
-index 195dc3f..a0e0d61 100644
+index ac9e909..1faa5b6 100644
--- a/src/pip/_vendor/distlib/scripts.py
+++ b/src/pip/_vendor/distlib/scripts.py
-@@ -155,6 +155,8 @@ class ScriptMaker(object):
+@@ -157,6 +157,8 @@ class ScriptMaker(object):
See also: http://www.in-ulm.de/~mascheck/various/shebang/#length
https://hg.mozilla.org/mozilla-central/file/tip/mach
"""
@@ -25,7 +25,7 @@ index 195dc3f..a0e0d61 100644
if os.name != 'posix':
simple_shebang = True
elif getattr(sys, "cross_compiling", False):
-@@ -363,7 +365,7 @@ class ScriptMaker(object):
+@@ -367,7 +369,7 @@ class ScriptMaker(object):
return
match = FIRST_LINE_RE.match(first_line.replace(b'\r\n', b'\n'))
similarity index 97%
rename from meta/recipes-devtools/python/python3-pip_26.2.1.bb
rename to meta/recipes-devtools/python/python3-pip_26.2.2.bb
@@ -26,7 +26,7 @@ inherit pypi python_flit_core
SRC_URI += "file://no_shebang_mangling.patch"
-SRC_URI[sha256sum] = "f6ad667e89a1fe78046c8f13232b247200f5258d7828f3f7883d660878e0813f"
+SRC_URI[sha256sum] = "3a8e5c800492787f33a4114ef54444546c340df428974ebba17e0fd47e11af2f"
CVE_PRODUCT = "pypa:pip"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *python3-pip* to *26.2.2* has Succeeded. Next steps: - apply the patch: git am 0001-python3-pip-upgrade-26.2.1-26.2.2.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From 3d854dfc2eb7e8eaa63c41abcd213bf215cfc943 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Wed, 21 Oct 2026 05:29:02 +0000 Subject: [PATCH] python3-pip: upgrade 26.2.1 -> 26.2.2 26.2.2 (2026-10-20) =================== Vendored Libraries ------------------ - Upgrade certifi to 2026.10.19 --- .../python/python3-pip/no_shebang_mangling.patch | 8 ++++---- .../{python3-pip_26.2.1.bb => python3-pip_26.2.2.bb} | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) rename meta/recipes-devtools/python/{python3-pip_26.2.1.bb => python3-pip_26.2.2.bb} (97%)