summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* kernel-module-split: make autoload and probeconf distribution specificJose Quaresma2023-07-201-5/+8
| | | | | | | | | | | | | | | | | | | | | | The modules-load.d [1] - Configure kernel modules to load at boot should install their configuration files in /usr/lib/modules-load.d. The modprobe.d [2] - Configuration directory for modprobe should install their configuration files in /lib/modprobe.d [1] https://man7.org/linux/man-pages/man5/modules-load.d.5.html [2] https://man7.org/linux/man-pages/man5/modprobe.d.5.html [YOCTO #12212] https://bugzilla.yoctoproject.org/show_bug.cgi?id=12212 CC: Ola x Nilsson <Ola.x.Nilsson@axis.com> CC: Peter Kjellerstedt <peter.kjellerstedt@axis.com> (From OE-Core rev: 6725922eadd093e8ee6a41898b596b5563eab0f3) Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 347830e67c5ad72b4da165d644e3add69c20acb8) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* kernel-module-split: use context manager to open filesJose Quaresma2023-07-201-13/+10
| | | | | | | | | (From OE-Core rev: 8fbf05a91667a054083b45632c1f8afb6b8e1367) Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit fc9c9471952042395bb405e7f6cf507bb2b72f31) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* kernel-module-split: install config modules directories only when they are ↵Jose Quaresma2023-07-201-22/+13
| | | | | | | | | | | | | | | needed Instaed of allways create the directories and removing it at the if they are not used, we can just do it when there are modules configuration to be created. So the best thing to do is install the directories only when necessary. (From OE-Core rev: 455baf41550431c22047fe718c8eaae71924b23f) Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 71460993f350bca3d5a22115fd5551696f955c9f) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* kernel: config modules directories are handled by kernel-module-splitJose Quaresma2023-07-201-2/+0
| | | | | | | | | (From OE-Core rev: e5b478fb435c96f6d6e8c2a93d6c54df996957e1) Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 38dc75c0e5eb7427ffcf201113fb45e0d5dad453) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* recipetool: Fix inherit in created -native* recipesYoann Congal2023-07-201-0/+4
| | | | | | | | | | | | native and nativesdk classes are special and must be inherited last : put them at the end of the gathered classes to inherit. (From OE-Core rev: 6de7a92c4366f8b15ff97e53be91db31348b3922) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit a6614fd800cbe791264aeb102d379ba79bd145c2) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* ifupdown: install missing directoriesYi Zhao2023-07-201-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are four directories in which scripts can be placed which will always be run for any interface during certain phases of ifup and ifdown commands: /etc/network/if-pre-up.d/ /etc/network/if-up.d/ /etc/network/if-down.d/ /etc/network/if-post-down.d/ Even if there are no scripts in these directories, ifup and ifdown commands will also search these directories by using run-parts command. Install these directories to fix the following runtime errors: $ cat /etc/network/interfaces auto lo iface lo inet loopback $ ifdown lo ifdown: interface lo not configured $ ifup lo run-parts: failed to open directory /etc/network/if-up.d: No such file or directory ifup: failed to bring up lo (From OE-Core rev: c248473e2d60cfa67c64aa586b404119dec728ff) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 277bc7ab1fedd81f4df578e544ec381c819a10f9) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* libxcrypt: fix hard-coded ".so" extensionEtienne Cordonnier2023-07-201-6/+0
| | | | | | | | | | | | | | | 2 issues: - the .so extension is hard-coded, and therefore the libxcryt package compiled with meta-darwin is empty, because the dylib files are not contained in FILES_${PN} - nothing actually produces a file libcrypt-*.so (the symlink file is libcrypt.so, without dash), thus defining FILES:${PN} manually to contain libcrypt-*.so has no effect. (From OE-Core rev: 06f8aaf8ee03b07f79e1a17708b5946782e389bd) Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 7ed6bfa2428b4f1ba7f09d6e9e67c462ff355153) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* rust-common.bbclass: move musl-specific linking fix from rust-source.incAlexander Kanavin2023-07-202-5/+4
| | | | | | | | | | | | | This needs to be done for any item that is linked under rustc, and not just rust itself. Latest python-cryptography exposes the issue. (From OE-Core rev: 967d847a9815df43d0c92ca61cc544e1fe5dcc03) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit d3811228747590ea06e8d68be4785d45ec9c478f) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* cargo.bbclass: set up cargo environment in common do_compileAlexander Kanavin2023-07-202-1/+4
| | | | | | | | | | | | | | | | | cargo_do_compile runs only if the recipe is built using cargo as the top level tool. Some recipes hide usage of cargo inside setuptools (or autoconf) and use do_compile definitions specific to those, and so the environment isn't properly set up. This was exposed by latest versions of python3-cryptography. (From OE-Core rev: a1946efdbec608d47f9e992c1b5cf3c671a204fc) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 9f4ff643a028d7f5670d80861f2ce19ca2d90faa) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* baremetal-helloworld: Fix race conditionAlejandro Hernandez Samaniego2023-07-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | There was a race condition during the Makefile execution in between the assemble and compile targets, only the assemble target had a dependency on creating the build directory. If the compile target was executed first, an error was thrown by bitbake since the build directory did not exist yet: | Assembler messages: | Fatal error: can't create build/hello_baremetal_aarch64.o: No such file or directory Update the SRCREV to reflect the latest changes serializing the makefile targets to avoid such race condition from happening. [YOCTO #15146] (From OE-Core rev: fe637f795238685f5d8e4e3dbf48235dabb1cc17) Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandro@enedino.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 9a999af292c7b3dd3bb7c0722cc31624c425f432) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* weston: Cleanup and fix x11 and xwayland dependenciesTom Hochstein2023-07-201-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | For the x11 backend package config, drop the redundant dependencies libxcb and cairo. The former is listed twice in the package config, while the latter is also listed globally. For the xwayland package config, add the missing dependencies libxcb and libxcursor. These dependencies are hidden when the x11 backend is enabled by default. When the default setting is overridden to disable the x11 backend, the following error occurs: ``` | Run-time dependency xcursor found: NO (tried pkgconfig and cmake) | | ../git/xwayland/meson.build:34:2: ERROR: Problem encountered: xwayland requires xcursor which was not found. Or, you can use '-Dxwayland=false'. ``` (From OE-Core rev: d8d60e0a0e838c332f044ecee89b8ad2acae9567) Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 49f4dd391b408a850d13010c90492c621b7912c3) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* libproxy: fetch from gitAlexander Kanavin2023-07-201-3/+4
| | | | | | | | | | | | Upstream no longer provides tarballs for newer versions. (From OE-Core rev: 32b258f5ce261b2576d20e0dac4123fa020642d7) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit e971f27cb4ad78b4df3c3bca2948f3cb60d0d5cf) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* lttng-ust: upgrade 2.13.5 -> 2.13.6Wang Mingyu2023-07-201-1/+1
| | | | | | | | | | | | | | | | | | | | Changelog: =========== * Fix: segmentation fault on filter interpretation in "switch" mode * Fix: `ip` context is expressed as a base-10 field * Fix: c99: use __asm__ __volatile__ * Fix: c99: static assert: clang build fails due to multiple typedef * Fix: Reevaluate LTTNG_UST_TRACEPOINT_DEFINE each time tracepoint.h is included * Fix: trace events in C++ constructors/destructors * Fix: trace events in C constructors/destructors * Fix: use unaligned pointer accesses for lttng_inline_memcpy (From OE-Core rev: c4bfec4b2f092bd76292ad8a03917514626a3a8f) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 656470b4b0db579308d218d1ece77bdacd168d14) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* libx11: upgrade 1.8.5 -> 1.8.6Wang Mingyu2023-07-201-1/+1
| | | | | | | | | | | | | | Changelog: ========== InitExt.c: Add bounds checks for extension request, event, & error codes Fixes CVE-2023-3138 (From OE-Core rev: 5d6169ec81cc260fccb3b65082100e0ef6102046) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 49b74259b196454d22fcca8b8ecc1c0d41487285) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* libksba: upgrade 1.6.3 -> 1.6.4Wang Mingyu2023-07-201-1/+1
| | | | | | | | | | | | Changelog: Correctly detect CMS write errors. (From OE-Core rev: 319370ab4031454e9a026a5b7d582fc23882f139) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 0296cf63007542c1cb209a4288be1c82aa2ba843) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* libassuan: upgrade 2.5.5 -> 2.5.6Wang Mingyu2023-07-201-1/+1
| | | | | | | | | | | | | | | | Changelog: =========== * Fix logging of confidential data. [rA0fc31770fa] * Fix memory wiping. [T5977] * Fix macOS build problem. [T5440,T5610] * Upgrade autoconf stuff. (From OE-Core rev: 569df0fb19ee9199fa9c3d86bb5bb75252b3c663) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 90126be6dc32170c08eb90223b6a6cc06c2133ce) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* gstreamer1.0: upgrade 1.22.3 -> 1.22.4Wang Mingyu2023-07-2011-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bugfixes: ========== - Security fixes for flacparse, dvdspu, and subparse - d3d11videosink: Fix error on pause and play - decklink: Correctly handle SDK strings on macOS and free strings after usage on Linux - filesink: Fix buffered mode writing of buffer lists and buffers with multiple memories - gldownload: handle passthrough without a critical - h265parse: Fix framerate handling regression - oggdemux: vp8 fixes - mp4mux, qtmux, qtdemux: Opus audio mapping fixes - pngdec: Fix wrong colours output from 16bit RGB images - ptp clock: Work around ptpd bug in default configuration - srtpdec: fix critical warnings on shutdown - v4l2src: fix support for bayer format - v4l2videoenc: support force-keyframe event in v4l2 encoder - vtenc: apply DTS offset to ensure DTS <= PTS - gst-python: allow more functions to be called before gst_init() - cerbero: fix vaapi variant; add qt6 build on windows; ensure errors on unguarded use of new APIs, require macOS 10.13 - packages: ship codecalpha, rtponvif, dvbsubenc, switchbin, videosignal plugins; fix pango crash on 32-bit windows - various bug fixes, memory leak fixes, and other stability and reliability improvements (From OE-Core rev: a071696747ece93409d533a2e966cd59195a056d) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit d7bf88db7f2f55540bf7891474a3a28f5681ddbb) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* freetype: upgrade 2.13.0 -> 2.13.1Wang Mingyu2023-07-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | Changelog: =========== * docs/VERSION.TXT: Add entry for version 2.13.1. * docs/CHANGES: Updated. * docs/release, docs/README, builds/macs/README: Updated. * README, src/base/ftver.rc, builds/windows/vc2010/index.html, builds/windows/visualc/index.html, builds/windows/visualce/index.html, builds/wince/vc2005-ce/index.html, builds/wince/vc2008-ce/index.html, docs/freetype-config.1: s/2.13.0/2.13/1/, s/2130/2131/. * include/freetype/freetype.h (FREETYPE_PATCH): Set to 1. * builds/unix/configure.raw (version_info): Set to 26:0:20. * CMakeLists.txt (VERSION_PATCH): Set to 1. * subprojects/libpng.wrap, subprojects/zlib.wrap, subprojects/dlg: Updated. (From OE-Core rev: b89e75cd39ee704e677ab1e770884cd53cd7f1e8) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 4447b2db3166bd8c76271f0293931392572c6977) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* diffutils: update 3.9 -> 3.10Alexander Kanavin2023-07-202-13/+8
| | | | | | | | | | | | | | | | | | | | | | | | * Noteworthy changes in release 3.10 (2023-05-21) [stable] ** Bug fixes cmp/diff can again work with file dates past Y2K38 [bug introduced in 3.9] diff -D no longer fails to output #ifndef lines. [bug#61193 introduced in 3.9] Remove the comment addition from the patch body, as it increases likelyhood of rebase conflicts, and repeats what the commit says. (From OE-Core rev: 21e40166870fadee986fb36be80019d3bcdb69e5) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 925155acc6922f7e9df2afa45e79ad1b2c57ba24) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* erofs-utils: fix CVE-2023-33551/CVE-2023-33552Changqing Li2023-07-205-0/+529
| | | | | | | | | | | | * CVE-2023-33551.patch is for fix CVE-2023-33551. * CVE-2023-33552-3.patch is upstream patch for fix CVE-2023-33552, since the patch context is changed, CVE-2023-33552-1.patch and CVE-2023-33552-2.patch is backported. (From OE-Core rev: 77b5c2f68ea0eef45e77936ce3e7caafa7bd3f54) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
* ghostscript: fix CVE-2023-36664Joe Slater2023-07-202-0/+166
| | | | | | | | | | | Combine two commits from git.ghostscript.com/ghostpdl. The first incompletely addresses the CVE. The second addresses defects in the first. (From OE-Core rev: 8173939cfa4d0be8c0ffaa45e371945b1f7a16ae) Signed-off-by: Joe Slater <joe.slater@windriver.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
* dmidecode: fix CVE-2023-30630Yogita Urade2023-07-205-0/+528
| | | | | | | | | | | | | | | | Dmidecode before 3.5 allows -dump-bin to overwrite a local file. This has security relevance because, for example, execution of Dmidecode via Sudo is plausible. References: https://nvd.nist.gov/vuln/detail/CVE-2023-30630 https://lists.nongnu.org/archive/html/dmidecode-devel/2023-04/msg00016.html https://lists.nongnu.org/archive/html/dmidecode-devel/2023-04/msg00017.html (From OE-Core rev: f92e59a0894145a828dc9ac74bf8c7a9355e0587) Signed-off-by: Yogita Urade <yogita.urade@windriver.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
* python3-requests: fix CVE-2023-32681Chee Yang Lee2023-07-202-0/+63
| | | | | | | (From OE-Core rev: 11b6e64c07df043441824511c931fb0bc9673adc) Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
* cve-update-nvd2-native: actually use API keysRoss Burton2023-07-131-11/+12
| | | | | | | | | | | | | | | There were vestigal remains of API key support which could be removed, but as using an API key - in theory - gives the user larger rate limits it's probably wise to expose it. If the user has an API key, then set NVDCVE_API_KEY. (From OE-Core rev: 64784e90c5ff559f4da6faadb970cc7aff549592) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit a542de684282bfec79f24ae2f1a2027ffde319d8) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* cve-update-nvd2-native: log a little moreRoss Burton2023-07-131-5/+7
| | | | | | | | | | | | | Add a note of what range we're fetching, and use bb.note() instead of debug() as messages about retrying shouldn't really be considered debug logging. (From OE-Core rev: cc82df9c0ff8ba17196b578e0182a5c726cfbbff) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit b64a869b9c5e1d504f1011da16b5c5ff721afbf0) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* cve-update-nvd2-native: increase retry countPeter Marko2023-07-131-1/+1
| | | | | | | | | | | | | | | | | Current 503 errors seem to last several seconds. In most cases there are two errors and third request succeeds. However sometimes the outage takes more than time needed for two retries and third one also fails. Extend retry count from 3 to 5 to improve the probablity that the fetcher succeeds. (From OE-Core rev: 5ca193e287c54bcb17f26e82e61e9446c21cd7e4) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit f4d118af2360cff7f234102fd5e4b65a6f4146a6) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* cve-update-nvd2-native: retry all errors and sleep between retriesPeter Marko2023-07-131-7/+4
| | | | | | | | | | | | | | | | | | | | Last couple days it is not possible to update NVD DB as servers are returning lot of errors. Mostly "HTTP Error 503: Service Unavailable" is observed but sporadially also some others. Retrying helps in most cases, so extend retries to all errors. Additionally add sleep which is recommended by NVD between requests. These retries are already implemented between successful requests, but giving servers time between failed ones is important, too. (From OE-Core rev: 75d2c50a10b8b506096b43a15bca3f06c6734e2f) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 88dad8f198baa80af5ab576498f4df6ed639d551) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* cve-update-nvd2-native: fix cvssV3 metricsPeter Marko2023-07-131-4/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After upgrade to soon-to-be-released kirkstone 4.0.11 CVE annotations got broken. Anything which has only cvssV3 does not resolve properly. Fix the API fields used to extract it. i0.0 score is now at level of NVD DB 1.1. All CVEs with UNKNOWN vector are not present in NVD DB 1.1. NVD API 1.1: sqlite> select vector, count(vector) from nvd group by vector; ADJACENT_NETWORK|4776 LOCAL|32146 NETWORK|167746 PHYSICAL|185 sqlite> select scorev3, count(scorev3) from nvd group by scorev3; 0.0|73331 1.8|7 1.9|3 ... NVD API 2.0 (broken): sqlite> select vector, count(vector) from nvd group by vector; ADJACENT_NETWORK|4587 LOCAL|26273 NETWORK|150421 UNKNOWN|24644 sqlite> select scorev3, count(scorev3) from nvd group by scorev3; 0.0|205925 NVD API 2.0 (fixed): sqlite> select vector, count(vector) from nvd group by vector; ADJACENT_NETWORK|5090 LOCAL|32322 NETWORK|168004 PHYSICAL|213 UNKNOWN|511 sqlite> select scorev3, count(scorev3) from nvd group by scorev3; 0.0|73841 1.8|7 1.9|3 ... (From OE-Core rev: babf20391305e514ddcd24be261b9b8487c8c767) Signed-off-by: Peter Marko <peter.marko@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 61a5857efdcc0f49c69c0deb24fce99007aeef19) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* cve-update-nvd2-native: use exact times, don't truncateRoss Burton2023-07-131-2/+2
| | | | | | | | | | | | | | | When requesting updates in a specific range, use the actual current time and database mtime instead of truncating to midnight, and explicitly set the timezone to UTC so that NIST don't treat the timestamps as _their_ local time when they're _our_ local time. (From OE-Core rev: aa03556732b295fcf4bc2de11e3bc2e2b364580e) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 9aa0ec37f5f74252588d2494a71c71a7d8e68df9) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* cve-update-nvd2-native: handle all configuration nodes, not just firstRoss Burton2023-07-131-4/+5
| | | | | | | | | | | | | | | | | Some CVEs, such as CVE-2013-6629, list multiple configurations which are vulnerable. The current JSON parser only considers the first configuration. Instead, consider every configuration. We don't yet handle the AND/OR logical operators, but this is a step in the right direction. (From OE-Core rev: a2d50c0fd1e1be869d8786b920f8b428a3292ed1) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit e1bf4f6dd686055fe9a8bdcc3f739eac2807bae0) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* build-appliance-image: Update to mickledore head revisionyocto-4.2.2mickledore-4.2.2Steve Sakoman2023-07-071-1/+1
| | | | | | (From OE-Core rev: 3ef283e02b0b91daf64c3a589e1f6bb68d4f5aa1) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* poky.conf: bump version for 4.2.2 releaseSteve Sakoman2023-07-071-1/+1
| | | | | | (From meta-yocto rev: ab16a59e94258be5a923f221ba06396b26dfab59) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* Revert "systemd: fix a dead link under /var/log"Steve Sakoman2023-07-072-43/+0
| | | | | | | | | | Needs to go to master branch before stable branches. This reverts commit 7702dc8fc6c9b34647067ffabbc0e24d6109abe7. (From OE-Core rev: ac4c9f5aa967507d028caa3ee70f3fce580f9a09) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* rootfs-postcommands.bbclass: add post func remove_unused_dnf_log_lockChangqing Li2023-07-071-0/+7
| | | | | | | | | | | | Remove log_lock.pid which maybe created during do_rootfs. In commit [dnf: only write the log lock to root for native dnf], native dnf changed to write log lock to root, and target dnf still use /var/log, so log_lock.pid need to be removed post do_rootfs. (From OE-Core rev: 595fbe4c9ad25e52e88d7bcf1d1864fe5ec324a5) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
* dnf: only write the log lock to root for native dnfChangqing Li2023-07-071-1/+2
| | | | | | | | | | | | | | | | | | From commit 742a1b7124, log_lock.pid is writen to root, but following file is not changed, which will make it never deleted, and an unexpected file exist in root dir after boot target. $ tail -n 1 etc/tmpfiles.d/dnf.conf r /var/log/log_lock.pid Besides, root dir may be read-only, so it is better still keep the log_lock.pid under /var/log, only write the log lock to root for native dnf for fixing issue mentioned in 742a1b7124 (From OE-Core rev: 207cc7acef40f92b5de306aa6f035258c0eec828) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
* ptest-runner: Pull in "runner: Remove threads and mutexes" fixRichard Purdie2023-07-071-1/+1
| | | | | | | | | | | | This fix simplifies the code to drop the pthread and mutexs which should address some of the buffering issues we were seeing in some test case failures. (From OE-Core rev: c0ebc132c279d3195aa8ed086d596ed1b000cc2a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit bffa6d381d7ea0a6aad19d61cd973c82aadef070) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* ptest-runner: Ensure data writes don't raceRichard Purdie2023-07-071-1/+1
| | | | | | | | | | | | | | | Currently the code can race as there is a read/write thread handling the stdio but there is no guarantee that when the process exits, the thread has handled all the data. This results in output where "END:" isn't actually at the end of the logs but somewhere in the middle of the output. Update to a revision with this fix. (From OE-Core rev: d73b83da26722890dac8ac9bea19890927b9ea3b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 6608ee551ed7e8864cdeabfb09832621313d3191) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* ptest-runner: Pull in sync fix to improve log warningsRichard Purdie2023-07-071-1/+1
| | | | | | | | | | | | | | | | | | | | | Pulls in: utils: Ensure buffers are flushed after child exits We currently wait for the child to exit but we don't flush the buffers. This can mean the output ends up out of sync and the END: line isn't at the end of the logs. We've recently seen a lot of issues related to this on the autobuilder. Add in a flush call for all fds to ensure buffers are in sync. This does appear to improve warnings on the autobuilder now we started detecting the issue. (From OE-Core rev: 0c484c5aa054f4a8f7794bba18b1d0d168dbb941) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit f051de5d5da7e9a2f4137013e24589b594ff6d35) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* logrotate: Do not create logrotate.status fileJermain Horsman2023-07-071-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | The first time logrotate runs it reports an error: error: state file /var/lib/logrotate.status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition... This check was added with https://github.com/logrotate/logrotate/commit/1f76a381e2caa0603ae3dbc51ed0f1aa0d6658b9 This error is only reported once as logrotate removes the world-readable permissions if this happens. Since logrotate creates this file if it does not exist, there should be no need to install it in the first place. (From OE-Core rev: d081071c99a814e43cdd2c3ca92892c10b631692) Signed-off-by: Jermain Horsman <jermain.horsman@nedap.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 8169cd2d18f1569e4357f082adbef492710e8c36) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* sysfsutils: fetch a supported fork from githubAlexander Kanavin2023-07-071-7/+3
| | | | | | | | | | | | | Debian does the same: https://packages.debian.org/source/sid/sysfsutils (From OE-Core rev: 0bf67fadffa24c00452acb25c58c1eb5648fe4c4) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 504b2f590cb94b217c5f48090cfb71a749bd5ac8) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* unzip: remove hardcoded LARGE_FILE_SUPPORTChen Qi2023-07-071-3/+0
| | | | | | | | | | | | | | Now that unzip's configure can correctly do the detection even in case of cross compilation, there's no need to use this hardcoded LARGE_FILE_SUPPORT flag. (From OE-Core rev: b7006ca2f56292312937fd1fa33e62ff908fad9f) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit dca7d1ce696e97ff4213dd63981f901dfd43ade2) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* unzip: fix configure check for cross compilationChen Qi2023-07-072-0/+104
| | | | | | | | | | | | | | The original configure runs a generated binary to determine features. This is not correct for cross compilation. So change the runtime tests into compile-time tests to fix the issue. (From OE-Core rev: ed61afde823bcd3eddb984a57c9dec317f8bbbf3) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit b9aca339b59238988c48b90ea5019bfc939ba4b3) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* zip: remove unnecessary LARGE_FILE_SUPPORT CLFAGSChen Qi2023-07-071-3/+0
| | | | | | | | | | | | | | As the zip's configure has been updated to use compile-time check, it now can do the check correctly, thus no need to pass LARGE_FILE_SUPPORT to CFLAGS. (From OE-Core rev: 0efe5f77027b902b276c925ed09caf5062f51170) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 601f45bc4e6c563ebf16e724d56519a128815034) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* zip: fix configure check by using _Static_assertChen Qi2023-07-072-0/+97
| | | | | | | | | | | | | | | It's incorrect to run a cross-compiled program on build machine to check if some feature is available or not. As these two checks in zip are basically just checking the size, we can use _Static_assert and sizeof to do such check at compile time. (From OE-Core rev: a54619ba8deb6731fdac97a1fe21e7a6ed2b5a75) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit dda778d855b1838ae3004a9af310724b913490b4) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* python3-bcrypt: Use BFD linker when building testsKhem Raj2023-07-071-0/+1
| | | | | | | | | | | | | | | | Some of the tests use symbols from libpython3 e.g. PyBytes_FromStringAndSize but does not add it to linker cmdline, its perhaps cargo which should be fixed for that, this however is not something we can fix in OE. So switch to using bfd linker explicitly when building with ptests (From OE-Core rev: 353b9c765218ed631fc14a406fcdfe1c36a8237b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit b4392ebb512fa48168a48fbff3e9140a8e1b7ec4) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* glib-networking: use correct error code in ptestTrevor Gamblin2023-07-071-1/+1
| | | | | | | | | | | | | | The eagain patch is currently using G_IO_ERROR_BUSY as part of the check to retry when the simul_read_thread test fails during ptests, but the actual error code is 27, which corresponds to G_IO_ERROR_WOULD_BLOCK. Change the check so that it looks for the right code. (From OE-Core rev: 669bb92fde575d3f9674b87044575873c3506df5) Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 8574fb1371e2d83c1c7ee58067c50319a62a22ea) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* rpm: write macros under libdirChen Qi2023-07-071-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | If we create a macros file under etc/, the populate_sdk task would fail if 'package-management' is in SDKIMAGE_FEATURES and nativesdk-rpm-build is installed.. The error message is like below: unable to place /.../sdk/image/etc/rpm in final SDK location This is because it's trying to move the etc/rpm dictory into the host sysroot but the <host_sysroot>/etc/rpm has already exists. To solve this problem, avoid creating /etc/rpm/macros for nativesdk-rpm-build, use ${libdir}/macros instead. In this way, the macros file is hold in nativesdk-rpm. As nativesdk-rpm-build depends on nativesdk-rpm, the 'rpmbuild' command inside SDK can still correctly find find-debuginfo binary. (From OE-Core rev: 2a13a671910cad68ab962ce369b9ed60a9bf7eea) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 5fde0eadf16d34d88a599009013913fe55d89283) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* sdk.py: fix moving dnf contentsChen Qi2023-07-071-1/+2
| | | | | | | | | | | | The dnf contents should be moved to <host_sysroot>/etc/dnf/xxx instead of just <host_sysroot>/etc. (From OE-Core rev: 313f009e346a5aa10a09d65706c12ceefddaf59d) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 74b78d160a985e98f869c777847ab798e419dd2d) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* sdk.py: error out when moving file failsChen Qi2023-07-071-1/+1
| | | | | | | | | | | | Instead of printing an error message and continuing, we should just error out when moving file fails. (From OE-Core rev: 3a195a2da81755c2a030b5b0354ef177d826bdb2) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 12aecd9da94b5f27041982c661e8bab316d365d4) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* bitbake.conf: add unzstd in HOSTTOOLSAlberto Planas2023-07-071-1/+1
| | | | | | | | | | | | | | | | | | rpm2cpio.sh can make calls to unzstd to uncompress the RPM payload that conform the cpio file. zstd is already part of HOSTTOOLS, as a link to the system installed zstd. This patch add unzstd in HOSTOOLS list as a non-optional binary, so is available to rpm2cpio.sh when it is required. (From OE-Core rev: d59c5c1e78a1165bd2b00b3185ff8e9119aeaf9a) Signed-off-by: Alberto Planas <aplanas@suse.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit bff58d337890e804d33d7decbaa46065a4d3bba4) Signed-off-by: Steve Sakoman <steve@sakoman.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-04 16:19:52 +0000