Thursday, 2020-11-19

*** vineela <vineela!~vtummala@> has quit IRC00:04
*** vineela <vineela!~vtummala@> has joined #yocto00:36
*** kiwi_29 <kiwi_29!> has quit IRC00:40
*** kiwi_29 <kiwi_29!> has joined #yocto00:40
*** vineela <vineela!~vtummala@> has quit IRC00:49
*** kiwi_29 <kiwi_29!> has quit IRC00:55
*** dev1990 <dev1990!> has quit IRC01:15
*** meow` <meow`!~sbourdeli@> has quit IRC01:30
*** B0ned1ger2 <B0ned1ger2!> has quit IRC01:35
*** B0ned1ger <B0ned1ger!> has joined #yocto01:35
*** kiwi_29 <kiwi_29!> has joined #yocto01:40
*** kiwi_29 <kiwi_29!> has quit IRC01:47
*** kiwi_29 <kiwi_29!> has joined #yocto01:47
kiwi_29bluelightning the issue of ${WORKDIR}${COREBASE} was misconfiguration on my end :(01:50
*** kaspter <kaspter!~Instantbi@> has joined #yocto01:57
kiwi_29Hello all, I am currently building sdk using "bitbake -c populate_sdk <MYCUSTOMDISTRO>"02:28
bluelightningkiwi_29: ah ok - anything we might want to consider in terms of additional checks / documentation?02:28
kiwi_29The following packages have unmet dependencies:02:28
kiwi_29 target-sdk-provides-dummy : Conflicts: coreutils02:28
kiwi_29E: Unable to correct problems, you have held broken packages.02:28
kiwi_29and I am getting this error02:28
kiwi_29bluelightning - the previous talk we had about ${WORKDIR}${COREBASE} was entirely my configuration problem02:29
kiwi_29the current issue about target-sdk-provides-dummy which conflicts with coreutils is a known bug it seems
kiwi_29has anybody been able to solve the issue?02:30
*** hpsy <hpsy!~hpsy@> has quit IRC02:34
*** stephano <stephano!> has quit IRC02:41
bluelightningkiwi_29: I've just reopened the bug FWIW02:42
*** extor <extor!extor@unaffiliated/extor> has joined #yocto02:43
kiwi_29many thanks bluelightning02:49
kiwi_29I am using deb ... and not rpm or ipk . I wonder if that is related02:49
*** camus1 <camus1!~Instantbi@> has joined #yocto02:53
*** kaspter <kaspter!~Instantbi@> has quit IRC02:53
*** camus1 is now known as kaspter02:53
*** sakoman <sakoman!~steve@> has quit IRC02:56
*** sakoman <sakoman!> has joined #yocto03:00
*** ahadi <ahadi!~ahadi@> has quit IRC03:07
*** ahadi <ahadi!~ahadi@> has joined #yocto03:09
*** hpsy <hpsy!~hpsy@> has joined #yocto03:25
*** kiwi_29 <kiwi_29!> has quit IRC03:29
*** kiwi_29 <kiwi_29!> has joined #yocto03:36
*** ericch <ericch!> has quit IRC03:39
kiwi_29all is there a way to remove target-sdk-provides-dummy from sdk build ?   I am facing errors while generating sdk using "bitbake -c populate_sdk <mycustmdistro>03:48
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has quit IRC04:21
*** kiwi_29 <kiwi_29!> has quit IRC04:26
*** kiwi_29 <kiwi_29!> has joined #yocto04:27
*** ojdo <ojdo!~ojdo@unaffiliated/ojdo> has joined #yocto04:28
*** B0ned1ger <B0ned1ger!> has quit IRC04:35
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto04:35
*** goliath <goliath!> has quit IRC04:45
*** camus1 <camus1!~Instantbi@> has joined #yocto04:48
*** kaspter <kaspter!~Instantbi@> has quit IRC04:50
*** camus1 is now known as kaspter04:50
*** kiwi_29 <kiwi_29!> has quit IRC05:24
*** kiwi_29 <kiwi_29!> has joined #yocto05:56
*** jobroe <jobroe!> has joined #yocto05:56
*** beneth <beneth!> has joined #yocto06:11
*** sno <sno!> has joined #yocto06:14
*** sno <sno!> has quit IRC06:26
*** sno <sno!> has joined #yocto06:29
*** pohly <pohly!> has joined #yocto06:32
*** AndersD <AndersD!> has joined #yocto06:38
*** sno <sno!> has quit IRC06:41
*** sno <sno!> has joined #yocto06:43
*** agust <agust!> has joined #yocto06:48
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC07:02
*** pharaon2502 <pharaon2502!> has joined #yocto07:04
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto07:05
*** sstiller <sstiller!> has joined #yocto07:20
*** wooosaii <wooosaii!> has quit IRC07:27
*** wooosaiiii <wooosaiiii!> has joined #yocto07:27
*** frsc <frsc!> has joined #yocto07:34
*** jobroe <jobroe!> has quit IRC07:36
*** mcc_ <mcc_!> has joined #yocto07:45
*** jobroe <jobroe!> has joined #yocto07:45
*** kiwi_29 <kiwi_29!> has quit IRC07:45
*** rabbit9911 <rabbit9911!> has quit IRC07:47
*** rabbit9911 <rabbit9911!> has joined #yocto07:48
*** mccc <mccc!> has quit IRC07:48
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/> has joined #yocto07:49
*** amitk <amitk!~amit@unaffiliated/amitk> has joined #yocto07:49
*** fl0v0 <fl0v0!~fvo@> has joined #yocto07:59
*** kpo_ <kpo_!> has quit IRC08:02
*** kpo_ <kpo_!> has joined #yocto08:02
*** dev1990 <dev1990!> has joined #yocto08:32
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:32
*** zillolo <zillolo!~zillolo@> has quit IRC08:42
*** oberstet <oberstet!~oberstet@> has joined #yocto08:45
*** kiwi_29 <kiwi_29!> has joined #yocto08:47
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto08:49
rburtonkiwi_29: deb is a bit more fragile, unless you have a hard need for it we recommend rpm or opkg08:49
*** florian_kc is now known as florian08:51
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has joined #yocto08:51
*** kiwi_29 <kiwi_29!> has quit IRC08:52
*** Yumasi <Yumasi!> has joined #yocto08:53
LetoThe2ndyo dudX08:54
* qschulz waves08:54
* LetoThe2nd "waves" back to qschulz
*** mckoan|away is now known as mckoan09:22
mckoangood morning09:22
LetoThe2ndpaulbarker: qschulz: you have both been nikhibaited again.09:32
*** amitk_ <amitk_!~amit@unaffiliated/amitk> has joined #yocto09:33
*** amitk <amitk!~amit@unaffiliated/amitk> has quit IRC09:35
*** B0ned1ger2 <B0ned1ger2!> has quit IRC09:35
*** B0ned1ger <B0ned1ger!> has joined #yocto09:36
qschulzLetoThe2nd: I know, does not mean I can't answer :)09:45
LetoThe2ndqschulz: obviously you're a better/braver man than me.09:46
qschulzI mean, this time the error was pretty obvious to me09:46
qschulzLetoThe2nd: there's no need for a ranking system :)09:47
LetoThe2ndreally? i skimmed it and was like, is there a single line thats not obviously wrong.09:47
qschulzLetoThe2nd: let's say, two lines were the obvious mistake, the rest was not harming except cluttering the code?09:47
LetoThe2ndthats a pretty euphemistiv but probably acceptable interpretation.09:48
*** eduardas <eduardas!~eduardas@> has joined #yocto09:53
*** habing <habing!~habing@2001:4bb8:188:5816:b486:552f:43c9:2> has joined #yocto09:53
eduardashello, what is the correct way to prepopulate the /dev directory with a console node for kernel's built-in initramfs in yocto?09:55
eduardasI've already taken a look at meta-initramfs, but the examples there do it at runtime09:55
*** likewise <likewise!> has joined #yocto09:57
eduardasIdeally I'd just like to drop a gen_init_cpio configuration file into the metadata, set a variable understood in poky and be done with it09:57
eduardasbut I have doubts whether that is supported09:57
*** Ox861726f6c64 <Ox861726f6c64!~Ox861726f@gateway/tor-sasl/ox861726f6c64> has joined #yocto10:02
qschulzndec: what's the issue with labels we actually use? (I can understand removing those which aren't used)10:03
ndecqschulz: consistency?10:03
qschulzndec: touché10:03
ndecand since we use the section name. that means that modiyfing the section name (for any reason) will force a developer to think twice about the change..10:04
qschulzndec: can't remember right now but how does bitbake labels work when referenced from YP docs?10:04
qschulz(and vice versa)10:04
qschulz*(just to be sure we don't break other docs)10:05
ndecwell, vice versa does not work :)10:05
ndecit's only YP which can refer to bitbake docs10:05
qschulztrue, makes no sense for bitbake to reference YP docs :p10:05
ndecand it works the same for labels and 'sections'10:05
ndece.g. :ref:`bitbake:xxx` and xxx can be a label or a section refernce10:06
ndecif you run  python -msphinx.ext.intersphinx <path to build folder>/html/objects.inv, you will get a list of all 'references' which are exposed10:07
ndeci haven't checked yet, if yocto-docs uses labels from bitbake-docs, we should remove the labels from bitbake as well!10:07
qschulzyeah I know for YP docs, in that case labels can be used with :ref:`label` whereas sections are always :ref:`subdir/doc:section` (or :ref:`section` if in same file?)10:08
qschulzso I'd imagine bitbake refs work the same way from YP docs perspective but I'm probably missing on something and I don't know where I'm going with this :p10:09
ndecqschulz: we always need the subdir.. even for refs in the same file. that is something i don't like much.. but it's how it works.10:13
*** leon-anavi <leon-anavi!~Leon@> has quit IRC10:13
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto10:13
ndecone other change i have in mind is to reduce the filename length.. too much duplication right now. e.g. "kernel-dev/kernel-dev-common.rst" should be kernel-dev/common.rst", at the very least.10:14
ndecthat's another magic sed for later..10:14
qschulznever ending list of improvements to make :)10:15
ndecwell, that's not a bad thing at all actually!10:16
ndecwhat would we do, if we were just done.10:16
qschulzindeed :)10:16
*** Ox861726f6c64 <Ox861726f6c64!~Ox861726f@gateway/tor-sasl/ox861726f6c64> has quit IRC10:18
LetoThe2ndndec: just like the kernel devs. i mean, they were basically done by 2.6.32, but they still just pretended the kernel needs more work and carried on like before :)10:18
*** dreyna <dreyna!> has quit IRC10:23
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:300a:f3c9:b99d:b59> has joined #yocto10:24
*** DanmerZ <DanmerZ!~op@> has joined #yocto10:59
*** DanmerZ <DanmerZ!~op@> has joined #yocto11:00
*** davidinux <davidinux!~davidinux@> has quit IRC11:08
*** davidinux <davidinux!~davidinux@> has joined #yocto11:11
*** Ox861726f6c64 <Ox861726f6c64!~Ox861726f@gateway/tor-sasl/ox861726f6c64> has joined #yocto11:18
qschulzLetoThe2nd: I don't want to hear you saying "I told you"11:23
LetoThe2ndqschulz: no worries. i'll not say it, but jsut type "I told you"11:25
LetoThe2ndqschulz: I told you.11:25
*** iceaway <iceaway!~pelle@> has joined #yocto11:55
iceawayhi everyone. I am running Yocto 2.5, and have a working image recipe which includes libgdiplus. Now a collegue of mine required the 32-bit version, so I added lib32-libgdiplus to my image recipe. Now I'm getting some strange build errors saying that "The postinstall intercept hook 'update_gio_module_cache' failed," followed by " do_rootfs: The following packages could not be configured offline and rootfs12:00
iceawayis read-only: ['101-libglib-2.0-0', '102-glib-networking', '100-lib32-libglib-2.0-0']".12:00
iceawayAny ideas if this can be resolved resorting to a read/write roootfs?12:03
LetoThe2ndiceaway: possibly :)12:03
iceawayI have been playing around with the associated postinst scripts etc, and found a bugfix in the update_gio_module_cache which I merged to my code, but that did not really help unfortunately.12:05
LetoThe2ndiceaway: its very well possible that a) this is an issue nobody else ran into so far b) it is fixed on current master c) it doesn't play nice with RO-rootfs. even combinations thereof.12:07
*** zyga-x240 <zyga-x240!~zyga@unaffiliated/zyga> has quit IRC12:07
iceawayThe error output from the build log is actually: "/home/pelle/development/var-fsl-yocto/build_kodkod/tmp/work/imx8qxpb0_var_som-poky-linux/tmlinux-image/1.0-r0/intercept_scripts-bd1c31820bf736a004f4ebe71461d6fa3ae23f7d97783c8f28a606e086741d8a/update_gio_module_cache-lib32: 15:12:09
iceaway/home/pelle/development/var-fsl-yocto/build_kodkod/tmp/work/imx8qxpb0_var_som-poky-linux/tmlinux-image/1.0-r0/intercept_scripts-bd1c31820bf736a004f4ebe71461d6fa3ae23f7d97783c8f28a606e086741d8a/update_gio_module_cache-lib32: lib32-qemuwrapper: not found"12:10
iceawaySince it is working fine with the 64-bit build, I'm a bit confused.12:10
LetoThe2ndiceaway: that might be a dependency problem12:10
iceawayI have bee scratching my head all day about what the root cause of this could be. I'm not sure if this is a dependency for glib-2.0, or for my image.12:13
iceawayI can build "lib32-qemuwrapper-cross" by adding that to the DEPENDS of my image, but the glib-2 recipe seem to look for "lib32-qemuwrapper", which it cannot find.12:14
LetoThe2ndi'd guess it needs lb32-qemuwrapper-native - but its really all guess work.12:14
LetoThe2ndthose are pathes seldom travelled here.12:15
iceawayAlright, thanks LetoThe2nd. I'll report back if I come up with anything useful that might help others.12:21
LetoThe2ndiceaway: yes, please do so. itmight also be useful to put a message on the ML just outlining your situation12:22
*** amitk_ <amitk_!~amit@unaffiliated/amitk> has quit IRC12:34
*** shan1 <shan1!> has joined #yocto12:35
*** Konsgnxx <Konsgnxx!> has joined #yocto12:36
*** amitk <amitk!~amit@unaffiliated/amitk> has joined #yocto12:36
*** shan1 <shan1!> has quit IRC12:38
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:300a:f3c9:b99d:b59> has quit IRC12:55
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:300a:f3c9:b99d:b59> has joined #yocto12:55
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto13:14
*** B0ned1ger <B0ned1ger!> has quit IRC13:36
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto13:36
JPEWiceaway: IIRC the GIO stuff executes some code in QEMU as part of the build. My guess is that there is something wrong with the QEMU part of it13:37
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has quit IRC13:51
*** sakoman <sakoman!> has joined #yocto13:55
*** rcw <rcw!~rcwoolley@> has joined #yocto14:05
*** stephano <stephano!> has joined #yocto14:15
*** B0ned1ger2 <B0ned1ger2!> has quit IRC14:20
*** B0ned1ger <B0ned1ger!> has joined #yocto14:20
* hmw1 sent a long message: < >14:21
*** elGamal <elGamal!~elg@> has joined #yocto14:22
*** kpo_ <kpo_!> has quit IRC14:28
*** kpo_ <kpo_!> has joined #yocto14:28
*** oberstet <oberstet!~oberstet@> has quit IRC14:38
*** oberstet <oberstet!~oberstet@> has joined #yocto14:39
LetoThe2ndqschulz: there's more chances to be properly nikhilized today!15:06
*** goliath <goliath!> has joined #yocto15:08
*** leon-anavi <leon-anavi!~Leon@> has quit IRC15:08
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto15:08
*** davisr <davisr!davisr@gateway/vpn/protonvpn/davisr> has quit IRC15:10
*** ericch <ericch!> has joined #yocto15:13
*** bsmerbeck <bsmerbeck!> has joined #yocto15:16
bsmerbeckI know it's a beaten horse, but any quick tips on potentially speeding up image creation? Making minor changes to my recipes, but do_rootfs and do_image are always a "set it and forget it" stage of my build process.15:17
LetoThe2ndbsmerbeck: just don't create images :)15:21
LetoThe2ndbsmerbeck: nach, seriously: have suffient fast storage.15:21
*** vmeson <vmeson!> has quit IRC15:24
bsmerbeckLetoThe2nd: Figured that might be the answer. I'm running on a PowerEdge R730, 6Gbps SATAs, gave the VM about 20 gigs of ram, and it has a xeon e515:26
LetoThe2ndso you're on a linux thats virtualized onto a windows box, or such?15:27
bsmerbeckYeah, yocto/bitbake are running on a centos VM I hosted on a newer server15:28
*** armpit <armpit!~armpit@2601:202:4180:a5c0:c937:fb7f:b6e0:3eef> has quit IRC15:28
LetoThe2ndthen get rid of the vm, thats the main bummer.15:28
bsmerbeckI was thinking that, given I've gone through the rounds of optimizing the parallel jobs and what not15:29
bsmerbeckMaybe i'll compare my current machine's spec to this server and see how big a difference there is now15:29
LetoThe2ndgetting out of a vm is always step #1 of n, not step #n of n15:30
bsmerbeckI've found work constraints tend to mix up the order of those steps, haha15:31
bsmerbeckIn any case, a project for another day. Thanks for the input!15:31
LetoThe2ndi guess for the wasted time in waiting for the builds you could have totally rearranged your constraints already :) but yeah, have fun115:32
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has left #yocto15:34
*** armpit <armpit!~armpit@2601:202:4180:a5c0:d28:9e3e:76f0:aaf1> has joined #yocto15:41
*** jobroe <jobroe!> has quit IRC15:41
*** AndersD <AndersD!> has quit IRC15:49
*** kaspter <kaspter!~Instantbi@> has quit IRC15:55
*** camus1 <camus1!~Instantbi@> has joined #yocto15:55
*** camus1 is now known as kaspter15:58
*** tproberts <tproberts!> has joined #yocto15:58
SaurJPEW: I was looking at whisk some time ago, and I know there was some example repository where you used it (I think it had doom for rpi or something like that), but now I can't find it again. Do you know where I can find it?15:58
*** amitk_ <amitk_!~amit@unaffiliated/amitk> has joined #yocto15:59
*** amitk <amitk!~amit@unaffiliated/amitk> has quit IRC16:02
*** tproberts is now known as TPRoberts16:07
moto-timozeddii: I'll try to kick the tires on k3s today... assuming you are still seeing issues ?16:10
zeddiiyep. I've broken it down to a simple first step now. Get the main node (server) to stop having the 4 required containers go into a crashbackoffloop16:11
*** amitk_ <amitk_!~amit@unaffiliated/amitk> has quit IRC16:11
zeddiiand b) how have we misconfigured it such that kubectl get logs doesn't work.16:11
zeddiimake sure to use my k3s-wip branch though, that has everything you need to get to where I am.16:12
*** amitk <amitk!~amit@unaffiliated/amitk> has joined #yocto16:12
moto-timozeddii: I've seen a number of ways to get crashbackoffloop, so maybe one of my tricks will help... plus I've stumbled on some random incantations that achieve some logs16:14
SaurJPEW: Thank you. :)16:14
moto-timozeddii: BTW, I LOVE the cni new bbclass idea16:14
moto-timozeddii: since I am now exclusively using cri-o and cni bridge networking in my current sandbox16:15
zeddiiit still needs work, but I wanted the concept out. Looking at k8s and k3s and others, it was clear they were all just thrashing stuff into the directory blindly.16:15
moto-timozeddii: like everything else in cloud native world16:16
zeddiiyup. flail with your slight variant!16:16
moto-timozeddii: we'll need to not assume docker in packagegroup-k8s-host, but you already knew that16:17
zeddiiyep, it isn't required. I was actually just breaking that out more yesterday. while testing.16:18
*** sstiller <sstiller!> has quit IRC16:19
zeddiisome of the strings I was tugging on yesterday involved 'docker ps' and they failed, but at the same time, I realized the granularity needed to be better.16:19
*** bsmerbeck <bsmerbeck!> has quit IRC16:19
JPEWSaur: FYI, if you poke around in that repo; it builds, but it doesn't actually do the advertised behavior of running Doom on the devices.... WIP :)16:26
*** vmeson <vmeson!> has joined #yocto16:36
LetoThe2ndJPEW: mark jonas has that already...
SaurJPEW: No problem. I was looking for a real example using whisk. ;)16:38
LetoThe2ndJPEW: he asked me about some small hint concerning dependencies during ELC-ALMOST-EU, and i still haven't responded... shame on me.16:39
*** eduardas <eduardas!~eduardas@> has quit IRC16:42
JPEWLetoThe2nd: That's cool. I'm more interested in using doom as a cool end demo for other interestings things.... mainly, I want to demo a CI setup with kubernetes+tekton that then runs tests on my devices16:45
JPEWAs an interesting demo, the "test" can be running doom :)16:45
*** frsc <frsc!> has quit IRC16:54
moto-timoarmpit: I updated 12850... or was I supposed to go to the wiki?16:55
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto16:56
*** vineela <vineela!~vtummala@> has joined #yocto16:59
zeddiion an unrelated note, the netflix documentary thing on video games, had an interesting segment on doom and Romero/Carmack. so watch that first :D16:59
moto-timozeddii: I'm working on recipes for cri-tools (crictl), tektoncd-cli (tkn) and k9s, but you know how fun Go is17:03
zeddiiyes, enjoy jiggling the components into the right place so go admits they are what is needed.17:04
zeddiiI wasn't getting to any of those any time soon, so I'll plug away on refreshing k8s (and others) and fighting with k3s.17:05
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has joined #yocto17:06
*** habing <habing!~habing@2001:4bb8:188:5816:b486:552f:43c9:2> has quit IRC17:07
*** vineela <vineela!~vtummala@> has quit IRC17:24
moto-timozeddii: building k3s now ;)17:25
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC17:25
zeddiiI primarily think it is something missing in my packagegroups, but I can't get the right log to see what it is.17:26
zeddiiOn an older k3s version, I had them start once last week, but haven't repeated that success yet.17:26
*** davisr <davisr!davisr@gateway/vpn/protonvpn/davisr> has joined #yocto17:31
*** fl0v0 <fl0v0!~fvo@> has quit IRC17:38
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto17:40
moto-timozeddii: I think I noticed some changes in behavior from k8s 1.18 to 1.19... hopefully something will jog my memory17:43
armpitmoto-timo, defect is fine. I will add it to wiki once the new section is written17:46
*** gsalazar <gsalazar!955a6fad@gateway/web/cgi-irc/> has quit IRC17:53
*** dmoseley <dmoseley!~dmoseley@> has quit IRC17:54
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto17:58
*** mckoan is now known as mckoan|away17:59
*** vineela <vineela!~vtummala@> has joined #yocto17:59
*** geheimnis` <geheimnis`!~geheimnis@> has quit IRC18:00
*** dreyna <dreyna!> has joined #yocto18:03
*** dreyna <dreyna!> has joined #yocto18:04
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC18:06
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has joined #yocto18:07
*** geheimnis` <geheimnis`!~geheimnis@> has joined #yocto18:10
*** Yumasi <Yumasi!> has quit IRC18:16
*** pharaon2502 <pharaon2502!> has quit IRC18:22
*** amitk <amitk!~amit@unaffiliated/amitk> has quit IRC18:45
*** kiwi_29 <kiwi_29!> has joined #yocto18:49
*** kiwi_29 <kiwi_29!> has quit IRC18:50
*** kiwi_29 <kiwi_29!> has joined #yocto18:51
*** kiwi_29 <kiwi_29!> has quit IRC18:55
moto-timozeddii: dear lazyweb, nothing provides kernel-module-ip-set needed by ipset-6.38-r0.qemux86_64 ??18:55
zeddiithere's a fragment that turns it on.18:56
zeddiibut if you know you have it on (i.e. built-in), you can hack that recipe to drop the rdepends.18:57
zeddiiI've kept it around as a canary in the mineshaft18:57
*** kiwi_29 <kiwi_29!> has joined #yocto19:00
moto-timozeddii: thank you. I'm not exactly paying attention because KubeCon+CloudNativeCon...19:04
qschulzLetoThe2nd: no comment, or please keep private :)19:07
*** zyga-mbp <zyga-mbp!~zyga@unaffiliated/zyga> has quit IRC19:07
bluelightninganyone seen pseudo abort happening when running bitbake -c populate_sdk ?19:14
bluelightning(with master of early nov... there don't seem to have been any fixes since then relating to it)19:15
*** aidanh_ <aidanh_!~aidanh@unaffiliated/aidanh> has joined #yocto19:19
*** aidanh <aidanh!~aidanh@unaffiliated/aidanh> has quit IRC19:19
*** aidanh_ is now known as aidanh19:19
*** B0ned1ger <B0ned1ger!> has quit IRC19:20
*** B0ned1ger <B0ned1ger!> has joined #yocto19:20
frayI've not seen any recent pseudo fixes.. but RP would know for sure19:28
*** vineela <vineela!~vtummala@> has quit IRC19:28
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC19:28
*** leon-anavi <leon-anavi!~Leon@> has quit IRC19:34
*** hpsy1 <hpsy1!~hpsy@> has joined #yocto19:35
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto19:35
*** hpsy <hpsy!~hpsy@> has quit IRC19:35
*** hpsy1 <hpsy1!~hpsy@> has quit IRC19:36
LetoThe2ndqschulz: :)19:56
moto-timozeddii: ha, crictl is already being built... I missed that20:02
moto-timozeddii: do I want packagegroup-k3s-host and packagegroup-k3s-node on the single node?20:03
moto-timowhen did I get so lazy20:11
*** meow` <meow`!~sbourdeli@> has joined #yocto20:29
*** vineela <vineela!~vtummala@> has joined #yocto20:32
*** jonasbits <jonasbits!~quassel@2001:2002:4e48:1aca:908e:1969:c028:2e1d> has quit IRC20:34
*** jonasbits <jonasbits!~quassel@2001:2002:4e48:1aca:908e:1969:c028:2e1d> has joined #yocto20:34
zeddiisorry, was in a meeting.20:42
zeddiimoto-timo: they were designed to both be present to do a single node setup. which I haven't gotten working yet.20:43
zeddiiI fell back to just trying to get the bloody controller to be more than "ready" .. have actual working containers.20:43
*** dv|2 <dv|2!~dv@> has joined #yocto20:45
dv|2Building NodeJS for x86_64 SDK. got "fatal error: unicode/uchar.h: No such file or directory". Do I have to install ICU on my host system or add build requirement to NodeJS recipe?20:47
*** vineela <vineela!~vtummala@> has quit IRC20:50
*** megabread <megabread!~megabread@2a01:4b00:e031:2600:300a:f3c9:b99d:b59> has quit IRC21:12
*** likewise <likewise!> has quit IRC21:13
*** creich <creich!> has quit IRC21:14
rabbit9911Any support for sstate_mirror over https/sftp/ssh with auth?21:16
neverpanicif ssh is an option for you, just do the auth using that and forward a port over it?21:22
*** vineela <vineela!~vtummala@> has joined #yocto21:22
moto-timoput an nginx reverse proxy in front of it?21:22
*** zyga <zyga!~zyga@unaffiliated/zyga> has joined #yocto21:22
rabbit9911The reverse proxy idea came up. That is on the docket. The port forward over ssh I have not thought of.. hmm..21:25
*** TPRoberts <TPRoberts!> has quit IRC21:38
*** DanmerZ <DanmerZ!~op@> has quit IRC21:51
*** dreyna <dreyna!> has quit IRC21:52
*** dreyna <dreyna!> has joined #yocto21:58
khemdv|2:  seems so it perhaps needs some patching to work with with icu 68 if you are on master22:00
dv|2I am on dumfell22:00
*** Konsgnxx <Konsgnxx!> has quit IRC22:02
*** kiwi_29 <kiwi_29!> has quit IRC22:03
*** pohly <pohly!> has quit IRC22:08
*** kiwi_29 <kiwi_29!> has joined #yocto22:27
*** LetoThe2nd <LetoThe2nd!uid453638@gateway/web/> has quit IRC22:31
*** rabbit9911 <rabbit9911!> has quit IRC22:48
*** beneth <beneth!> has left #yocto23:01
*** zyga <zyga!~zyga@unaffiliated/zyga> has quit IRC23:01
RPbluelightning: we've fixed the known issues, its possible there are others23:05
moto-timopatches welcome :)23:14
moto-timozeddii: so far, it seems like cni networking isn't live, but I have not been too deep yet23:15
moto-timozeddii: I had to get it "ready" first (yeah, use the correct virtual/foo)23:16
*** B0ned1ger <B0ned1ger!> has quit IRC23:20
*** B0ned1ger2 <B0ned1ger2!> has joined #yocto23:20
*** ssajal <ssajal!> has quit IRC23:24
*** mprokos <mprokos!> has joined #yocto23:42
*** Ox861726f6c64 <Ox861726f6c64!~Ox861726f@gateway/tor-sasl/ox861726f6c64> has quit IRC23:46
*** kiwi_29 <kiwi_29!> has quit IRC23:57

Generated by 2.17.2 by Marius Gedminas - find it at!