python3-markupsafe: upgrade 3.0.2 -> 3.0.3
PATCH 1/5 python3-markupsafe: upgrade 3.0.2 -> 3.0.3
From: Ankur Tyagi <[email protected]>
Changelog:
https://github.com/pallets/markupsafe/releases/tag/3.0.3
---
...{python3-markupsafe_3.0.2.bb => python3-markupsafe_3.0.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-markupsafe_3.0.2.bb => python3-markupsafe_3.0.3.bb} (82%)meta/recipes-devtools/python/python3-markupsafe_3.0.3.bb renamed from meta/recipes-devtools/python/python3-markupsafe_3.0.2.bb +1 -1
@@ -3,7 +3,7 @@ HOMEPAGE = "http://github.com/mitsuhiko/markupsafe" LICENSE = "BSD-3-Clause" LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=ffeffa59c90c9c4a033c7574f8f3fb75" -SRC_URI[sha256sum] = "ee55d3edf80167e48ea11a923c7386f4669df67d7994554387f84e7d8b0a2bf0" +SRC_URI[sha256sum] = "722695808f4b6457b320fdc131280796bdceb04ab50fe1795cd540799ebe1698" PYPI_PACKAGE = "markupsafe" inherit pypi python_setuptools_build_meta ptest-python-pytest
PATCH 2/5 resolvconf: upgrade 1.93 -> 1.94
From: Ankur Tyagi <[email protected]>
---
.../resolvconf/{resolvconf_1.93.bb => resolvconf_1.94.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-connectivity/resolvconf/{resolvconf_1.93.bb => resolvconf_1.94.bb} (98%)meta/recipes-connectivity/resolvconf/resolvconf_1.94.bb renamed from meta/recipes-connectivity/resolvconf/resolvconf_1.93.bb +1 -1
@@ -15,7 +15,7 @@ SRC_URI = "git://salsa.debian.org/debian/resolvconf.git;protocol=https;branch=un file://0001-avoid-using-m-option-for-readlink.patch \ " -SRCREV = "ab766fa31f7939f6d879123236b4275320b7ff64" +SRCREV = "505c258d1efb287ffdbf132531a86437d2bf0513" # the package is taken from snapshots.debian.org; that source is static and goes stale # so we check the latest upstream from a directory that does get updated
PATCH 3/5 lttng-modules: upgrade 2.14.2 -> 2.14.3
In reply to [email protected]From: Ankur Tyagi <[email protected]>
* Fix: Set CTF version in metadata packet headers for CTF2
* fix: always print to kernel log on module load failure
* fix: get_pfnblock_flags_mask / get_pfnblock_migratetype wrappers for v6.17
* fix: remove duplicated MODULE macros
---
.../lttng/{lttng-modules_2.14.2.bb => lttng-modules_2.14.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-kernel/lttng/{lttng-modules_2.14.2.bb => lttng-modules_2.14.3.bb} (94%)meta/recipes-kernel/lttng/lttng-modules_2.14.3.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.14.2.bb +1 -1
@@ -15,7 +15,7 @@ SRC_URI = "https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2 \ # Use :append here so that the patch is applied also when using devupstream SRC_URI:append = " file://0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch \ " -SRC_URI[sha256sum] = "a581dd44ea61af869a935e71498d4273be59944d56f906135c6451d6548742a5" +SRC_URI[sha256sum] = "35a1875ad96e8b4b6aa8729f59af350bfc788ba65c6856deaa84d33acc0f28c2" export INSTALL_MOD_DIR = "kernel/lttng-modules"
PATCH 4/5 usbutils: upgrade 018 -> 019
In reply to [email protected]From: Ankur Tyagi <[email protected]>
Changelog:
https://github.com/gregkh/usbutils/blob/v019/NEWS
---
meta/recipes-bsp/usbutils/{usbutils_018.bb => usbutils_019.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-bsp/usbutils/{usbutils_018.bb => usbutils_019.bb} (93%)meta/recipes-bsp/usbutils/usbutils_019.bb renamed from meta/recipes-bsp/usbutils/usbutils_018.bb +1 -1
@@ -15,7 +15,7 @@ DEPENDS = "libusb1 virtual/libiconv udev" SRC_URI = "${KERNELORG_MIRROR}/linux/utils/usb/usbutils/usbutils-${PV}.tar.gz \ " -SRC_URI[sha256sum] = "0048d2d8518fb0cc7c0516e16e52af023e52b55ddb3b2068a77041b5ef285768" +SRC_URI[sha256sum] = "347c52b65a6aeb22cfe3af8382192004f99725850e1dc5f705336e54cf6d59fc" inherit meson pkgconfig update-alternatives
PATCH 5/5 openssh: upgrade 10.1p1 -> 10.2p1
In reply to [email protected]From: Ankur Tyagi <[email protected]>
Drop patch merged[1] in this release.
Changelog:
https://www.openssh.org/releasenotes.html#10.2p1
[1] https://github.com/openssh/openssh-portable/commit/11a5e5179077f73c2d45bcdf3f60153ae3f17815
---
...c-use-the-absolute-path-in-the-SSH-e.patch | 35 -------------------
.../{openssh_10.1p1.bb => openssh_10.2p1.bb} | 3 +-
2 files changed, 1 insertion(+), 37 deletions(-)
delete mode 100644 meta/recipes-connectivity/openssh/openssh/0001-regress-test-exec-use-the-absolute-path-in-the-SSH-e.patch
rename meta/recipes-connectivity/openssh/{openssh_10.1p1.bb => openssh_10.2p1.bb} (98%)meta/recipes-connectivity/openssh/openssh/0001-regress-test-exec-use-the-absolute-path-in-the-SSH-e.patch deleted +0 -35
@@ -1,35 +0,0 @@ -From 9dcccafe44ea17e972e7cddea205bbe9fe71d8d6 Mon Sep 17 00:00:00 2001 -From: Jose Quaresma <[email protected]> -Date: Mon, 15 Jul 2024 18:43:08 +0100 -Subject: [PATCH] regress/test-exec: use the absolute path in the SSH env - -The SSHAGENT_BIN was changed in [1] to SSH_BIN but -the last one don't use the absolute path and consequently -the function increase_datafile_size can loops forever -if the binary not found. - -[1] https://github.com/openssh/openssh-portable/commit/a68f80f2511f0e0c5cef737a8284cc2dfabad818 - -Upstream-Status: Submitted [https://github.com/openssh/openssh-portable/pull/510] - -Signed-off-by: Jose Quaresma <[email protected]> ---- - regress/test-exec.sh | 5 +++++ - 1 file changed, 5 insertions(+) - -diff --git a/regress/test-exec.sh b/regress/test-exec.sh -index 8a00c72..2891f27 100644 ---- a/regress/test-exec.sh -+++ b/regress/test-exec.sh -@@ -179,6 +179,11 @@ if [ "x$TEST_SSH_OPENSSL" != "x" ]; then - fi - - # Path to sshd must be absolute for rexec -+case "$SSH" in -+/*) ;; -+*) SSH=`which $SSH` ;; -+esac -+ - case "$SSHD" in - /*) ;; - *) SSHD=`which $SSHD` ;;
meta/recipes-connectivity/openssh/openssh_10.2p1.bb renamed from meta/recipes-connectivity/openssh/openssh_10.1p1.bb +1 -2
@@ -24,9 +24,8 @@ SRC_URI = "https://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-${PV}.ta file://run-ptest \ file://sshd_check_keys \ file://0001-regress-banner.sh-log-input-and-output-files-on-erro.patch \ - file://0001-regress-test-exec-use-the-absolute-path-in-the-SSH-e.patch \ " -SRC_URI[sha256sum] = "b9fc7a2b82579467a6f2f43e4a81c8e1dfda614ddb4f9b255aafd7020bbf0758" +SRC_URI[sha256sum] = "ccc42c0419937959263fa1dbd16dafc18c56b984c03562d2937ce56a60f798b2" CVE_STATUS[CVE-2007-2768] = "not-applicable-config: This CVE is specific to OpenSSH with the pam opie which we don't build/use here."