Monday, 2022-03-14

*** florian <florian!~florian@dynamic-078-048-066-215.78.48.pool.telefonica.de> has joined #yocto00:27
*** sgw <sgw!~swold_loc@user/sgw> has joined #yocto00:44
*** florian <florian!~florian@dynamic-078-048-066-215.78.48.pool.telefonica.de> has quit IRC (Ping timeout: 252 seconds)00:49
*** geoffhp <geoffhp!~geoff@cpe-107-185-48-203.socal.res.rr.com> has joined #yocto01:08
*** starblue <starblue!~juergen@dslb-188-100-138-006.188.100.pools.vodafone-ip.de> has quit IRC (Ping timeout: 250 seconds)02:25
*** starblue <starblue!~juergen@dslb-088-078-101-131.088.078.pools.vodafone-ip.de> has joined #yocto02:27
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)02:53
*** camus <camus!~Instantbi@2409:8a1e:9118:ceb0:f0b5:d093:efab:87> has quit IRC (Remote host closed the connection)03:13
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto03:37
*** jclsn5 <jclsn5!~jclsn@84.242.19.232.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto03:39
*** jclsn <jclsn!~jclsn@185.82.19.197.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 240 seconds)03:41
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has joined #yocto03:48
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Quit: camus)04:20
*** amitk <amitk!~amit@103.208.71.35> has joined #yocto05:31
*** camus <camus!~Instantbi@2409:8a1e:9118:ceb0:a87d:716:a2ef:fa7c> has joined #yocto06:35
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto06:49
*** jclsn5 is now known as jclsn07:19
jclsnMorning07:29
jclsnShouldn't the kernel binary be identical when INHERIT += " reproducible-build" is set?07:30
jclsnI just built it two times and the md5sum differs07:30
*** frieder <frieder!~frieder@i4DF677E2.static.tripleplugandplay.com> has joined #yocto07:51
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)07:57
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto08:04
*** mckoan|away is now known as mckoan08:10
mckoangood morning08:11
*** jclsn is now known as jclsn_08:12
RPjclsn_: can depend on a lot of things including which kernel it is :/08:13
*** jclsn_ is now known as jclsn08:13
jclsnRP: Hmm it is the linux-fslc-imx kernel08:13
*** JaMa <JaMa!~martin@109.238.218.228> has quit IRC (Quit: reboot)08:17
RPjclsn: We made sure linux-yocto does the right things (as far as I know) but I can't comment on that kernel :/08:19
RPrburton: the series in master-next for crypto in core is close but two issues. Arm ptest failure (missing import tomli) and reproducibility failure08:20
jclsnRP: Are you saying you recommend using another kernel?08:24
*** zavorka <zavorka!~zavorka@static-84-42-206-118.net.upcbroadband.cz> has quit IRC (Remote host closed the connection)08:26
RPjclsn: no, I suspect you need that kernel for your hardware. I'm just saying that the people who made it probably haven't paid attention to reproducubility :(08:29
jclsnotavio: Is that true?08:30
jclsnRP: I don08:30
jclsnRP: I don't think so actually. More probable that my patches are the cause08:30
* landgraf is back08:31
RPlandgraf: welcome back08:35
RPjclsn: I don't know. I do know we had to be careful about the configuration and the way linux-yocto was built and I don't know if others have spent time on that08:35
RPjclsn: reproducibility isn't top of everyone's priority list even if we have core working well08:36
jclsnHmm okay08:37
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto08:42
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto08:45
RPjclsn: you might be right and it may be your patches but I'm not sure...08:46
*** Guest4 <Guest4!~Guest4@2a02-a440-b6e3-1-cd5-22eb-4f84-728d.fixed6.kpn.net> has joined #yocto08:48
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has joined #yocto08:49
Guest4Is the following link meant for custom hardware? https://www.yoctoproject.org/docs/latest/bsp-guide/bsp-guide.html08:51
RPrburton: have the reproducibility fix, just need the ptest one...08:51
*** lucaceresoli <lucaceresoli!~lucaceres@77.244.183.192> has joined #yocto08:59
*** davidinux <davidinux!~davidinux@82.102.21.198> has quit IRC (Quit: WeeChat 2.8)09:04
*** davidinux <davidinux!~davidinux@84.17.59.182> has joined #yocto09:06
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Quit: ZZZzzz…)09:07
*** mvlad <mvlad!~mvlad@2a02:2f08:4114:c500:24d7:51ff:fed6:906d> has joined #yocto09:10
jclsnWhat do these messages mean?09:18
jclsnWARNING: linux-fslc-imx-5.10.98+git999-r0 do_fetch: /usr/lib/python3.8/ast.py:371: PendingDeprecationWarning: visit_Str is deprecated; add visit_Constant09:18
jclsn  return visitor(node)09:18
jclsnWARNING: linux-fslc-imx-5.10.98+git999-r0 do_populate_lic: /usr/lib/python3.8/ast.py:371: PendingDeprecationWarning: visit_Str is deprecated; add visit_Constant09:18
jclsn  return visitor(node)09:18
jclsnWARNING: linux-fslc-imx-5.10.98+git999-r0 do_deploy_source_date_epoch: /usr/lib/python3.8/ast.py:371: PendingDeprecationWarning: visit_Str is deprecated; add visit_Constant09:18
jclsn  return visitor(node)09:18
jclsnIs my Python deprecated?09:18
Guest4jclsn What are you trying to accomplish and what did you do to reach those warnings?09:21
jclsnThey appear when I build the kernel09:22
jclsnEvery time09:22
Saur[m]jclsn: There are a couple of commits in OE-Core fixing problems like that. Search the Git log for "visit_Constant".09:26
jclsnI think I also made some progress regarding this weird issue with the kernel09:26
jclsnWhen I checkout linux-fslc-imx to a workspace with devtool modify, everything works fine. When I devtool reset and build normall, the kernel panic occurs. How can this be?09:27
jclsnMaybe checking out silently fails somehow09:27
jclsnSaur: Will have a look09:27
*** tgamblin <tgamblin!~tgamblin@2607:fea8:c2a0:8640::61be> has quit IRC (Ping timeout: 250 seconds)09:28
*** tgamblin_ <tgamblin_!~tgamblin@cpe64777de11593-cm64777de11590.cpe.net.cable.rogers.com> has joined #yocto09:28
jclsngit log | grep -b3 visit_Constant returns nothing09:29
jclsnIn meta-oe, if that is correct09:30
Saur[m]No, that is not OE-Core. Search in meta (or poky)09:31
*** T_UNIX[m] <T_UNIX[m]!~tunixmatr@2001:470:69fc:105::9ea> has joined #yocto09:43
RPjclsn: which version of the project is that with?09:47
jclsnRP: honister09:48
RPjclsn: it means deprecated API in python is being used but I thought we'd fixed that09:48
RPjclsn: e.g. https://git.yoctoproject.org/poky/commit/?id=ca8ef6bc38b8bfd772ff19931b49a076de5c1ec4 and https://git.yoctoproject.org/poky/commit/?id=09ca5e87ec3e19303587c3534e6445ff1d70e47309:48
RPjclsn: those are what Saur[m] was referring to09:49
*** Guest4 <Guest4!~Guest4@2a02-a440-b6e3-1-cd5-22eb-4f84-728d.fixed6.kpn.net> has quit IRC (Ping timeout: 256 seconds)09:49
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto09:49
*** vladest <vladest!~Thunderbi@81-229-209-18-no288.tbcn.telia.com> has joined #yocto09:51
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has joined #yocto09:53
JaMarburton: FWIW: I've added some graphs in https://github.com/shr-project/test-oe-build-time/commit/081926d88779bbcc3fe348a8f7d56c94e2e1b46e I'm happy with my config in https://raw.githubusercontent.com/shr-project/test-oe-build-time/081926d88779bbcc3fe348a8f7d56c94e2e1b46e/threadripper-3970x-128gb-gentoo-kirkstone-2022-03/luneos-dev-emulator-appliance-j70-bb8-with-webruntime-j40.png09:55
JaMaanother interesting behavior was that 8bb-threads happened to use more swap than 64bb-threads, but I guess that's just unlucky scheduling when more heavier do_compile had their memory-usage peak at the same time in https://raw.githubusercontent.com/shr-project/test-oe-build-time/081926d88779bbcc3fe348a8f7d56c94e2e1b46e/threadripper-3970x-128gb-gentoo-kirkstone-2022-03/5-build-8-bb-threads.png compared with09:59
JaMahttps://raw.githubusercontent.com/shr-project/test-oe-build-time/081926d88779bbcc3fe348a8f7d56c94e2e1b46e/threadripper-3970x-128gb-gentoo-kirkstone-2022-03/5-build-8-bb-threads.png09:59
RPJaMa: interesting. I wish I had more time to look at performance :/10:17
* RP has a patch which cuts a couple of million getVar calls out but not sure whether it massively helps or not10:18
Saur[m]A couple of million getVar calls less sounds like it could have an impact...10:19
RPSaur[m]: they hit the expand cache so not as much as you'd think10:19
Saur[m]Ah, ok.10:20
RPSaur[m]: I have another which knocks about 25% of the getVarFlag calls out but I think it breaks something, need to try and track down what10:20
RPI really need to come up with a better timing metric too10:21
Saur[m]Sounds like interesting patches.10:21
LetoThe2ndyo dudX10:26
RPSaur[m]: two different experiments in https://git.yoctoproject.org/poky-contrib/commit/?h=rpurdie/t222&id=e728323330c7e5b26d61775c53fabfc1e308856610:28
RPDoing something with __depends might also help if we had somewhere other than the datastore to poke it10:28
*** flodo <flodo!~flodo@p57987511.dip0.t-ipconnect.de> has joined #yocto10:33
flodohey there guys! I am new to yocto and I am facing some problems I can't solve. I hope someone can help me a bit.10:34
flodoI am trying to boot a core image via pxe and syslinux, I was able to build the bzImage and now I am serving it via pxe10:35
flodoafter loading the bzImage the device is telling me that it is not able to mount the root fs on an unknown block (0,0)10:36
flodoI guess I would therefore also need an initramfs?10:37
Saur[m]RP: You can move the if not srcflags test outside and skip the entire for loop if there are no flags.10:37
*** ilunev <ilunev!~koolkhel@80.72.17.178> has joined #yocto10:43
RPSaur[m]: least of the problems in that code10:47
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has quit IRC (Quit: reboot)10:55
rburtonRP: got a link for the outstanding crypto failure?10:56
*** JaMa <JaMa!~martin@109.238.218.228> has joined #yocto10:56
rburtonarmpit/khem: can you fix meta-oe master now so it builds against oe-core master?11:00
*** ilunev <ilunev!~koolkhel@80.72.17.178> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)11:02
*** kriive <kriive!~kriive@user/kriive> has joined #yocto11:02
*** starblue <starblue!~juergen@dslb-088-078-101-131.088.078.pools.vodafone-ip.de> has quit IRC (Ping timeout: 250 seconds)11:05
*** kriive <kriive!~kriive@user/kriive> has quit IRC (Remote host closed the connection)11:05
*** starblue <starblue!~juergen@dslb-088-078-101-131.088.078.pools.vodafone-ip.de> has joined #yocto11:06
*** kriive <kriive!~kriive@user/kriive> has joined #yocto11:08
RPrburton: I think the main issue now is the 2GB min memory requirement and the test runtime11:12
RPrburton: arm shows https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/2969/steps/12/logs/stdio and IA shows no failure, I think as there isn't free memory11:13
RPrburton: I have a patch locally for the missing tomli dependency11:13
RPrburton: 20 mins so far for the crypto test on arm :/11:14
*** creich <creich!~creich@p200300f6af20a3108e4028e254030d35.dip0.t-ipconnect.de> has quit IRC (Quit: Leaving)11:14
RP(since I don't have KVM)11:14
rburtonamazing news https://gitlab.freedesktop.org/polkit/polkit/-/commit/c7fc4e1b61f0fd82fc697c19c604af7e9fb291a2 polkit can use duktape instead of mozjs11:25
rburtonRP: urgh slow11:25
RPrburton: 32 mins, still going11:25
*** zeddii <zeddii!~zeddii@173.34.88.218> has quit IRC (Excess Flood)11:26
RPrburton: nice, finally :)11:26
rburtonRP: maintainers were understandably trying to not introduce huge regressions but yeah took a while11:26
RPrburton: definitely understandable11:27
*** zeddii <zeddii!~zeddii@173.34.88.218> has joined #yocto11:27
* RP wonders why core-image-ptest-all would have less than 2GB free memory when it has 4GB :/11:30
RPX?11:31
rburtondoubt it11:31
RPit is x86 specific11:31
rburtondoes it actually have 4gb though?11:31
RPqemu is being called with -m 409611:32
rburtonok, fair11:32
RP[    0.027261] Kernel command line: root=/dev/vda rw  mem=4096M ip=192.168.7.2::192.168.7.1:255.255.255.0::eth0:off:8.8.8.8 console=ttyS0 console=ttyS1 oprofile.timer=1 tsc=reliable no_timer_check rcupdate.rcu_expedited=1  printk.time=111:33
RP[    0.036338] Memory: 2028184K/2096600K available (16396K kernel code, 2134K rwdata, 3584K rodata, 1692K init, 2156K bss, 68156K reserved, 0K cma-reserved)11:33
RPdoes anyone know why x86-64 would do that? :/11:35
rburtonwell q35 should support up to 4gb11:38
*** zkrx <zkrx!~slimshady@adsl-89-217-230-50.adslplus.ch> has quit IRC (Ping timeout: 240 seconds)11:39
rburtonq35 does do games with memory though11:40
RPrburton: the ptest had one failure out of 2855 tests :(11:42
RPopenssl memory leak11:42
rburtonif you can share info about the leak I can forward to someone who might be able to fix it11:43
RPrburton: log mailed11:45
Perceval[m]Hello all :) I'm trying to disable all agetty services. I added 'PACKAGECONFIG_remove = "serial-getty-generator"' in systemd_%.bbappend but the services are still there. How would you do it?11:48
rburtonRP: colleague looking quickly now.  i suggest we just disable that test for now though.11:55
rburtonits a grand 300bytes leaked11:55
RPrburton: can you sort a patch to disable?11:57
rburtonyeah11:57
RPrburton: I updated master-next to all the pieces I currently know we need11:58
*** Guest4 <Guest4!~Guest4@2a02-a440-b6e3-1-cd5-22eb-4f84-728d.fixed6.kpn.net> has joined #yocto12:11
rburtonRP: do you remmeber why we have USRBINPATH?12:12
rburtonit's always set to bindir12:12
rburtonah no, it's not12:13
rburtongotcha12:13
RPrburton: Sounds like you have an answer. I'm sure there was a reason...12:15
rburtonbecause its where the interpreters will live12:15
rburtonso native/nativesdk is always /usr/bin, even if the target prefix is /foobar12:15
RPah, yes12:15
rburtonwas the leak only on arm?12:19
rburtonRP ^12:19
rburtonpytest lets you do programatic xfails, so we can make it expected-to-fail on arm hosts12:19
rburtonself-reporting when it works again too that way12:20
RPrburton: it didn't run on x86 so I don't know yet12:20
RPrburton: actually, results just in, seems to work on x8612:20
*** zkrx <zkrx!~slimshady@adsl-89-217-230-95.adslplus.ch> has joined #yocto12:20
RPer, no, didn't run at all12:20
rburtoni wonder why it didn't run at all12:21
RPrburton: lack of memory. I need to debug that12:21
RPrburton: I do at least have a local build to poke at now12:22
rburton one of the leaks is fixed upstream already12:24
RPrburton: setting to 8GB gives me 6GB so we should be able to check x86 now12:26
* RP is wondering where the missing 2GB is going12:26
RPrburton: fails on x86 too12:31
rburtonok12:32
rburtoncan i send you a commit to test?12:32
rburtonlikely faster than me building12:33
RPrburton: yes12:35
RPrburton: ditching the kernel mem= parameter fixes the memory12:35
* RP grabbing some food, back shortly12:35
rburtonRP: poky-contrib:ross/ssl12:38
jclsnRP: Yes, this is in my log. I might have to add that this message only occurs when I have checked out a workspace for linux-fslc-imx. I was wrong about it happening always.12:52
jclsnIt is also weird that my kernel is resolved when I check out a workspace12:53
jclsn*kernel issue12:53
jclsnI mean there shouldn't be a difference if I don't modify the code12:53
qschulzjclsn: there is some gotchas with files in WORKDIR and devtool12:58
qschulzjclsn: I wouldn't be too surprised there are some issues related to the defconfig12:58
jclsnqschulz: gotchas?12:58
*** tgamblin_ <tgamblin_!~tgamblin@cpe64777de11593-cm64777de11590.cpe.net.cable.rogers.com> has quit IRC (Quit: Leaving)12:59
qschulzjclsn: the relative paths between S and WORKDIR aren't the same in devtool and in "normal" bitbake execution12:59
jclsnAh okay12:59
qschulzalso, the defconfig is sometimes only installed if there isn't already a defconfig/.config in WORKDIR12:59
*** tgamblin <tgamblin!~tgamblin@2607:fea8:c2a0:8640::10d4> has joined #yocto12:59
jclsnI am using my defconfigs from the meta-layer12:59
qschulzso that's your next step I guess, doing a diff between a normal bitbake and a devtool'ed run and see what are the differences in the source files13:00
jclsnlike meta-custom/recipes-kernel/linux/linux-fslc-imx/mx8/defconfig13:00
jclsnOkay thanks I will investigate13:00
jclsnAt least I am getting fruther13:01
jclsnStill weird that my colleagues can build without isses13:01
jclsn*issues13:01
jclsnWhere does bitbake checkout the repos btw?13:02
jclsnSearched for them under tmp13:03
qschulzjclsn: in S13:03
qschulzwhich is typically in WORKDIR13:03
qschulzin/under13:03
jclsnso tmp/work?13:04
qschulzif you're looking for tarballs or git repositories before checkout, they are in DL_DIR, which named "downalods"13:04
qschulzjclsn: that and in subdirectories specific to the architecture and name of the recipe but yes13:05
qschulzjclsn: for the kernel, though, it is tmp/work-shared/13:05
jclsnah yeah13:05
jclsnfzf is my friend13:05
jclsnand you :)13:05
jclsntmp/work-shared/machine/kernel-source13:06
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto13:07
jclsnMaybe building in zsh is not a good idea13:11
jclsnWill see if bash makes a difference tomorrow13:11
qschulzjclsn: do the diff of the sources13:11
jclsnHave to go now13:12
jclsnqschulz: I will13:12
RPrburton: its rebuilding quite a bit...13:12
jclsnBut even if I find them, that won't explain why my colleagues can build successfully13:12
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto13:12
qschulzjclsn: you're trying to understand something you don't even know what it is. Figure out what is the issue first and then you can start investigating why it happened13:17
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has joined #yocto13:17
*** Guest4 <Guest4!~Guest4@2a02-a440-b6e3-1-cd5-22eb-4f84-728d.fixed6.kpn.net> has quit IRC (Ping timeout: 256 seconds)13:29
*** wooosaiiii <wooosaiiii!~wooo@89-212-21-243.static.t-2.net> has joined #yocto13:35
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto13:36
rburtonRP: maybe should have made that patch class-target for testing13:38
RPrburton: failed :/13:39
RPrburton: error looks the same13:40
rburtoncan you share the log again? at least one of the error should have gone13:40
RPrburton: looks the same to me. This one is x8613:41
RPrburton: sent13:42
rburtoni'll make it xfail for now :)13:45
*** SSmoogen is now known as Ebeneezer_Smooge13:46
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto13:52
vvnhi all -- so basically python applications implementing a setup.py must now switch to wheels?13:55
rburtonvvn: must, no.  ideally, yes.  that's a change from upstream python, not from us.13:57
rburtonif you want to use setup.py build/install then inherit setuptools3_legacy13:58
vvnrburton: I know it's not from you guys ;-) If the change is trivial I'll switch to wheels13:58
rburtonvvn: leave the inherit as setuptools3 and see if the packaging is the same13:59
rburtonbadly behaved setup.py will suddenly start putting files inthe wrong place with wheels13:59
rburtonbasically, if the setup used absolute paths in data_files, you can't use wheels13:59
vvnrburton: the packages fails with poetry_core.bbclass:1: Could not inherit file classes/pip_install_wheel.bbclass14:04
rburtonyes, there's a patch for meta-oe which didn't get merged yet14:04
rburtontell armpit/khem14:04
rburtonits on the list14:04
rburton(oe-devel)14:04
rburtonRP: ross/ssl has hopefully a workaround for pycrypto14:05
rburtoni'm hoping it was just that one test that failed anyway14:05
vvnrburton: do you have a link? I can add a tested-by if that matters14:07
vvnlet me look for it14:07
rburtonhttps://lists.openembedded.org/g/openembedded-devel/message/9596314:07
rburtoni'm sure you can find the patchwork or lore link if you want to apply it14:07
vvnI think I know its author ;)14:08
vvnnot that easy to find the link14:14
rburtonhttps://lore.kernel.org/openembedded-devel/20220312085607.1129037-1-raj.khem@gmail.com/T/#u14:16
rburtonerm no not that one14:16
rburtonhttps://lore.kernel.org/openembedded-devel/20220312200609.382925-1-ross.burton@arm.com/14:17
rburtonthat one14:17
rburtonlore is great for grabbing the actual patches, https://lore.kernel.org/openembedded-devel/ for oe-devel14:17
vvnadding https://lore.kernel.org/openembedded-devel/20220312200609.382925-1-ross.burton@arm.com/raw to meta-openembedded!14:19
*** creich <creich!~creich@p200300f6af1194100000000000000100.dip0.t-ipconnect.de> has joined #yocto14:19
*** davidinux <davidinux!~davidinux@84.17.59.182> has quit IRC (Ping timeout: 252 seconds)14:31
*** davidinux <davidinux!~davidinux@net-130-25-196-238.cust.vodafonedsl.it> has joined #yocto14:33
*** AKN <AKN!~AKN@122.162.3.216> has joined #yocto14:44
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has quit IRC (Quit: Leaving)14:46
vvnrburton: build fixed with setuptools3_legacy and your patch14:57
RPrburton: do I want the ssl leak fixes too?14:59
rburtonif they don't help, don't bother i guess14:59
RPrburton: I couldn't seem to see any difference so either they don't or a messed up :/15:00
rburtoni'll kick a build and see15:03
moto-timoMore gremlins in py crypto?15:05
moto-timoSigh15:05
*** flodo <flodo!~flodo@p57987511.dip0.t-ipconnect.de> has quit IRC (Quit: Client closed)15:12
RPmoto-timo: oh yes :/15:23
moto-timo:/15:26
*** amitk <amitk!~amit@103.208.71.35> has quit IRC (Ping timeout: 250 seconds)15:26
RPmoto-timo: reproducibility failed, qemux86 testing memory limits were wrong, ptest on python3-crypto fails, there was a typo in the ptest patch and so on15:29
RPmoto-timo: I'll squash master-next a bit soon but it currently gives a bit of the story15:30
RPrburton: that patch doesn't work :/15:33
RPrburton: I've mailed it to you15:34
*** AKN <AKN!~AKN@122.162.3.216> has quit IRC (Ping timeout: 250 seconds)15:38
moto-timoRP: I’ve been trying to follow along15:41
*** fleg <fleg!dfbb34cb39@user/fleg> has quit IRC (Remote host closed the connection)15:42
rburtonRP: bah15:42
*** raghavgururajan <raghavgururajan!ea769b8000@user/raghavgururajan> has quit IRC (Remote host closed the connection)15:42
*** fleg <fleg!dfbb34cb39@user/fleg> has joined #yocto15:42
rburtonRP: oh ffs, sorry15:42
*** raghavgururajan <raghavgururajan!ea769b8000@user/raghavgururajan> has joined #yocto15:42
RPrburton: I at least clearly did apply your patch :)15:44
rburtonrepushed, it needed reason="..."15:45
RPrburton: right :)15:45
*** chep <chep!~chep@82-65-36-115.subs.proxad.net> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)15:45
*** chep <chep!~chep@82-65-36-115.subs.proxad.net> has joined #yocto15:48
*** expert[m] <expert[m]!~expertmat@2001:470:69fc:105::c8b> has quit IRC (Quit: You have been kicked for being idle)16:00
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)16:12
*** frieder <frieder!~frieder@i4DF677E2.static.tripleplugandplay.com> has quit IRC (Remote host closed the connection)16:17
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has quit IRC (Quit: Leaving)16:19
*** frieder <frieder!~frieder@i4DF677E2.static.tripleplugandplay.com> has joined #yocto16:23
*** frieder <frieder!~frieder@i4DF677E2.static.tripleplugandplay.com> has quit IRC (Remote host closed the connection)16:42
*** AKN <AKN!~AKN@103.163.248.14> has joined #yocto16:42
*** AKN <AKN!~AKN@103.163.248.14> has quit IRC (Client Quit)16:42
*** AKN <AKN!~AKN@103.163.248.14> has joined #yocto16:43
RPrburton: good news. that works :)16:47
rburtonphew16:47
rburtonsorry about that16:47
RPrburton: we're getting there16:50
* RP notes the installer patch does get on with master-next but easily fixed16:50
*** AKN <AKN!~AKN@103.163.248.14> has quit IRC (Read error: Connection reset by peer)16:53
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 260 seconds)16:55
*** AKN <AKN!~AKN@103.163.248.14> has joined #yocto16:57
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed)17:04
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto17:08
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)17:12
*** ecdhe_ <ecdhe_!~ecdhe@user/ecdhe> has quit IRC (Read error: Connection reset by peer)17:12
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has joined #yocto17:13
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 240 seconds)17:15
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection)17:24
armpitvvn: fix now in master: https://git.openembedded.org/meta-openembedded/commit/?id=3d93230c3e0fff2157fbdf63769629878cd3653217:28
kanavinRP: looks like doing version updates during freeze isn't causing too much trouble?17:30
kanavinRP: should I do another batch after AUH runs tomorrow?17:30
RPkanavin: so far so good. I'm having  headache with other issues17:31
RPkanavin: I'm not against another batch for evaluation17:31
kanavinRP: right, ask if you think I can help somewhere17:31
rfs613for a CVE fix affecting multiple branches, should I submit multiple patches, or is there a tag etc to say "apply to these branches" ?17:40
rburtonrfs613: please sent multiple patches as it's unlikely the same patch will apply to all the branches anyway17:40
rburtondifferent maintainers for each branch, you see17:41
rfs613rburton: I was afraid you'd say that... but yeah I understand :-)17:41
RPkanavin: thanks, I don't quite know what I'm doing anymore now, let alone where I need help! :)17:41
kanavinRP: maybe your neurons are asking for afk so they can rearrange themselves? :)17:43
*** mckoan is now known as mckoan|away17:43
RPkanavin: I think they're dreading trying to make sense of all the things in -next into a coherent patch series17:44
*** Herrie <Herrie!~Herrie@110-31-146-85.ftth.glasoperator.nl> has quit IRC (Ping timeout: 240 seconds)17:46
*** lucaceresoli <lucaceresoli!~lucaceres@77.244.183.192> has quit IRC (Quit: Leaving)17:54
RPGreat, we now see the same failure on x86 and arm :)17:55
*** florian_kc <florian_kc!~florian@dynamic-093-131-129-253.93.131.pool.telefonica.de> has joined #yocto18:01
*** florian_kc <florian_kc!~florian@dynamic-093-131-129-253.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 240 seconds)18:07
vvnarmpit: thank you18:10
*** Herrie <Herrie!~Herrie@110-31-146-85.ftth.glasoperator.nl> has joined #yocto18:13
*** AKN <AKN!~AKN@103.163.248.14> has quit IRC (Read error: Connection reset by peer)18:21
*** Herrie|2 <Herrie|2!~Herrie@110-31-146-85.ftth.glasoperator.nl> has joined #yocto18:26
*** Herrie <Herrie!~Herrie@110-31-146-85.ftth.glasoperator.nl> has quit IRC (Ping timeout: 256 seconds)18:27
*** Herrie|2 is now known as Herrie18:27
*** roussinm <roussinm!~mroussin@bras-base-qubcpq1306w-grc-35-74-12-165-208.dsl.bell.ca> has joined #yocto18:37
rburtonRP: you're going to squash bits of master-next before merging right :)18:48
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)18:53
rfs613newbie question about layers... I've added a layer and its dependencies... but bitbake doesn't seem to want to see any of the recipes contained in the new layer. How to debug what I did wrong?18:54
rfs613(this is actually for the CVE fix on multiple branches, to check that it actually applies/builds)18:55
*** Guma <Guma!~Guma@172.93.207.156> has joined #yocto18:59
*** goliath <goliath!~goliath@user/goliath> has joined #yocto19:03
smurrayrfs613: does "bitbake-layers show-layers" look like you expect?19:08
rfs613smurray: yes, it appears in there19:09
rfs613smurray: and19:10
smurrayrfs613: that does seem strange, then19:10
rfs613"bitbake-layers layerindex-show-depends meta-security" also seems happy (i'm adding meta-security)19:10
smurrayyou'd get an error if an explicitly required layer wasn't present19:11
smurrayi.e. via LAYERDEPS19:11
*** cambrian_invader <cambrian_invader!~cambrian_@50-195-82-171-static.hfc.comcastbusiness.net> has joined #yocto19:12
rfs613yep, when I first tried to add it, it wanted several other layers, meta-perl and meta-python for example, so I added those as well.19:12
smurrayperhaps look through "bitbake-layers show-recipes" to see if any of the recipes are being seen, and look for a stray BBMASK definition in your conf, maybe19:13
cambrian_invaderdoes anyone know where to send patches for https://source.codeaurora.org/external/qoriq/qoriq-components/meta-qoriq/ ?19:13
rfs613smurray: oh, I got it now... meta-security has several meta-layers within, I only added the top-most one.19:15
*** dev1990 <dev1990!~dev@37-128-75-106.adsl.inetia.pl> has joined #yocto19:16
GumaI was wondering if anyone knows how to fix this issue I encountered. I am conneced to my remote machine (ubuntu) from my macosx over ssh. When  connected I do try to run minicom to connect to serial port (yocto embedded device). Everything works fine but I do not see cursor  on command line or in vim. TERM=console.19:16
GumaSame thing happens when I am working from my ubuntu machine so it does not seem it is related to Mac. But when using putty on windows everything works19:17
smurrayrfs613: whew19:17
smurraycambrian_invader: that's a good question, probably will have to ask your NXP support contact if you have one.  If it's something where there's still qoriq bits in meta-freescale, like the kernel, you could maybe switch to using that version and working with the community folks19:20
cambrian_invadersmurray: I have some patches for meta-qoriq itself; specifically enabling some dynamic layers19:21
cambrian_invaderI'19:21
cambrian_invaderll try seeing if I can get an answer from NXP support19:22
smurraycambrian_invader: right, but NXP do not engage with the community at all for any of their BSP stuff, you'll not the README.md in that layer has no contact information19:22
smurrayerr, note19:22
cambrian_invaderwell, I asked on the meta-freescale list19:22
cambrian_invaderwhich seems active19:22
cambrian_invaderbut no response as of yet19:22
smurraycambrian_invader: stuff like meta-qoriq and meta-imx are developed by NXP and thrown over the wall, they don't involve anyone from the community19:23
cambrian_invaderoh, is meta-freescale something different?19:23
*** florian_kc <florian_kc!~florian@dynamic-093-131-129-253.93.131.pool.telefonica.de> has joined #yocto19:23
cambrian_invaderI can tell that meta-qoriq is "over the wall"19:24
smurraycambrian_invader: AIUI some people working on meta-freescale used to be under contract with Freescale/NXP, but that ended a couple of years ago and it's pretty much just community maintained now19:24
cambrian_invaderhuh, interesting19:24
cambrian_invaderI saw some nxp emails on the mailing list19:24
cambrian_invaderso I assumed it was official19:24
smurraycambrian_invader: they do push some things, but their party-line is to use meta-imx which adds a bunch of stuff on top AFAIK19:25
cambrian_invaderyeah, I'm not really happy with how diverged from mainline the *-imx stuff is19:25
cambrian_invaderlayerscape/qoriq seems better, but only because it doesn't seem like there is as much development19:26
smurrayyes, there's a bunch of parallel dev going on inside NXP by different groups, I recently stumbled upon a whole different set of layers for the S32 chips by different devs AFAICT19:27
RPrburton: yes, that is the plan19:38
*** Guma <Guma!~Guma@172.93.207.156> has quit IRC (Quit: Good Night Everyone...)20:53
rburtonmoto-timo: why does py-crypto have a RDEPENDS:class-target?20:59
rburtonRP: some small fixups in ross/ssl you'll want to squash in21:02
moto-timorburton: those are stdlib from python3… at one point that was breaking -native or nativesdk-  or so I remember from JaMa21:08
rburtonthat means python should be fixed then surely21:09
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 240 seconds)21:12
moto-timoAnyway, it’s just a separation of deps that always apply vs. python3 sub packages that are only needed for target21:12
rburtonthere's no native/target configuration in the recipe, so it sounds like the native/sdk provides are (were?) incomplete?21:13
moto-timosub packages as in https://git.yoctoproject.org/poky/tree/meta/recipes-devtools/python/python3/python3-manifest.json#n91721:15
moto-timoSo no, those don’t apply to native/nativesdk21:15
moto-timoMinimal install without full stdlib on target21:17
*** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has joined #yocto21:24
rburtonmoto-timo: python3-native will rprovide those21:25
rburton(should)21:25
moto-timoSure. It’s mostly just handy to remember what is a sub package vs. a recipe for a module. But I’m not going to die on that mountain. Do what you think is best. It has probably been a couple years since that behavior was broken.21:27
moto-timoThings with Perl are more obvious because the oe specific sub packages are named Perl-module-foo. With python you have to remember to look at the manifest first, since you won’t fine e.g. python-numbers on layerindex or pypi21:32
moto-timos/fine/find/21:32
moto-timoThis confuses folks21:33
moto-timos/python/python3/21:33
*** dev1990 <dev1990!~dev@37-128-75-106.adsl.inetia.pl> has quit IRC (Quit: Konversation terminated!)21:46
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto21:50
*** florian_kc <florian_kc!~florian@dynamic-093-131-129-253.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 240 seconds)21:51
*** behanw <behanw!uid110099@id-110099.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)21:52
*** mvlad <mvlad!~mvlad@2a02:2f08:4114:c500:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)22:05
*** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has quit IRC (Quit: Client closed)22:05
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)22:16
*** dgriego <dgriego!~dgriego@user/dgriego> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)22:17
*** florian_kc <florian_kc!~florian@dynamic-093-131-129-253.93.131.pool.telefonica.de> has joined #yocto22:26
*** florian_kc <florian_kc!~florian@dynamic-093-131-129-253.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 268 seconds)22:36
*** pabigot <pabigot!~pab@67-1-16-117.tcso.qwest.net> has quit IRC (Ping timeout: 256 seconds)22:40
*** yannd <yannd!~yann@88.120.44.86> has joined #yocto22:40
*** pabigot <pabigot!~pab@67-1-16-117.tcso.qwest.net> has joined #yocto22:42
moto-timoRP: thank you for sending out the patch bomb... I was about to ask what you wanted me to do about it22:53
RPmoto-timo: it took a bit of beating into shape but I think we're kind of there (keeping history of changes from the meta-oe version)22:56
moto-timoRP: yeah... not so smooth as we would have hoped22:56
moto-timoRP: it also highlights the disparity between what is in meta-openembedded vs. what is hammered on in core with the AB22:57
RPmoto-timo: right, core does have a slightly higher bar :/22:58
moto-timoRP: which is the entire reason we wanted py-crypto to move... it needs to be hammered on22:58
* moto-timo happy despite the churn22:58
RPmoto-timo: it is all driving me slightly crazy :(23:01
moto-timoRP: you and me both23:01
* RP lost half the weekend to it :(23:01
moto-timoRP: sorry... I clearly did not expect so much trouble... sigh23:06
RPmoto-timo: I'd hoped it would be better :)23:12
RPThere is just so much stuff going on, that is the challenge23:12
*** kevinrowland <kevinrowland!~kevinrowl@104.129.199.51> has joined #yocto23:24
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)23:25
*** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto23:27
kevinrowlandHow can I determine why a "-dev" package was added to my image manifest and rootfs, when it wasn't added to `IMAGE_INSTALL` and doesn't show up in the `RDEPENDS` of any other package?  `FILES_${PN}-dev` for this package is set to `/usr/include /usr/lib`, which I know is wrong, but I'm not looking to fix that right now. I'm interested in knowing23:28
kevinrowlandwhich bit of `bitbake` noticed that some library in `/usr/lib` is needed by some other package at runtime, and therefore decided to install the whole "-dev" package. Any pointers?23:28
RPkevinrowland: it will be the shlibs code in package.bbclass23:30
RPkevinrowland: I'd imagine it was injected into the RDEPENDS of some packages at package creation time23:31
kevinrowlandRP: Wonderful, thank you, I'll take a look23:31
*** florian_kc <florian_kc!~florian@dynamic-093-131-129-253.93.131.pool.telefonica.de> has joined #yocto23:33
*** Bardon <Bardon!~Bardon@user/Bardon> has quit IRC (Ping timeout: 272 seconds)23:37
*** fitzsim <fitzsim!~user@69-165-165-189.dsl.teksavvy.com> has quit IRC (Read error: Connection reset by peer)23:42
*** Bardon <Bardon!~Bardon@user/Bardon> has joined #yocto23:46
*** fitzsim <fitzsim!~user@69-165-165-189.dsl.teksavvy.com> has joined #yocto23:46

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!