summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* libnotify: remove dependency dbusKai Kang2023-04-131-1/+1
| | | | | | | | | | | | | It ported to use GDBus in libnotify 0.7.0 [1]. So remove dbus from DEPENDS. And GDBus is provided by glib-2.0. [1]: https://gitlab.gnome.org/GNOME/libnotify/-/commit/f63e8ab (From OE-Core rev: 3e585e41f561aab73685290631f2263795f571b9) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: wic: Add test for --part-name argumentDit Kozmaj2023-04-132-0/+30
| | | | | | | | | | | | | | | | | | | Add test for wic --part-name argument in .wks file. Test three different cases: - Set only the --part-name argument. - Set only the --label argument. In this case the GPT partition label is set to the value of --label for compatibility reasons. - Set both. In this case the code has been changed to set the GPT partition label to the --part-name value. The test uses a test_gpt_partition_name.wks file created for this purpose. (From OE-Core rev: 06af6795cf6f079362303bddb39a14459e228e72) Signed-off-by: Dit Kozmaj <dit.kozmaj@kynetics.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: use part_name when definedDit Kozmaj2023-04-131-10/+4
| | | | | | | | | | | | | | | So far part.label has been used to define GPT partition label even if part.part_name was defined. Fix the code to use part.part_name whenever available, as it makes sense to have a GPT partition label which is different from the contained filesystem label. (From OE-Core rev: 7704d5fc36eb065224792bf4d5543814eaa5fed3) Signed-off-by: Dit Kozmaj <dit.kozmaj@kynetics.com> Signed-off-by: Diego Rondini <diego.rondini@kynetics.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* logrotate: add ptest supportFrank WOLFF2023-04-133-2/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Below is an extract of the test log: root@qemux86-64:~# ptest-runner START: ptest-runner 2023-04-05T12:20 BEGIN: /usr/lib/logrotate/ptest make check-TESTS make[1]: Entering directory '/usr/lib/logrotate/ptest' make[2]: Entering directory '/usr/lib/logrotate/ptest' PASS: test-0001.sh PASS: test-0002.sh ... ... PASS: test-0107.sh PASS: test-0108.sh ============================================================================ Testsuite summary for logrotate 3.21.0 ============================================================================ # TOTAL: 102 # PASS: 97 # SKIP: 5 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 ============================================================================ make[2]: Leaving directory '/usr/lib/logrotate/ptest' make[1]: Leaving directory '/usr/lib/logrotate/ptest' DURATION: 353 END: /usr/lib/logrotate/ptest 2023-04-05T12:26 STOP: ptest-runner TOTAL: 1 FAIL: 0 Reviewed-by: Yoann CONGAL <yoann.congal@smile.fr> (From OE-Core rev: 0bdfe34c016c8db1f18d76b59a38af280b4c70aa) Signed-off-by: Frank WOLFF <frank.wolff@smile.fr> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* at-spi2-core: update 2.46.0 -> 2.48.0Markus Volk2023-04-131-10/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | What's new in at-spi2-core 2.48.0: * Add a "atk-only" build option. This allows atk to be built without libdbus installed, but it does not build libatspi or the atk bridge. * Fix some typos in the documentation. What's new in at-spi2-core 2.47.90: * Downgrade meson requirement to 0.63. * at-spi-dbus-bus service: set stop timeout to 5s * Fix possible crash in screen_reader_signal_watcher. What's new in at-spi2-core 2.47.1: * The meson options -Dx11 and -Dintrospection are now implemented with meson features - https://mesonbuild.com/Build-options.html#features Instead of accepting values of "yes/no/auto", they take "enabled/disabled/auto". Please change your build scripts accordingly if you use these options. * Use gi-docgen to generate documentation. * Register key grabs using the focused window, rather than the root window. This should prevent the window from losing focus when a key grab is used. * atk-adaptor: Handle sockets in GetChildren. * Improve documentation of the dbus interfaces. * Various code clean-ups. Some unused code has been removed. (From OE-Core rev: c589c87a8caef0afbc731c219fe713ba970a2055) Signed-off-by: Markus Volk <f_l_k@t-online.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gobject-introspection: reduce dependenciesPetr Kubizňák2023-04-131-5/+7
| | | | | | | | | | | | | | When GI_DATA_ENABLED is 'False' (e.g. because 'gobject-introspection-data' is not in DISTRO_FEATURES), gobject-introspection, gobject-introspection-native and qemu-native should not be added to DEPENDS. This is to reduce dependency chain when g-i is disabled. (From OE-Core rev: 4e51c1815c92bb15977a3bdb14171d770da44004) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot: Upgrade to 2023.04Fabio Estevam2023-04-135-44/+3
| | | | | | | | | | | | Upgrade to U-Boot 2023.04. Remove the patch that is now upstream. (From OE-Core rev: 57003af06d50fbbb33b94a4b10ea6c77fa294027) Signed-off-by: Fabio Estevam <festevam@denx.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ffmpeg: update 5.1.2 -> 6.0Alexander Kanavin2023-04-136-238/+54
| | | | | | | | | | Add a patch to gstreamer1.0-libav to address an API compatibility fail. (From OE-Core rev: 2ebea6658458ca926af58b4904cecdbec7416e04) 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>
* cve-exclusions: Document some further linux-yocto CVE statusesRichard Purdie2023-04-112-0/+16
| | | | | | | | | Add some information about some further kernel CVEs which don't apply for either linux-yocto or don't apply for linux-yocto 6.1. (From OE-Core rev: 85c1713bf0c01c68558bfba38edcc005c1ebb1c9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-extra-exclusion: ignore disputed CVE-2023-23005Yoann Congal2023-04-071-0/+10
| | | | | | | | (From OE-Core rev: 39274240b7756f498507b229d5f3461c207f1823) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Reviewed-by: Frank WOLFF <frank.wolff@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-exclusions_6.1: ignore patched CVE-2022-38457 & CVE-2022-40133Yoann Congal2023-04-071-0/+14
| | | | | | | | | | | | | | Ignore CVE-2022-38457 & CVE-2022-40133 as they looks patched in our 6.1 branch. I've asked the NVD to add the commit as the patch for these CVEs, but in the meantime, other sources seem to agree that the commit fixes these CVEs (and I concur). (From OE-Core rev: 990d1cbb1628577bd159e8266fa15976f1f17062) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2023-04-061-1/+1
| | | | | | (From OE-Core rev: 2bcb015b6fe72aa4c928741285c49d3d9ec55e85) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* manuals: improve and fix target for supported distrosMichael Opdenacker2023-04-063-4/+4
| | | | | | | | | | - Fix the location of the target for supported distributions - Improve the name of this target (From yocto-docs rev: 40f0cf9302b9f0ce01a1270977644b1b2fdfc650) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-extra-exclusions: ignore inapplicable linux-yocto CVEsYoann Congal2023-04-061-0/+25
| | | | | | | | | | | CVEs CVE-2023-0179, CVE-2023-1079 and CVE-2023-1513 are patched in our kernels but appear as active because the NVD database is not up to date. (From OE-Core rev: ae1e7999a06c56c6f752413296b8f6b505475f8b) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Reviewed-by: Frank WOLFF <frank.wolff@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cpio: Fix wrong CRC with ASCII CRC for large filesMarek Vasut2023-04-062-0/+40
| | | | | | | | | | | | | Due to signedness, the checksum is not computed when filesize is bigger a 2GB. Pick a fix for this problem from CPIO ML, where the fix has been posted for 5 years. Since CPIO upstream is effectively unresponsive and any and all attempts to communicate with the maintainer and get the fix applied upstream failed, add the fix here instead. (From OE-Core rev: bfff138af4bdd356ac66571e6ad91c1a5599b935) Signed-off-by: Marek Vasut <marex@denx.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa ping.py: fail test if target IP address has not been setMikko Rapeli2023-04-061-0/+1
| | | | | | | | | | | It is possible to call exported tests with --target-ip set to ":22" where IP address is not set at all. Detect this case and fail the test instead of calling ping without an IP address. (From OE-Core rev: 17c995c53775b8cee279ca4ced916092067e1195) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa ping.py: avoid busylooping failing ping commandMikko Rapeli2023-04-061-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use a sleep on error path before trying again. For example when oeqa runtime tests are executed without setting target IP address correctly, the tests are drowning logs with messages: 2023-04-04 07:19:24,985 - runtime - INFO - test_ping (ping.PingTest.test_ping) ping: usage error: Destination address required ping: usage error: Destination address required ping: usage error: Destination address required ping: usage error: Destination address required ping: usage error: Destination address required ping: usage error: Destination address required ping: usage error: Destination address required ping: usage error: Destination address required ping: usage error: Destination address required ping: usage error: Destination address required ping: usage error: Destination address required ping: usage error: Destination address required ... 2023-04-04 07:19:55,002 - runtime - INFO - ... FAIL 2023-04-04 07:19:55,002 - runtime - INFO - Traceback (most recent call last): File \"/lava-62618/3/tests/3_oeqa-runtime-tests/image/lib/oeqa/runtime/cases/ping.py\", line 23, in test_ping output += proc.communicate()[0].decode('utf-8') ^^^^^^^^^^^^^^^^^^ File \"/usr/lib/python3.11/subprocess.py\", line 1194, in communicate stdout = self.stdout.read() ^^^^^^^^^^^^^^^^^^ File \"/lava-62618/3/tests/3_oeqa-runtime-tests/image/lib/oeqa/core/decorator/oetimeout.py\", line 18, in _timeoutHandler raise OEQATimeoutError(\"Timed out after %s \" oeqa.core.exception.OEQATimeoutError: Timed out after 30 seconds of execution (From OE-Core rev: 87ec75710b5cd7b3f35d886003844d62d3182b54) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devicetree.bbclass: fix typoLuca Ceresoli2023-04-061-1/+1
| | | | | | | (From OE-Core rev: d523079bbea54f791039bf40db3bbc5c5e857ca3) Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* grep: upgrade 3.9 -> 3.10Denys Dmytriyenko2023-04-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | This is to announce grep-3.10, a stable release, fixing a bug with -P and \d. TL;DR, grep-3.9 would do this: $ LC_ALL=en_US.UTF-8 grep -P '\d' <<< ٠١٢٣٤٥٦٧٨٩ ٠١٢٣٤٥٦٧٨٩ It should print nothing, like it has always done. For more detail, see https://lists.gnu.org/r/bug-grep/2023-03/msg00005.html Thanks to Paul Eggert for catching the \D variant and to Bruno Haible for assiduously tending gnulib and for testing grep on so many different systems. There have been 12 commits by 2 people in the 17 days since 3.9. (From OE-Core rev: 7ac3bcf228ceb4b56f82c65941b95a276d7d3b95) Signed-off-by: Denys Dmytriyenko <denis@denix.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xz: upgrade 5.4.1 -> 5.4.2Denys Dmytriyenko2023-04-061-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | COPYING files had 2 updates w/o affecting licensing: * URLs to gnu.org and fsf.org switched to https * Clarifying licensing of liblzma Doxygen-generated docs - details below 5.4.2 (2023-03-18) * All fixes from 5.2.11 that were not included in 5.4.1. * If xz is built with support for the Capsicum sandbox but running in an environment that doesn't support Capsicum, xz now runs normally without sandboxing instead of exiting with an error. * liblzma: - Documentation was updated to improve the style, consistency, and completeness of the liblzma API headers. - The Doxygen-generated HTML documentation for the liblzma API header files is now included in the source release and is installed as part of "make install". All JavaScript is removed to simplify license compliance and to reduce the install size. - Fixed a minor bug in lzma_str_from_filters() that produced too many filters in the output string instead of reporting an error if the input array had more than four filters. This bug did not affect xz. * Build systems: - autogen.sh now invokes the doxygen tool via the new wrapper script doxygen/update-doxygen, unless the command line option --no-doxygen is used. - Added microlzma_encoder.c and microlzma_decoder.c to the VS project files for Windows and to the CMake build. These should have been included in 5.3.2alpha. * Tests: - Added a test to the CMake build that was forgotten in the previous release. - Added and refactored a few tests. * Translations: - Updated the Brazilian Portuguese translation. - Added Brazilian Portuguese man page translation. (From OE-Core rev: 0331fac93570b8e2960ac94b2a6a7eb71cb1a1d0) Signed-off-by: Denys Dmytriyenko <denis@denix.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: efibootpartition.py: fix QEMU_USE_KVM usageMartin Jansa2023-04-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | * if you don't have QEMU_USE_KVM in local.conf it fails with: 2023-03-12 18:06:29,591 - oe-selftest - DEBUG - Checking if qemux86-64 is not this MACHINE 2023-03-12 18:06:29,594 - oe-selftest - INFO - ... ERROR 2023-03-12 18:06:29,594 - oe-selftest - INFO - Traceback (most recent call last): File "/OE/build/poky/meta/lib/oeqa/core/decorator/__init__.py", line 35, in wrapped_f return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/OE/build/poky/meta/lib/oeqa/selftest/cases/efibootpartition.py", line 18, in test_boot_efi if oe.types.qemu_use_kvm(self.td['QEMU_USE_KVM'], self.td["TARGET_ARCH"]): ~~~~~~~^^^^^^^^^^^^^^^^ KeyError: 'QEMU_USE_KVM' [YOCTO #12937] (From OE-Core rev: 7c32ca2f91beb98769c89470b37f06cb4b99aebb) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-bcrypt-crates.inc: regenerate with updated bbclassMartin Jansa2023-04-061-49/+49
| | | | | | | | | | | | | | | * it's needed for compatibility with updated fetcher from: https://patchwork.yoctoproject.org/project/bitbake/patch/20230405122125.3358972-1-enrico.scholz@sigma-chemnitz.de/ * easiest way to regenerate these is: echo > meta/recipes-devtools/python/python3-bcrypt-crates.inc bitbake -c update_crates python3-bcrypt git commit (From OE-Core rev: ccef8f0b0d6e4e8b099953df3cf092b1545aca20) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-cryptography-crates.inc: regenerate with updated bbclassMartin Jansa2023-04-061-66/+66
| | | | | | | | | | | | | | | * it's needed for compatibility with updated fetcher from: https://patchwork.yoctoproject.org/project/bitbake/patch/20230405122125.3358972-1-enrico.scholz@sigma-chemnitz.de/ * easiest way to regenerate these is: echo > meta/recipes-devtools/python/python3-cryptography-crates.inc bitbake -c update_crates python3-cryptography git commit (From OE-Core rev: bf6a3cd70d13f05f0e2af2b54635214690a68a78) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cargo-update-recipe-crates.bbclass: Do not add name= to crate:// URIsPeter Kjellerstedt2023-04-061-1/+1
| | | | | | | | | | | | | With the recent change to the crate fetcher, which automatically sets the name to for each crate to be versioned, there is no longer a need to explicitly set the name= parameter for each URI. This also results in generated files that are compatible with the crate fetcher in Kirkstone and Langdale. (From OE-Core rev: eb272afcd9a12ce2b2f43436b3f84f52cb6cdfb7) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/crate: create versioned 'name' entriesEnrico Scholz2023-04-062-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | It is common for rust packages to depend on different versions of the same crate. E.g. | crate://crates.io/windows_x86_64_msvc/0.42.2 \ | crate://crates.io/windows_x86_64_msvc/0.48.0 \ Identification only by the plain crate name makes the sha256sum ambiguous | SRC_URI[windows_x86_64_msvc.sha256sum] = "9aec5da331524158c6d1a4ac0ab1541149c0b9505fde06423b02f5ef0106b9f0" | SRC_URI[windows_x86_64_msvc.sha256sum] = "1a515f5799fe4961cb532f983ce2b23082366b898e52ffbce459c86f67c8378a" and requires lot of manual work to fix the SRC_URI list. Making the 'name' property unique by appending the version allows direct copy & paste of reported sha256sum errors to complete the crates list. (Bitbake rev: ae2efb05196f9e29ef56ad9a84e2eae5fbdd8030) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2023-04-051-1/+1
| | | | | | (From OE-Core rev: 5a96847e7ef2ff72958d739a91c90e2085c04bc6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.conf: Bump version for 4.2 mickledore releaseRichard Purdie2023-04-051-2/+2
| | | | | | (From meta-yocto rev: 9294211a349523a07a81eebf6ce4edb126797d23) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2023-04-051-1/+1
| | | | | | (From OE-Core rev: 76f16451343b9e6a0f87eaf15a5c6f5a80b73633) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: Bump to version 2.4.0Richard Purdie2023-04-052-2/+2
| | | | | | (Bitbake rev: 46e1ea2e9a203992bb4de48ea21a8e736419ada2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: move hwclock init earlier in startupChris Elledge2023-04-051-0/+1
| | | | | | | | | | | | | | | | hwclock.sh had default update-rc parameters which made it run after other tasks that work with the clock such as connman. This causes a time obtained by NTP to be clobbered by a potentially incorrect time in the RTC. Provide non-default INITSCRIPT_PARAMS to have hwclock.sh run during the rc startup before runlevel initscripts start. (From OE-Core rev: 3012bac35ada9a9f66d9e6e2fecaee09527b9d44) Signed-off-by: Chris Elledge <celledge@siteworx.io> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/bblogging: uncomment python stdout checksMark Asselstine2023-04-051-12/+6
| | | | | | | | | | | | Since bitbake commit 81a58647b2f4fc0a2589b2978fc9d81b2bfe6aec [bitbake: build: Make python output print to stdout when running with -v (verbose)] we no longer need to comment out the python stdout checks. (From OE-Core rev: 67886a8473c511c8ab3db2e4587cc5a070979d11) Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: rename deprecated --enable-trace-backend configure optionThomas De Schampheleire2023-04-051-1/+1
| | | | | | | | | | | | | | qemu 6.2 deprecated the configure option '--enable-trace-backend' in favor of '--enable-trace-backends' [1] Rename accordingly. [1] https://wiki.qemu.org/ChangeLog/6.2#Build_Information (From OE-Core rev: 9e41fac1c2ee15aaff9926dac3c0233430adff12) Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: retain default trace backend if 'ust' is not enabledThomas De Schampheleire2023-04-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | The qemu build system enables the 'log' trace backend by default, if no explicit choice was made with '--enable-trace-backend=CHOICE'. However, the qemu recipe uses the following PACKAGECONFIG line: PACKAGECONFIG[ust] = "--enable-trace-backend=ust,--enable-trace-backend=nop,lttng-ust," which means that the 'nop' trace backend will be explicitly selected if the 'ust' feature is not enabled. The 'nop' backend removes almost all trace points at compile time, and thus basically means 'disable tracing'. To retain the default trace backend if 'ust' is not enabled, the above PACKAGECONFIG line should either explicitly fall back to the 'log' backend, or not provide any value for the 'disabled' case. This commit chooses the latter to not make any assumption about the upstream default. (From OE-Core rev: c31396a30dcf17ab23ff4dd5943eef5fba20cba6) Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: make tracetool-generated output reproducibleThomas De Schampheleire2023-04-052-0/+88
| | | | | | | | | | | '#line' directives written by qemu's tracetool makes the 'debug' package not reproducible due to absolute paths. Apply a patch to use a relative path instead. (From OE-Core rev: 85e30c507b63fa9126887dc6435d1ee6e23bd887) Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-extra-exclusions: ignore inapplicable linux-yocto CVEsGeoffrey GIRY2023-04-055-3/+74
| | | | | | | | | | | | | | | | | | Multiple CVEs are patched in kernel but appear as active because the NVD database is not up to date. In common file cve-extra-exclusion.inc, CVEs are ignored if and only if all versions of kernel used are patched. In cve-exclusion_6.1.inc, only ignore CVEs that are patched in v6.1, and not patched in v5.15. Recipes of version 6.1 should include this file. Reviewed-by: Yoann Congal <yoann.congal@smile.fr> (From OE-Core rev: 5feb065f1b1aaf218f71cc9d31a9251b139b9442) Signed-off-by: Geoffrey GIRY <geoffrey.giry@smile.fr> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xdg-utils: Fix CVE numberRichard Purdie2023-04-052-2/+2
| | | | | | | | | In the previous commit I somehow mixed up and used an incorrect CVE number. Use the correct one. (From OE-Core rev: b3e2729f686ff6e16e11590bcd701c057ae5f1e2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.bbclass: Update minimum gcc version to 8.0Mark Hatle2023-04-041-3/+3
| | | | | | | | | | | | | | With a gcc older then 8.0, mesa-native will fail to build with the error: sorry, unimplemented: non-trivial designated initializers not supported According to https://docs.mesa3d.org/install.html?highlight=gcc+version#compile the required minimum compiler version is now GCC 8.0. (From OE-Core rev: aa466053bf8a4b7998a462f0b49372d3a68a28e3) Signed-off-by: Mark Hatle <mark.hatle@amd.com> Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-extra-exclusions.inc: Exclude some issues not present in linux-yoctoRichard Purdie2023-04-041-0/+40
| | | | | | | | | | | | | Exclude some CVEs where the patches were backported to the stable series kernels we have. https://www.linuxkernelcves.com/cves/CVE-XXXX-XXXX is useful to help with this. Reviewed-by: Yoann Congal <yoann.congal@smile.fr> (From OE-Core rev: 33448393493d507c4d81c40e43537065a7b61d4c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xdg-utils: Add a patch for CVE-2020-27748Richard Purdie2023-04-042-0/+146
| | | | | | | | | Take a patch submitted upstream for the issue while upstream decide what to do. We don't use thunderbird integration so this isn't an issue for us. (From OE-Core rev: b85b7714a44caa70beb2f115483ee52745aa1b97) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Increase minimum GCC version to 8.0Ross Burton2023-04-041-1/+1
| | | | | | | | | | | | We've increased the minimum GCC version to 8.0[1] so update the documentation to match. [1] sanity.bbclass: Update minimum gcc version to 8.0 (From yocto-docs rev: c74254fa7406c76b26e47b968685115699f95c55) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vte: depend on glib-2.0-nativePetr Kubizňák2023-04-041-1/+1
| | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native package dependency is not pulled in but vte has a hard dependency on it (do_configure fails due to missing glib-mkenums). (From OE-Core rev: 686e0cb93f9f6ef663243e62c7a8cc43ca1dcd3a) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: Display all missing checksum at onceFrederic Martinsons2023-04-041-8/+10
| | | | | | | | | | | | | | | | | | | | | | | | Instead of only display the first and stop. For recipe (crago based) that can contains several artifacts to fetch with their checksum, it will particularly handy to display all of missing one. An example of error message would be NOTE: Executing Tasks ERROR: zvariant-3.12.0-r0 do_fetch: Missing SRC_URI checksum, please add those to the recipe: SRC_URI[anyhow-1.0.70.sha256sum] = "7de8ce5e0f9f8d88245311066a578d72b7af3e7088f32783804676302df237e4" SRC_URI[chrono-0.4.24.sha256sum] = "4e3c5919066adf22df73762e50cffcde3a758f2a848b113b586d1f86728b673b" SRC_URI[serde-1.0.158.sha256sum] = "771d4d9c4163ee138805e12c710dd365e4f44be8be0503cb1bb9eb989425d9c9" SRC_URI[system-deps-1.3.2.sha256sum] = "0f3ecc17269a19353b3558b313bba738b25d82993e30d62a18406a24aba4649b" ERROR: zvariant-3.12.0-r0 do_fetch: Bitbake Fetcher Error: BBFetchException('There was some missing checksums in the recipe') ERROR: Logfile of failure stored in: /home/jenkins/yocto-poky-master/poky/build/tmp/work/core2-64-poky-linux/zvariant/3.12.0-r0/temp/log.do_fetch.1025 ERROR: Task (/home/jenkins/yocto-poky-master/poky/meta-selftest/recipes-extended/zvariant/zvariant_3.12.0.bb:do_fetch) failed with exit code '1' (Bitbake rev: dafa07c080e05975b6319b5adf78a9691c6b6643) Signed-off-by: Frederic Martinsons <frederic.martinsons@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0-plugins: package the internal libraries explicitlyRoss Burton2023-04-041-0/+2
| | | | | | | | | | An upcoming change will simplify the setuptools3-base FILES assignments, which means this recipe needs to package a library explicitly. (From OE-Core rev: bab2e8c76453cf9982af936f20c6b22cc2237ba7) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bind: don't package non-existant .la files into -staticdevRoss Burton2023-04-041-1/+0
| | | | | | | | | | If these files exist they should be packaged into PN-dev, and are with the default FILES:${PN}-dev. (From OE-Core rev: 738434bf567d25de692cd145156263eea1a5de13) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes-recipe/setuptools3-base: clean up FILES assignmentsRoss Burton2023-04-041-10/+3
| | | | | | | | | | | Simply inheriting setuptools3-base should put everything in $libdir in PN, and there's no need to replicate the pkgconfig packaging rules as those are the defaults. (From OE-Core rev: 56a32e31d4fdfb908f0edf513d21bc0f2b8c721e) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libnotify: depend on glib-2.0-nativePetr Kubizňák2023-04-041-1/+1
| | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native package dependency is not pulled in but libnotify has a hard dependency on it (do_configure fails due to missing glib-mkenums). (From OE-Core rev: 63cc22caf4dfcde1d7a3a8410559bb227ed95c33) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* webkitgtk: add missing dependenciesPetr Kubizňák2023-04-041-0/+2
| | | | | | | | | | | When gobject-introspection feature is disabled, gettext-native and glib-2.0-native dependencies are not pulled in, which causes failures in do_compile due to missing xgettext and gdbus-codegen. (From OE-Core rev: c9e4c3d437ba7cadb87bc30b85f602b8551a0e17) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gconf: add missing dependenciesPetr Kubizňák2023-04-041-1/+1
| | | | | | | | | | | | When gobject-introspection feature is disabled, glib-2.0-native and gobject-introspection package dependencies are not pulled in but gconf has a hard dependency on them (do_configure fails due to missing introspection.m4 file and glib-gettextize). (From OE-Core rev: d87bc67fde3c8bc6068cb67708953ce88ac31e3f) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pygobject: depend on gobject-introspectionPetr Kubizňák2023-04-041-1/+1
| | | | | | | | | | When g-i feature is disabled, the gobject-introspection package dependency is not pulled in but pygobject has a hard dependency on it. (From OE-Core rev: 7fae697c6889e17dd47415808a7173670b507047) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* graphene: add gobject-types PACKAGECONFIGPetr Kubizňák2023-04-041-1/+2
| | | | | | | | | | | | | | Add an option to enable/disable build of graphene-gobject. When enabled, add glib dependency (not pulled in implicitly if the gobject-introspection feature is disabled). Default is to enable gobject-types so that graphene-gobject is built (dependency of gtk4). (From OE-Core rev: b82781498cda67f4797de5b8b7c2b90a275a72e1) Signed-off-by: Petr Kubizňák <kubiznak@2n.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-05 08:03:52 +0000