Skip to contentSkip to conversation

python3-imageio: Upgrade 2.37.3 -> 2.37.4

PATCH New Leon Anavi 1 participant 3 messages Jul 20

lore
Share & tools
lore

Leon Anavi

author
#0 lore raw

PATCH 1/3 python3-imageio: Upgrade 2.37.3 -> 2.37.4

Upgrade to release 2.37.4:

- Set filename parameter of FileNotFoundError exception
- Fix typos in docstrings and comments

---
 .../{python3-imageio_2.37.3.bb => python3-imageio_2.37.4.bb}    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-python/recipes-devtools/python/{python3-imageio_2.37.3.bb => python3-imageio_2.37.4.bb} (81%)
meta-python/recipes-devtools/python/python3-imageio_2.37.4.bb renamed from meta-python/recipes-devtools/python/python3-imageio_2.37.3.bb +1 -1
similarity index 81%
rename from meta-python/recipes-devtools/python/python3-imageio_2.37.3.bb
rename to meta-python/recipes-devtools/python/python3-imageio_2.37.4.bb
index b90f1ba863..5beb1c5239 100644
@@ -5,7 +5,7 @@ SECTION = "devel/python"
 LICENSE = "BSD-2-Clause"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=6c492278d46e42af592aa26d7cab1e54"
 
-SRC_URI[sha256sum] = "bbb37efbfc4c400fcd534b367b91fcd66d5da639aaa138034431a1c5e0a41451"
+SRC_URI[sha256sum] = "e45cbc5e83502047fb138f7f585f7f105a136a57eea5f4b3cfc6ce1b52720bd3"
 
 inherit pypi python_setuptools_build_meta
 
Signature · 1 line
2.47.3
author
#1 lore raw

PATCH 2/3 python3-autobahn: Upgrade 26.6.1 -> 26.7.1

Upgrade to release 26.7.1:

- Fix WebSocket maxMessagePayloadSize being enforced against the compressed on-the-wire frame length instead of the uncompressed reassembled message size when permessage-compress (deflate/bzip2/snappy/brotli) is negotiated. A small compressed frame could inflate far beyond the configured limit and be delivered to the application (a decompression-bomb style denial-of-service; security advisory GHSA-hxp9-w8x3-p566, same class as CVE-2016-10544). The limit is now re-checked at the inflation site against the running uncompressed message size, and the connection is failed with close code 1009 (message too big) before delivery - for both the whole-message and streaming receive APIs and every compression backend. Behaviour change:
a compressed message that inflates past maxMessagePayloadSize is now rejected where it previously passed; uncompressed traffic and the per-frame maxFramePayloadSize wire guard are unaffected
- Fix the permessage-deflate max_message_size receive cap silently truncating an over-limit message and raising a zlib error instead of cleanly rejecting it: the bounded decompress(..., max_length) left the remaining input in unconsumed_tail undrained, so the message was corrupted rather than reported. Decompression is now bounded cumulatively across frames and raises PayloadExceededError as soon as the uncompressed size would exceed the cap
- Make bounded decompression backend-agnostic:
decompress_message_data() gains an optional max_output_len argument (documented on the PerMessageCompress base class) and every permessage-compress backend now honours it. deflate and bzip2 stop inflating once the limit is reached (native incremental cap); snappy and brotli, whose libraries expose no output-length argument, inflate the frame (already bounded on the wire by maxFramePayloadSize) and then reject - a weaker but still clean per-frame guarantee. The WebSocket receive path passes the remaining maxMessagePayloadSize budget so a compressed frame no longer expands unbounded into memory before the size check; the previous post-inflation check remains as a backstop. Previously only deflate had any decompressed-output cap, so a snappy/bzip2/brotli frame could inflate fully into memory first
- Make the asyncio RawSocket receive size limit configurable, at parity with the Twisted backend. The asyncio WampRawSocketFactory now exposes setProtocolOptions(maxMessagePayloadSize=...) / resetProtocolOptions() (bounds [512, 2**24], default 16 MB), and the configured value drives both the advertised handshake length exponent and the enforced receive cap (rounded up to the next power of two), matching the Twisted factory. Previously the asyncio receive limit was hardwired to 16 MB (a dead max_size=None branch), so an asyncio WAMP peer could not tighten its RawSocket receive limit for DoS hardening and Crossbar's RawSocket max_message_size had no effect on the asyncio path

---
 ...essing-for-external-cross-toolchains.patch | 88 +++++++++++++++++++
 ...n_26.6.1.bb => python3-autobahn_26.7.1.bb} |  4 +-
 2 files changed, 91 insertions(+), 1 deletion(-)
 create mode 100644 meta-python/recipes-devtools/python/python3-autobahn/0001-Skip-march-guessing-for-external-cross-toolchains.patch
 rename meta-python/recipes-devtools/python/{python3-autobahn_26.6.1.bb => python3-autobahn_26.7.1.bb} (77%)
meta-python/recipes-devtools/python/python3-autobahn/0001-Skip-march-guessing-for-external-cross-toolchains.patch new file +88 -0
new file mode 100644
index 0000000000..8f2e8f0d01
@@ -0,0 +1,88 @@
+From c677aa7a80fd551abb391a8f6abd28dc9f5c43a2 Mon Sep 17 00:00:00 2001
+From: Leon Anavi <[email protected]>
+Date: Mon, 20 Jul 2026 15:52:32 +0300
+Subject: [PATCH] Skip -march guessing for external cross toolchains
+
+Don't add -march flag when CC/CROSS_COMPILE names an external cross
+toolchain (Yocto/OpenEmbedded, Buildroot, ...). These already
+inject the correct target. Avoid issues such as an unknown value
+'x86-64-v2' for '-march' when cross compiling for ARM machine.
+
+Upstream-Status: Pending [https://github.com/crossbario/autobahn-python/pull/1934]
+
+Signed-off-by: Leon Anavi <[email protected]>
+---
+ src/autobahn/nvx/_compile_args.py | 36 ++++++++++++++++++++++++++++---
+ 1 file changed, 33 insertions(+), 3 deletions(-)
+
+diff --git a/src/autobahn/nvx/_compile_args.py b/src/autobahn/nvx/_compile_args.py
+index 2a35ab31..173e5fd4 100644
+--- a/src/autobahn/nvx/_compile_args.py
++++ b/src/autobahn/nvx/_compile_args.py
+@@ -81,6 +81,10 @@ CIBUILDWHEEL : str, optional
+ AUDITWHEEL_PLAT : str, optional
+     Set by auditwheel/manylinux builds. Indicates wheel build.
+ 
++CC, CROSS_COMPILE : str, optional
++    If either names a triplet-prefixed compiler (e.g. "aarch64-poky-linux-gcc"),
++    an external cross toolchain is assumed and no -march flag is added.
++
+ Examples
+ --------
+ 
+@@ -212,9 +216,6 @@ def get_compile_args():
+         # But default codegen is already optimized for current arch
+         return ["/O2", "/W3"]
+ 
+-    # GCC/Clang on POSIX (Linux, macOS, *BSD)
+-    machine = _get_target_machine()
+-
+     # Base flags for all POSIX platforms
+     base_args = [
+         "-std=c99",
+@@ -233,6 +234,14 @@ def get_compile_args():
+         # deployments). It is NOT safe for distributed wheels or cross-compilation.
+         return base_args + ["-march=native"]
+ 
++    if _is_external_toolchain():
++        # Cross toolchain (Yocto/OpenEmbedded, Buildroot, ...) already sets its
++        # own -march/-mtune; don't second-guess it (#1930).
++        return base_args
++
++    # GCC/Clang on POSIX (Linux, macOS, *BSD)
++    machine = _get_target_machine()
++
+     # Default for everyone (AUTOBAHN_ARCH_TARGET unset or "safe"): a portable
+     # baseline architecture. Defaulting to "safe" rather than -march=native is
+     # what makes cross-compilation work out of the box - a cross toolchain
+@@ -248,6 +257,27 @@ def get_compile_args():
+     return base_args
+ 
+ 
++def _is_external_toolchain():
++    """
++    True if ``CC`` or ``CROSS_COMPILE`` names a triplet-prefixed compiler (e.g.
++    ``aarch64-poky-linux-gcc``), the convention used by externally managed
++    toolchains such as Yocto/OpenEmbedded and Buildroot.
++
++    Returns
++    -------
++    bool
++        True if an externally managed cross toolchain is detected.
++    """
++    for var in ("CC", "CROSS_COMPILE"):
++        value = os.environ.get(var, "")
++        if not value:
++            continue
++        exe = os.path.basename(value.split()[0])
++        if "-" in exe:
++            return True
++    return False
++
++
+ def _get_target_machine():
+     """
+     Return the *target* machine architecture for the build.
+-- 
+2.43.0
+
meta-python/recipes-devtools/python/python3-autobahn_26.7.1.bb renamed from meta-python/recipes-devtools/python/python3-autobahn_26.6.1.bb +3 -1
similarity index 77%
rename from meta-python/recipes-devtools/python/python3-autobahn_26.6.1.bb
rename to meta-python/recipes-devtools/python/python3-autobahn_26.7.1.bb
index f9239b4904..7829a0e149 100644
@@ -3,7 +3,9 @@ HOMEPAGE = "http://crossbar.io/autobahn"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=49165a577911c4178e915dc26e2802a3"
 
-SRC_URI[sha256sum] = "66b27e066a8ea265541eb07fd964e3116e2b8f51d797eea8a46b55c07fd81a07"
+SRC_URI += "file://0001-Skip-march-guessing-for-external-cross-toolchains.patch"
+
+SRC_URI[sha256sum] = "c6949a2c6eb95fb1c218837dbda0a59abbbebafb8b11098551c01a7061dfd245"
 
 CVE_PRODUCT = "autobahn"
 
Signature · 1 line
2.47.3
author
#2 lore raw

PATCH 3/3 python3-invoke: Upgrade 2.2.1 -> 3.0.3

In reply to Leon Anavi

Upgrade to release 3.0.3:

- Reverted the @task return value type hint change; it actually just makes things worse. Taking this one back to the drawing table for later.

From 3.0.2:

- Define a custom __repr__ for Promise so it can be displayed in interactive sessions or other debug contexts, without running afoul of AttributeError. Thanks to Leonid Shvechikov for the original bug report.
- Make the return value type hint for @task more specific; as-is it would trigger typecheck errors when handing regular, decorated task functions as inputs to add_task and similar methods.

From 3.0.1:

- Minor tweaks to documentation and type hints/inheritance (mostly around Promise).

From 3.0.0:

- Add access to the core CLI parser's remainder value, via Context.remainder - this allows for more elegant wrapper tasks.
- Update the return value, and type hint, of run and friends to be Result instead of Optional[Result].
- run now includes local subprocess PIDs in Result objects (as .pid), via the new Runner.get_pid method. This may be generally useful for auditing or similar tasks, but is primarily intended for users of disown=True who want to perform their own subprocess management.
- Fix a grab bag's worth of Sphinx doc render problems, among which were some class attributes (eg Context.command_cwds) that had silently disappeared from the class' autodoc output after our 2.0 release.
- Expanded mypy type hint checking to more of the codebase & generally touched up some type hints here and there. More of this is planned to occur as we go.
- Dropped support for Python versions <3.9. That's right, we've caught up to Python's own EOL regime... as of late 2024! As part of this change, we also switched over to using pyproject.toml for packaging metadata.

Fixes:

WARNING: python3-invoke-3.0.3-r0 do_check_backend: QA Issue:
inherits setuptools3 but has pyproject.toml with setuptools.build_meta, use the correct class [pep517-backend]

---
 .../{python3-invoke_2.2.1.bb => python3-invoke_3.0.3.bb}      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta-python/recipes-devtools/python/{python3-invoke_2.2.1.bb => python3-invoke_3.0.3.bb} (74%)
meta-python/recipes-devtools/python/python3-invoke_3.0.3.bb renamed from meta-python/recipes-devtools/python/python3-invoke_2.2.1.bb +2 -2
similarity index 74%
rename from meta-python/recipes-devtools/python/python3-invoke_2.2.1.bb
rename to meta-python/recipes-devtools/python/python3-invoke_3.0.3.bb
index bcff343480..e9d19da088 100644
@@ -3,9 +3,9 @@ HOMEPAGE = "https://www.pyinvoke.org/"
 LICENSE = "BSD-2-Clause"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=a8815068973f31b78c328dc067e297ab"
 
-SRC_URI[sha256sum] = "515bf49b4a48932b79b024590348da22f39c4942dff991ad1fb8b8baea1be707"
+SRC_URI[sha256sum] = "437b6a622223824380bfb4e64f612711a6b648c795f565efc8625af66fb57f0c"
 
-inherit pypi setuptools3
+inherit pypi python_setuptools_build_meta
 
 RDEPENDS:${PN} += " \
         python3-fcntl \
Signature · 1 line
2.47.3