Monday, 2024-03-04

*** florian <florian!> has quit IRC (Ping timeout: 272 seconds)00:10
khemRP: sent a fix for rust 1.75 on rv3200:20
RPzeddii: I've go 1.22 in master-next. No idea if it will work but I think I fixed the two issues seen on oe-core on the autobuilder00:24
RPkhem: ok, will try and test in the next round of builds00:25
RPkhem: I'm wondering about something like
khemhmm so idea is per recipe build-tools tarball ?00:30
khemRP: I am building the usual suspects in meta-oe with go 1.22 and see if there are any hidden daemons00:31
*** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 255 seconds)01:25
*** justache <justache!~justache@user/justache> has joined #yocto01:27
*** zenstoic <zenstoic!> has quit IRC (Quit: Connection closed for inactivity)01:28
*** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 255 seconds)01:52
*** justache <justache!~justache@user/justache> has joined #yocto01:54
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 264 seconds)02:04
*** davidinux <davidinux!~davidinux@> has joined #yocto02:04
moto-timoFWIW, the crops yocto-dockerfiles and poky-containers are updated to include fedora-37 (yes, I know it is already EOL), fedora-38, fedora-39 and opensuse-15.502:20
moto-timodebian-12 is one of those distros that insists you should not use pip to install anything, so it will force a change in the test scripts02:21
moto-timoI also noticed the extsdk-container had lapsed out of weekly builds, so those are triggered again. GitHub Actions times out if the repo has not had any recent commits... but this repo doesn't need new anything... the underlying container needs updating to get new security and vulnerability fixes.02:22
*** jclsn <jclsn!~jclsn@2a04:4540:6507:6200:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 272 seconds)02:36
*** jclsn <jclsn!~jclsn@2a04:4540:650f:6c00:2ce:39ff:fecf:efcd> has joined #yocto02:37
*** xmn <xmn!> has quit IRC (Read error: Connection reset by peer)02:43
*** xmn <xmn!> has joined #yocto02:45
*** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 264 seconds)02:50
*** justache <justache!~justache@user/justache> has joined #yocto02:55
*** xmn <xmn!> has quit IRC (Ping timeout: 272 seconds)03:12
*** prabhakarlad <prabhakarlad!~prabhakar@> has quit IRC (Quit: Client closed)03:30
moto-timopaulg:  is already rolling his eyes
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Read error: Connection reset by peer)03:35
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto03:39
*** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 264 seconds)03:52
*** justache <justache!~justache@user/justache> has joined #yocto03:53
*** mulk <mulk!> has quit IRC (Ping timeout: 255 seconds)04:09
*** mulk <mulk!> has joined #yocto04:10
*** Perflosopher <Perflosopher!~perflosop@> has quit IRC (Quit: The Lounge -
*** Saur2 <Saur2!~Saur26@> has quit IRC (Quit: Client closed)04:51
*** Saur2 <Saur2!~Saur2@> has joined #yocto04:52
*** amitk <amitk!~amit@> has joined #yocto05:07
*** simone <simone!~ile@2a02:810d:a940:35fc:5831:bcce:40fa:28eb> has quit IRC (Ping timeout: 255 seconds)05:29
paulgretirement looks more appealing every day....05:38
*** alperak <alperak!~alperak@> has joined #yocto05:45
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has joined #yocto05:47
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 272 seconds)05:58
*** amitk <amitk!~amit@> has joined #yocto06:01
*** npcomp <npcomp!~user@user/npcomp> has joined #yocto06:05
*** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 264 seconds)06:10
*** justache <justache!~justache@user/justache> has joined #yocto06:11
*** alessioigor <alessioigor!~alessioig@> has joined #yocto06:38
*** goliath <goliath!~goliath@user/goliath> has joined #yocto07:08
*** Chaser <Chaser!~Chaser@user/chaser> has joined #yocto07:08
*** Chaser <Chaser!~Chaser@user/chaser> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)07:22
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 264 seconds)07:23
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has quit IRC (Remote host closed the connection)07:23
*** amitk <amitk!~amit@> has joined #yocto07:25
*** vladest <vladest!> has quit IRC (Ping timeout: 260 seconds)07:29
*** mckoan|away is now known as mckoan07:29
mckoangood morning07:33
*** Kubu_work <Kubu_work!> has joined #yocto07:34
*** mvlad <mvlad!~mvlad@2a02:2f05:850d:7800:9306:d1a3:f874:d884> has joined #yocto07:36
*** rob_w <rob_w!> has joined #yocto07:44
*** vladest <vladest!~Thunderbi@> has joined #yocto07:55
*** vladest <vladest!~Thunderbi@> has quit IRC (Remote host closed the connection)08:00
*** vladest <vladest!~Thunderbi@> has joined #yocto08:04
LetoThe2ndyo mckoan08:05
*** vladest <vladest!~Thunderbi@> has quit IRC (Remote host closed the connection)08:07
*** vladest <vladest!~Thunderbi@> has joined #yocto08:10
*** rfuentess <rfuentess!> has joined #yocto08:12
*** vladest <vladest!~Thunderbi@> has quit IRC (Client Quit)08:12
*** vladest <vladest!~Thunderbi@> has joined #yocto08:16
*** zpfvo <zpfvo!> has joined #yocto08:21
*** ptsneves <ptsneves!> has joined #yocto08:23
*** ptsneves1 <ptsneves1!> has joined #yocto08:25
*** ptsneves <ptsneves!> has quit IRC (Read error: Connection reset by peer)08:25
*** ptsneves1 is now known as ptsneves08:25
*** zpfvo <zpfvo!> has quit IRC (Ping timeout: 264 seconds)08:40
*** Chaser <Chaser!~Chaser@user/chaser> has joined #yocto08:40
*** mbulut <mbulut!> has joined #yocto08:43
*** zpfvo <zpfvo!> has joined #yocto08:54
mckoanLetoThe2nd: hey09:11
*** kanavin <kanavin!~Alexander@2a02:2454:299:c100:b25:37c3:ea9f:574c> has quit IRC (Remote host closed the connection)09:19
*** frieder <frieder!> has joined #yocto09:28
*** mbulut <mbulut!> has quit IRC (Quit: Leaving)09:30
*** florian <florian!> has joined #yocto09:42
*** Saur22 <Saur22!~Saur2@> has joined #yocto09:51
*** Saur2 <Saur2!~Saur2@> has quit IRC (Ping timeout: 250 seconds)09:55
*** pidge <pidge!~pidge@> has joined #yocto10:03
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 272 seconds)10:04
*** prabhakalad <prabhakalad!~prabhakar@> has joined #yocto10:05
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto10:06
*** zpfvo <zpfvo!> has quit IRC (Quit: Leaving.)10:10
*** zpfvo <zpfvo!> has joined #yocto10:10
*** kanavin <kanavin!~Alexander@2a02:2454:299:c100:b25:37c3:ea9f:574c> has joined #yocto10:16
*** florian <florian!> has quit IRC (Ping timeout: 272 seconds)10:22
*** zpfvo <zpfvo!> has quit IRC (Ping timeout: 255 seconds)10:26
*** zpfvo <zpfvo!~fvo@> has joined #yocto10:41
Piraty   so CVE_PRODUCT is part of the nvd/CPE ?10:41
*** florian <florian!> has joined #yocto10:48
rburtonPiraty: its the vendor:product name of that project in the NVD11:28
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 264 seconds)11:33
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto11:34
*** florian_kc <florian_kc!> has joined #yocto11:38
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto11:41
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)12:04
Piratycan you hint me the entry point to the command ?12:10
rfs613Piraty: not sure if this is what you are looking for, but usually you enable this check by adding INHERIT += "cve-check" to local.conf12:22
rfs613that way it runs as part of the normal image build, on every recipe. Alternatively you can run it for a single recipe by doing "bitbake -c cve_check recipiename"12:23
Piratyi want to understand what it does, i.e. see the api call or whatever12:25
Piratycan't really it in poky12:26
rfs613ah, well, best to look at the code - there are two parts, one to download the NVD database and produce a local version (sqlite? it's been a while since i looked)12:26
rfs613and the second part does lookups for each package against that database12:27
Piratyi found meta/classes/cve-check.bbclass12:27
Piratybeat you :p12:27
rfs613by seconds ;-)12:28
Piratypulling the whole DB from nvd and store it in sql3 seems common for many of those cve tools12:28
rfs613yeah... you don't want to be querying on each build12:29
rfs613and incrementally updating the db makese sense too, it's huge12:29
Piratymatching a package to cpe and filtering irrelevant cve entries from db query's response is the hard part12:29
Piratyhuge: no .   is nvd hell slow at providing the db? yes12:29
rfs613that's part of it... but the DB itself often contains less-than-ideal information, filtering that (and perhaps trying to get it fixed) is also a big part12:29
rfs613especially it is hard to track fixes that get backported to olde maintenance branches... the way nvd tries to capture that is a frequent source of incorrect reports12:30
Piratythat bbclass file looks like the inbreed of Makefile + python3 i never wanted to see12:31
Piratymust be a pain to debug12:34
rfs613hehe i haven't deatl with it in a while (like a few years)12:35
rburtonthere is a plan to rip it out into a standalone tool for easier development/testing/etc.12:36
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 252 seconds)12:57
*** zpfvo <zpfvo!> has joined #yocto13:20
*** luc4 <luc4!~luca@2a00:6d43:501:1201:1c91:4774:fadd:2ce4> has joined #yocto13:23
*** rob_w <rob_w!> has quit IRC (Ping timeout: 272 seconds)13:41
*** rob_w <rob_w!> has joined #yocto13:50
*** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 264 seconds)13:56
*** justache <justache!~justache@user/justache> has joined #yocto14:03
*** xmn <xmn!> has joined #yocto14:05
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto14:23
*** sotaoverride is now known as Guest700514:39
*** Guest7005 <Guest7005!> has quit IRC (Killed ( (Nickname regained by services)))14:39
*** ctraven is now known as sotaoverride14:39
*** sotaover1ide <sotaover1ide!> has joined #yocto14:39
*** Dr_Who <Dr_Who!~tgall@> has joined #yocto14:40
*** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 264 seconds)14:42
*** justache <justache!~justache@user/justache> has joined #yocto14:47
*** rob_w <rob_w!> has quit IRC (Remote host closed the connection)14:52
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)15:00
*** rsalveti <rsalveti!> has joined #yocto15:17
*** Dr_Who <Dr_Who!~tgall@> has quit IRC (Quit: ZZZzzz…)15:47
qschulzdoes anyone have a multi-repo setup within gitlab-ci with kas for testing merge requests from one repo still build in the other repo? (e.g. I have a public bsp layer and a private demo layer, I want to make sure when I push to the bsp layer, the demo layer still builds)15:58
*** vladest <vladest!~Thunderbi@> has quit IRC (Ping timeout: 264 seconds)16:01
yoctonqschulz: partialy (not kas and it's still a WIP)16:05
qschulzyocton: if not kas, are you using the "new" layer tool in Yocto or something handcrafted?16:08
*** frieder <frieder!> has quit IRC (Remote host closed the connection)16:09
yoctonqschulz: we use yocto-cooker (not related to the Yocto project)
*** Saur62 <Saur62!~Saur22@> has joined #yocto16:10
yocton... but we will hapilly migrate to the new tool16:10
*** luc4 <luc4!~luca@2a00:6d43:501:1201:1c91:4774:fadd:2ce4> has quit IRC (Ping timeout: 256 seconds)16:11
*** Saur22 <Saur22!~Saur2@> has quit IRC (Ping timeout: 250 seconds)16:13
*** Dr_Who <Dr_Who!~tgall@> has joined #yocto16:14
*** starblue <starblue!> has joined #yocto16:43
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has joined #yocto16:48
*** rfuentess <rfuentess!> has quit IRC (Remote host closed the connection)16:53
*** mckoan is now known as mckoan|away17:04
moto-timoqschulz: pidge and tgamblin and I were talking about such an architecture, but we haven't really gotten it going yet.17:06
moto-timoqschulz: happy to bounce ideas around. It seems like a fairly obvious direction to go in.17:07
* moto-timo also happy to use the new tool17:07
*** florian <florian!> has quit IRC (Quit: Ex-Chat)17:09
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 264 seconds)17:12
*** zpfvo <zpfvo!> has quit IRC (Remote host closed the connection)17:12
*** vladest <vladest!> has joined #yocto17:15
qschulzmoto-timo: maybe I should shoot a mail on the ML, because I have a feeling this may require a bit more than a few lines on IRC :)17:16
moto-timoqschulz: agreed17:19
qschulzmoto-timo: that'll take some time though, need to do some research on gitlab-ci multi-repo pipelines :)17:25
moto-timoqschulz: I get it. This is part of why we didn't get anything "baked" yet.17:26
qschulzmoto-timo: I got a bit crazy last week and implemented dynamic child pipelines for runtime generation of jobs in gitlab ci :)17:28
qschulz(but nothing we could use for multi-repo stuff :/)17:28
*** Smokey <Smokey!> has joined #yocto17:34
*** Dr_Who <Dr_Who!~tgall@> has quit IRC (Quit: ZZZzzz…)17:35
*** Dr_Who <Dr_Who!~tgall@> has joined #yocto17:38
*** kpo <kpo!> has joined #yocto17:41
*** Dr_Who <Dr_Who!~tgall@> has quit IRC (Ping timeout: 255 seconds)17:42
*** ptsneves <ptsneves!> has quit IRC (Ping timeout: 252 seconds)17:46
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 246 seconds)17:58
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto18:00
*** Saur78 <Saur78!~Saur62@> has joined #yocto18:05
*** Saur62 <Saur62!~Saur22@> has quit IRC (Ping timeout: 250 seconds)18:08
*** Smokey <Smokey!> has quit IRC (Quit: Client closed)18:35
moto-timoqschulz: I might just try to recreate the git submodules bot update script we had back in the "Living on Master" days (2018?)18:52
moto-timoqschulz: kas is great, but I am also trying to entertain the submodules folks.18:52
khemqschulz: if you like github actions then look at yoe distro ci and meta-clang ci19:02
*** alperak <alperak!~alperak@> has quit IRC (Quit: Client closed)19:05
*** alperak <alperak!~alperak@> has joined #yocto19:07
moto-timokhem: as you know, yoe-distro is my poster child for both GitHub Actions and submodules.19:10
jdiezhi, I am trying to debug a build tool written in python (colcon) that seems to not detect one of the plugins it needs to build my recipe. The python `sys.path` looks correct. Is there any way I can run python (or other commands) in the native sysroot, as bitbake would?19:12
*** Haxxa <Haxxa!> has quit IRC (Quit: Haxxa flies away.)19:15
jdiezhm, i tried sourcing the temp/run.do_compile.XXX script but that actually called do_compile and `exit`ed my shell19:17
khemmoto-timo: kool.. ( KDE plasma 6.0 released this week so 'c' is now 'k' for sometime )19:17
moto-timokhem: and it's all about Qt6 so there's that19:18
*** Haxxa <Haxxa!> has joined #yocto19:18
khembut I am impressed with plasma6, this is the best release ever19:18
moto-timokhem: I have been intrigued by plasma, so I will have to take a look. I still want a "Yocto Project built daily driver desktop". Why not?19:18
khemyeah use meta-kde19:19
khemmy daily drivers are arch and nixos but thats just convenience19:19
moto-timoI guess I'm still on GNOME by default on Ubuntu and Debian.19:19
khemugh caveman :)19:19
moto-timoI never quite got arch installing easily. I gave up on Gentoo when it broke my ethernet after a couple weeks of no upgrades. NixOS is interesting, but not a silver bullet.19:20
moto-timoI will freely admit that I do hold on to some old ways.19:20
khemI installed arch once in 2016 and since then I have been just doing pacman -Syu19:20
moto-timoyeah. but can you explain in a few sentences what you did in 2016? lol19:21
khemI want to keep this machine going till 2026 so I can say I managed a machine with rolling release for 10 years19:21
moto-timoI'm sure it got better. I looked at it in 2017-2018 I think.19:21
khemyes arch has a very good handbook follow step by step. you will never mess it up19:22
moto-timoI kind of wish we could claim arch was a support distro for YP. oh well.19:22
moto-timoOk. The next workstation I will start with that.19:23
*** florian_kc <florian_kc!> has joined #yocto19:23
khemyou can also use some derivatives like EndevourOS, Garuda19:23
moto-timoI am tired of grumbling about ubuntu (snaps are horrible) and debian (too sluggish)19:23
moto-timosluggish meaning they do not upgrade packages often enough19:23
khemthey have graphical installers, I personally find Garuda quite impressive but never used it for long19:23
moto-timoFedora is too much churn for me these days. RH engineers are doing all kinds of new things, but it's hard to stay in sync.19:24
khemNixos is whole new game19:24
moto-timoI gave up on Fedora being a daily driver around fedora-28. When the Modularity stuff was churning HARD.19:24
khemespecially with flakes AI tools become to easy to use19:25
moto-timoOh, I have watched some NixOS live streams. It makes a lot of sense for infrastructure roll-out.19:25
moto-timoBut I was watching the Mastodon livestream when Kris Nova gave up on NixOS because it eventually introduced new problems.19:25
moto-timoand I don't do enough virtualization for my daily drivers to make proxmox make sense.19:26
moto-timoI've also now got enough Terraform/OpenTofu under my belt that cloud infra is rolled out with that.19:27
JaMajdiez: you can use devtool to simulate the env, but when I'm already in WORKDIR,then I usually source the corresponding run.do_* file (if it's shell task) after editting out the exit calls (3-4 of them typically)19:29
jdiezJaMa: yeah, the latter is what I did, and seemed to work for my purpose19:29
jdiezhow do you do it with devtool?19:29
*** simonew <simonew!~ile@2a02:810d:a940:35fc:f47d:1bff:e43a:e97a> has joined #yocto19:33
halsteadmoto-timo: We had an ArchLinux worker for a bit and SUSE Tumbleweed for a long time. Does it make sense to test the build system on rolling releases though?19:33
JaMakhem: I'm close to 20 years of rolling gentoo install :)19:34
halsteadI ran Gentoo on my home server for years when I had one. Arch is on my personal laptop and I love it.19:34
moto-timohalstead: It probably does not make sense. But we have a lot of folks in the field using Arch Linux as a daily driver (and Gentoo). In practice? I just add my own distro to the SANITY_TESTED_DISTROS and ignore the fact that it isn't tested by the AB.19:35
* halstead nods.19:35
moto-timoit's just this "we know you are using Arch Linux, why do we remind you that you aren't supported every time you run a build" nag that I wonder about.... but as I said. I have a hammer for that.19:35
*** sev99 <sev99!> has joined #yocto19:35
moto-timoI also figure folks that are running Arch also don't give a crap about that warning. :)19:36
JaMathe hammer makes sense in this case, because each install will be different, so you manually adding it to SANITY_TESTED_DISTROS you agree that you're the warrantee of your OS19:36
moto-timoJaMa: very VERY good point.19:37
moto-timosort of like "I_PROMISE_TO_STOP_USING_PYTHON_2"19:37
JaMahaving it in e.g. poky's SANITY_TESTED_DISTROS would be very misleading on the other hand19:37
moto-timoyeah. my usual half baked idea19:38
moto-timoI was even reminded about which versions are currently claimed in sanity tested distros when I added some new ones to crops yesterday. This is why those builds do not fail on warnings ;)19:39
*** vladest <vladest!> has quit IRC (Remote host closed the connection)19:40
moto-timoAlso, for the record, a rolling Yocto Project release in the field was HIGHLY unpopular amongst customers.19:40
JaMagentoo "works" for me as well, but living on the edge sometimes gives some challenges (which I don't mind but others might), being one of first to willingly switch to python 3.12, latest gcc, glibc-2.39 (and building uninative locally before it's built officially) :)19:41
moto-timo(ClearLinux proved that no one in embedded wanted a rolling release updating multiple times a day)19:41
moto-timoAlso, going away to lunch and coming back and your build breaks is not going to make developers happy. (Training session I took on CL)19:42
JaMaI think it's very different to have rolling distro for devs (who can deal with some daily changes or even breakages) or having it for everybody (who don't really care about the underlaying OS)19:42
moto-timoThis is the point.19:42
moto-timoThanks for stating it so nicely.19:43
moto-timoand then there is the CIP end of things where nothing is allowed to change or update ever but yet it needs to be supported for 30 years and be secure and hardened.19:43
moto-timo(mostly tongue in cheek, but there is some truth)19:44
JaMano problem, just release it perfect on 1st try :)19:44
moto-timoRelease: develop it, test it, build it, ship it encased in lead and concrete and deploy it to the bottom of the ocean.19:44
moto-timoIt will be perfect forever.19:45
moto-timoI think I'll start a new OS project called "Amber".19:45
moto-timoAll commits and pull requests will be automatically rejected.19:45
moto-timoIt will use the Linux 2.26 kernel of course.19:46
frayrolling releases are fine for operating system/integration developers..   but the screaming that comes from app devs, app integrators, devops teams, etc is remarkable..19:47
moto-timoand yet they want the newest NodeJS and the latest npms19:48
fraythe only time I've heard the screaming 'reduced' on any sort of rolling release, is when those teams have to deal with CVEs in libraries they depend on19:48
fraywell of course, cause NPMS are never compromised19:48
moto-timojust like basing your critical infrastructure on an ephemeral OS that just updated to some random commit hash for 1000 repos an hour ago is JustFIne.19:49
frayalso the amount of "pip has it, just download the binary!"19:50
moto-timo"Yes, you can install a binary wheel. Don't."19:50
moto-timola la la19:50
*** Kubu_work <Kubu_work!> has quit IRC (Quit: Leaving.)19:55
rburtonmoto-timo: aah clear linux such memories20:09
moto-timorburton: I knew you would "enjoy" that20:09
moto-timoit did some very interesting things. but not for embedded.20:10
rburtonstill surprised its (relatively) active20:14
moto-timostress-ng is still updated regularly for it20:24
moto-timo(about the only thing I get notificatons about)20:24
*** ptsneves <ptsneves!> has joined #yocto20:27
*** Saur23 <Saur23!~Saur78@> has joined #yocto20:31
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)20:32
*** paulg <paulg!> has quit IRC (Ping timeout: 240 seconds)20:32
*** Saur78 <Saur78!~Saur62@> has quit IRC (Ping timeout: 250 seconds)20:34
*** Chaser <Chaser!~Chaser@user/chaser> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)20:37
*** zenstoic <zenstoic!> has joined #yocto20:39
*** paulg <paulg!> has joined #yocto20:46
*** alperak <alperak!~alperak@> has quit IRC (Quit: Client closed)20:50
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)20:54
*** ptsneves <ptsneves!> has quit IRC (Ping timeout: 260 seconds)21:04
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 260 seconds)21:17
*** mvlad <mvlad!~mvlad@2a02:2f05:850d:7800:9306:d1a3:f874:d884> has quit IRC (Remote host closed the connection)21:28
*** Smokey <Smokey!> has joined #yocto21:32
SmokeyI am seeing this error from `bitbake secure-core-image` immediately after the build configuration is shown (before parsing):
SmokeyNot sure how to debug this...21:36
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has quit IRC (Remote host closed the connection)21:39
*** flom84 <flom84!~flom84@user/flom84> has joined #yocto21:41
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has joined #yocto21:43
Smokey... I mean *after* parsing21:47
*** tgamblin <tgamblin!> has quit IRC (Ping timeout: 268 seconds)21:50
yoctonSmokey: do you have "ext4" in IMAGE_FSTYPES? Sound like it is missing...21:50
Smokeyyocton: thanks, but it looks like I do have ext4:
*** tgamblin <tgamblin!> has joined #yocto22:00
*** schtobia <schtobia!> has quit IRC (Quit: Bye!)22:00
*** schtobia <schtobia!> has joined #yocto22:01
yocton"bitbake-getvar IMAGE_FSTYPES -r secure-core-image-initramfs"?22:01
RPJaMa: I'm more than happy for you to run crazy host distros, we're just not going to recommend or say we "support" them :)22:03
yoctonSmokey: its weird to look for the do_image_ext4 of a initramfs image... I'd say the dependency (bootimage->ext4) is wrong not the fact that do_image_ext4 does not exists...22:03
vmesonyocton: I was thinking the same thing but didn't say anything since I haven't played with initramfs images lately.22:08
SmokeyRP: yes... we are creating a distro and I got thrown into it. :)22:09
Smokeyyocton: how would you recommend that I investigate the dependency? The initramfs is coming from which I believe is an approved layer.22:11
RPyocton: I've merged those meta-oe exclusions but I'm wondering if we shouldn't write them to an inc file in the layer22:14
Ad0mckoan|away, I will try it, worth a shot22:16
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has left #yocto (ERC 5.4 (IRC client for GNU Emacs 28.2))22:19
yoctonRP: that's a good idea! Having AB config handle this list feel like a waste of time22:19
*** flom84 <flom84!~flom84@user/flom84> has quit IRC (Ping timeout: 260 seconds)22:21
RPyocton: agreed, I think we can do better22:23
*** vladest <vladest!> has joined #yocto22:26
mischieffor bitbake --setscene-only, can i print what was missing? we're trying to see why our sstate appears to be missing a bunch of stuff at the moment.22:31
yoctonSmokey: maybe bitbake -e ? (it does print where some task depends comes from). Also, "bitbake -g"  might be useful (it generates the task dependency graph). Try for both secure-core-image-initramfs and secure-core-image22:37
Smokeyyocton: thanks, will try those.22:41
yoctonSmokey: Oh I just noticed, you set IMAGE_FSTYPES from a machine inc file. Maybe that overrides ? You can do a "bitbake-getvar IMAGE_FSTYPES -r secure-core-image-initramfs" to check.22:52
Smokeyyocton: looks like your hunch was right: What's happening here?22:55
Smokeyyocton: hang on, that's my doing...22:55
yoctonSmokey: IMAGE_FSTYPES="cpio.gz" is what I'd expect for a initramfs image22:56
RPmischief: -DDD gives a lot of output but should say23:00
mischiefRP: is there a way to only check the sstate stats instead of actually running setscene?23:00
RPmischief: -n (dry run) maybe?23:02
mischiefthis is indeed a lot of output23:04
mischiefquite odd, we're missing sstate for things i think would not change much, like bzip2 package_write_ipk23:12
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 264 seconds)23:36
*** chep <chep!chep@gateway/vpn/airvpn/chep> has quit IRC (Quit: ZNC 1.8.2 -
*** chep <chep!chep@gateway/vpn/airvpn/chep> has joined #yocto23:37
moto-timokhem: do you remember any outcome of
moto-timokhem: seems like we are seeing it with the poky-altcfg experiment line 233 or so23:45
khemmoto-timo: no solutions thus far, my problems are hardly solved :)23:46
moto-timoYeah, you mostly fix my problems ;)23:46
khemI know it happens when two qemu runs are happening in parallel23:58
khema re-run passes23:58

Generated by 2.17.2 by Marius Gedminas - find it at!