linux/poky.git/scripts, branch honister

wic/plugins/rootfs: Fix permissions when splitting rootfs folders across partitions

2022-06-01T10:20:24+00:00

This patches makes locating the file database containing the file and folder usernames and permissions more reliable. In addition to locating it relative to the partition directory, we also try to locate it relative to the IMAGE_ROOTFS. Prior to this patch, the database was not found when using --rootfs-dir=${IMAGE_ROOTFS}/ in the WIC script, leading to erronous file permissions and ownership. (From OE-Core rev: d730fbc26993c2187c908e57a465536a508e9ee2) Signed-off-by: Felix Moessbauer Signed-off-by: Richard Purdie (cherry picked from commit 09e18ee246da8b56f446c4db548fb9c7e895142b) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

scripts/git: Ensure we don't have circular references

2022-05-12T15:42:13+00:00

This is horrible but I'm running out of better ideas. We hit circular reference issues which we were trying to avoid in the core HOSTTOOLS code. When building the eSDK, there can be two copies of the script. Therefore assume git will never be in a directory called scripts. This fixes eSDK build failures. (From OE-Core rev: 8b1d8ba7e1b2e4278c9127654a66336d2615e58b) Signed-off-by: Richard Purdie (cherry picked from commit 27de610ac30d4c81352efc794df7e9b1060f7a68) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

scripts: Make git intercept global

2022-05-12T15:42:13+00:00

The previous minimially invasive git intercept simply isn't enough. For example, meson used in the igt-gpu-tools recipe hardcodes the path to git in the configure step so at install time, changing PATH has no effect. There are lots of interesting things we could do to try and avoid problems but making the git intercept and dropping fakeroot privs for git global is probably the least worst solution at this point. It will add slight overhead to git calls but we don't make many so the overall impact is likely minimal. (From OE-Core rev: 2863b1237128906bccf7d2e9ecb739afb395fe4e) Signed-off-by: Richard Purdie (cherry picked from commit af27c81eaf68ee681dcd9456a74cca6a9ab40bf6) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

install/devshell: Introduce git intercept script due to fakeroot issues

2022-05-12T15:42:13+00:00

In a devshell, recent versions of git will complain if the repo is owned by someone other than the current UID - consider this example: ------ bitbake -c devshell linux-yocto [...] kernel-source#git branch fatal: unsafe repository ('/home/paul/poky/build-qemuarm64/tmp/work-shared/qemuarm64/kernel-source' is owned by someone else) To add an exception for this directory, call: git config --global --add safe.directory /home/paul/poky/build-qemuarm64/tmp/work-shared/qemuarm64/kernel-source kernel-source# ------ Of course the devshell has UID zero and the "real" UID is for "paul" in this case. And so recent git versions complain. As the whole purpose of the devshell is to invoke a shell where development can take place, having a non-functional git is clearly unacceptable. Richard suggested we could use PSEUDO_UNLOAD=1 to evade this issue, and I suggested we probably will see other similar instances like this and should make use of PATH to intercept via devshell wrappers - conveniently we already have examples of this. Here, we copy the existing "ar" example and tune it to the needs of git to combine Richard's suggestion and mine. As such we now also can store commit logs and use send-email with our user specific settings, instead of "root", so in additon to fixing basic commands like "git branch" it should also increase general usefulness. RP: Tweaked the patch so the PATH change only applies to the devshell task and is a generic git intercept rather than devshell specific. RP: Also apply the PATH change to do_install tasks since that also runs under fakeroot and several software projects inject "git describe" output into their binaries (systemd, iputils, llvm, ipt-gpu-tools at least) causing reproducibility issues from systems with different git versions. (From OE-Core rev: 262470f5c01c08826e0fcf3d08337d17952a257d) Signed-off-by: Paul Gortmaker Signed-off-by: Richard Purdie (cherry picked from commit 3266c327dfa186791e0f1e2ad63c6f5d39714814) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

scripts/runqemu: Fix memory limits for qemux86-64

2022-04-22T15:12:17+00:00

When setting memory to 4GB, qemu is only running with 2GB for x86_64. Avoid this by removing the mem= option to the kernel and letting the qemu configuration handle it for x86 in a similar way to mips. (From OE-Core rev: ad7a8bf827a24f195df55a5d49e3ace949b6e23e) Signed-off-by: Richard Purdie (cherry picked from commit 2fd53417eba354c31c058c4bb066bb882e098add) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

oe-pkgdata-util: Adapt to the new variable override syntax

2022-04-09T07:27:04+00:00

(From OE-Core rev: 8d44f3d72af8791ef526eea12710f7b8b6c3d750) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie (cherry picked from commit 2bf6a0ca9fdf639418646700b20b65c9960efdbe) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

wic: Use custom kernel path if provided

2022-03-15T16:38:29+00:00

If the custom kernel path is provided in options, then use that path instead of the default path. (From OE-Core rev: bced1ddc2358350a5df5b397be7a3ab7d64b08f6) Signed-off-by: Bill Pittman Signed-off-by: Richard Purdie (cherry picked from commit 1068102216a894c467f71f6046fdb37d5577545c) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

devtool: explicitly set main or master branches in upgrades when available

2022-03-10T16:39:50+00:00

In particular this resolves devtool's inability to pick a branch when the same tagged commit is avaiable in main and in a release maintenance branch. Thanks to Peter Kjellerstedt for the suggestion. (From OE-Core rev: e2f27f05018a7f7882166b1b82ffd4b443ca9dc0) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie (cherry picked from commit bcb21ee2760a2c76039412a56c6cda43fbf96fd0) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

devtool: deploy-target: Remove stripped binaries in pseudo context

2022-02-24T11:12:39+00:00

deploy-target may fail the second time with "pseudo abort" because devtool-deploy-target-stripped is deleted outside of pseudo's fakeroot context. (From OE-Core rev: 23b0efb5428343b395a3abf76c84b21b08bbc33c) Signed-off-by: Florian Amstutz Signed-off-by: Richard Purdie (cherry picked from commit 2338a33b690b0bbe279cde3f73764911b239cb50) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

scripts/runqemu-ifdown: Don't treat the last iptables command as special

2022-02-24T11:12:39+00:00

The runqemu-ifup script performs a bunch of setup steps that runqemu-ifdown attempts to undo later on. While a bunch of said setup operations are considered fatal should they fail, the iptables based NAT setup notably is not. The tear down procedure in runqemu-ifdown, however, has the iptables based tear down as the last operation, with the status of it determining the overall status of the script. Hence, if this step fails, the script is considered a failure overall. That is arguably inconsistent: If the NAT setup did not succeed, the tear down cannot succeed either. To ensure similarity of the two paths, let's not treat the last iptables tear down operation any special and allow it to fail the runqemu-ifdown script, but just ignore failures. Background: we have seen a NAT related setup problem on the ifup path (which didn't cause script failure), but then saw an issue bubbled up when this operation was meant to be undone on the ifdown path. (From OE-Core rev: 2832f0277e29811cfb32fb9962fc2983afb34c8f) Signed-off-by: Daniel Müller Signed-off-by: Richard Purdie (cherry picked from commit 0ebcfb034bcad81efef5f746f0aa0b69772901a0) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie