Oh jesus I'm a morron I haven't noticed that I'm missing chrpath Do not bother this messages:P
Cheers, Piotr ________________________________ Od: [email protected] <[email protected]> w imieniu użytkownika Piotr Łobacz via lists.openembedded.org <[email protected]> Wysłane: wtorek, 25 lipca 2023 17:22 Do: Alexander Kanavin <[email protected]> DW: Alexandre Belloni <[email protected]>; [email protected] <[email protected]> Temat: ODP: ODP: [OE-Core][PATCH v10][master-next 1/5] package_ipk.bbclass: add support for ACLs and xattr Hi Alex, at the beginning I would like to thank you for your suggestions, and I want to mention that this is what I wanted to do that from the very beginning, but I could not find any good HowTo or manual how to do that. Right now, I have this poky-contrib:abelloni/master-next branch downloaded, which also has the patches given by me. Now, I'm trying to run it using these commands: . ./oe-init-build-env build and than: oe-selftest -r reproducible but for some reason it produces me an error: raceback (most recent call last): File "/home/plobacz/workspace/poky-contrib/scripts/oe-selftest", line 60, in <module> ret = main() File "/home/plobacz/workspace/poky-contrib/scripts/oe-selftest", line 47, in main results = args.func(logger, args) File "/home/plobacz/workspace/poky-contrib/meta/lib/oeqa/selftest/context.py", line 406, in run self._process_args(logger, args) File "/home/plobacz/workspace/poky-contrib/meta/lib/oeqa/selftest/context.py", line 252, in _process_args bbvars = get_bb_vars() File "/home/plobacz/workspace/poky-contrib/meta/lib/oeqa/utils/commands.py", line 248, in get_bb_vars bbenv = get_bb_env(target, postconfig=postconfig) File "/home/plobacz/workspace/poky-contrib/meta/lib/oeqa/utils/commands.py", line 244, in get_bb_env return bitbake("-e", postconfig=postconfig).output File "/home/plobacz/workspace/poky-contrib/meta/lib/oeqa/utils/commands.py", line 234, in bitbake return runCmd(cmd, ignore_status, timeout, output_log=output_log, **options) File "/home/plobacz/workspace/poky-contrib/meta/lib/oeqa/utils/commands.py", line 212, in runCmd raise AssertionError("Command '%s' returned non-zero exit status %d:\n%s" % (command, result.status, exc_output)) AssertionError: Command 'bitbake -e' returned non-zero exit status 1: ERROR: The following required tools (as specified by HOSTTOOLS) appear to be unavailable in PATH, please install them in order to proceed: chrpath But: echo $PATH /home/plobacz/workspace/poky-contrib/scripts:/home/plobacz/workspace/poky-contrib/bitbake/bin:/home/plobacz/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin Maybe I'm doing it somehow in wrong order? BR Piotr ________________________________ Od: Alexander Kanavin <[email protected]> Wysłane: wtorek, 25 lipca 2023 12:28 Do: Piotr Łobacz <[email protected]> DW: Alexandre Belloni <[email protected]>; [email protected] <[email protected]> Temat: Re: ODP: [OE-Core][PATCH v10][master-next 1/5] package_ipk.bbclass: add support for ACLs and xattr On Tue, 25 Jul 2023 at 11:58, Piotr Łobacz <[email protected]> wrote: > > Yeah, I have just checked it for acpid-src packages and diffoscope worked > without any errors. > > Question, is this test being run with acl or/and xattr? Because from what I > remember it was not. Can you check? > If this will confirm, then something is still wrong with the gnu format, > because right now all posix - meaning with acl/xattr support - packages are > working for me. Hello Piotr, may I suggest: you need to learn to reproduce the autobuilder failures locally. Integrators are stretched very thin, they juggle a ton of patches (other than the ones you want to get in), and the expectation is that when they tell you something fails, it is on you to do further investigation. Here's how you do it: - start by finding the failed build in the list of their definitions: https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.yoctoproject.org%2Fyocto-autobuilder-helper%2Ftree%2Fconfig.json&data=05%7C01%7Cp.lobacz%40welotec.com%7C29e17992f2b148e9206c08db8cf9e54c%7C25111a7f1d5a4c51a4ca7f8e44011b39%7C0%7C0%7C638258777149507734%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3czxntfPZq68MvQxKQtJT6Rk5la4O0cca9osxYGcVqI%3D&reserved=0<https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.json> You can see that it's this one: "reproducible" : { "MACHINE" : "qemux86-64", "SDKMACHINE" : "x86_64", "step1" : { "shortname" : "Reproducible Selftest", "EXTRACMDS" : ["${SCRIPTSDIR}/checkvnc; OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail/ DISPLAY=:1 oe-selftest -r reproducible"], "ADDLAYER" : ["${BUILDDIR}/../meta-selftest"] } What that means is you need to set up a plain poky build (no extra layers, no custom configs specific to your organization), then run 'oe-selftest -r reproducible'. That is however a heavy test as it builds everything, so we need to narrow it down to just the failing pieces. - the failure log shows that reproducibility is tested via meta/lib/oeqa/selftest/cases/reproducible.py. If you open that file, you can see OEQA_REPRODUCIBLE_TEST_TARGET narrows down the targets used to test reproducibility, and you can also set OEQA_REPRODUCIBLE_TEST_PACKAGE similarly. - now you can run oe-selftest -r reproducible. Once it finishes and confirms the failure, head to build-st/reproducibleA and build-st/reproducibleB, to see where the difference first appears. You can also replicate reproducibility test by manually setting up two different build directories with identical configs. Alex H
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#184850): https://lists.openembedded.org/g/openembedded-core/message/184850 Mute This Topic: https://lists.openembedded.org/mt/100352544/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
