summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
...
* 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>
* 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>
* libxml2: Do not use lld linker when building with tests on rv64Khem Raj2023-07-071-0/+2
| | | | | | | | | | | | | | lld ends up with errors on some tests | riscv64-yoe-linux-ld.lld: error: section size decrease is too large Therefore do not use lld when building ptests (From OE-Core rev: 23bcd0dbf3aeaff6b6914d347954bec22a133e23) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 154e81bb6b05b23c0c673b431cb7cee868421335) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* strace: Update patches/tests with upstream fixesRichard Purdie2023-07-074-38/+102
| | | | | | | | | | Replace the sockopt disable patch with a fix from upstream (From OE-Core rev: c1beb73526e3ade75bd6dae5f9310107c50f1226) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit ac921989991c319ecad01bec37c4ccaa15a7b58f) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* strace: Merge two similar patchesRichard Purdie2023-07-073-48/+30
| | | | | | | | | | | Both patches change the same paths to gawk, merge them together as we only need one patch for this. (From OE-Core rev: 6080138fd0c27db7029b5a76e69b8dc241ad8dc3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 79c0b18e29cad337640860f57683f0a170f6daab) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* rpcsvc-proto: Upgrade to 1.4.4Khem Raj2023-07-073-90/+6
| | | | | | | | | | | Drop already upstreamed patch in 1.4.4 (From OE-Core rev: f3ce18bcc993c636c7f7ac898cd5cb2de92df8ea) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 1dddd4bf9bdb26069a1a0d4fcb8aeefd5761c620) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* gdb: upgrade 13.1 -> 13.2Alexander Kanavin2023-07-076-313/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes: * PR testsuite/30158 (rustc testsuite fails with 13.1, apparently worked before with trunk 20230114 on i686-linux-gnu and powerpc64le-linux-gnu) * PR gdb/30214 (GDB 13.1 does not compile on FreeBSD 13.1) * PR gdb/30240 ((linux/aarch) thread.c:86: internal-error: inferior_thread: Assertion `current_thread_ != nullptr' failed) * PR gdb/30249 ([13 regression] hookpost-extended-remote will not work) * PR exp/30271 (Addresses of static thread_local fields are badly calculated sometimes) * PR symtab/30357 (Segmentation fault for the 'start' command) * PR symtab/30369 ([gdb/symtab] False match issue in skip_prologue_using_linetable) * PR gdb/30423 (Build failures with clang 16) * PR build/30450 (Build failure (linux-low.cc:5393:45: error: expected ':' before ')' token) with musl-1.2.4) (From OE-Core rev: 900379776878c363ff7c802f6b740ee89661ea9c) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit d10764916624f61d39cb9ea368359837156ad960) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* wireless-regdb: upgrade 2023.02.13 -> 2023.05.03Alexander Kanavin2023-07-071-1/+1
| | | | | | | | | (From OE-Core rev: 77889442edaa7540c5c865ceb69dcdd972dd5fd7) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 47438402fa430499864a4b1f1a13eaac66aa21c0) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* wget: upgrade 1.21.3 -> 1.21.4Alexander Kanavin2023-07-072-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Stable version release Noteworthy changes in release 1.21.4 (2023-05-11) ** Document --retry-on-host-error in help text ** Increase read buffer size to 64k. This should speed up downloads on gigabit and faster connections ** Update deprecated option '--html-extension' to '--adjust-extension' in documentation ** Update gnulib compatibility layer. Fixes HSTS test failures on i686. (Thanks to Andreas Enge for ponting it out) License-Update: copyright years (From OE-Core rev: 4e7ec4bef86c79b4221a800ace700c58ce033de1) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 67ec2d5bab891cb92af9ca32304a4927daf51ed0) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* serf: upgrade 1.3.9 -> 1.3.10Alexander Kanavin2023-07-075-92/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Apache Serf 1.3.10 [2023-05-31, from tags/1.3.10, r1910048] Support for OpenSSL 3 (r1901937, ...) Fix issue #171: Win32: Running tests fails with "no OPENSSL_Applink" error Fix issue #194: Win32: Linking error when building against OpenSSL 1.1+ Fix issue #198: OpenSSL BIO control method incorrectly handles unknown requests Fix issue #202: SSL tests are not passing with OpenSSL 3 Fix error handling when reading the outgoing request body (r1804534, ...) Fix handling of invalid chunk lengths in the dechunk bucket (r1804005, ...) Fix an endless loop in the deflate bucket with truncated input (r1805301) Fix BIO control handlers to support BIO_CTRL_EOF (r1902208) Fix a CRT mismatch issue caused by using certain OpenSSL functions (r1909252) Build changes to support VS2017, VS2019 and VS2022 (r1712131, ...) Build changes to support Python 3 (r1875933) As serf is undead, we need to reassess all the remaining patches. (From OE-Core rev: 17a46eee905f0ecfdbebb014533848dc7e906ec7) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 775cbcc876edcb6c339f342a3253f5afcf6ef163) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* linux-firmware: upgrade 20230404 -> 20230515Alexander Kanavin2023-07-071-2/+2
| | | | | | | | | | | License-Update: additional firmwares (From OE-Core rev: 0903f615b89c8aecf660d1cbd8161e6ba0b354bc) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 64603f602d00999220fe5bafeed996ddcb56d36b) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* libx11: upgrade 1.8.4 -> 1.8.5Alexander Kanavin2023-07-071-1/+1
| | | | | | | | | | | | | | | | | | Bug fix release * autoconf & libtool updates (!187, !188) * Restore missing text in XSetScreenSaver man page (#187, !203) * Update am_ET.UTF-8 compose keys to use dead-vowel symbols, in coordination with xkeyboard-config 2.39 (!205) * Assorted updates to en_US.UTF-8 compose keys (!189, !195, !196, !198, !199, !200, !201, !207, !208, !209) (From OE-Core rev: fe81e39b0bac276bda508e4b2667c81c052392e2) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 4e931f490854100c2504ce771d5c920e3a62efdd) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* gnupg: upgrade 2.4.0 -> 2.4.2Alexander Kanavin2023-07-073-13/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Stable version update Noteworthy changes in version 2.4.2 =================================== * gpg: Print a warning if no more encryption subkeys are left over after changing the expiration date. [rGef2c3d50fa] * gpg: Fix searching for the ADSK key when adding an ADSK. [T6504] * gpgsm: Speed up key listings on Windows. [rG08ff55bd44] * gpgsm: Reduce the number of "failed to open policy file" diagnostics. [rG68613a6a9d] * agent: Make updating of private key files more robust and track display S/N. [T6135] * keyboxd: Avoid longish delays on Windows when listing keys. [rG6944aefa3c] * gpgtar: Emit extra status lines to help GPGME. [T6497] * w32: Avoid using the VirtualStore. [T6403] (From OE-Core rev: d4ab498958db518a7c67b8cc1f9c15d6ee253097) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit c9eddfded59819a2a375b6f5518bf2c3184237d2) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* gawk: upgrade 5.2.1 -> 5.2.2Alexander Kanavin2023-07-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a bug fix release. Changes from 5.2.1 to 5.2.2 --------------------------- 1. Infrastructure upgrades: makeinfo 7.0.1 must be used to format the manual. As a result, the manual can also now be formatted with LaTeX by running it through `makeinfo --latex'. 2. Gawk no longer builds an x86_64 executable on M1 macOS systems. This means that PMA is unavailable on those systems. 3. Gawk will now diagnose if a heap file was created with a different setting of -M/--bignum than in the current invocation and exit with a fatal message if so. 4. Gawk no longer "leaks" its free list of NODEs in the heap file, resulting in much more efficient usage of persistent storage. 5. PROCINFO["pma"] exists if the PMA allocator is compiled into gawk. Its value is the PMA version. 6. The time extension is no longer deprecated. The strptime() function from gawkextlib's timex extension has been added to it. 7. Better information is passed to input parsers for when they want to decide whether or not to take control of a file. In particular, the readdir extension is simplified for Windows because of this. 8. The various PNG files are now installed for Info and HTML. The images files now have gawk_ prefixed names to avoid any conflicts with other installed PNG file names. 9. As usual, there have been several minor code cleanups and bug fixes. See the ChangeLog for details. (From OE-Core rev: 3ace3af1e57b701308ab397c6ac45a6fa703ed40) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 8504a35f1fe222d256241ff00c05b63e24e9adcb) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* perl: Fix CVE-2023-31484 & CVE-2023-31486Soumya2023-07-074-0/+279
| | | | | | | | | | | | | | | | | | | | | | | CPAN.pm before 2.35 does not verify TLS certificates when downloading distributions over HTTPS. HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates. References: https://nvd.nist.gov/vuln/detail/CVE-2023-31484 https://nvd.nist.gov/vuln/detail/CVE-2023-31486 Upstream patches: https://github.com/andk/cpanpm/commit/9c98370287f4e709924aee7c58ef21c85289a7f0 https://github.com/chansen/p5-http-tiny/commit/77f557ef84698efeb6eed04e4a9704eaf85b741d https://github.com/chansen/p5-http-tiny/commit/a22785783b17cbaa28afaee4a024d81a1903701d (From OE-Core rev: f4fe9861d6aebd971a3120a0eb43f752c73ce2fb) Signed-off-by: Soumya <soumya.sambu@windriver.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
* grub: submit determinism.patch upstreamAlexander Kanavin2023-07-041-1/+1
| | | | | | | | | (From OE-Core rev: ce5337d19ad290f30c0250158a1833a2cc3bd0ac) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 61947762e410c685f667e0af6440fb8a33cd6777) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* useradd-staticids.bbclass: improve error messageMikko Rapeli2023-07-041-1/+1
| | | | | | | | | | | | | | | | | | | | | Current error message is difficult to read: ERROR: Nothing PROVIDES 'image' trs-image was skipped: image - image: normal username test does not have a static ID defined. Add test to one of these files It's not clear that first "image" is recipe name, second "image" is binary package name and that "test" is the user account which does not have a static ID defined. Improve the error message so that these are more explicit. Now the error message looks like: image was skipped: Recipe image, package image: normal username "test" does not have a static ID defined. (From OE-Core rev: 3285f6080161ccc808efb7fce7db9dc0dd236ffa) Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> (cherry picked from commit 07898218f3908a83e07178b6530dfa48d55d4ec2) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* parted: Add missing libuuid to linker cmdline for libparted-fs-resize.soKhem Raj2023-07-042-0/+35
| | | | | | | | | (From OE-Core rev: 8e42a4364921fabccf0f1c4bc4e661da72c82d06) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> (cherry picked from commit 493b6a17ede8033be11eb61aef347f6f5df42f7d) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* gobject-introspection: remove obsolete DEPENDSRoss Burton2023-07-041-1/+1
| | | | | | | | | | | This recipe uses meson, so doesn't need to DEPEND on autoconf-archive. (From OE-Core rev: b5e006b15d0e95ab83a1a42de194d28152c67f48) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> (cherry picked from commit cb09a2d7077e4e0809e16ad6d23cd4f3b2a3bbca) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* babeltrace2: Always use BFD linker when building tests with ld-is-lld distro ↵Khem Raj2023-07-041-0/+1
| | | | | | | | | | | | | | | | | | | feature lld results in textrels in some .so used in tests, fixes babeltrace2-ptest: ELF binary /usr/lib/babeltrace2/ptest/tests/lib/test-plugin-plugins/plugin-minimal.so has relocations in .text babeltrace2-ptest: ELF binary /usr/lib/babeltrace2/ptest/tests/lib/test-plugin-plugins/plugin-sfs.so has relocations in .text [textrel] ERROR: babeltrace2-2.0.5-r0 do_package_qa: QA Issue: babeltrace2: ELF binary /usr/lib/babeltrace2/plugins/babeltrace-plugin-ctf.so has relocations in .text babeltrace2: ELF binary /usr/lib/babeltrace2/plugins/babeltrace-plugin-utils.so has relocations in .text babeltrace2: ELF binary /usr/lib/babeltrace2/plugins/babeltrace-plugin-text.so has relocations in .text [textrel] (From OE-Core rev: 092ea60841b5dd45ddbfff9c94b4380855f8e639) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> (cherry picked from commit 18d443b53a0d76102fbbc1088fbcb3f8087a2b1b) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* maintainers.inc: unassign Ricardo Neri from ovmfAlexander Kanavin2023-07-041-2/+2
| | | | | | | | | | | | We were not able to get a response about availability over email, and so the recipe has to be unassigned. (From OE-Core rev: 8bd8ea8293a75ffa0e850513c3c15be6bc8c8692) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 56f1af6d5b3019dccbc27bb0a9692a5f1a32f87b) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* maintainers.inc: unassign Oleksandr Kravchuk from python3 and all other itemsAlexander Kanavin2023-07-041-17/+17
| | | | | | | | | | | | We were not able to get a response about availability over email, and so the recipes have to be unassigned. (From OE-Core rev: 66dfaff6bdf9c02a2cc6b1e8829c86e38908b195) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 2d2c75530fe336eda72e8ce72f994725b3a77ea0) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* maintainers.inc: unassign Chase Qi from libc-testAlexander Kanavin2023-07-041-1/+1
| | | | | | | | | | | | We were not able to get a response about availability over email, and so the recipe has to be unassigned. (From OE-Core rev: 20c7da2785e0e85264c2ef711b079920eb4bb26a) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 5be575577d74a3cb81594392b88df74226be9192) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* maintainers.inc: unassign Alistair Francis from opensbiAlexander Kanavin2023-07-041-1/+1
| | | | | | | | | | | | We were not able to get a response about availability over email, and so the recipe has to be unassigned. (From OE-Core rev: deacda2bdccc682b845d5a909adfc172ccfcb5cf) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 60eda3dcbf96b5982a0e282fd0c3c13b0b4d7787) Signed-off-by: Steve Sakoman <steve@sakoman.com>
* maintainers.inc: unassign Adrian Bunk from wireless-regdbAlexander Kanavin2023-07-041-1/+1
| | | | | | | | | | | | We were not able to get a response about availability over email, and so the recipe has to be unassigned. (From OE-Core rev: 41fa071b1b32a795e5c5b671580d4f962dbabf20) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 3beb88060be9484cfe75dfa60f041b0b32214978) Signed-off-by: Steve Sakoman <steve@sakoman.com>