Wednesday, 2019-10-02

*** jij <jij!jonashg@nat/axis/x-kmkoargdyezvjfjt> has quit IRC00:03
*** Saur <Saur!pkj@nat/axis/x-uienismpsqbfwfai> has quit IRC00:04
*** learningc <learningc!~learningc@> has quit IRC00:20
*** vineela <vineela!vtummala@nat/intel/x-pkjfrbpvxmorsust> has quit IRC00:27
*** learningc <learningc!> has joined #yocto00:33
*** Crofton <Crofton!~Crofton@> has quit IRC01:04
*** tgamblin <tgamblin!> has quit IRC01:15
*** armpit <armpit!~armpit@> has quit IRC01:19
*** lucaceresoli <lucaceresoli!> has quit IRC01:37
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC01:37
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto01:37
*** lucaceresoli <lucaceresoli!> has joined #yocto01:39
*** vineela <vineela!vtummala@nat/intel/x-ykxvoohhfdwsjcvd> has joined #yocto02:23
*** vineela <vineela!vtummala@nat/intel/x-ykxvoohhfdwsjcvd> has quit IRC02:33
*** cp <cp!> has quit IRC02:54
*** cp <cp!> has joined #yocto02:56
*** vineela <vineela!~vtummala@> has joined #yocto03:16
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto03:29
*** jeranio <jeranio!290dbceb@> has joined #yocto03:31
jeranioIs the next Coding live Yocto on the 8th October?03:32
jeranio5pm Berlin Time ?03:32
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC03:33
*** jeranio <jeranio!290dbceb@> has quit IRC03:37
*** armpit <armpit!~armpit@2601:202:4180:a5c0:2c5e:3326:62f0:95f9> has joined #yocto03:45
*** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has quit IRC04:33
*** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has joined #yocto04:33
*** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has joined #yocto04:33
*** lazyape_home <lazyape_home!~lazyape@> has joined #yocto04:36
*** elfGamal <elfGamal!~elg@> has quit IRC04:37
*** elGamal <elGamal!~elg@> has joined #yocto04:38
*** jaeckel <jaeckel!~jaeckel@unaffiliated/jaeckel> has quit IRC04:38
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC04:38
*** lazyape <lazyape!~lazyape@> has quit IRC04:38
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC04:38
*** linuxjacques <linuxjacques!~jacques@nslu2-linux/jacques> has quit IRC04:38
*** smartin <smartin!> has quit IRC04:38
*** jaeckel <jaeckel!~jaeckel@unaffiliated/jaeckel> has joined #yocto04:49
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto04:51
*** linuxjacques <linuxjacques!~jacques@nslu2-linux/jacques> has joined #yocto04:52
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto04:52
*** smartin <smartin!> has joined #yocto04:52
*** agust <agust!> has joined #yocto05:05
*** thomasd13 <thomasd13!> has joined #yocto05:11
*** AndersD <AndersD!> has joined #yocto05:19
*** AndersD <AndersD!> has quit IRC05:22
*** kroon <kroon!~kroon@> has joined #yocto05:43
*** AndersD <AndersD!> has joined #yocto05:43
*** Bunio_FH <Bunio_FH!> has quit IRC06:03
*** Klox <Klox!> has quit IRC06:14
*** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has quit IRC06:19
*** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has joined #yocto06:19
*** kroon <kroon!~kroon@> has quit IRC06:23
*** mckoan|away is now known as mckoan06:25
*** florian_kc is now known as florian06:32
*** goliath <goliath!> has joined #yocto06:32
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:45
*** Klox <Klox!> has joined #yocto06:59
*** goliath <goliath!> has quit IRC07:00
*** yann <yann!> has quit IRC07:05
*** coretec <coretec!d43ed5a2@> has joined #yocto07:06
*** TobSnyder <TobSnyder!> has joined #yocto07:16
*** amine <amine!> has joined #yocto07:26
*** yacar_ <yacar_!~yacar@> has joined #yocto07:47
*** amine <amine!> has quit IRC07:50
*** amine <amine!> has joined #yocto07:52
*** Saur <Saur!pkj@nat/axis/x-wlpbmpksfrvbvlyq> has joined #yocto07:58
*** Bunio_FH <Bunio_FH!> has joined #yocto07:59
*** bluca <bluca!~bluca@2a01:4b00:f419:6f00:7a8e:ed70:5c52:ea3> has joined #yocto08:01
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@ubuntu/member/locutusofborg> has joined #yocto08:15
LocutusOfBorghello, I have a simple question for imx6q mfgtool handling, is anybody out there to help?08:16
LocutusOfBorgthe question is: I have an imx6qsabresd, and I would like to build the mfgtools artifacts via yocto (e.g. warrior is fine)08:16
LetoThe2ndLocutusOfBorg: pick your poison:
LocutusOfBorgI fail to find documentation on the "current" mfgtool version and documentation on the build procedure, e.g.08:19
LocutusOfBorgLetoThe2nd, this fails.... for some reasons, 1) meta-fsl-arm is dead, 2) fsl-image-mfgtool-initramfs is not buildable for imx6q but only for imx6s08:20
LocutusOfBorg3) imx-uuc was working really good, it contains even a patch done by me... but it relies on FSL_UTP feature, that is now dropped on the kernel side, so it seems to be not working anymore08:20
LocutusOfBorg4) new mfgtool seems to have changed the way of communicating, deprecating FSL_UTP08:20
LocutusOfBorg5) I can't find proper documentation on the current way, and I don't want to build an oooooold yocto version just to have mfgtool artifacts08:21
LetoThe2ndLocutusOfBorg: well then your best chances are probably poking the layer maintainer if there's something in the making, or actually sending patches. the layerindex gives you the current publicly available state, and if that is obsolete, then... :-(08:22
mckoanLocutusOfBorg: the new name of meta-fsl-arm is meta-freescale08:24
LocutusOfBorgmckoan, yes, since some years, but the stuff in meta-freescale is not working, as said above08:24
LocutusOfBorgI was even the probably first person to complain when they moved layer without making people aware...08:24
*** tvm <tvm!> has joined #yocto08:31
yacar_ zeddi: I worked on the bug yesterday, I've added SPDX Identifier to scc and cfg files, there's a file : cfg/debug/kgdb/debug-kgdb-serial-console.scc~ which looks like an open file by an editor, should I remove the file?08:44
yacar_zeddii: I misspelled your pseudo sorry !08:45
*** prabhakarlad <prabhakarlad!c18ddb24@> has joined #yocto08:49
prabhakarladHi all, what is the correct way to append COMPATIBLE_MACHINE for a recipe08:49
mckoanprabhakarlad: can you describe better your question?08:55
Domin1kprabhakarlad: i prefere +=08:55
Domin1kprabhakarlad: COMPATIBLE_MACHINE is just a variable08:56
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:59
prabhakarladDomin1k COMPATIBLE_MACHINE += doesnt work, nor does _append08:59
*** tprrt <tprrt!~tprrt@> has joined #yocto09:02
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:03
Domin1kprabhakarlad: oh sorry im wrong. it looks like it should be made like this COMPATIBLE_MACHINE = "qemux86|qemux86-64"09:03
prabhakarladyes, but how do we append it in a bbappend file ?09:05
*** woutervh <woutervh!~woutervh@> has joined #yocto09:08
Domin1kprabhakarlad: i would guess doing COMPATIBLE_MACHINE += "|my_new_machine". But if you say this does not work i would wait until an yocto expert answers your question. I'm just a rookie that is trying to help.09:09
LetoThe2ndDomin1k: i'd guess thats pretty close, yet _append instead of +=. because append doesn't insert a blank space09:10
Domin1kLetoThe2nd: (y)09:12
prabhakarladLetoThe2nd, the original bb file has COMPATIBLE_MACHINE = "(qemux86|qemux86-64)" so now when I create a bbappend file and do +=/append it doesnt work.09:13
Domin1kprabhakarlad: it looks like the ) makes it unappendable09:15
*** prabhakarlad <prabhakarlad!c18ddb24@> has quit IRC09:16
*** dreyna_ <dreyna_!> has quit IRC09:20
Domin1kIm wondering if ther is a good way handling with big rescources in bitbake? I Have a Repo with a lot of rescources like Images, Videos etc. I would like to install them to my Image directly within the bitbake process. But it looks like the bitbake duplikates these files quite often. I have the fetched resources in the workdir, a duplicate as a09:23
Domin1ktar.gz inside the folder "build/download/", the rpm-package and finaly inside my wic-image. By now i need about 1.2 TB of diskspace for a build.09:23
LetoThe2ndDomin1k: all which is some form opf payload isn't really meant to go into the layers. the layers, as the meta- already suggests, should not contain those images, videos, etc.09:26
LetoThe2ndDomin1k: if you have already properly split them out into a payload recipe that fetches them, then i'm not aware of any redcution technique at the moment.09:27
Domin1kWhat do you actually mean with a payload recipe? I have a recipe that builds my app within my own foo_poky/meta-foocraft/ layer inside this recipe i have seprerated the resources in a package with PACKAGES += "${PN}-resources" FILES_${PN}-resources += "/mnt/app/resources/*"09:34
*** kroon <kroon!~kroon@> has joined #yocto09:35
LetoThe2ndDomin1k: seperating means, the recipe pulls the resourced from some out-of tree location, like ftp or whatever, as does not acutally contain them as files next to the recipe.09:37
Domin1kLetoThe2nd: I pull them from a clearcase-vob (VCS-repository) so that should be ok. I have to ask my boss for another diskupgrade then.09:42
LetoThe2ndDomin1k: "you wann make big app boss, you gonna big disk boss""09:43
Domin1kLetoThe2nd: for a development scenario this isn't that much relevant. I could build the image without the app resources and work with a nfs mount from my device to the resources repo on my workstation09:44
Domin1kLetoThe2nd: the final size of the wic image is just 234 GB but needing 5 times that much to build this image sounds a bit crazy.09:47
*** marler899721 <marler899721!> has quit IRC09:48
LetoThe2ndDomin1k: our images are usually ~40M and we need 30GB or 40GB to build them. don't you think my "why does it need a thousand times the space for the build" sounds more crazy than your 5?09:49
*** yacar_ <yacar_!~yacar@> has quit IRC09:51
*** Bunio_FH <Bunio_FH!> has quit IRC09:51
*** Bunio_FH <Bunio_FH!> has joined #yocto09:52
Domin1kLetoThe2nd: My boss thinks we would do better using a ubuntu image. At the moment we are using a stripped down debian image but i'm sure yocto will help us to build a better image and solve a lot of issues that we have at the moment with our current image-build-environment.09:53
LetoThe2ndDomin1k: it all depends on the use case, and using debian/ubunt can be totally valid too. it all depend.09:55
LetoThe2ndDomin1k: you can of course use some evil magic and "inject" the payload through some rootfs postprocessing, but it kinda defeats the point of OE/yocto. and if thats only for the couple of bucks that some disk space costs, its a bad deal taking the maintenance effort into account.09:56
*** rburton <rburton!> has joined #yocto10:05
*** coretec <coretec!d43ed5a2@> has quit IRC10:19
*** learningc <learningc!> has quit IRC10:22
*** bluca <bluca!~bluca@2a01:4b00:f419:6f00:7a8e:ed70:5c52:ea3> has quit IRC10:32
*** Domin1k <Domin1k!c1669b04@> has quit IRC10:39
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto10:43
*** bluca <bluca!~bluca@> has joined #yocto10:50
*** learningc <learningc!~learningc@> has joined #yocto11:03
*** yann|work <yann|work!~yann@> has joined #yocto11:06
*** thinkmassive <thinkmassive!thinkmassi@gateway/shell/> has quit IRC11:07
*** kayterina <kayterina!kayterina-@gateway/shell/> has quit IRC11:07
*** nrossi <nrossi!nrossimatr@gateway/shell/> has quit IRC11:07
*** bachp <bachp!bachpmatri@gateway/shell/> has quit IRC11:07
*** MarcWe1 <MarcWe1!hmwmatrixo@gateway/shell/> has quit IRC11:07
*** wak-work <wak-work!wak-workma@gateway/shell/> has quit IRC11:07
*** silviof <silviof!silv-iomat@gateway/shell/> has quit IRC11:07
__angelohi folks :) question : i see different directory layouts when yocto-based distros are created, what should be a good directory layout to use ?11:10
rburtonpersonally i put bitbake and all the layers alongside each other11:11
rburtonassuming thats what you mean11:11
__angelorburton, yes. I find different layouts around, probably coming from different tutorial/how to11:11
__angelorburton, so you use kind of older oe style, right ?11:12
rburtonnot sure i'd call it old11:12
*** thomasd13 <thomasd13!> has quit IRC11:13
__angelook. so you are not using poky stuff ?11:14
rburtonthat' a good example of bitbake and layers all in one place11:16
rburton*poky is an example*11:16
rburtonif you want your own distro make your own distro11:16
rburtonotherwise you'll be upset when eg poky changes11:16
rburton(which is does, often)11:17
*** yacar_ <yacar_!~yacar@> has joined #yocto11:17
__angelomany thanks11:17
*** bachp <bachp!bachpmatri@gateway/shell/> has joined #yocto11:17
*** ThomasD13 <ThomasD13!> has joined #yocto11:21
__angeloabout  "upset when eg poky changes", this is not totally clear. Can i fix to a revision and work on that ?11:25
LetoThe2nd__angelo: for example when you update from sumo to thud, to warrior, there might be changes in poky11:26
*** pepone <pepone!> has joined #yocto11:31
__angeloLetoThe2nd, ok11:32
peponeHey, I'm trying to track down a bug with network stack in core-image-minimal, what is the default libc build with core-image-minimal?11:32
*** nrossi <nrossi!nrossimatr@gateway/shell/> has joined #yocto11:33
*** silviof <silviof!silv-iomat@gateway/shell/> has joined #yocto11:33
LetoThe2ndpepone: glibc11:34
peponeI getting some issues with TCP close connection, specially sever sending TCP FIN/RST gets unoticed by client, server connection gets closed but client conn remains open11:36
*** berton <berton!~berton@> has joined #yocto11:37
peponetesting with a bunch of distros and only getting this issues with Yocto Warrior11:37
kanavin_pepone, are you using the latest warrior?11:40
rburtonpepone: what kernel though11:40
rburtonpepone: most BSPs provide their own kernel11:40
kanavin_particularly, you probably need this fix11:41
kanavin_commit f5cc3bf166c8eca58630e267cc58bdd88fbc6e9511:41
kanavin_Author: Bruce Ashfield <>11:41
kanavin_Date:   Fri Apr 26 10:52:17 2019 -040011:41
kanavin_    linux-yocto/5.0: integrate TCP timeout / hang fix11:41
kanavin_it was a bug in 5.0 kernels11:41
pepone5.0.3-yocto-standard #1 PREEMPT Mon Sep 9 17:44:34 UTC 2019 armv7l armv7l armv7l GNU/Linux11:41
peponekanavin_: Thanks I will give it a try if I manage to update the BB kernel11:43
rburtonthat was in 2.7.1 though11:44
*** tgamblin <tgamblin!~tgamblin@> has joined #yocto11:44
*** jij <jij!jonashg@nat/axis/x-ugwcqvgzevzigrmf> has joined #yocto11:46
peponeYes I have that commit in my tree11:47
*** berton <berton!~berton@> has quit IRC11:59
*** berton <berton!~berton@> has joined #yocto11:59
*** nighty- <nighty-!> has joined #yocto12:09
*** kroon <kroon!~kroon@> has quit IRC12:12
*** goliath <goliath!> has joined #yocto12:18
*** pharaon2502 <pharaon2502!~hropatest@> has left #yocto12:24
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:24
*** orzen <orzen!> has quit IRC12:30
*** Domin1k <Domin1k!c1669b04@> has joined #yocto12:31
*** orzen <orzen!> has joined #yocto12:37
*** AndersD <AndersD!> has quit IRC12:45
*** woutervh <woutervh!~woutervh@> has quit IRC12:55
*** Crofton <Crofton!~Crofton@> has joined #yocto12:58
*** goliath <goliath!> has quit IRC13:03
zeddiiRP: at least we got a bit of interest in the strace report on lkml.13:06
RPzeddii: yes, I saw. Hopefully we can get them to reproduce it and then get somewhere :)13:07
zeddiiI had to scramble to dig up the manual build steps for it, I hope I didn't screw them up :D13:08
*** ThomasD13 <ThomasD13!> has quit IRC13:11
RPzeddii: we'll see what they say and worst case we may have to come up with a simpler reprocuder13:11
RPvmeson: ^^^13:12
*** Domin1k <Domin1k!c1669b04@> has quit IRC13:13
*** WillMiles <WillMiles!> has joined #yocto13:20
*** pepone <pepone!> has quit IRC13:25
kanavin_zeddii, do you have a link?13:27
*** thomasd13 <thomasd13!> has joined #yocto13:28
*** iceaway2_ <iceaway2_!~pelle@> has quit IRC13:32
kanavin_zeddii, thanks, hope they manage to reproduce13:32
kanavin_zeddii, it does not happen on opensuse's 5.2 kernel though :(13:32
thomasd13When I specify a kernel feature with KERNEL_FEATURES_append , does it matter if this feature is built in the kernel or if it is provided as kernel module?13:33
*** comptroller <comptroller!> has quit IRC13:35
*** comptroller <comptroller!> has joined #yocto13:39
zeddiikanavin_: there may be some kernel config at play then. I saw it on a mainline test that I ran, but I’ll revisit that before they tell me they can’t reproduce it. I suppose I could diff the opensuse 5.2 kernel to see if they have a patch in that area.13:42
kanavin_zeddii, yes, also maybe running the test on physical hardware could help narrow it down13:44
kanavin_(e.g. nuc or something like that)13:44
zeddiiI saw it on linux-yocto-dev as well, which is pretty much a raw mainline kernel, so I know it wasn’t fixed in the 5.3 cycle. but the kernel config is very similar to the 5.2 one we use. I’m going to test 5.4-rc1 shortly to see if it is there.13:45
kanavin_it might be specific to qemu13:46
zeddiiI don’t have any h/w test boxes handy to test on. Do we have results for 5.2 on genericx86-64 that don’t show the issue ?  or do we not run those there .. or is that not h/w ? I’m not aware of all the details there.13:47
*** AndersD <AndersD!> has joined #yocto13:50
kanavin_I don't think the AB has any real HW, everything runs through qemu, maybe RP can clarify13:51
RPkanavin_: all AB stuff runs on qemu. There are manual QA tests, its unclear if they'd run the ptests on the real hardware though14:03
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC14:04
*** lfa <lfa!~lfa@> has quit IRC14:07
*** thomasd13 <thomasd13!> has quit IRC14:18
*** tprrt <tprrt!~tprrt@> has quit IRC14:59
*** behanw <behanw!uid110099@gateway/web/> has joined #yocto15:12
*** yacar_ <yacar_!~yacar@> has quit IRC15:12
*** Crofton <Crofton!~Crofton@> has quit IRC15:30
*** Bunio_FH <Bunio_FH!> has quit IRC15:35
*** yacar_ <yacar_!~yacar@> has joined #yocto15:49
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC15:52
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto15:52
*** yann|work <yann|work!~yann@> has quit IRC15:54
*** Crofton <Crofton!~Crofton@> has joined #yocto15:55
*** learningc <learningc!~learningc@> has quit IRC16:04
*** Bunio_FH <Bunio_FH!> has joined #yocto16:14
*** TobSnyder <TobSnyder!> has quit IRC16:15
CroftonThe autobuilder runs on imaginary hardware16:16
*** yacar_ <yacar_!~yacar@> has quit IRC16:20
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC16:20
mckoanCrofton: LOL16:21
*** mckoan is now known as mckoan|away16:25
*** dreyna <dreyna!> has joined #yocto16:29
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto16:58
*** vineela <vineela!~vtummala@> has joined #yocto17:02
RPCrofton: I'm now thinking we'd have to number them with imaginary numbers17:08
Croftonof course17:08
CroftonA guy asked me about this email last night17:09
CroftonLooks like no repleis17:09
JPEWI was thinking that wouldn't be hard too add an optional QA check for that case.17:10
CroftonI you care about reproducible builds AUTOREV in a recipe is a serious issue17:14
JPEWRight, I think they understood that the layers are poorly written(?) since AUTOREV is non-optional, but there's no tool to detect it ATM17:15
JPEWThe hard part is making AUTOREV a valid option (e.g. not fail QA) when it does make sense and someone does actually want it...17:17
JPEWMaybe tie the QA check to the reproducibl_build.bbclass?17:17
JPEWSounds like I'm volunteering to reply to the email :)17:18
CroftonRP ^^^17:21
RPJPEW: sounds like the right track to me FWIW17:22
Croftonah yes, I was going there was a class that flagged the system we super care about reproducibilty17:22
CroftonStuff like this is why we need to get out and actually meet with people. He pointed the email out to us last night17:23
RPIndeed. I tend to feel bad as there are a lot of emails that should get replies that don't17:24
Croftonsecond blog post needs review17:28
JPEWRP, Crofton: Does this look OK: ?17:51
yoctiBug 13567: normal, Undecided, ---, ross.burton, NEW , Add QA check for recipes that use AUTOREV by default17:51
CroftonYes, we don't want to trip people expecting a reproducible build with autorev recieps17:53
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC18:25
yoctiNew news from stackoverflow: Failure while compiling apt - Yocto <>18:30
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto18:43
*** tgamblin <tgamblin!~tgamblin@> has quit IRC18:59
*** kroon <kroon!> has joined #yocto19:03
*** bluca <bluca!~bluca@> has quit IRC19:09
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:13
yoctiNew news from stackoverflow: Adding sqlite Qt5 plugin in Yocto <>19:30
TartarusRP: Can you tag bitbake 1.43.2 please?19:36
RPTartarus: I can but there aren't many tags in there :/19:37
TartarusThere's only 44 tags I see, yeah19:37
Tartarusimho, tags for BB_MIN_VERSION values is helpful for ease of switching branches around19:37
RPTartarus: probably, I just now worry which other ones I'll be asked for19:38
Tartarussec ;)19:39
Tartarus1.39.1, which is what thud asks for19:40
Tartarusolder than that is no longer actively supported19:40
RPalready there19:40
TartarusSo shrug19:40
* Tartarus kicks bitbake19:40
* Tartarus kicks git19:40
RPcareful, bitbake can kick back ;-)19:41
TartarusSo, yeah, I think with that, that's enough tags now19:41
Tartarusand hopefully a mental note to tag bitbake when bumping BB_MIN_VERSION in the future will be 'it'.19:42
RPTartarus: I will try19:42
radsquirrelis there something written down out there that helps you decide when to use = vs ?= vs ??=19:49
radsquirreland _append vs +=19:49
radsquirrelfrom a best practices point of view.19:49
*** Ad0 <Ad0!~Ad0@> has quit IRC19:55
kroonradsquirrel, there is always the bitbake manual19:55
kroonradsquirrel, I think I've seen some bitbake cheat sheet aswell19:55
*** Bunio_FH <Bunio_FH!> has quit IRC19:55
*** Ad0 <Ad0!~Ad0@> has joined #yocto20:00
mischiefwhat is the variable ROOTFS_BOOTSTRAP_INSTALL for?20:00
*** yates <yates!> has joined #yocto20:02
yatesdo .rpm packages provide a method to run pre- and/or post-install scripts, or are they basically just files which get copied over?20:03
yatesand/or does "smart" provide such a capability on top of the .rpm file installation?20:04
bluelightningyates: we do intrinsically support pre/postinstall (and pre-postuninstall) scripts, and they get funnelled through into the packages (rpms in this case)20:07
bluelightningyates: smart supports them in as much that it calls rpm and rpm will run them20:07
bluelightningthe only "special" bit is that when building the image, we try to execute them on the build host, and if they succeed then great - if not, they get deferred to first boot20:08
*** khem <khem!~khem@unaffiliated/khem> has quit IRC20:08
bluelightning(which of course won't work if you are using a read-only rootfs)20:08
bluelightningthere is a little bit of magic to explicitly mark postinsts that are known to require running on the target in more recent versions but if you're talking about smart I suspect that won't apply in your case20:09
bluelightningthe best practice is to try to ensure the postinstalls *can* run during image construction20:09
bluelightningwhat that really means is use $D in front of paths20:10
bluelightningand don't assume any special hardware is there20:10
yatesbluelightning: the scripts are put into the .rpm file?20:10
yateswhat do you mean by "first boot"?20:11
yatesdeferred to first boot?20:11
kergothit means exactly what it says. they run the first time the device boots. which isn't viable on an r/o fs20:12
yateswhy can't you run a first-boot script on a r/o fs?20:14
yatesbecause they have to be deleted after first boot?20:14
yatesbluelightning: so it seems there is a provision in both the .rpm format and in yocto to do this.20:15
bluelightningyates: yes and yes20:15
yatesdoes the now-ancient morty support this?20:16
bluelightningwe've had it for a very long time20:16
yatesbluelightning: thanks for this info. Very valuable.20:16
*** rburton <rburton!> has quit IRC20:28
*** kroon <kroon!> has quit IRC20:44
radsquirrelkroon: I've definitely read the bitbake manual.20:53
radsquirrelit describes the differences in behaviors between the different operators very well.20:54
radsquirrelwas looking more for the "why"20:54
radsquirrelI have been thinking about starting a blog.  my first post might be called "how to choose a bitbake variable assignment operator"20:59
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto21:00
ecdhethat's great radsquirrel21:00
ecdheI still don't know what ?= means21:00
ecdheI'm not sure how to search for it on google or what the name of the operator is21:00
radsquirrelit means if the same variable has been assigned previously with = it won't take your assignment with ?=21:01
radsquirrelby previously I mean in the global configuration (so something assigned by way of bitbake.conf)21:01
radsquirrelor in the case of a recipe and a bbappend, previously would mean the recipe21:02
ecdhenice and contextually ambiguous -- makes debugging so much easier when you can't tell what the effect of it will be just by looking at it.21:02
radsquirrelwell...I'll see what I can do about the blog :-)21:03
radsquirreland if anyone wants to drop hints on why I might pick = over ?= or ??= over ?= ... feel free.21:03
radsquirrelI'll include them.21:03
*** rburton <rburton!> has joined #yocto21:04
mischiefis there a way to specify some packages on a per-machine basis that are initramfs only? or should i invent a new variable?21:10
*** berton <berton!~berton@> has quit IRC21:15
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC21:18
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC21:24
*** rburton <rburton!> has quit IRC21:24
*** falstaff <falstaff!~quassel@> has quit IRC21:25
*** Hauke <Hauke!> has quit IRC21:28
*** yann <yann!> has joined #yocto22:06
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto22:17
kergothugh, the vscode bitbake extensions reliably hang my Remote - SSH workspace when opening a medium sized .inc. at least, the two extensions that work at all do22:27
kergothguess i'll do without highlighting for now..22:28
*** agust <agust!> has quit IRC22:37
khemkergoth: or switch to neovim :)22:38
kergoththat's what i usually use, been playing around with vscode + Remote - SSH recently22:38
khemyeah vscode is quite good IDE, I would say22:39
khemI use it quite a lot myself but time and again nvim fallback is used :)22:40
khemfor kernel sources it works fine22:40
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC22:50
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC23:23
*** Hauke <Hauke!> has joined #yocto23:56
*** vineela <vineela!~vtummala@> has quit IRC23:59

Generated by 2.11.0 by Marius Gedminas - find it at!