linux/poky.git, branch yocto-5.0.7

build-appliance-image: Update to scarthgap head revision

2025-01-26T22:08:20+00:00

(From OE-Core rev: 62cb12967391db709315820d48853ffa4c6b4740) Signed-off-by: Steve Sakoman

rust: correctly link rust-snapshot into build/stage0

2025-01-26T22:04:46+00:00

This does not seem to be used in regular builds, but is beneficial in rust selftest, where it allows dropping a custom patch that is unsuitable for upstream (and was rejected by them). Also remove an obsolete comment that seems related to the code but describes something that was resolved long time ago. I have confirmed that the rust selftest continues to pass with just this one commit on top of master (as the following changes do break the selftest). (From OE-Core rev: 9b23f995fbc1886c36f02b0c6e1ccaf2ee0f6daa) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie (cherry picked from commit bf5732e2b235ce06fa1f24fe8f0dbcbc068500e3) Signed-off-by: Steve Sakoman

rust: use rust-snapshot binaries only in rust-native

2025-01-26T22:04:46+00:00

Otherwise, use rust-native and cargo-native binaries as that allows our native tweaks in them to be used for target/nativesdk rust - same as for everything else written in rust. In particular, this allows building target rust with cargo-native that includes important reproducibility tweaks. Unfortunately, this also breaks rust selftest, and that is partially addressed by the following commit. [YOCTO #15185] (From OE-Core rev: d592bc02b0846411796c1d481c09833559d1d29f) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 8f2230cb51fe22ef4711a56fecfab4858c04e35b) Signed-off-by: Steve Sakoman

rust: build the default set of tools

2025-01-26T22:04:46+00:00

Setting it explicitly replaces rust's default choice which is rustdoc (needed for example in selftests and otherwise expected to be present in typical rust installations): https://github.com/rust-lang/rust/blob/master/config.example.toml#L320 This addresses some of the rust selftest failures but not all. Help is appreciate to restore the selftest. Unfortunately, this also breaks rust reproducibility (or rather exposes that it was never properly fixed, as explained here: https://lists.openembedded.org/g/openembedded-core/message/199288 ) (From OE-Core rev: 4d739fe248d1023eb2c3c040fc4d33273dd16bc1) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 58eaf2ee6c0809bf0a0d3c1d177e62bda7241651) Signed-off-by: Steve Sakoman

Revert "rust: Add new varaible RUST_ENABLE_EXTRA_TOOLS"

2025-01-26T22:04:46+00:00

This reverts commit 136a25567499191b23a4d000a06bf83a473224ca. Signed-off-by: Steve Sakoman

build-appliance-image: Update to scarthgap head revision

2025-01-25T14:26:18+00:00

(From OE-Core rev: 3c31639dd53e32e57af64d50ad168f5c3911c299) Signed-off-by: Steve Sakoman

poky.conf: bump version for 5.0.7

2025-01-25T14:22:54+00:00

(From meta-yocto rev: 03c7935bcdb15fd903d26828085d49c00267b8d9) Signed-off-by: Steve Sakoman

boost: fix do_fetch error

2025-01-25T14:20:37+00:00

Change the SRC_URI to the correct value due to the following error: WARNING: boost-native-1.84.0-r0 do_fetch: Checksum failure encountered with download of https://boostorg.jfrog.io/artifactory/main/release/1.84.0/source/boost_1_84_0.tar.bz2 - will attempt other sources if available (From OE-Core rev: 7ecd0d5584b7692b58ac8039b4107c4e0836d553) Signed-off-by: Jiaying Song Signed-off-by: Steve Sakoman

rust-target-config: Fix TARGET_C_INT_WIDTH with correct size

2025-01-25T14:20:37+00:00

[YOCTO #15600] The TARGET_C_INT_WIDTH value was incorrectly set to 64 instead of 32. It is updated for PPC, Mips, and riscv64 architectures. Discussion links for solution: https://lists.openembedded.org/g/openembedded-core/message/207486 https://lists.openembedded.org/g/openembedded-core/message/207496 (From OE-Core rev: 0e02d0feba8bd48a27c41db875dcd33d46e4dc0d) Signed-off-by: Harish Sadineni Signed-off-by: Richard Purdie (cherry picked from commit b9df8cd8b29064d115dab3bfd1ea14f94a5c0238) Signed-off-by: Steve Sakoman

rsync: fix CVE-2024-12747

2025-01-25T14:20:37+00:00

A flaw was found in rsync. This vulnerability arises from a race condition during rsync's handling of symbolic links. Rsync's default behavior when encountering symbolic links is to skip them. If an attacker replaced a regular file with a symbolic link at the right time, it was possible to bypass the default behavior and traverse symbolic links. Depending on the privileges of the rsync process, an attacker could leak sensitive information, potentially leading to privilege escalation. (From OE-Core rev: e85beb88add5e94567d7221e00cabfb3d5010be7) Signed-off-by: Archana Polampalli Signed-off-by: Steve Sakoman