Wednesday, 2022-09-21

jaskij[m]RP: not sure if I should ping you or khem @khem:matrix.org: , but (in a Reddit thread) I've been asked for input and use case why I'm on Rust 1.59. I'll do my best to reply, but perhaps one of you two could also reply? GH issue: https://github.com/rust-lang/libs-team/issues/7200:03
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto00:14
*** rhowell <rhowell!~rhowell@2605:a601:a937:b200:f415:61fb:9343:78f9> has quit IRC (Quit: Client closed)00:16
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Client Quit)00:18
jaskij[m]Gnome depends on it's Rust SVG implementation, right?00:19
*** vmeson <vmeson!~rmacleod@23-233-86-175.cpe.pppoe.ca> has joined #yocto00:23
*** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has quit IRC (Read error: Connection reset by peer)00:32
*** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has joined #yocto00:35
*** seninha <seninha!~seninha@user/seninha> has joined #yocto00:36
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)00:38
*** Habbie <Habbie!peter@lorentz.7bits.nl> has quit IRC (Ping timeout: 244 seconds)00:42
*** Habbie <Habbie!peter@lorentz.7bits.nl> has joined #yocto00:42
*** vmeson <vmeson!~rmacleod@23-233-86-175.cpe.pppoe.ca> has quit IRC (Ping timeout: 264 seconds)01:01
*** davidinux <davidinux!~davidinux@host-87-14-156-1.retail.telecomitalia.it> has quit IRC (Ping timeout: 265 seconds)01:04
*** davidinux <davidinux!~davidinux@host-79-31-160-214.retail.telecomitalia.it> has joined #yocto01:07
*** rber|res <rber|res!~rber|res@88-117-85-248.adsl.highway.telekom.at> has joined #yocto01:32
*** RobertBerger <RobertBerger!~rber|res@88-117-85-248.adsl.highway.telekom.at> has quit IRC (Ping timeout: 265 seconds)01:35
*** behanw <behanw!uid110099@id-110099.uxbridge.irccloud.com> has joined #yocto01:44
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)01:53
*** seninha <seninha!~seninha@user/seninha> has joined #yocto02:10
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Client Quit)02:13
*** seninha <seninha!~seninha@user/seninha> has joined #yocto02:20
*** Tokamak_ <Tokamak_!~Tokamak@172.58.188.58> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)02:27
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto02:32
*** chep <chep!~chep@82-65-36-115.subs.proxad.net> has quit IRC (Read error: Connection reset by peer)02:52
*** chep <chep!~chep@82-65-36-115.subs.proxad.net> has joined #yocto02:52
*** chep` <chep`!~chep@82-65-36-115.subs.proxad.net> has joined #yocto02:59
*** chep <chep!~chep@82-65-36-115.subs.proxad.net> has quit IRC (Read error: Connection reset by peer)02:59
*** chep` is now known as chep02:59
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)03:00
PhoenixMagewhat is the location of the initramfs on the host disk after bitbaking an image?03:01
*** seninha <seninha!~seninha@user/seninha> has joined #yocto03:15
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)03:52
*** seninha <seninha!~seninha@user/seninha> has joined #yocto03:57
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 244 seconds)03:58
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto03:59
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Client Quit)03:59
*** barometz <barometz!~dvanb@31-151-148-212.dynamic.upc.nl> has quit IRC (Remote host closed the connection)04:02
*** barometz <barometz!~dvanb@31-151-148-212.dynamic.upc.nl> has joined #yocto04:03
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 265 seconds)04:03
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto04:04
*** seninha <seninha!~seninha@user/seninha> has joined #yocto04:08
*** amitk <amitk!~amit@103.59.74.87> has joined #yocto04:17
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)04:37
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)04:48
*** thomasd13 <thomasd13!~thomasd13@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto04:52
*** esai[m] <esai[m]!~charlesme@2001:470:69fc:105::2:83b9> has left #yocto04:54
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto05:02
*** beneth <beneth!5cb2199230@xmpp.beneth.fr> has quit IRC (Read error: Connection reset by peer)05:14
thomasd13I have a question regrading providing an (e)SDK for the application developer: Assume the app-developer wants to build an app, which requires the linux-kernel-headers and also some custom library A. So the linux-kernel-headers are included in (e)SDK. But can I also package the custom library A also in (s)SDK?05:34
thomasd13Or is the "normal" workflow like this: app-dev will install e(SDK) on his machine to have the correct toolchains/common linux libs/kernel, and will install himself all other required 3th party libs?05:36
*** behanw <behanw!uid110099@id-110099.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)05:44
*** thomasd13 <thomasd13!~thomasd13@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC (Ping timeout: 265 seconds)05:49
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto05:59
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 265 seconds)06:39
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto06:39
*** thomasd13 <thomasd13!~thomasd13@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto06:39
*** ptsneves <ptsneves!~Thunderbi@031011128148.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto06:41
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 252 seconds)06:43
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto06:44
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto06:47
*** smudge-the-cat <smudge-the-cat!smudge-the@2600:3c01::f03c:93ff:fe0c:9b23> has joined #yocto06:48
*** smudge-the-cat <smudge-the-cat!smudge-the@2600:3c01::f03c:93ff:fe0c:9b23> has left #yocto06:48
RPjaskij[m]: Worryingly, kirkstone is only 6 months old and we're hitting this :(06:49
*** astlep5504 <astlep5504!~thelounge@107-136-136-210.lightspeed.nsvltn.sbcglobal.net> has joined #yocto06:49
*** astlep550 <astlep550!~thelounge@107-136-136-210.lightspeed.nsvltn.sbcglobal.net> has quit IRC (Ping timeout: 252 seconds)06:50
RPthomasd13: if you have a recipe for it, yes and you can either ship the binaries in sstate and lock it down, or have it build it on demand06:50
*** mckoan|away is now known as mckoan07:00
mckoangood morning07:00
thomasd13RP, I have no recipe for "custom library A" yet. If I would have, how can I ship that?07:04
*** tre <tre!~tre@ip5f5886dd.dynamic.kabel-deutschland.de> has joined #yocto07:10
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto07:11
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has joined #yocto07:23
thomasd13Do you mean to do it "manually", so search for the built binary in sstate and provide it by hand?07:23
LetoThe2ndyo dudX07:27
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has quit IRC (Quit: Leaving.)07:30
*** zpfvo <zpfvo!~fvo@i59f5ce57.versanet.de> has joined #yocto07:30
thomasd13Another question: package-X requires CMake 3.24 to build. All other packages should use the "normal" CMake version. What is the best way to handle this?07:42
*** pbergin <pbergin!~pbergin@83.218.73.98> has joined #yocto07:42
LetoThe2ndthomasd13: no good solution, bitbake is not meant to handle multiple versions of a package in a single build.07:44
thomasd13LetoThe2nd, I was thinking to explicit create a package with the name cmake-3-24, to have the "normal" version via "cmake" and new version via "cmake-3-24" by hand. Is that somehow possible?07:45
LetoThe2ndthomasd13: maybe rather "cmake-my-patched-version", and yes, that is one way to get around it.07:46
RPthomasd13: you could write a recipe which packages up the binaries if you're sure they're compatible, you will need a recipe either source or binary based07:46
RPthomasd13: what you describe with a version in PN can work but it can sometimes be a bit tricky to have work correctly07:47
LetoThe2ndRP: if it wasn't tricky, then it would be a good way (TM)07:48
thomasd13Thank you both guys! Assume i have a cmake-my-patched-version package. How can I tell yocto, that this cmake should be used for package-A ?07:50
RPLetoThe2nd: recipe specific sysroots made it possible, you just have to ensure there isn't another dependency on the other version somewhere back down the dependency chain07:50
LetoThe2ndRP: possible != simple :-)07:51
RPthomasd13: DEPENDS += "somerecipe-myversion" assuming you changed PN to that07:51
LetoThe2ndthomasd13: first stab would be inheriting cmake and then modifying the result.07:51
thomasd13perfect, thanks guys!07:52
RPLetoThe2nd: I just mention it is possible and can work, not that it is a good idea07:52
LetoThe2ndRP: hi507:52
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-158.mrsn.at> has joined #yocto07:55
qschulzRP: got NVD to say they limited the CVE to jpeg-turbo 2.0.5 :) \o/07:59
* qschulz hi5 RP07:59
*** LetoThe2nd <LetoThe2nd!~Josef_Hol@static.124.2.243.136.clients.your-server.de> has quit IRC (Quit: WeeChat 3.5)07:59
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-158.mrsn.at> has quit IRC (Ping timeout: 265 seconds)08:01
*** zpfvo <zpfvo!~fvo@i59f5ce57.versanet.de> has quit IRC (Ping timeout: 252 seconds)08:02
*** mihai <mihai!~mihai@user/mihai> has quit IRC (Quit: Leaving)08:02
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto08:04
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has joined #yocto08:05
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-158.mrsn.at> has joined #yocto08:05
*** smudge-the-cat <smudge-the-cat!smudge-the@2600:3c01::f03c:93ff:fe0c:9b23> has joined #yocto08:11
*** smudge-the-cat <smudge-the-cat!smudge-the@2600:3c01::f03c:93ff:fe0c:9b23> has left #yocto08:11
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-158.mrsn.at> has quit IRC (Read error: Connection reset by peer)08:12
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-158.mrsn.at> has joined #yocto08:12
RPqschulz: they tried to tell me something different but I convinced them otherwise08:13
qschulzRP: ah, well.. good job I guess then :D08:13
qschulzRP: got a very unclear message from Mitre for adding a link with the patch fixing a CVE for U-Boot, but tha'ts another story08:14
*** manuel__ <manuel__!~manuel198@185.144.162.58> has joined #yocto08:15
RPqschulz: if it doesn't look right tell them and they generally get there in the end08:15
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has quit IRC (Ping timeout: 264 seconds)08:16
RPqschulz: I forwarded you the discussion I had with them08:16
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has joined #yocto08:16
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-158.mrsn.at> has quit IRC (Ping timeout: 244 seconds)08:17
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has quit IRC (Ping timeout: 250 seconds)08:21
*** davidinux <davidinux!~davidinux@host-79-31-160-214.retail.telecomitalia.it> has quit IRC (Ping timeout: 265 seconds)08:22
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has joined #yocto08:22
RPLooks like we're down to two CVEs for master without a plan08:24
RPCVE-2022-39046: glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3904608:25
RPCVE-2022-38128: binutils-cross-x86_64:binutils:binutils-cross-testsuite https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3812808:25
*** mvlad <mvlad!~mvlad@2a02:2f08:4904:c800:24d7:51ff:fed6:906d> has joined #yocto08:25
*** LetoThe2nd <LetoThe2nd!~Josef_Hol@2a01:4f8:211:1bdd::2> has joined #yocto08:27
qschulzRP: when did you forward the mail? haven't received anything on personal or pro mail I think08:28
RPqschulz: 10pm yesterday08:28
qschulztoo many mails on personal inbox, should configure the mailing lists better to only receive what i want :)08:29
qschulzI see it now, thx08:29
*** davidinux <davidinux!~davidinux@92.118.62.163> has joined #yocto08:30
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 265 seconds)08:34
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto08:36
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto08:38
*** lexano <lexano!~lexano@174.119.69.134> has quit IRC (Ping timeout: 265 seconds)08:39
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)08:49
*** beneth <beneth!5cb2199230@xmpp.beneth.fr> has joined #yocto08:50
*** d-s-e <d-s-e!~d-s-e@i5C7587B7.versanet.de> has joined #yocto08:52
*** lexano <lexano!~lexano@174.119.69.134> has joined #yocto08:52
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto08:54
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has quit IRC (Ping timeout: 268 seconds)09:08
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto09:09
*** Tyaku <Tyaku!~Tyaku@lfbn-orl-1-342-50.w90-35.abo.wanadoo.fr> has joined #yocto09:10
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has joined #yocto09:10
*** abelloni_ is now known as abelloni09:11
TyakuHi, yesterday I speak about a problem that has been resolved, but during this we speak about bitbake-getvars. And today I need to access a bitbake variable from commandline. this is the "MACHINE" variable. Problem: I never found bitbake-getvars and google didn't help me.09:15
TyakuIs there any way to get the content of a bitbake variable from command line ?09:15
qschulzTyaku: bitbake-getvar is pretty new09:17
qschulzI think it was backported recently to dunfell09:17
qschulzin any case, you can use bitbake -e recipe | awk '/^# \$FOOBAR \[/,/^FOOBAR/' instead09:18
LetoThe2ndRP: am i guessing right that the sstate logic is in https://git.openembedded.org/bitbake/tree/lib/bb/cache.py ?09:18
LetoThe2ndor is that the metadata cache?09:19
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has joined #yocto09:23
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Quit: ZZZzzz…)09:24
Tyakuqschulz: Is this the unique way ? Which recipe I have to put to make it working ? Any one ? (MACHINE is supposed to be defined in local.conf and possibly somewhere with ??=)09:27
qschulzTyaku: any will do since MACHINE is set in a conf file and won't change09:29
RPLetoThe2nd: that is parsing cache. sstate is pretty much in oe-core09:29
RPLetoThe2nd: meta/lib/oe/sstatesig.py and sstate.bbclass09:29
RPLetoThe2nd: bitbake side they hook into siggen.py and runqueue has the execution logic09:30
RPLetoThe2nd: how worried should I be? :)09:31
LetoThe2ndRP: not at all, guess just one of my devs going astray. and I'm not going to stop anybody who wants to learn more about the internals :-)09:31
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Ping timeout: 252 seconds)09:31
RPLetoThe2nd: was just curious on the context, I wouldn't stop anyone like that either :)09:32
LetoThe2ndRP: the trigger is the usual "why are we rebuilding so much", but I'm pretty certain that digging in that code is not the solution. yet it should be educational, hence i support it.09:33
RPLetoThe2nd: comparing sstate sigs is usually the answer to that09:33
RPLetoThe2nd: bitbake-diffisgs09:33
LetoThe2ndyep i know, but he seems to be missing something. my reproducer is not ready yet.09:34
PhoenixMagehmmm, had to increase the size of my initramfs and now when I attempt to boot I get "kworker/u8:0 invoked oom-killer" the VM I am using has 32Gb RAM allocated and 29 Gb free... I cant seem to find a switch to increase the qemu vm mem size on run? Any hints?09:34
LetoThe2ndah we've got a split in -global and -recipe classes? didn't notice, can anybody give me an executive summary? ;-)09:35
RPLetoThe2nd: very recent and not documented yet09:35
LetoThe2ndperfect summary!09:36
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto09:36
qschulzLetoThe2nd: split for classes that should be INHERIT vs classes that should be inherit :)09:36
qschulz(INHERIT for all recipes to inherit the class, inherit for per recipe)09:36
RPLetoThe2nd: basically it enforces anything that are in the recipes/global directories09:36
qschulz(and meta/classes for classes that can be inherited both ways IIRC)09:37
LetoThe2ndk09:37
RPideally we'll make things one or the other09:37
*** manuel__ <manuel__!~manuel198@185.144.162.58> has quit IRC (Ping timeout: 244 seconds)09:38
*** Tyaku <Tyaku!~Tyaku@lfbn-orl-1-342-50.w90-35.abo.wanadoo.fr> has quit IRC (Quit: Lost terminal)09:42
*** wkawka <wkawka!~wkawka@84-10-27-202.static.chello.pl> has joined #yocto09:57
*** ptsneves <ptsneves!~Thunderbi@031011128148.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Quit: ptsneves)10:01
*** manuel1985 <manuel1985!~manuel198@185.144.162.58> has joined #yocto10:06
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has quit IRC (Ping timeout: 252 seconds)10:17
*** odra_ is now known as odra10:19
*** mckoan is now known as mckoan|away10:19
*** EilsNFhlannagin[ <EilsNFhlannagin[!~yoctopidg@2001:470:69fc:105::2:8672> has joined #yocto10:23
*** EilsNFhlannagin[ is now known as pidge[m]10:28
*** zpfvo <zpfvo!~fvo@i59f5ce57.versanet.de> has joined #yocto10:32
*** seninha <seninha!~seninha@user/seninha> has joined #yocto10:35
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)11:14
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto11:17
*** Guest9 <Guest9!~Guest9@softbank-robotics-gw1.ter4.eqx2.par.cust.as8218.eu> has joined #yocto11:21
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)11:23
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto11:24
jaskij[m]RP: oh? I haven't hit it yet, and feel like I don't know enough to properly explain it in that issue. Or should I move this discussion to the mailing list?11:25
RPjaskij[m]: well, we're seeing rust move forward and "obsolete" versions but that isn't really a surprise. We can mention what we're doing on that issue but we'll just be told not to do that :/11:29
jaskij[m]For... Reasons, despite a few years of working experience with Yocto I have not yet had any system put in production.11:29
RPjaskij[m]: I don't know what we should do as the stable branches aren't meant to have large version changes11:30
jaskij[m]I skimmed that discussion and people there seem more open minded than usual.11:30
jaskij[m]And yeah, I get you, 1.59 has an ICE error I seem to hit fairly often and the fix wasn't backported11:30
*** odra is now known as odra_11:32
*** odra_ is now known as odra11:32
jaskij[m]RP: The maintainer of RHEL and Fedora Rust packages also participated and the replies were relatively open-minded. Worst case Yocto will get similar treatment to whatever they end up on deciding for Debian.11:32
jaskij[m]But if you feel it useless, I'll just chip in with my own experience and leave it at that.11:34
RPjaskij[m]: I've commented with our position, factually11:37
RPjaskij[m]: I can't really do more. I'm not a rust person really :/11:37
jaskij[m]And I'm someone who merely writes some small services in Rust, don't really participate11:38
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Ping timeout: 252 seconds)11:38
jaskij[m]Is Khem still working on Rust in OE? Iirc he did quite a lot of the initial support.11:39
RPjaskij[m]: sometimes. vmeson too11:39
jaskij[m]Feel like I'll need to add some more context - I'm willing to bet that none of the Rust folks in the issue even heard of Yocto11:42
jaskij[m]RP: I'll ping Khem via GitHub then11:42
jaskij[m]But thanks for participating, hopefully they will take OE into account11:42
*** ptsneves <ptsneves!~Thunderbi@031011128148.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto12:12
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)12:19
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto12:19
rfuentessI'm trying to understand BBCLASSEXTEND. If by example, I want to add an extra feature (e.g. the dbg recipe) to an image. Can I use this variable from a custom config file (or an environment var) to do it?12:20
rfuentessI'm reading it documentation and trying to find examples. But as far I see it only for the pre-existent "native" class12:20
qschulzrfuentess: maybe you're looking for IMAGE_FEATURES rather?12:21
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Ping timeout: 252 seconds)12:21
qschulzand depending on which features are in it, you'd add or not a package to your image?12:21
rfuentessyeah,  EXTRA_IMAGE_FEATURES could be ?12:22
rfuentessthe idea that we have is to try to determine a "baking" time (bitbake <image>) if we want GDB or not in the final image12:22
qschulzrfuentess: be careful, because using this for a "debug" image only goes so far12:25
qschulzwhat we usually recommend is to have a debug distro based on your normal distro12:25
qschulzthis drastically increases build time but it is much cleaner and allows for much more customization than trying to do everything in an image12:26
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has joined #yocto12:26
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)12:29
rfuentessok, I'm still trying to learn  yocto itself. But, "debug distro based on your normal distro" means, to have an extra layer that is identical to our distro but with the extra debugging features?12:31
qschulzan extra distro configuration file12:32
*** otavio <otavio!~otavio@200.102.164.25> has joined #yocto12:32
jaskij[m]<rfuentess> "the idea that we have is to..." <- There's an existing `debug-tweaks` feature. It doesn't add -dbg packages, but disables root password, and adds GDB and some other stuff12:36
rfuentessohhh12:37
rfuentessuh, `poky/meta/recipes-sato/images/core-image-sato-sdk.bb` this example looks interesting with the IMAGE_FEATURES  selection12:40
jaskij[m]rfuentess: what I'm doing is maintain two images, with exact same content, but one has those tweaks and some other development utilities. To make it work in a sane way, you need to set up package groups so you don't end up with different base content.12:40
jaskij[m]Used to do it with classes inherited by the images, but package groups are saner12:41
rfuentessjaskij[m]: basically you have distro.conf and distro_debug.conf where the distro.conf set the packages groups and the latest just add new ones ?12:42
jaskij[m]No, I do it all in the images12:42
jaskij[m]Didn't set up a separate distro12:42
qschulzrfuentess: you only need a distro once you start saying "I want this package to have a different file or compile option if it's in the debug image"12:43
qschulzbecause recipe data is local, and images are recipes, so you cannot modify a package recipe from your image recipe12:44
rfuentessOk, I'm starting to understand this better12:47
*** ptsneves <ptsneves!~Thunderbi@031011128148.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Quit: ptsneves)12:48
rfuentessTime to read my notes and going further to try to understand properly all your recommendations. Thanks!12:50
Guest9qschulz: Do you think this can be used to have a normal kernel config file and a debug one? for now I have two different MACHINE which is not good12:55
qschulzGuest9: two machines or two distros, up to you13:00
qschulz(two distros is cleaner)13:00
Guest9qschulz: oki many thanks I preffered it with distros too.13:05
vvnis there a "yocto" way to compile virtual/kernel with allmodconfig? So that I can have a minimal kernel and host / install necessary modules afterwards?13:10
*** seninha <seninha!~seninha@user/seninha> has joined #yocto13:14
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 265 seconds)13:19
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto13:19
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 250 seconds)13:24
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto13:24
qschulzvvn: KERNEL_CONFIG_COMMAND13:26
*** Guest9 <Guest9!~Guest9@softbank-robotics-gw1.ter4.eqx2.par.cust.as8218.eu> has quit IRC (Ping timeout: 252 seconds)13:29
*** zpfvo <zpfvo!~fvo@i59f5ce57.versanet.de> has quit IRC (Ping timeout: 252 seconds)13:32
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 252 seconds)13:36
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:dbe1:d702:70ab:858> has quit IRC (Quit: vladest)13:36
*** kevinrowland <kevinrowland!~kevinrowl@136.226.67.0> has quit IRC (Quit: Client closed)13:38
dwagenkqschulz: I recently watched the talk recording of your and your colleagues presentation "Secure Boot from A to Z"  where you talk about a dependency loop in yocto with kernel-fitimage and dm-verity. You mention an adapted kernel-fitimage class that works around this issue. Is that class open source and published somewhere?13:39
dwagenkI'm currently in a similar situation with signed UnifiedKernelImages (for UEFI boot on x86-64) and looking for inspiration...13:39
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto13:39
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Quit: Leaving)13:39
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:8b78:c3eb:3027:d2a4> has joined #yocto13:40
qschulzdwagenk: unfortunately no and I don't have access to this class anymore13:41
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto13:42
qschulzthere's a new way of passing the root hash to the kernel via kcli parameters IIRC13:43
dwagenkqschulz: thanks. I've got a vague idea of how I'll approach it and hope no big issues come up with that13:43
dwagenkwell, it's on bare metal and the goal is to have the UnifiedKernelImage directly started by the uefi firmware, to eliminate additional components (bootloaders) in the secure boot chain. I guess kcli is not the correct tool in this scenario.13:45
qschulzdwagenk: you need to verify the rootfs signature13:46
dwagenkThe hashed rootfs and all combinations of kernel+initrd+cmdline are known in advance, so it should be achievable.13:46
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has joined #yocto13:47
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed)13:50
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto13:52
dwagenkwell, if it is part of the cmdline that is part of the signed UnifiedKernelImage13:52
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto13:59
*** ptsneves <ptsneves!~Thunderbi@031011128148.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto14:12
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)14:15
*** vmeson <vmeson!~rmacleod@23-233-86-175.cpe.pppoe.ca> has joined #yocto14:17
*** wkawka <wkawka!~wkawka@84-10-27-202.static.chello.pl> has quit IRC (Quit: Client closed)14:18
*** pbergin <pbergin!~pbergin@83.218.73.98> has quit IRC (Quit: Leaving)14:26
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has joined #yocto14:36
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has quit IRC (Read error: Connection reset by peer)14:40
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has joined #yocto14:40
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has quit IRC (Read error: Connection reset by peer)14:47
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has joined #yocto14:49
*** brazuca <brazuca!~brazuca@2804:7f4:3590:3b60:2046:3172:5065:1e44> has joined #yocto14:51
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto14:56
*** d-s-e <d-s-e!~d-s-e@i5C7587B7.versanet.de> has quit IRC (Ping timeout: 252 seconds)14:57
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto14:58
*** rcw <rcw!~rcwoolley@216.154.26.130> has joined #yocto15:04
*** brazuca <brazuca!~brazuca@2804:7f4:3590:3b60:2046:3172:5065:1e44> has quit IRC (Quit: Client closed)15:07
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed)15:11
*** rcw <rcw!~rcwoolley@216.154.26.130> has quit IRC (Quit: Leaving)15:13
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)15:13
*** thomasd13 <thomasd13!~thomasd13@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC (Ping timeout: 268 seconds)15:16
RPrburton: https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/153/steps/14/logs/stdio is a new and intersting failure mode (arm worker but probably a general issue)15:17
rburtonwell that looks horrible15:31
rburtontriggered by 3670f3685e63345df0501f26acad2044e3544d7b?15:32
rfuentessqschulz: IMAGE_INSTALL is used for the packages that must always goes with a package. Whereas IMAGE_FEATURE may be packages installed by some bbclasses or config files ?  And finally, EXTRA_IMAGE_FEATURE when I want to add non-expected features from my local.conf file ?15:33
*** manuel1985 <manuel1985!~manuel198@185.144.162.58> has quit IRC (Ping timeout: 244 seconds)15:39
qschulzrfuentess: IMAGE_INSTALL is a list of packages to install in an image, to be set in an image recipe15:40
qschulzIMAGE_FEATURE is for controlling the behavior of an image (doing something specific after all packages are installed in the image, installing multiple related packages, disabling root password, etc...)15:40
qschulzto be set in an image recipe15:41
qschulzrfuentess: we have extensive documentation here: https://docs.yoctoproject.org/ref-manual/variables.html15:41
*** tre <tre!~tre@ip5f5886dd.dynamic.kabel-deutschland.de> has quit IRC (Remote host closed the connection)15:41
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)15:41
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto15:42
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has quit IRC (Quit: Leaving)15:44
RPrburton: maybe, I don't know. That shouldn't have changed much should it?15:44
rburtonmaaaaybe15:44
RPrburton: I suspect it is just a genuine race :/15:44
rburtoncan't see anything else jumping out though15:44
rburtonyeah could be15:44
RPrburton: I was wondering about trying to claim it was arm specific15:45
rburtoni doubt it is ;)15:45
RPrburton: can you prove it though? :)15:45
rfuentessqschulz: thanks. I'm reading right now the https://docs.yoctoproject.org/ref-manual/images.html and also that one. But was trying to understand why In the former the IMAGE_FEATURE is also offered as a complement to IMAGE_INSTALL15:45
rfuentessqschulz: OH!  core-image-minimal-dev and core-image-minimal just made me to understand better what you and qschulz were speaking before15:48
*** PhoenixMage <PhoenixMage!~phoenix@206.83.118.102> has quit IRC (Ping timeout: 265 seconds)15:50
*** PhoenixMage <PhoenixMage!~phoenix@206.83.113.14> has joined #yocto15:51
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has quit IRC (Ping timeout: 252 seconds)16:07
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has joined #yocto16:09
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)16:16
*** denisoft81 <denisoft81!~denisoft8@host-87-20-65-92.retail.telecomitalia.it> has joined #yocto16:18
*** kevinrowland <kevinrowland!~kevinrowl@136.226.67.0> has joined #yocto16:21
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Read error: Connection reset by peer)16:29
*** denisoft81 <denisoft81!~denisoft8@host-87-20-65-92.retail.telecomitalia.it> has quit IRC (Quit: Leaving)16:30
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:8b78:c3eb:3027:d2a4> has quit IRC (Ping timeout: 268 seconds)16:30
*** kscherer <kscherer!~kscherer@dsl-173-206-235-242.tor.primus.ca> has joined #yocto16:33
*** zpfvo <zpfvo!~fvo@i59F5CE57.versanet.de> has quit IRC (Quit: Leaving.)16:35
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto16:52
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 244 seconds)17:14
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has quit IRC (Ping timeout: 260 seconds)17:14
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has joined #yocto17:16
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 265 seconds)17:39
*** wyre <wyre!~wyre@user/wyre> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)17:41
*** wyre <wyre!~wyre@user/wyre> has joined #yocto17:42
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto17:44
kevinrowlandHi all. I'm trying to understand how bitbake knows to re-fetch a local file (those with file:// URIs) when the file has changed. I think I've got a handle on it (siggen.prep_taskhash() calls fetch2.get_file_checksums() and then siggen.get_taskhash() adds those file checksums to the taskhash). While experimenting, I noticed that if I start with a18:14
kevinrowlandfile [lets say it's in state A] and build, then modify that file [now let's say it's in state B] and re-build, then the file is re-fetched and the configure/compile/deploy/etc tasks are all re-run. Then if I _remove the modification_ [to return to state A] and re-build again, bitbake will re-compute the file checksum, land at the same taskhash as18:14
kevinrowlandthe first build, and pull from sstate cache rather than re-running all of the tasks. That's super cool, and it means bitbake can clearly hold on to multiple cache entries for one task. My question is: is there any upper limit to the number of cache entries that bitbake will maintain for a given task? Or will the cache grow unbounded if I continue18:14
kevinrowlandto modify this local file?18:14
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Ping timeout: 264 seconds)18:35
*** seninha <seninha!~seninha@user/seninha> has joined #yocto18:36
*** davidinux <davidinux!~davidinux@92.118.62.163> has quit IRC (Ping timeout: 264 seconds)18:41
*** davidinux <davidinux!~davidinux@138.199.54.250> has joined #yocto18:43
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 264 seconds)18:54
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto18:54
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 265 seconds)18:59
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto18:59
*** florian_kc <florian_kc!~florian@dynamic-078-049-051-206.78.49.pool.telefonica.de> has joined #yocto19:05
kergothkevinrowland: sstate cache management is up to you, bitbake never removes anything from the sstate cache dir.19:14
kergothsome folks will use access time to periodically remove sstate artifacts that haven't been used by any builds in a certain amount of time19:14
*** florian_kc <florian_kc!~florian@dynamic-078-049-051-206.78.49.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds)19:15
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has quit IRC (Read error: Connection reset by peer)19:21
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has joined #yocto19:23
kevinrowlandkergoth: thanks for the response19:52
*** kscherer <kscherer!~kscherer@dsl-173-206-235-242.tor.primus.ca> has quit IRC (Ping timeout: 264 seconds)19:58
*** kscherer <kscherer!~kscherer@dsl-173-206-68-85.tor.primus.ca> has joined #yocto19:58
*** kscherer_ <kscherer_!~kscherer@dsl-173-206-91-150.tor.primus.ca> has joined #yocto20:03
*** kscherer <kscherer!~kscherer@dsl-173-206-68-85.tor.primus.ca> has quit IRC (Ping timeout: 252 seconds)20:03
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has quit IRC (Read error: Connection reset by peer)20:05
*** amitk <amitk!~amit@103.59.74.87> has quit IRC (Ping timeout: 265 seconds)20:06
*** florian_kc <florian_kc!~florian@dynamic-078-049-051-206.78.49.pool.telefonica.de> has joined #yocto20:08
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto20:08
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has joined #yocto20:10
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)20:14
*** kscherer_ <kscherer_!~kscherer@dsl-173-206-91-150.tor.primus.ca> has quit IRC (Quit: Konversation terminated!)20:22
*** mvlad <mvlad!~mvlad@2a02:2f08:4904:c800:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)20:28
*** odra <odra!~odra@201-69-114-148.dial-up.telesp.net.br> has quit IRC (Ping timeout: 268 seconds)20:30
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)20:34
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 250 seconds)20:34
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)20:36
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has joined #yocto20:40
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has quit IRC (Quit: Leaving)20:48
*** florian_kc <florian_kc!~florian@dynamic-078-049-051-206.78.49.pool.telefonica.de> has quit IRC (Ping timeout: 265 seconds)21:18
*** seninha <seninha!~seninha@user/seninha> has joined #yocto21:41
*** florian_kc <florian_kc!~florian@dynamic-078-049-051-206.78.49.pool.telefonica.de> has joined #yocto22:01
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)22:05
*** Estrella_ <Estrella_!~quassel@192-063-174-177.res.spectrum.com> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)22:10
*** Estrella_ <Estrella_!~quassel@192-063-174-177.res.spectrum.com> has joined #yocto22:16
*** seninha <seninha!~seninha@user/seninha> has joined #yocto22:16
*** florian_kc <florian_kc!~florian@dynamic-078-049-051-206.78.49.pool.telefonica.de> has quit IRC (Ping timeout: 265 seconds)22:46
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Ping timeout: 265 seconds)22:48
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has quit IRC (Ping timeout: 265 seconds)23:20
*** Tokamak <Tokamak!~Tokamak@172.58.188.234> has joined #yocto23:27
*** RP <RP!~richard@dan.rpsys.net> has quit IRC (Ping timeout: 248 seconds)23:30
*** seninha <seninha!~seninha@user/seninha> has joined #yocto23:37
*** RP <RP!~richard@dan.rpsys.net> has joined #yocto23:54

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