| *** florian <florian!~florian@dynamic-093-135-017-034.93.135.pool.telefonica.de> has quit IRC (Ping timeout: 272 seconds) | 00:10 | |
| khem | RP: sent a fix for rust 1.75 on rv32 | 00:20 |
|---|---|---|
| RP | zeddii: 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 autobuilder | 00:24 |
| RP | khem: ok, will try and test in the next round of builds | 00:25 |
| RP | khem: I'm wondering about something like https://git.openembedded.org/meta-openembedded-contrib/commit/?h=rpurdie/imagemagick&id=8380515ebe0a94469db885f10b62917b6749cba6 | 00:25 |
| khem | hmm so idea is per recipe build-tools tarball ? | 00:30 |
| khem | RP: I am building the usual suspects in meta-oe with go 1.22 and see if there are any hidden daemons | 00:31 |
| *** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 255 seconds) | 01:25 | |
| *** justache <justache!~justache@user/justache> has joined #yocto | 01:27 | |
| *** zenstoic <zenstoic!uid461840@id-461840.hampstead.irccloud.com> 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 #yocto | 01:54 | |
| *** davidinux <davidinux!~davidinux@194.34.233.249> has quit IRC (Ping timeout: 264 seconds) | 02:04 | |
| *** davidinux <davidinux!~davidinux@194.34.233.249> has joined #yocto | 02:04 | |
| moto-timo | FWIW, 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.5 | 02:20 |
| moto-timo | debian-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 scripts | 02:21 |
| moto-timo | I 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 #yocto | 02:37 | |
| *** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has quit IRC (Read error: Connection reset by peer) | 02:43 | |
| *** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has joined #yocto | 02:45 | |
| *** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 264 seconds) | 02:50 | |
| *** justache <justache!~justache@user/justache> has joined #yocto | 02:55 | |
| *** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has quit IRC (Ping timeout: 272 seconds) | 03:12 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.10> has quit IRC (Quit: Client closed) | 03:30 | |
| moto-timo | paulg: is already rolling his eyes https://www-infoworld-com.cdn.ampproject.org/c/s/www.infoworld.com/article/3713203/white-house-urges-developers-to-dump-c-and-c.amp.html | 03:33 |
| *** 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 #yocto | 03:39 | |
| *** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 264 seconds) | 03:52 | |
| *** justache <justache!~justache@user/justache> has joined #yocto | 03:53 | |
| *** mulk <mulk!~mulk@p5b11264f.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 255 seconds) | 04:09 | |
| *** mulk <mulk!~mulk@p5b2dc813.dip0.t-ipconnect.de> has joined #yocto | 04:10 | |
| *** Perflosopher <Perflosopher!~perflosop@136.62.181.44> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 04:41 | |
| *** Saur2 <Saur2!~Saur26@195.60.68.152> has quit IRC (Quit: Client closed) | 04:51 | |
| *** Saur2 <Saur2!~Saur2@195.60.68.152> has joined #yocto | 04:52 | |
| *** amitk <amitk!~amit@58.84.61.106> has joined #yocto | 05:07 | |
| *** simone <simone!~ile@2a02:810d:a940:35fc:5831:bcce:40fa:28eb> has quit IRC (Ping timeout: 255 seconds) | 05:29 | |
| paulg | retirement looks more appealing every day.... | 05:38 |
| *** alperak <alperak!~alperak@176.33.65.159> has joined #yocto | 05:45 | |
| *** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has joined #yocto | 05:47 | |
| *** amitk <amitk!~amit@58.84.61.106> has quit IRC (Ping timeout: 272 seconds) | 05:58 | |
| *** amitk <amitk!~amit@58.84.62.194> has joined #yocto | 06:01 | |
| *** npcomp <npcomp!~user@user/npcomp> has joined #yocto | 06:05 | |
| *** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 264 seconds) | 06:10 | |
| *** justache <justache!~justache@user/justache> has joined #yocto | 06:11 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.238> has joined #yocto | 06:38 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 07:08 | |
| *** Chaser <Chaser!~Chaser@user/chaser> has joined #yocto | 07:08 | |
| *** Chaser <Chaser!~Chaser@user/chaser> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…) | 07:22 | |
| *** amitk <amitk!~amit@58.84.62.194> 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@58.84.60.74> has joined #yocto | 07:25 | |
| *** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Ping timeout: 260 seconds) | 07:29 | |
| *** mckoan|away is now known as mckoan | 07:29 | |
| mckoan | good morning | 07:33 |
| *** Kubu_work <Kubu_work!~kubu@arennes-654-1-262-155.w2-13.abo.wanadoo.fr> has joined #yocto | 07:34 | |
| *** mvlad <mvlad!~mvlad@2a02:2f05:850d:7800:9306:d1a3:f874:d884> has joined #yocto | 07:36 | |
| *** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto | 07:44 | |
| *** vladest <vladest!~Thunderbi@217.192.139.41> has joined #yocto | 07:55 | |
| *** vladest <vladest!~Thunderbi@217.192.139.41> has quit IRC (Remote host closed the connection) | 08:00 | |
| *** vladest <vladest!~Thunderbi@217.192.139.41> has joined #yocto | 08:04 | |
| LetoThe2nd | yo mckoan | 08:05 |
| *** vladest <vladest!~Thunderbi@217.192.139.41> has quit IRC (Remote host closed the connection) | 08:07 | |
| *** vladest <vladest!~Thunderbi@217.192.139.41> has joined #yocto | 08:10 | |
| *** rfuentess <rfuentess!~rfuentess@adijon-159-1-11-151.w92-161.abo.wanadoo.fr> has joined #yocto | 08:12 | |
| *** vladest <vladest!~Thunderbi@217.192.139.41> has quit IRC (Client Quit) | 08:12 | |
| *** vladest <vladest!~Thunderbi@217.192.139.41> has joined #yocto | 08:16 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF41.versanet.de> has joined #yocto | 08:21 | |
| *** ptsneves <ptsneves!~Thunderbi@031011128046.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto | 08:23 | |
| *** ptsneves1 <ptsneves1!~Thunderbi@031011128046.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto | 08:25 | |
| *** ptsneves <ptsneves!~Thunderbi@031011128046.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Read error: Connection reset by peer) | 08:25 | |
| *** ptsneves1 is now known as ptsneves | 08:25 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF41.versanet.de> has quit IRC (Ping timeout: 264 seconds) | 08:40 | |
| *** Chaser <Chaser!~Chaser@user/chaser> has joined #yocto | 08:40 | |
| *** mbulut <mbulut!~mbulut@ip1f128e51.dynamic.kabel-deutschland.de> has joined #yocto | 08:43 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF41.versanet.de> has joined #yocto | 08:54 | |
| mckoan | LetoThe2nd: hey | 09:11 |
| *** kanavin <kanavin!~Alexander@2a02:2454:299:c100:b25:37c3:ea9f:574c> has quit IRC (Remote host closed the connection) | 09:19 | |
| *** frieder <frieder!~frieder@i4df677e2.static.tripleplugandplay.com> has joined #yocto | 09:28 | |
| *** mbulut <mbulut!~mbulut@ip1f128e51.dynamic.kabel-deutschland.de> has quit IRC (Quit: Leaving) | 09:30 | |
| *** florian <florian!~florian@dynamic-002-244-082-084.2.244.pool.telefonica.de> has joined #yocto | 09:42 | |
| *** Saur22 <Saur22!~Saur2@195.60.68.152> has joined #yocto | 09:51 | |
| *** Saur2 <Saur2!~Saur2@195.60.68.152> has quit IRC (Ping timeout: 250 seconds) | 09:55 | |
| *** pidge <pidge!~pidge@194.110.145.164> has joined #yocto | 10:03 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 272 seconds) | 10:04 | |
| *** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has joined #yocto | 10:05 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto | 10:06 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF41.versanet.de> has quit IRC (Quit: Leaving.) | 10:10 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF41.versanet.de> has joined #yocto | 10:10 | |
| *** kanavin <kanavin!~Alexander@2a02:2454:299:c100:b25:37c3:ea9f:574c> has joined #yocto | 10:16 | |
| *** florian <florian!~florian@dynamic-002-244-082-084.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 272 seconds) | 10:22 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF41.versanet.de> has quit IRC (Ping timeout: 255 seconds) | 10:26 | |
| *** zpfvo <zpfvo!~fvo@89.245.207.65> has joined #yocto | 10:41 | |
| Piraty | https://docs.yoctoproject.org/dev-manual/vulnerabilities.html#fixing-cve-product-name-and-version-mappings so CVE_PRODUCT is part of the nvd/CPE ? | 10:41 |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 10:48 | |
| rburton | Piraty: its the vendor:product name of that project in the NVD | 11:28 |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 264 seconds) | 11:33 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto | 11:34 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 11:38 | |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto | 11:41 | |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe) | 12:04 | |
| Piraty | can you hint me the entry point to the https://docs.yoctoproject.org/ref-manual/classes.html#ref-classes-cve-check command ? | 12:10 |
| rfs613 | Piraty: not sure if this is what you are looking for, but usually you enable this check by adding INHERIT += "cve-check" to local.conf | 12:22 |
| rfs613 | that 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 |
| Piraty | i want to understand what it does, i.e. see the api call or whatever | 12:25 |
| Piraty | can't really it in poky | 12:26 |
| rfs613 | ah, 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 |
| rfs613 | and the second part does lookups for each package against that database | 12:27 |
| Piraty | i found meta/classes/cve-check.bbclass | 12:27 |
| rfs613 | https://git.yoctoproject.org/poky/tree/meta/classes/cve-check.bbclass | 12:27 |
| Piraty | beat you :p | 12:27 |
| rfs613 | by seconds ;-) | 12:28 |
| Piraty | pulling the whole DB from nvd and store it in sql3 seems common for many of those cve tools | 12:28 |
| rfs613 | yeah... you don't want to be querying on each build | 12:29 |
| rfs613 | and incrementally updating the db makese sense too, it's huge | 12:29 |
| Piraty | matching a package to cpe and filtering irrelevant cve entries from db query's response is the hard part | 12:29 |
| Piraty | huge: no . is nvd hell slow at providing the db? yes | 12:29 |
| rfs613 | that'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 part | 12:29 |
| rfs613 | especially 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 reports | 12:30 |
| Piraty | that bbclass file looks like the inbreed of Makefile + python3 i never wanted to see | 12:31 |
| Piraty | must be a pain to debug | 12:34 |
| rfs613 | hehe i haven't deatl with it in a while (like a few years) | 12:35 |
| rburton | there is a plan to rip it out into a standalone tool for easier development/testing/etc. | 12:36 |
| *** zpfvo <zpfvo!~fvo@89.245.207.65> has quit IRC (Ping timeout: 252 seconds) | 12:57 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF41.versanet.de> has joined #yocto | 13:20 | |
| *** luc4 <luc4!~luca@2a00:6d43:501:1201:1c91:4774:fadd:2ce4> has joined #yocto | 13:23 | |
| *** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Ping timeout: 272 seconds) | 13:41 | |
| *** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto | 13:50 | |
| *** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 264 seconds) | 13:56 | |
| *** justache <justache!~justache@user/justache> has joined #yocto | 14:03 | |
| *** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has joined #yocto | 14:05 | |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto | 14:23 | |
| *** sotaoverride is now known as Guest7005 | 14:39 | |
| *** Guest7005 <Guest7005!~aatir@ool-4578fe22.dyn.optonline.net> has quit IRC (Killed (molybdenum.libera.chat (Nickname regained by services))) | 14:39 | |
| *** ctraven is now known as sotaoverride | 14:39 | |
| *** sotaover1ide <sotaover1ide!~aatir@ool-4578fe22.dyn.optonline.net> has joined #yocto | 14:39 | |
| *** Dr_Who <Dr_Who!~tgall@192.210.17.164> has joined #yocto | 14:40 | |
| *** justache <justache!~justache@user/justache> has quit IRC (Ping timeout: 264 seconds) | 14:42 | |
| *** justache <justache!~justache@user/justache> has joined #yocto | 14:47 | |
| *** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Remote host closed the connection) | 14:52 | |
| *** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe) | 15:00 | |
| *** rsalveti <rsalveti!uid117878@id-117878.uxbridge.irccloud.com> has joined #yocto | 15:17 | |
| *** Dr_Who <Dr_Who!~tgall@192.210.17.164> has quit IRC (Quit: ZZZzzz…) | 15:47 | |
| qschulz | does 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@217.192.139.41> has quit IRC (Ping timeout: 264 seconds) | 16:01 | |
| yocton | qschulz: partialy (not kas and it's still a WIP) | 16:05 |
| qschulz | yocton: if not kas, are you using the "new" layer tool in Yocto or something handcrafted? | 16:08 |
| *** frieder <frieder!~frieder@i4df677e2.static.tripleplugandplay.com> has quit IRC (Remote host closed the connection) | 16:09 | |
| yocton | qschulz: we use yocto-cooker (not related to the Yocto project) https://github.com/cpb-/yocto-cooker | 16:09 |
| *** Saur62 <Saur62!~Saur22@195.60.68.152> has joined #yocto | 16:10 | |
| yocton | ... but we will hapilly migrate to the new tool | 16:10 |
| *** luc4 <luc4!~luca@2a00:6d43:501:1201:1c91:4774:fadd:2ce4> has quit IRC (Ping timeout: 256 seconds) | 16:11 | |
| *** Saur22 <Saur22!~Saur2@195.60.68.152> has quit IRC (Ping timeout: 250 seconds) | 16:13 | |
| *** Dr_Who <Dr_Who!~tgall@192.210.17.164> has joined #yocto | 16:14 | |
| *** starblue <starblue!~juergen@dslb-088-078-106-216.088.078.pools.vodafone-ip.de> has joined #yocto | 16:43 | |
| *** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has joined #yocto | 16:48 | |
| *** rfuentess <rfuentess!~rfuentess@adijon-159-1-11-151.w92-161.abo.wanadoo.fr> has quit IRC (Remote host closed the connection) | 16:53 | |
| *** mckoan is now known as mckoan|away | 17:04 | |
| mckoan|away | Ad0: https://wiki.koansoftware.com/index.php/Support_other_languages_and_keyboards_than_English_in_Yocto | 17:05 |
| moto-timo | qschulz: pidge and tgamblin and I were talking about such an architecture, but we haven't really gotten it going yet. | 17:06 |
| moto-timo | qschulz: 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 tool | 17:07 | |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat) | 17:09 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 264 seconds) | 17:12 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF41.versanet.de> has quit IRC (Remote host closed the connection) | 17:12 | |
| *** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto | 17:15 | |
| qschulz | moto-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-timo | qschulz: agreed | 17:19 |
| qschulz | moto-timo: that'll take some time though, need to do some research on gitlab-ci multi-repo pipelines :) | 17:25 |
| moto-timo | qschulz: I get it. This is part of why we didn't get anything "baked" yet. | 17:26 |
| qschulz | moto-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!~Smokey@45-31-46-52.lightspeed.sndgca.sbcglobal.net> has joined #yocto | 17:34 | |
| *** Dr_Who <Dr_Who!~tgall@192.210.17.164> has quit IRC (Quit: ZZZzzz…) | 17:35 | |
| *** Dr_Who <Dr_Who!~tgall@192.210.17.164> has joined #yocto | 17:38 | |
| *** kpo <kpo!~kpo@87-206-161-246.dynamic.chello.pl> has joined #yocto | 17:41 | |
| *** Dr_Who <Dr_Who!~tgall@192.210.17.164> has quit IRC (Ping timeout: 255 seconds) | 17:42 | |
| *** ptsneves <ptsneves!~Thunderbi@031011128046.dynamic-3-poz-k-0-2-0.vectranet.pl> 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 #yocto | 18:00 | |
| *** Saur78 <Saur78!~Saur62@195.60.68.152> has joined #yocto | 18:05 | |
| *** Saur62 <Saur62!~Saur22@195.60.68.152> has quit IRC (Ping timeout: 250 seconds) | 18:08 | |
| *** Smokey <Smokey!~Smokey@45-31-46-52.lightspeed.sndgca.sbcglobal.net> has quit IRC (Quit: Client closed) | 18:35 | |
| moto-timo | qschulz: 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-timo | qschulz: kas is great, but I am also trying to entertain the submodules folks. | 18:52 |
| khem | qschulz: if you like github actions then look at yoe distro ci and meta-clang ci | 19:02 |
| *** alperak <alperak!~alperak@176.33.65.159> has quit IRC (Quit: Client closed) | 19:05 | |
| *** alperak <alperak!~alperak@176.33.65.159> has joined #yocto | 19:07 | |
| moto-timo | khem: as you know, yoe-distro is my poster child for both GitHub Actions and submodules. | 19:10 |
| jdiez | hi, 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!~Haxxa@202-65-68-206.ip4.superloop.au> has quit IRC (Quit: Haxxa flies away.) | 19:15 | |
| jdiez | hm, i tried sourcing the temp/run.do_compile.XXX script but that actually called do_compile and `exit`ed my shell | 19:17 |
| khem | moto-timo: kool.. ( KDE plasma 6.0 released this week so 'c' is now 'k' for sometime ) | 19:17 |
| moto-timo | khem: and it's all about Qt6 so there's that | 19:18 |
| *** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has joined #yocto | 19:18 | |
| khem | but I am impressed with plasma6, this is the best release ever | 19:18 |
| moto-timo | khem: 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 |
| khem | yeah use meta-kde | 19:19 |
| moto-timo | 👍 | 19:19 |
| khem | my daily drivers are arch and nixos but thats just convenience | 19:19 |
| moto-timo | I guess I'm still on GNOME by default on Ubuntu and Debian. | 19:19 |
| khem | ugh caveman :) | 19:19 |
| moto-timo | I 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-timo | I will freely admit that I do hold on to some old ways. | 19:20 |
| khem | I installed arch once in 2016 and since then I have been just doing pacman -Syu | 19:20 |
| moto-timo | yeah. but can you explain in a few sentences what you did in 2016? lol | 19:21 |
| khem | I want to keep this machine going till 2026 so I can say I managed a machine with rolling release for 10 years | 19:21 |
| moto-timo | I'm sure it got better. I looked at it in 2017-2018 I think. | 19:21 |
| khem | yes arch has a very good handbook follow step by step. you will never mess it up | 19:22 |
| moto-timo | I kind of wish we could claim arch was a support distro for YP. oh well. | 19:22 |
| khem | https://wiki.archlinux.org/title/installation_guide | 19:22 |
| moto-timo | Ok. The next workstation I will start with that. | 19:23 |
| *** florian_kc <florian_kc!~florian@dynamic-002-244-082-084.2.244.pool.telefonica.de> has joined #yocto | 19:23 | |
| khem | you can also use some derivatives like EndevourOS, Garuda | 19:23 |
| moto-timo | I am tired of grumbling about ubuntu (snaps are horrible) and debian (too sluggish) | 19:23 |
| moto-timo | sluggish meaning they do not upgrade packages often enough | 19:23 |
| khem | they have graphical installers, I personally find Garuda quite impressive but never used it for long | 19:23 |
| moto-timo | Fedora 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 |
| khem | Nixos is whole new game | 19:24 |
| moto-timo | I gave up on Fedora being a daily driver around fedora-28. When the Modularity stuff was churning HARD. | 19:24 |
| khem | especially with flakes AI tools become to easy to use | 19:25 |
| moto-timo | Oh, I have watched some NixOS live streams. It makes a lot of sense for infrastructure roll-out. | 19:25 |
| moto-timo | But I was watching the Mastodon livestream when Kris Nova gave up on NixOS because it eventually introduced new problems. | 19:25 |
| moto-timo | and I don't do enough virtualization for my daily drivers to make proxmox make sense. | 19:26 |
| moto-timo | I've also now got enough Terraform/OpenTofu under my belt that cloud infra is rolled out with that. | 19:27 |
| JaMa | jdiez: 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 |
| jdiez | JaMa: yeah, the latter is what I did, and seemed to work for my purpose | 19:29 |
| jdiez | how do you do it with devtool? | 19:29 |
| *** simonew <simonew!~ile@2a02:810d:a940:35fc:f47d:1bff:e43a:e97a> has joined #yocto | 19:33 | |
| halstead | moto-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 |
| JaMa | khem: I'm close to 20 years of rolling gentoo install :) | 19:34 |
| halstead | I 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-timo | halstead: 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-timo | it'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!~sev99@pool-108-32-48-117.pitbpa.fios.verizon.net> has joined #yocto | 19:35 | |
| moto-timo | I also figure folks that are running Arch also don't give a crap about that warning. :) | 19:36 |
| JaMa | the 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 OS | 19:36 |
| moto-timo | JaMa: very VERY good point. | 19:37 |
| moto-timo | sort of like "I_PROMISE_TO_STOP_USING_PYTHON_2" | 19:37 |
| JaMa | having it in e.g. poky's SANITY_TESTED_DISTROS would be very misleading on the other hand | 19:37 |
| moto-timo | "I_KNOW_WHAT_I_AM_DOING_ARCH_WORKS_FOR_ME" | 19:37 |
| moto-timo | yeah. my usual half baked idea | 19:38 |
| moto-timo | I 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!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Remote host closed the connection) | 19:40 | |
| moto-timo | Also, for the record, a rolling Yocto Project release in the field was HIGHLY unpopular amongst customers. | 19:40 |
| JaMa | gentoo "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-timo | Also, 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 |
| JaMa | I 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-timo | This is the point. | 19:42 |
| moto-timo | Thanks for stating it so nicely. | 19:43 |
| moto-timo | and 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 |
| JaMa | no problem, just release it perfect on 1st try :) | 19:44 |
| moto-timo | Release: 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-timo | It will be perfect forever. | 19:45 |
| moto-timo | I think I'll start a new OS project called "Amber". | 19:45 |
| moto-timo | All commits and pull requests will be automatically rejected. | 19:45 |
| moto-timo | It will use the Linux 2.26 kernel of course. | 19:46 |
| fray | rolling 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-timo | and yet they want the newest NodeJS and the latest npms | 19:48 |
| fray | the 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 on | 19:48 |
| moto-timo | this | 19:48 |
| moto-timo | lol | 19:48 |
| fray | well of course, cause NPMS are never compromised | 19:48 |
| moto-timo | just 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 |
| moto-timo | CloudChaos. | 19:49 |
| moto-timo | CloudChaOS. | 19:49 |
| JaMa | :) | 19:50 |
| fray | also the amount of "pip has it, just download the binary!" | 19:50 |
| moto-timo | cough | 19:50 |
| moto-timo | "Yes, you can install a binary wheel. Don't." | 19:50 |
| moto-timo | la la la | 19:50 |
| *** Kubu_work <Kubu_work!~kubu@arennes-654-1-262-155.w2-13.abo.wanadoo.fr> has quit IRC (Quit: Leaving.) | 19:55 | |
| rburton | moto-timo: aah clear linux such memories | 20:09 |
| moto-timo | rburton: I knew you would "enjoy" that | 20:09 |
| moto-timo | it did some very interesting things. but not for embedded. | 20:10 |
| rburton | absolutely | 20:14 |
| rburton | still surprised its (relatively) active | 20:14 |
| moto-timo | same | 20:24 |
| moto-timo | stress-ng is still updated regularly for it | 20:24 |
| moto-timo | (about the only thing I get notificatons about) | 20:24 |
| *** ptsneves <ptsneves!~Thunderbi@031011128046.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto | 20:27 | |
| *** Saur23 <Saur23!~Saur78@195.60.68.152> has joined #yocto | 20:31 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 20:32 | |
| *** paulg <paulg!~paulg@198-84-237-91.cpe.teksavvy.com> has quit IRC (Ping timeout: 240 seconds) | 20:32 | |
| *** Saur78 <Saur78!~Saur62@195.60.68.152> 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!uid461840@id-461840.hampstead.irccloud.com> has joined #yocto | 20:39 | |
| *** paulg <paulg!~paulg@198-84-237-91.cpe.teksavvy.com> has joined #yocto | 20:46 | |
| *** alperak <alperak!~alperak@176.33.65.159> has quit IRC (Quit: Client closed) | 20:50 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.238> has quit IRC (Quit: alessioigor) | 20:54 | |
| *** ptsneves <ptsneves!~Thunderbi@031011128046.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Ping timeout: 260 seconds) | 21:04 | |
| *** amitk <amitk!~amit@58.84.60.74> 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!~Smokey@45-31-46-52.lightspeed.sndgca.sbcglobal.net> has joined #yocto | 21:32 | |
| Smokey | I am seeing this error from `bitbake secure-core-image` immediately after the build configuration is shown (before parsing): https://pastebin.com/w2AQ0V4Q | 21:36 |
| Smokey | Not 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 #yocto | 21:41 | |
| *** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has joined #yocto | 21:43 | |
| Smokey | ... I mean *after* parsing | 21:47 |
| *** tgamblin <tgamblin!~tgamblin@d24-150-219-207.home.cgocable.net> has quit IRC (Ping timeout: 268 seconds) | 21:50 | |
| yocton | Smokey: do you have "ext4" in IMAGE_FSTYPES? Sound like it is missing... | 21:50 |
| Smokey | yocton: thanks, but it looks like I do have ext4: https://pastebin.com/i8QV8q62 | 21:53 |
| *** tgamblin <tgamblin!~tgamblin@d24-150-219-207.home.cgocable.net> has joined #yocto | 22:00 | |
| *** schtobia <schtobia!~quassel@schmidl.dev> has quit IRC (Quit: Bye!) | 22:00 | |
| *** schtobia <schtobia!~quassel@schmidl.dev> has joined #yocto | 22:01 | |
| yocton | "bitbake-getvar IMAGE_FSTYPES -r secure-core-image-initramfs"? | 22:01 |
| RP | JaMa: 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 |
| yocton | Smokey: 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 |
| vmeson | yocton: I was thinking the same thing but didn't say anything since I haven't played with initramfs images lately. | 22:08 |
| Smokey | RP: yes... we are creating a distro and I got thrown into it. :) | 22:09 |
| Smokey | yocton: how would you recommend that I investigate the dependency? The initramfs is coming from https://github.com/Wind-River/meta-secure-core/tree/kirkstone which I believe is an approved layer. | 22:11 |
| RP | yocton: I've merged those meta-oe exclusions but I'm wondering if we shouldn't write them to an inc file in the layer | 22:14 |
| Ad0 | mckoan|away, I will try it, worth a shot | 22:16 |
| Ad0 | thanks! | 22: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 | |
| yocton | RP: that's a good idea! Having AB config handle this list feel like a waste of time | 22:19 |
| *** flom84 <flom84!~flom84@user/flom84> has quit IRC (Ping timeout: 260 seconds) | 22:21 | |
| RP | yocton: agreed, I think we can do better | 22:23 |
| *** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto | 22:26 | |
| mischief | for 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 |
| yocton | Smokey: 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-image | 22:37 |
| Smokey | yocton: thanks, will try those. | 22:41 |
| yocton | Smokey: Oh I just noticed, you set IMAGE_FSTYPES from a machine inc file. Maybe that overrides https://github.com/Wind-River/meta-secure-core/blob/sumo/meta/recipes-core/images/secure-core-image-initramfs.bb#L28C1-L28C39 ? You can do a "bitbake-getvar IMAGE_FSTYPES -r secure-core-image-initramfs" to check. | 22:52 |
| Smokey | yocton: looks like your hunch was right: https://pastebin.com/g2yzu0zb. What's happening here? | 22:55 |
| Smokey | yocton: hang on, that's my doing... | 22:55 |
| yocton | Smokey: IMAGE_FSTYPES="cpio.gz" is what I'd expect for a initramfs image | 22:56 |
| RP | mischief: -DDD gives a lot of output but should say | 23:00 |
| mischief | RP: is there a way to only check the sstate stats instead of actually running setscene? | 23:00 |
| RP | mischief: -n (dry run) maybe? | 23:02 |
| mischief | this is indeed a lot of output | 23:04 |
| mischief | quite odd, we're missing sstate for things i think would not change much, like bzip2 package_write_ipk | 23:12 |
| *** florian_kc <florian_kc!~florian@dynamic-002-244-082-084.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 264 seconds) | 23:36 | |
| *** chep <chep!chep@gateway/vpn/airvpn/chep> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in) | 23:37 | |
| *** chep <chep!chep@gateway/vpn/airvpn/chep> has joined #yocto | 23:37 | |
| moto-timo | khem: do you remember any outcome of https://lore.kernel.org/all/CAMKF1spKdnjMFpD=Qf_1vCzOeAN-Xg5GqQJviNLPXRq6md-tbQ@mail.gmail.com/T/ | 23:44 |
| moto-timo | khem: seems like we are seeing it with the poky-altcfg experiment https://autobuilder.yoctoproject.org/typhoon/#/builders/101/builds/7392/steps/14/logs/stdio line 233 or so | 23:45 |
| khem | moto-timo: no solutions thus far, my problems are hardly solved :) | 23:46 |
| moto-timo | Yeah, you mostly fix my problems ;) | 23:46 |
| moto-timo | lol | 23:46 |
| khem | I know it happens when two qemu runs are happening in parallel | 23:58 |
| khem | a re-run passes | 23:58 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!