summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* boost: fix do_fetch errorJiaying Song2025-01-041-1/+1
| | | | | | | | | | Change the SRC_URI to the correct value due to the following error: WARNING: boost-native-1.86.0-r0 do_fetch: Checksum failure encountered with download of https://boostorg.jfrog.io/artifactory/main/release/1.86.0/source/boost_1_86_0.tar.bz2 - will attempt other sources if available (From OE-Core rev: 8dd4814c5994ff008969591e863f931692740361) Signed-off-by: Jiaying Song <jsong-cn@ala-lpggp7.wrs.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: add volatile file for lastlog2Yi Zhao2025-01-041-1/+8
| | | | | | | | | | | | Add volatile file for lastlog2 to fix runtime error with sysvinit: $ lastlog2 lastlog2: Couldn't read entries for all users lastlog2: Cannot open database (/var/lib/lastlog/lastlog2.db): unable to open database file (From OE-Core rev: 440f4830d1f1bac9d55584fc4e48627920493cb9) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: replace local patch with upstream patchYi Zhao2025-01-043-66/+83
| | | | | | | | | | | | There is a better solution upstream to fix the pam_lastlog2 installation issue[1]. Backport this patch to replace the local patch. [1] https://github.com/util-linux/util-linux/pull/3173 (From OE-Core rev: 1c984d0a06cdcba49f8b0acd12edebfeaedf3aa5) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpam: set pam module path to ${base_libdir}/securityYi Zhao2025-01-041-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | After upgrading to 1.7.0, the pam module path is set to ${libdir}/security[1]. But from the pam.conf(5) man page, the default location seems to be "Module location: /lib/security/ or /lib64/security/, depending on the architecture"[2]. Many third-party pam modules still use {base_libdir}/security as the default module path, such as pam_lastlog2 (from util-linux), pam_cgroup (from libcgroup), pam_cap (from libcap), etc. So currently if you don't use the absolute path to these modules in the files in /etc/pam.d/, they will not be found: PAM unable to dlopen(/usr/lib/security/pam_lastlog2.so): /usr/lib/security/pam_lastlog2.so: cannot open shared object file: No such file or directory This change only affects sysvinit without usrmerge feature enabled, and has no effect on systems using systemd. [1] https://git.openembedded.org/openembedded-core/commit/?id=00eb730291f9630eb70480d37ed48fbadecc547a [2] https://www.man7.org/linux/man-pages/man5/pam.conf.5.html (From OE-Core rev: bc307ac262956a763fb68d621fb6463b1460bf59) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_rpm: set a timestamp handling policy with the new macro ↵Bin Lan2025-01-041-1/+1
| | | | | | | | | | | | | | | | %build_mtime_policy There is the following warning when the do_package_write_rpm task is executed when bitbake linux-yocto: warning: %clamp_mtime_to_source_date_epoch is deprecated, please use %build_mtime_policy After RPM is upgraded to 4.20.0, the %clamp_mtime_to_source_date_epoch macro is now deprecated in favor of %build_mtime_policy set to clamp_to_source_date_epoch. (From OE-Core rev: fa9b9e599bbf3ac73c7a9b1d15ccb0e0bbbe4c11) Signed-off-by: Bin Lan <bin.lan.cn@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* file: upgrade 5.45 -> 5.46Alexander Kanavin2025-01-044-30/+130
| | | | | | | | | Drop patch merged upstream. (From OE-Core rev: 85fabd7ab4847aa62669ec4edc0dcf02bc7e9b21) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow: exclude pre-releases from version checksAlexander Kanavin2025-01-041-0/+1
| | | | | | | (From OE-Core rev: c76f59968c5d11dda9f521baa63a336d54cbfac9) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shadow: merge .inc into .bbAlexander Kanavin2025-01-042-225/+224
| | | | | | | (From OE-Core rev: e7f39f67977a3915290ce26a2a828eecc6dddda4) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kbd: update 2.6.4 -> 2.7.1Alexander Kanavin2025-01-042-82/+3
| | | | | | | (From OE-Core rev: 1e116a0f45a218a751a8c11faa642d976182c021) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* iproute2: update 6.11.0 -> 6.12.0Alexander Kanavin2025-01-045-142/+93
| | | | | | | (From OE-Core rev: f8c665ca16bf643039bd3f0a918ea9cf9d1a3726) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rt-tests: update 2.7 -> 2.8Alexander Kanavin2025-01-042-3/+3
| | | | | | | (From OE-Core rev: 5ace733314256540e4211f9228f691fdef199659) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxshmfence: update 1.3.2 -> 1.3.3Alexander Kanavin2025-01-042-42/+1
| | | | | | | | | Drop patch as issue solved upstream. (From OE-Core rev: f9b7b8885913f583f1442b3140c743b98a52e68e) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxt: update 1.3.0 -> 1.3.1Alexander Kanavin2025-01-042-8/+7
| | | | | | | (From OE-Core rev: 0a5eb0b01048341a430c3ba49aa4bd7983ace444) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gettext: update 0.22.5 -> 0.23.1Alexander Kanavin2025-01-0410-95/+28
| | | | | | | | | | | | | | | | | Drop patches: parallel.patch (obsolete as no .a files are installed) 0001-intl-Fix-build-failure-with-make-j.patch (backport) Gettext no longer installs anything into $libdir/gettext by default but still creates the directory and so it should be packaged. (From OE-Core rev: a414f47009811fa6886e43fd2b4c928a906a65f3) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* formfactor: add support for qemuriscv64 and qemuriscv32Maxin John2025-01-032-0/+20
| | | | | | | | | | | | Add machine config files for qemuriscv64 and qemuriscv32. Fixes [YOCTO #15427]. (From OE-Core rev: ec01090759677f8b69352c56aa29940314ca73e7) Signed-off-by: Maxin John <maxin.john@gmail.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image/populate_sdk: Support usrmerge in toolchain SDK buildsPhilip Lorenz2025-01-032-26/+27
| | | | | | | | | | | | | SDKs which aren't built from an image recipe should also come with drop-in symlinks for `/bin`, `/lib` and `/sbin`. Support this by moving the common functionality into `populate_sdk_base` and enabling the symlink creation when the `usrmerge` DISTRO_FEATURE is on. (From OE-Core rev: 8e1e86cc9d5d4e866ff0ab62c8954db0e65c19e6) Signed-off-by: Philip Lorenz <philip.lorenz@bmw.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: enable create-log-dirsChangqing Li2025-01-031-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | By default, create-log-dirs is enabled in systemd, and a link /var/log/README will be created, point to {{DOC_DIR}}/README.logs, but, for oe, there are two problems here, firstly, DOC_DIR is packaged in another package systemd-doc, so /var/log/README is a dead link when systemd-doc is not installed, secondly, even systemd-doc is installed, when volatile log is used, DOC_DIR is a wrong relateive path, Refer [1]. So in commit [2], we disable create-log-dirs for above issue. with this change, /var/log/journal is not created, and /run/log is used, this makes systemd log always non persistent, refer [3][4]. if user need persistent log, they need to disable volatile log, and also change journald.conf, make "Storage" to "persistent". This is a behavoir change. Previously, to make systemd log persistent, user only need to disable volatile log. This commit reenable create-log-dirs to revert the behavior change, and since README is not very userful, just remove it. [ YOCTO #15678 ] [1] https://github.com/systemd/systemd/blob/main/tmpfiles.d/legacy.conf.in#L16 [2] https://git.openembedded.org/openembedded-core/commit/?id=18d46e11d85da1f6feaba5a135931e43060024d6 [3] https://github.com/systemd/systemd/blob/main/src/journal/meson.build#L189 [4] https://www.freedesktop.org/software/systemd/man/journald.conf.html [5] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15678 (From OE-Core rev: f82d9c997ba8cc23b472d44a43489c597bf452af) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: upgrade 257 -> 257.1Wang Mingyu2025-01-034-1/+1
| | | | | | | | (From OE-Core rev: 4c4f4798862d80f44e03ccbbe7efc2d8b723968c) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.bbclass: Lower the length of TMPDIR limit to 400Changqing Li2025-01-031-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When TMPDIR has length 410, bitbake uninative-tarball will fail at do_populate_sdk with error: Failed to open backup database: "TMPDIR/work/x86_64-nativesdk-pokysdk-linux/uninative-tarball/1.0/sdk/image/var/lib/dnf/history.sqlite" sqlite3 has a hardcode max pathname limit 512, refer [1], and there is a check, refer [2], pathname + 8 > max path name limit(512) is not allowed. So the pathname length need to <= 504. While, length of "TMPDIR/work/x86_64-nativesdk-pokysdk-linux/uninative-tarball/1.0/sdk/image/var/lib/dnf/history.sqlite" is 505, so error happened. We had met similar issue [3], and refer the comments, upstream reject the change of the hardcode length, see [4][5]. This patch try to improve and workaround this issue by lower max TMPDIR length to 400, at least for distro name length <=13, the build can success. [1] https://github.com/sqlite/sqlite/blob/master/src/os_unix.c#L180 [2] https://github.com/sqlite/sqlite/blob/master/src/pager.c#L4777 [3] https://bugzilla.yoctoproject.org/show_bug.cgi?id=12374 [4] https://sqlite.org/cgi/src/tktview/c060923a5422590b3734 [5] https://sqlite.org/forum/forumpost/0b1b8b5116 (From OE-Core rev: da1c0998bdaf5def7ae94f44a33b9a505edc99c1) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/bitbake.conf: move addfragments to just after the local.conf includeAlexander Kanavin2025-01-031-3/+5
| | | | | | | | | | | | | There was a report that the existing addfragments statement comes in too late, specifically after the DISTRO/MACHINE includes have already been handled. The goal for fragments content is to behave exactly like the settings in local.conf would and so we need to handle the fragments just after that file. (From OE-Core rev: e820fa96d078478ea3510164373989090e8c9419) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-tools-profile: skip VALGRIND for loongarch64Hongxu Jia2025-01-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Due to packagegroup-core-tools-profile run time depend on package valgrind and recipe valgrind does not support loongarch64, then skip VALGRIND for loongarch64 $ echo "MACHINE = 'qemuloongarch64'" >> conf/local.conf $ bitbake world |ERROR: Nothing RPROVIDES 'valgrind' (but oe-core/meta/recipes-core/ packagegroups/packagegroup-core-tools-profile.bb RDEPENDS on or otherwise requires it) |valgrind was skipped: incompatible with host loongarch64-wrs-linux (not in COMPATIBLE_HOST) |NOTE: Runtime target 'valgrind' is unbuildable, removing... |Missing or unbuildable dependency chain was: ['valgrind'] |ERROR: Required build target 'meta-world-pkgdata' has no buildable providers. |Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'packagegroup-core-tools-profile', 'valgrind'] (From OE-Core rev: 2ef616b4e43f5c4d3155201f743e48d6ff6bb400) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-tools-testapps: skip KEXECTOOLS for loongarch64Hongxu Jia2025-01-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Due to recipe packagegroup-core-tools-testapps run time depend on package kexec and recipe kexec-tools does not support loongarch64, then skip KEXECTOOLS for loongarch64 $ echo "MACHINE = 'qemuloongarch64'" >> conf/local.conf $ bitbake world |ERROR: Nothing RPROVIDES 'kexec' (but oe-core/meta/recipes-core/packagegroups/ packagegroup-core-tools-testapps.bb RDEPENDS on or otherwise requires it) |kexec-tools RPROVIDES kexec but was skipped: incompatible with host loongarch64-wrs-linux (not in COMPATIBLE_HOST) |NOTE: Runtime target 'kexec' is unbuildable, removing... |Missing or unbuildable dependency chain was: ['kexec'] |ERROR: Required build target 'meta-world-pkgdata' has no buildable providers. |Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'packagegroup-core-tools-testapps', 'kexec'] (From OE-Core rev: 37ff515da6e13126f8822b3a55e44cdc62882a51) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-module-install: remove loongarch64 from COMPATIBLE_HOSTHongxu Jia2025-01-032-2/+2
| | | | | | | | | | | | | | | | | | | | | | | Due to initramfs-module-install runtime depend on grub, and grub did not support loongarch64, remove loongarch64 from COMPATIBLE_HOST $ echo "MACHINE = 'qemuloongarch64'" >> conf/local.conf $ bitbake world |ERROR: Nothing RPROVIDES 'grub' (but oe-core/meta/recipes-core/initrdscripts/ initramfs-module-install_1.0.bb RDEPENDS on or otherwise requires it) |grub was skipped: incompatible with host loongarch64-wrs-linux (not in COMPATIBLE_HOST) |NOTE: Runtime target 'grub' is unbuildable, removing... |Missing or unbuildable dependency chain was: ['grub'] |ERROR: Required build target 'meta-world-pkgdata' has no buildable providers. |Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'initramfs-module-install', 'grub'] (From OE-Core rev: 6440e1010ade2b4207879a2e8cd288bcd714a445) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: upgrade 3.13.0 -> 3.13.1Trevor Gamblin2025-01-033-111/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changelog: https://docs.python.org/3/whatsnew/changelog.html#python-3-13-1-final - Patch 'fix-armv5.patch' is in 3.13.1, so no longer needed: |tgamblin@megalith ~/workspace/git/pythonsrc/cpython ((HEAD detached from v3.13.1))$ git tag --contains 18b9079ddbc149d6b99c922630c246812e4d8ae7 |v3.13.1 - While patch 'crosspythonpath.patch' is listed as 'Inappropriate [OE-Core integration specific]' specific in the commit message, it is now breaking the build, while removing it allows python3 to build OK. It appears that there is a similar change in upstream 3.13.1: https://github.com/python/cpython/commit/909d5ac2959e - gcc-symlinks had to be added to ptest RDEPENDS so that 'gcc' could be found on the path for the test_ctypes.test_dlerror.TestNullDlsym.test_null_dlsym test. - Also reformat the DEPENDS and RDEPENDS lists to be alphabetical and one-per-line, since that's easier to read and modify. - buildall-qemu output: |BUILDALL-QEMU LOG FOR python3 |START TIME: 2024-12-18_20:38:01 |HOSTNAME: megalith |HOST OS: Debian GNU/Linux 12 (bookworm) |HOST KERNEL: 6.1.0-28-amd64 |=============== |BUILD RESULTS: |[glibc] |FAIL: qemuloongarch64 |PASS: qemuriscv32 |PASS: qemuarmv5 |PASS: qemuppc |PASS: qemumips64 |PASS: qemuriscv64 |PASS: qemuarm64 |PASS: qemuarm |PASS: qemux86-64 |PASS: qemuppc64 |PASS: qemux86 |PASS: qemumips |[musl] |FAIL: qemuloongarch64 |FAIL: qemuriscv32 |PASS: qemuarmv5 |PASS: qemuppc |PASS: qemumips64 |PASS: qemuriscv64 |PASS: qemuarm64 |PASS: qemuarm |PASS: qemux86-64 |PASS: qemuppc64 |PASS: qemux86 |PASS: qemumips |=============== |PASSED: 21 |FAILED: 3 (From OE-Core rev: 08c44d3b140b220ead6334db26097b28612d445a) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libdnf: backport patch to fix segfaultTrevor Gamblin2025-01-032-0/+85
| | | | | | | | | | | | This is needed to allow libdnf to build OK with python 3.13.1. Without it, a vague "Could not invoke dnf" error is seen during rootfs (e.g. when building core-image-full-cmdline), with a return code of -11. (From OE-Core rev: 5104807bdb952e90e831759266bd830d523e3d16) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: upgrade from 256.9 to 257Chen Qi2025-01-0333-566/+604
| | | | | | | | | | | | | | | | | Patch changes: * 0003-coredump-set-ProtectHome-to-read-only.patch is drop as it's a backported patch. * 0009-don-t-pass-AT_SYMLINK_NOFOLLOW-flag-to-faccessat.patch is drop as AT_SYMLINK_NOFOLLOW has been supportd in musl. * Other patches are either refreshed or changed to fit the current version. systemd-boot changes: * Use src/boot instead src/boot/efi in do_install and do_deploy. See upstream change 97318131fd06 (Rename src/boot/efi to just src/boot). (From OE-Core rev: 4891f47cdaf919033bf1c02cc12e4805e5db99a0) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-attrs: upgrade 24.2.0 -> 24.3.0Richard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: 30a7c3c7a1e12b7fb2463e7135d97a478e763c9e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xxhash: upgrade 0.8.2 -> 0.8.3Richard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: 15216916a2ea00738553ff96734e90146a1f184c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-urllib3: upgrade 2.2.3 -> 2.3.0Richard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: a4397139fbe9313f7f80d0accc7a9e9565d07805) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-ruamel-yaml: upgrade 0.18.6 -> 0.18.7Richard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: f98c9c192f62f495f07c5a5fb2fe486ca0fe0494) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pyparsing: upgrade 3.2.0 -> 3.2.1Richard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: 3238994e20864b57d302eee28c29892d71e5140f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-maturin: upgrade 1.7.8 -> 1.8.1Richard Purdie2025-01-032-57/+91
| | | | | | (From OE-Core rev: 4a208683cb875cdb8907040e865e7adaae912aee) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-hypothesis: upgrade 6.122.6 -> 6.123.2Richard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: 316ae45adbe150792a1e095bd5b0777937578e8b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-cryptography{,-vectors}: upgrade 43.0.3 -> 44.0.0Richard Purdie2025-01-035-43/+47
| | | | | | (From OE-Core rev: c3c612608d816eb6b40575a86e0907701cf525dc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* puzzles: upgrade to latest revisionRichard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: f98d6f604272f5031552e4cf440c1fa7499f0d43) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* piglit: upgrade to latest revisionRichard Purdie2025-01-036-11/+8
| | | | | | (From OE-Core rev: 16dd4c836a5c8d71f0a5f4dffcf0c160956fea67) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nettle: upgrade 3.10 -> 3.10.1Richard Purdie2025-01-033-12/+6
| | | | | | (From OE-Core rev: 601327a0c8a66226877f03b21bad0c7e67ee14de) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libical: upgrade 3.0.18 -> 3.0.19Richard Purdie2025-01-032-6/+3
| | | | | | (From OE-Core rev: 0045f51478e49755b61088f5ff6a4e6d3efbb06b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcap: upgrade 2.71 -> 2.73Richard Purdie2025-01-034-7/+7
| | | | | | (From OE-Core rev: 4b5978ca9c7280beaf1ca7cf3c1f9f1baed0bd08) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* init-system-helpers: upgrade 1.67 -> 1.68Richard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: e901a0f154fe6149b9cfb9b0e7b9289f31f441b9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gpgme: upgrade 1.24.0 -> 1.24.1Richard Purdie2025-01-0310-39/+27
| | | | | | (From OE-Core rev: abbc6639b74fe7e19802e764ca438d897b9ae92c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* debianutils: upgrade 5.20 -> 5.21Richard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: 34907f324c1362d1510300501a5bdff6eb99ae9b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cracklib: upgrade 2.10.2 -> 2.10.3Richard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: 4bcd39044064e61a00b37637314717663c6b3ef0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake-native,cmake: upgrade 3.31.0 -> 3.31.3,3.31.0 -> 3.31.3Richard Purdie2025-01-036-5/+5
| | | | | | (From OE-Core rev: 0d73ac24ae8ce2318e95db0203df4bfdaba60ae5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ca-certificates: upgrade 20240203 -> 20241223Richard Purdie2025-01-036-29/+38
| | | | | | (From OE-Core rev: 48a236c2f78fee5e6db19c6be23b4a18df025607) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bash-completion: upgrade 2.15.0 -> 2.16.0Richard Purdie2025-01-031-1/+1
| | | | | | (From OE-Core rev: 4be37279bf7b098382966fc81b24962a157b31c3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-passwd: upgrade 3.6.5 -> 3.6.6Richard Purdie2025-01-038-8/+8
| | | | | | (From OE-Core rev: 29e96baca3916c2f686717e922c079a332b21970) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: doc: update releases.rstAntonin Godard2024-12-281-9/+10
| | | | | | | | | | Add Styhead as a supported release manual, and move Dunfell to the outdated releases manuals. (Bitbake rev: d726f4537f16d99512b21ab0a0f476cef832b955) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: doc/bitbake-user-manual-metadata: fix unindent warningsAntonin Godard2024-12-281-3/+3
| | | | | | | | | | | | | Fix Sphinx warnings (treated as errors on local builds): bitbake-user-manual-metadata.rst:979: WARNING: Bullet list ends without a blank line; unexpected unindent. bitbake-user-manual-metadata.rst:982: WARNING: Bullet list ends without a blank line; unexpected unindent. bitbake-user-manual-metadata.rst:985: WARNING: Bullet list ends without a blank line; unexpected unindent. (Bitbake rev: 51d89ce0fc8d188bf10a8bcc6a112466268899ae) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* migration-guides: update the release notes for 5.2Antonin Godard2024-12-282-2/+399
| | | | | | | | | | | | | | Update the release note and migration guide for the 5.2 release. This release is not due until April 2025, but this catches up what has already been applied since 5.1. Precisely, this tracks the important changes between commits 8149e74258 and 87d7341465 in poky. (From yocto-docs rev: a51a94f0b228d570d915dff36a49132e90e93cf1) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>