Monday, 2021-09-27

*** bluelightning <bluelightning!~paul@2406:e003:1528:db01:ec70:5247:35b6:390d> has joined #yocto00:01
*** jwillikers <jwillikers!> has quit IRC (Remote host closed the connection)00:59
*** Guest24 <Guest24!~Guest24@2601:647:5100:4240:d4bb:e96e:d807:6ef8> has joined #yocto02:01
*** Guest24 <Guest24!~Guest24@2601:647:5100:4240:d4bb:e96e:d807:6ef8> has quit IRC (Client Quit)02:02
*** arlen <arlen!> has joined #yocto03:29
*** wooosaii <wooosaii!> has joined #yocto04:01
*** wooosaiii <wooosaiii!> has quit IRC (Ping timeout: 252 seconds)04:04
*** davidinux <davidinux!~davidinux@> has joined #yocto04:23
*** pgowda <pgowda!> has joined #yocto04:37
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 240 seconds)04:49
*** kanavin_ <kanavin_!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has joined #yocto05:08
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has quit IRC (Read error: Connection reset by peer)05:08
*** rfuentess <rfuentess!> has joined #yocto05:38
*** zibri <zibri!> has quit IRC (*.net *.split)05:48
*** mcfrisk <mcfrisk!> has quit IRC (*.net *.split)05:48
*** ykrons_ <ykrons_!~guillaume@> has quit IRC (*.net *.split)05:48
*** woky <woky!> has quit IRC (*.net *.split)05:48
*** georgem <georgem!> has quit IRC (*.net *.split)05:48
*** zibri <zibri!> has joined #yocto05:48
*** mcfrisk <mcfrisk!> has joined #yocto05:48
*** georgem <georgem!> has joined #yocto05:48
*** ykrons_ <ykrons_!~guillaume@> has joined #yocto05:48
*** woky <woky!> has joined #yocto05:49
*** tgamblin <tgamblin!~tgamblin@2607:fea8:c29d:d7c0::81de> has quit IRC (*.net *.split)05:54
*** OutBackDingo <OutBackDingo!~quassel@> has quit IRC (*.net *.split)05:54
*** ldts <ldts!> has quit IRC (*.net *.split)05:54
*** nsbdfl <nsbdfl!nsfbdl@user/nsbdfl> has quit IRC (*.net *.split)05:54
*** Shaun <Shaun!~shaun@user/shaun> has quit IRC (*.net *.split)05:54
*** thekappe <thekappe!~user@> has quit IRC (*.net *.split)05:54
*** madisox <madisox!> has quit IRC (*.net *.split)05:54
*** Tartarus <Tartarus!> has quit IRC (*.net *.split)05:54
*** frosteyes <frosteyes!~frosteyes@> has quit IRC (*.net *.split)05:54
*** override_ <override_!> has quit IRC (*.net *.split)05:54
*** dv_ <dv_!> has quit IRC (*.net *.split)05:54
*** jpnurmi <jpnurmi!jpnurmi@user/jpnurmi> has quit IRC (*.net *.split)05:54
*** ldts <ldts!> has joined #yocto05:54
*** Shaun <Shaun!> has joined #yocto05:54
*** OutBackDingo <OutBackDingo!~quassel@> has joined #yocto05:54
*** thekappe <thekappe!~user@> has joined #yocto05:55
*** madisox <madisox!> has joined #yocto05:55
*** dv_ <dv_!> has joined #yocto05:55
*** frosteyes <frosteyes!~frosteyes@> has joined #yocto05:55
*** Tartarus <Tartarus!> has joined #yocto05:55
*** tgamblin <tgamblin!~tgamblin@2607:fea8:c29d:d7c0::81de> has joined #yocto05:55
*** jpnurmi <jpnurmi!jpnurmi@user/jpnurmi> has joined #yocto05:55
*** Sion <Sion!> has joined #yocto05:56
*** override_ <override_!> has joined #yocto05:59
*** ThomasD13 <ThomasD13!> has joined #yocto06:09
*** goliath <goliath!~goliath@user/goliath> has joined #yocto06:10
*** saYco[m] <saYco[m]!~saycomatr@2001:470:69fc:105::1:2a0> has joined #yocto06:18
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto06:22
JosefHolzmayrTheyo dudX06:33
manuel_JosefHolzmayrThe y006:34
*** manuel_ <manuel_!~manuel198@2a02:1748:dd5c:f290:894b:df66:de34:69> has quit IRC (Quit: Leaving)06:35
*** mckoan|away is now known as mckoan06:42
mckoangood morning06:42
SionGood morning.06:44
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto06:44
SionHello everyone, I'm fairly new with Yocto (love it atm). I do have a question regarding the tested distribution list, I'm currently using Debian Bullseye in combination with the latest hardknott and I don't see any immidiate issues but is the Yocto team currently testing Debian 11 as well?06:47
JosefHolzmayrTheSion: i have no definitive statement on that, but i'm pretty sure it will get into the autobuilder testing in some not-too-distant future.06:48
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Remote host closed the connection)06:49
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto06:50
SionOk, thanks for the quick reply.06:50
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)06:52
*** fleg <fleg!64bf4386e9@user/fleg> has joined #yocto06:54
*** xmn <xmn!> has quit IRC (Ping timeout: 265 seconds)06:56
*** zpfvo <zpfvo!~fvo@> has joined #yocto06:56
*** oobitots <oobitots!> has joined #yocto07:01
*** frieder <frieder!> has joined #yocto07:10
*** fbre <fbre!~fbre@> has joined #yocto07:22
RPSion: it isn't officially tested, no. It should work ok though and we likely will add testing for it soon07:27
*** tnovotny <tnovotny!> has joined #yocto07:44
*** goliath <goliath!~goliath@user/goliath> has joined #yocto07:44
JosefHolzmayrThe(stupid) question. does the adduser mechanism require something specific in the recipe?07:50
JosefHolzmayrTheerm, image?07:50
JosefHolzmayrThespecifically, does it need useradd/groupadd to be present?07:50
*** zeddii <zeddii!> has quit IRC (Ping timeout: 252 seconds)08:03
*** zeddii <zeddii!> has joined #yocto08:04
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)08:11
wCPOIs bumping allowed on mailing list? or should I just wait and hope <someone> merge it: ? :)08:12
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 265 seconds)08:19
JosefHolzmayrThewCPO: i guess a gentle one-time bump is not problematic.08:19
*** pabigot <pabigot!> has quit IRC (Ping timeout: 252 seconds)08:21
*** pabigot <pabigot!> has joined #yocto08:22
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:24
fbreJosefHolzmayrThe: I just have this in my machine .conf file:08:25
fbreINHERIT += "extrausers"08:25
fbreEXTRA_USERS_PARAMS = "usermod -P MyRootPassword root; useradd -P MyNewUserAccountPassword -G foo useraccount42"08:25
fbre(replace with your account names and passwords)08:25
JosefHolzmayrThefbre: thanks... but i guess in my case the problem is not the metadata per se, but the image generation.08:26
*** florian <florian!> has joined #yocto08:27
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 265 seconds)08:28
*** camus <camus!~Instantbi@> has joined #yocto08:28
fbreJosefHolzmayrThe: I did not install specific useradd/groupadd stuff for the account which runs the image generation08:29
JosefHolzmayrThefbre: no, but i guess that your image brings those and therefore they at least end up in the sysroot, right?08:30
fbreJosefHolzmayrThe: It's not an account which needs root rights08:31
JosefHolzmayrThefbre: no, thats not what i'm talking about.08:31
JosefHolzmayrTheanyways, i'll give your approach a spin and check if there are different effects.08:32
JosefHolzmayrThenope, perfectly the same.08:35
fbreJosefHolzmayrThe: Which error does happen?08:35
JosefHolzmayrThefbre: i con't copy it out at the moment, but upon inspection there is no useradd/usermod in the -native sysroot. hence, it fails. so i guess my real question is: what form of dependency do i need for that tool to show up.08:38
fbreJosefHolzmayrThe: I don't know what you mean with "in the -native sysroot"...08:39
JosefHolzmayrThefbre: your EXTRA_USERS_PARAMS needs the usermod command to be available. unless specific actions are taken, my understanding is that it will be taken from the -native sysroot for the recipe in question (in this case, the image)08:41
JosefHolzmayrThefbre: and if the command is not there, it cannot be executed.08:41
fbreWhat is a "sysroot" and what is its property "-native"08:43
fbreSorry, can't help further08:43
*** lucaceresoli <lucaceresoli!> has joined #yocto08:44
qschulzJosefHolzmayrThe: ?08:44
JosefHolzmayrThefbre: sysroots are the environments that are created per recipe, basically from the dependencies. and the -native incarnation is the one thats meant to run during the build. no problem, i know its a complicated problem.08:45
*** mihai <mihai!~mihai@user/mihai> has quit IRC (Quit: Leaving)08:45
JosefHolzmayrTheqschulz: looks like shadow should provide it.08:45
fbreWhat is "shadow" in this case?08:47
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto08:48
fbreah OK, likely I use another package which draws "shadow" in then08:49
JosefHolzmayrThei wonder why this doesn't kick in:
qschulzJosefHolzmayrThe: extrausers IMAGE_CLASSES does not include that bbclass I think?08:52
RPJosefHolzmayrThe: You'd not expect it to show up in the native sysroot, you'd expect it to be in the target one?08:52
JosefHolzmayrTheRP: -native one.08:52
JosefHolzmayrTheall in all, i'm poking that recipe:
JosefHolzmayrTheand as it inherits useradd, i'd naively expect it to pull in all things needed for... "adding users" :)08:54
RPJosefHolzmayrThe: I think I'm misreading the above, I thought you mean the user/group wasn't in the native sysroot. You're right that the tools should be added08:54
JosefHolzmayrTheRP: exactly, but it seems that this is not the case.08:55
RPJosefHolzmayrThe: for your demo recipe, you could put a chown call in the do_install08:55
JosefHolzmayrTheRP: to get rid of the dummy?08:55
qschulzJosefHolzmayrThe: also, FILES:${PN} :)08:56
RPJosefHolzmayrThe: no, just that you're not using the user/group you're creating anywhere08:56
JosefHolzmayrTheRP: lemme try.08:56
RPJosefHolzmayrThe: it won't change anything much but it would fail if there was an issue08:57
JosefHolzmayrTheRP: yeah thought so.08:57
JosefHolzmayrThewhy doesn't FILES_${PN} err out on parsing?08:59
RPJosefHolzmayrThe: it can't know that is an override. It only errors on "_append" which it knows is bad08:59
JosefHolzmayrThebut DEPENDing on neither shadow-native nor shadow-sysroot seem to give me the commands09:04
wCPOWhy would a recipe has a -native dependency? Ex:
JosefHolzmayrThewCPO: whenever you want to run something during build time.09:19
wCPOJosefHolzmayrThe: Make sense, but why does it have libtpm-native then?09:20
JosefHolzmayrThewCPO: no idea, look at the recipe to see what it needs. it might also be something that its build process relies on inside.09:20
*** camus1 <camus1!~Instantbi@> has joined #yocto09:20
wCPOJosefHolzmayrThe: I will and I'm currently trying to understand why it is there, thanks for explanation :)09:21
JosefHolzmayrThehave fun09:21
wCPO"fun" :)09:22
qschulzremove it and you shall see where it fails :)09:22
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 265 seconds)09:22
*** camus1 is now known as camus09:22
wCPOqschulz: it doesn't fail, then why I'm confused09:23
wCPObut I also updated the recipe to 0.6.1, maybe I should try the current version first09:23
*** davidinux <davidinux!> has joined #yocto09:31
RPwCPO: sometimes these things persist when they're no longer needed09:34
wCPORP: yep, I'm gonna CC the guy who updated it in the past when I submit the patch, maybe he know09:35
sveinseIf I specify "bitbake -k packagegroup-something package-index" will a) package-index be run even if packagegroup-something fails and b) will it execute last?09:37
rburtonyes, no09:38
sveinseok, thanks09:38
rburton(they'll execute in parallel)09:38
sveinsepackage-index on its own invocation step then, got it09:38
rburtonyou can try and see if you can make it work properly09:39
rburtonoh no, not that09:39
rburtonhuh where is my class09:39
sveinseYeah, the use case is that we're building to a packagefeed, but occational not every package compiles successfully, so in order to have a valid package feed, I'd like to update the repo I've got09:40
sveinseNormally bitbake packagegroup-x does this if and only if it completely succeeds09:40
rburtoni had a patch that would run package-index in the closing stages of the build so you could always have an up to date feed, but i appear to have lost it09:42
RPrburton: you've lost it? :)09:43
rburtoni lost it long ago09:43
RPrburton: I suspect we all did...09:44
*** thekappe <thekappe!~user@> has quit IRC (Quit: WeeChat 1.9.1)09:46
RPMakefile:DIST_DIR := $(shell mktemp -d /tmp/glew.XXXXXX)/$(DIST_NAME) seems a little antisocial09:47
JosefHolzmayrThe"of all the things that i have lost, i miss my mind the most"09:47
RPand we never actually use that09:47
* qschulz laughs at the timing of RP and JosefHolzmayrThe messages :D09:51
JosefHolzmayrTheqschulz: me too.09:51
JosefHolzmayrThegreat minds think alike, they say.09:51
sveinseIs there a yocto/bb-way of disabling a systemd service in a ROOTFS_POSTPROCESS step? For those services that has been installed with systemd.bbclass and have a system-preset/98-*.preset entry09:55
*** thekappe <thekappe!~user@> has joined #yocto09:56
sveinseI'm not sure how the preset logic actually work. Something in (yocto) first time startup activates the presets and thus enables/disables these services?09:58
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)09:58
qschulzto be done in the recipe providing the systemd service09:59
sveinseqschulz: Yes. And say the bb enables a service via these mechanisms, but then the image wants the service disabled. Whats the right way of doing that?09:59
qschulzI assume proper way would be a bbappend for that bb, or a distro. For the hackish way, looking at how it is done by the systemd class and call the same things from within the rootfs might do it10:01
sveinseIs .bb the right spot? I mean the recipe/package might be correct, but multiple images might want different enable/disables. Then I'd need a separate bbappend for each of those image variants, right?10:02
qschulzthat's policy and policy is what the distro is responsible for10:04
qschulzotherwise you can always try to run `systemctl disable <service name>` in your ROOTFS_POSTPROCESS_CMD but it does not feel super right10:07
jaskij[m]Does anyone have a link or something with arguments I could use to allow my boss to open source my recipes?10:09
RPjaskij[m]: I'm not sure we have anything written into the docs. michaelo, do you know anything?10:10
RPjaskij[m]: I did write is which different but related10:10
rburtonjaskij[m]: if they're recipes for relatively common software then the best argument is that other people will test/maintain. if you get a recipe into meta-oe for example then other will also help keep it up to date10:18
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto10:23
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 245 seconds)10:25
*** camus <camus!~Instantbi@> has joined #yocto10:25
jaskij[m]<rburton> "jaskij: if they're recipes for..." <- That's the common one, although I'm not sure how effective this would be in my case. Something to think on.10:25
jaskij[m]This is probably the first OSS project I honestly want to contribute to. Gotta take a look at the tracker when I've got some time.10:28
*** agners <agners!~ags@2a02:169:3df5:10:5c1d:e28a:f461:57d5> has quit IRC (Ping timeout: 252 seconds)10:38
*** wwilly <wwilly!> has quit IRC (Ping timeout: 252 seconds)10:47
*** agners <agners!> has joined #yocto10:54
*** etam[m] <etam[m]!~etam@user/etam> has joined #yocto10:55
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto10:57
*** manuel1985 <manuel1985!~manuel198@> has joined #yocto11:00
manuel1985Did you guys manage to run qemux86-64 with graphics acceleration? I'm building my wayland-based project for raspi4 and qemu. On raspi it runs smooth, but on qemu it's a disaster.11:02
manuel1985Doing runqemu with kvm, but guess that doesn't help anything w.r.t. graphics.11:02
*** etam <etam!~etam@user/etam> has joined #yocto11:03
*** etam <etam!~etam@user/etam> has quit IRC (Quit: Konversation terminated!)11:08
*** xmn <xmn!> has joined #yocto11:08
*** agners <agners!> has quit IRC (Ping timeout: 252 seconds)11:11
*** agners <agners!~ags@2a02:169:3df5:10:5c1d:e28a:f461:57d5> has joined #yocto11:13
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 265 seconds)11:15
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto11:15
sveinseqschulz: I see. Under the yocto paradigm, a distro handles policy, that all good. It would then imply that you'd need multiple distros to make different policies, or startup policies, like in this case, wouldn't it? Doesn't that make it, uhm, a big machine for an image variant? Or is that how yocto distros are?11:30
sveinseNot arguing, only trying to understand11:31
*** GillesM <GillesM!> has joined #yocto11:33
*** GillesM <GillesM!> has quit IRC (Quit: Leaving)11:46
*** xmn <xmn!> has quit IRC (Ping timeout: 265 seconds)11:53
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)11:54
*** camus1 <camus1!~Instantbi@> has joined #yocto11:57
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 245 seconds)11:58
*** camus1 is now known as camus11:58
jaskij[m]I'm trying to wrap my head around variable flags, as used commonly with `PACKAGECONFIG`, for example in
jaskij[m]if I'm looking right, it somehow goes through `PACKAGECONFIG` variable flags and uses the values of the flags that are listed in the base variable?12:12
jaskij[m]is this normal, or is this something that comes from one of the classes inherited?12:13
*** angolini <angolini!> has joined #yocto12:13
jaskij[m]uh, guess this shows how I only read the manual in small parts12:18
*** tgamblin <tgamblin!~tgamblin@2607:fea8:c29d:d7c0::81de> has quit IRC (Quit: Leaving)12:20
*** tgamblin <tgamblin!~tgamblin@2607:fea8:c29d:d7c0::81de> has joined #yocto12:20
qschulzthis is the standard mechanism12:25
jaskij[m]It is, but I went reading about varflags instead of PACKAGECONFIG, and it threw me for a loop.12:27
Saurjaskij[m]: Well, varflags is a standard mechanism. How they are used is up to the classes, however. E.g., support for PACKAGECONFIG is implemented in meta/classes/base.bbclass.12:30
jaskij[m]yeah, I found that12:31
jaskij[m]just that I was reading the BitBake manual, not looking specifically at PACKAGECONFIG, is all12:31
*** wwilly <wwilly!> has joined #yocto12:36
*** wwilly_ <wwilly_!> has joined #yocto12:37
*** wwilly <wwilly!> has quit IRC (Ping timeout: 252 seconds)12:40
*** wwilly_ is now known as wwilly12:48
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:2a3:1764:1ba:5e89> has joined #yocto12:49
*** yates <yates!> has quit IRC (Remote host closed the connection)12:53
sveinseWhile on systemd: Has anyone made an overview of the most common systemd targets for use in yocto? Or is our systemd usage so vanilla systemd that its really a systemd default question?13:03
sveinsesystemd targets = system policy = distro = so in poky I suppose13:05
*** rfuentess <rfuentess!> has quit IRC (Ping timeout: 252 seconds)13:11
perdmannHi i have a big problem what i dont understand:
*** yates <yates!> has joined #yocto13:20
perdmannbb.process.NotFoundError: Execution of 'git rev-parse --abbrev-ref HEAD' failed: command not found13:20
perdmannBut git is installed13:20
yatesis there a verbatim log of a bitbake build stashed somewhere, perhaps in build/tmp? i'm not referring to the individual build/tmp/.../temp logs13:21
yatesthere are some qa warnings i received on a previous build that i'm trying to review and i've since rebooted so the terminal containing them is gone13:22
yatesi also occasionally want to see the last value N that was reported as "N tasks of M completed" in an unsuccessful build, so i know how far along it got. is that data stored in a log somwhere?13:24
*** rfuentess <rfuentess!> has joined #yocto13:27
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Quit: Client closed)13:30
yatesperdmann: perhaps something in the build is hosing your path13:32
yateswhat, you never lived in San Jose, CA circa the 80s? :)13:33
perdmannHow can i find out of it ruins something?13:34
*** arr <arr!~ar@> has joined #yocto13:35
perdmannyates: i was born 86 :-)13:35
yatesperdmann: one way i can think of is to cd to the appropriate .../temp directory, find out the run.do_whatever is being run, and hack it to spit out the path13:36
yates(if it's a bash script. python run.do_xyz scripts are not so easy)13:36
perdmannyates: haha, feels good that somebody says this to me ;-)13:38
yatesenjoy it while it lasts... ;)13:38
yatesps: subtract 29 from your birth year..13:38
perdmannsenior developer :-D13:39
*** agners <agners!~ags@2a02:169:3df5:10:5c1d:e28a:f461:57d5> has quit IRC (Quit: WeeChat 3.2.1)13:40
*** agners <agners!~ags@2a02:169:3df5:10:5c1d:e28a:f461:57d5> has joined #yocto13:40
perdmannyates: i dont have any run. files...13:41
yatesi missed your entire message. what is the entire message?13:41
yatesor context?13:41
yatesperdmann: is this the first time you've tried to build a yocto project on that system?13:43
yateshave you successfully built a project on that system previously?13:44
perdmannyates: no... I just built one yesterday, and it worked with qemu13:44
perdmannBut now i try to wrap that into an integration... And now it fails13:45
rburton'bb.process.NotFoundError: Execution of 'git rev-parse --abbrev-ref HEAD' failed: command not found'13:45
rburtonyou don't have git inside your container13:45
perdmannrburton: how can i add this? I built on a native machine...13:46
rburtonwell, what's different between this time and last?  not git suggest you're doing a build inside a really minimal container? if so, add more stuff to the container.13:47
perdmanni dont use any container technique, iam running on the native machine. The same machine i have built a "Quick yocto built" yesterday13:50
rburtonwell it says you don't have git installed13:50
rburtonso thats very much your problem to resolve13:50
perdmanngit 2.33.0 is installed on that machine13:51
rburtondelete tmp/ and try again13:51
rburtonpossibly, the hosttools links are all broken13:51
perdmannrburton: i'll try13:52
yatesdid matchbox-sato move from this location?
yatesthe last commit there seems to be 2016!13:53
perdmannrburton: maybe the remote SSTATE CACHES break that built?13:53
perdmannrburton: i expected them to work...13:53
rburtonyates: its just a theme, doesn't change much13:53
rburtonperdmann: remote sstate work for me and no, this is before sstate happens13:53
perdmannrburton: its a slow machine ;-)13:56
perdmannrburton: i got the same error again ...13:57
rburtonwell, you'll have to figure out why it thinks git doesn't exist.  it will be trying to run tmp/hosttools/git13:57
perdmannrburton: ok, its linking to the correct git... Thats not goot i guess?13:59
perdmannrburton: ok ... i initialize with "source sources/poky/oe-init-build-env sources/misc/build"14:02
*** mrpelotazo <mrpelotazo!> has joined #yocto14:02
rburtonand sources/misc/build/tmp/hosttools/git is a link to the right git binary?14:02
perdmanni have put this source ... into another file and i source this one too... i will try without this14:03
*** sakoman <sakoman!> has joined #yocto14:04
perdmannrburton: no that was not the problem14:09
*** davidinux <davidinux!> has quit IRC (Ping timeout: 245 seconds)14:11
*** davidinux <davidinux!> has joined #yocto14:13
*** mrpelotazo <mrpelotazo!> has quit IRC (Quit: Hasta la vista!)14:14
*** mrpelotazo <mrpelotazo!> has joined #yocto14:16
perdmannrburton: its still not working. The links are ok. Is there something else i can check?14:18
*** davidinux <davidinux!> has quit IRC (Ping timeout: 265 seconds)14:20
*** mrpelotazo <mrpelotazo!> has quit IRC (Quit: Hasta la vista!)14:20
*** davidinux <davidinux!> has joined #yocto14:22
*** arlen_ <arlen_!> has joined #yocto14:23
perdmannERROR: Execution of event handler 'defaultbase_eventhandler' failed14:23
*** arlen <arlen!> has quit IRC (Ping timeout: 252 seconds)14:23
*** oobitots <oobitots!> has quit IRC (Quit: Client closed)14:25
*** ThomasD13 <ThomasD13!> has quit IRC (Ping timeout: 265 seconds)14:26
*** mrpelotazo <mrpelotazo!> has joined #yocto14:31
*** otavio_ <otavio_!> has joined #yocto14:32
*** otavio <otavio!> has quit IRC (Read error: Connection reset by peer)14:32
*** mrpelotazo <mrpelotazo!> has quit IRC (Client Quit)14:33
*** mrpelotazo <mrpelotazo!> has joined #yocto14:33
*** mrpelotazo <mrpelotazo!> has quit IRC (Remote host closed the connection)14:33
*** mrpelotazo <mrpelotazo!> has joined #yocto14:34
*** mrpelotazo <mrpelotazo!> has quit IRC (Client Quit)14:36
sveinseIs there some way to remove (BACKFILL?) a specific package from an image - despite breaking deps?14:36
rburtonwhat do you actually want to do14:39
rburtonconsidering you're breaking depends, so most likely breaking something14:39
sveinseI have an image that is using a kernel that doesn't support lttng-modules and the dependency for lttng-modules is deep in the dependency hierarchy14:40
*** mrpelotazo <mrpelotazo!> has joined #yocto14:41
rburtongo and patch that depends to a recommends14:41
sveinsehmm, actually I can't find where this dep gets pulled in. Grepping for lttng-module doesn't reveal anything immediate obvious.14:46
*** mrpelotazo <mrpelotazo!~mrpelotaz@user/mrpelotazo> has quit IRC (Quit: Hasta la vista!)14:47
*** mrpelotazo <mrpelotazo!~mrpelotaz@user/mrpelotazo> has joined #yocto14:48
*** oobitots <oobitots!> has joined #yocto14:48
*** frieder <frieder!> has quit IRC (Ping timeout: 265 seconds)14:51
qschulzsveinse: bitbake -g <image> and then read the .dot files with your favorite text editor14:53
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Ping timeout: 252 seconds)15:04
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)15:05
perdmannIs it possible that mnt/data/yocto/CTS_Yocto/sources/misc/build/../../../sources/poky/meta/classes/base.bbclass15:06
perdmannis a bad idea_15:06
sveinsethanks qschulz15:06
jaskij[m]sveinse: or get graphviz and draw an svg or something, if you prefer15:08
sveinsejaskij[m]: jep, I'm familiar with dot files15:09
jaskij[m]btw: who's using IRC? I'm not sure which parts of Matrix don't get forwarded to IRC. Say, did my emoji reaction work?15:10
qschulzif you have hours of CPU time to burn, please use graphviz ;)15:10
qschulzjaskij[m]: no it did not15:10
sveinseqschulz: I like to use my CPU on bitbake :P15:10
qschulzjaskij[m]: the Matrix bridge is very recent, so I'd say most of the folks here are still using IRC the old way :)15:11
sveinse..and I'm fetish about it I think, as I just did a full Hardknott compile from no sstate on a wsl2 instance. Left my home office pretty warm :D15:12
qschulzjaskij[m]: if you want to check by yourself15:12
jaskij[m]qschulz: I'm actually more worried I'll get an OOM while it's working, I've got like two gigs available right now15:12
*** frieder <frieder!> has joined #yocto15:13
fabatera[m]Building a BOOST application on YOCTO Gatesgarth fails during do_configure. Tough, it builds on Zeus.15:13
fabatera[m]It can't recognize AX_BOOST_BASE from configure.ac15:13
fabatera[m]I've found adding DEPENDS = "autoconf-archive" works.15:13
fabatera[m]Am I missing something ? Should I add something to so devtools add can recognize the dependency?15:13
qschulzIf you're not compiling web browsers, it should be okay-ish15:13
qschulzIIRC we used to say 2GB*nproc in RAM is the minimum15:13
qschulzbut anything involving web browsers... at least 32GB IIRC15:14
perdmannIs this helpfull for you? FileNotFoundError: [Errno 2] No such file or directory: '/mnt/data/yocto/CTS_Yocto/sources/misc/build/../../../sources/poky/meta-poky:/mnt/data/yocto/CTS_Yocto/sources/misc/build:/mnt/data/yocto/CTS_Yocto/sources/misc/build/../../'15:14
rburtonfabatera[m]: adding DEPENDS was right, that application must be assuming that you have autoconf-archive installed and doesn't include copies of those macros15:15
jaskij[m]I've got 32 GiB on my workstation, of which 20 gigs is allocated to the VM which builds Yocto. Add in CLion, PyCharm and a browser open and I'll just say I'm living dangerously.15:15
sveinseI'm building boost, qt including webkit on my laptop with 32Gb. It succeeds, yet you're in for a long pause15:15
sveinse..on wsl2 and the sstate cache over ntfs which is SLOW!15:15
jaskij[m]I might ask to WFH, just because of the faster PC at home15:16
qschulzsveinse: might be a good idea to use the to-be-released or recently-released new NTFS kernel driver on Linux :)15:16
qschulzperdmann: the semi colon in it are dubious15:16
*** Net147 <Net147!> has joined #yocto15:17
sveinseqschulz: yeah, the pain with ntfs and bb is not the sstate cache, but the git dl of linux kernels. THAT is slow. Like hours slow.15:17
jaskij[m]qschulz: the Paragon NTFS driver is in 5.15, which is on -rc3 now15:18
qschulzjaskij[m]: :+1:15:18
sveinselike it15:18
qschulzaaah, found it :p15:18
perdmannqschulz: i only find colons in that string?15:18
qschulzperdmann: colon indeed. Long week-end :)15:18
sveinsewow, my utf-8 font has thumbs up codepoint :o15:18
qschulzperdmann: I can't even makes sense of what this path should really hold or in which variable it could be15:19
perdmannqschulz: of course. :) Clubs are open again ;-) Do you have an idea wgere tgus was added?15:19
qschulzthere seems to be a mix of a layer directory, the build directory and... something else :p15:20
qschulzperdmann: Drove the motorcycle for 9h ~650km yesterday, not clubbing :)15:20
perdmannso the build directory should be placed somewhere else?15:20
perdmannqschulz: Oh, i see. youre located in Hildesheim?15:20
qschulzperdmann: clearly Bitbake expects a path and you're giving it three paths split by a colon15:21
qschulzperdmann: Vienna15:21
fabatera[m]<rburton> "fabatera: adding DEPENDS was..." <- Is there a better autotools way to set BOOST dependency on so devtool add can get the dependency?15:21
sveinseWill the package-index index everything in tmp/deploy/ipk? Or just the packages relevant to that MACHINE that bitbake was called with?15:21
rburtonfabatera[m]: afaik AX_BOOST_BASE is part of autoconf-archive, not boost15:22
perdmannqschulz: Oh, really wrong -.-15:22
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Ping timeout: 252 seconds)15:23
perdmannqschulz: Where did i set this? :-D15:23
qschulzperdmann: bitbake -e <recipe that fails> and look for those paths15:23
jaskij[m]re: kernel, do you folks think 5.15 will be the next LTS?15:24
fabatera[m]rburton: yes, you are correct! My question was wrong ☹️.15:24
fabatera[m]I mean a way to set autoconf-archive dependency15:24
qschulz5.4, 5.10, probably 5.16?15:24
jaskij[m]earlier it was every fifth iirc15:25
jaskij[m]5.4 to 5.10 was the exception15:25
jaskij[m]but who knows?15:25
jaskij[m]so long it makes it into Yocto 3.5 ;)15:25
qschulz4.4, 4.9, 4.14, 4.19 indeed15:25
rburtonfabatera[m]: DEPENDS += "autoconf-archive" is exactly what you want15:25
perdmannso i really broke that :-D15:25
qschulzperdmann: BBLAYERS is a space separated list of paths :)15:26
*** Sion <Sion!> has quit IRC (Ping timeout: 268 seconds)15:27
qschulzperdmann: with bitbake -e you have the history of the variable, so you can see where all gets messed up15:28
jaskij[m]qschulz: I'm still angry at my SoM vendor - outdated imx-sc-fw means I'm stuck at 4.14 :/15:28
fabatera[m]rburton: Thank you! I was wondering if the dependency could be auto generated. (It was not needed on previous Yocto zeus release).15:28
rburtonbuild dependencies are explicit15:29
qschulzperdmann:  have you also triple checked that you have the correct branch checked out for all your layers and Bitbake (if you use openembedded-core without poky)?15:29
qschulzotherwise, noidea.gif and I'm now afk so good luck :)15:29
qschulzjaskij[m]: sc-fw?15:30
qschulzjaskij[m]: imx SoCs support in upstream kernel is very good usually15:30
perdmannqschulz: wait what do i use? ...15:31
jaskij[m]qschulz: Might've misnamed. The firmware for the built-in M4 in i.MX8X. It must much the sec firmware, and one of the two is causing issues with the kernel if I try 5.4.15:32
*** tnovotny <tnovotny!> has quit IRC (Quit: Leaving)15:32
jaskij[m]afaik they wrote that firmware against pre-mainline kernel released by NXP15:37
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto15:40
jaskij[m]qschulz: eh, getting that graph was not that bad - merely ten minutes on an R5 3600 for my biggest image (no graphics)15:41
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Ping timeout: 252 seconds)15:43
*** dev1990 <dev1990!~dev@> has joined #yocto15:46
*** Net147 <Net147!> has joined #yocto15:47
*** fbre <fbre!~fbre@> has quit IRC (Quit: fbre)15:47
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 260 seconds)15:52
sveinsejaskij[m]: I am too. We're stuck at rocko due to some vendor opengl driver. I'm sure there is newer kernel+yocto combos that work, but its quite the validation work. Dunfell/Gatesgarth/Hardknott has too new systemd for the kernel15:53
jaskij[m]I at least was able to port the kernel and firmwares to Dunfell, might not be fully validated but seems to work nicely15:54
jaskij[m]sveinse: if you're using i.MX, afaik there's a reverse-engineered OpenGL driver for the VCG which has perf parity with the closed source one15:55
sveinsejaskij[m]: yes, the etnaviv - it's the same. However there are some GL operations etnaviv doesn't support. E.g. dithering is not great in etnaviv so the UX team put the veto foot down15:56
jaskij[m]and I really don't want an older systemd than what's in Dunfell, I really want the nice CAN support in systemd-networkd15:57
sveinsewait what, does systemd support operations from CAN?15:57
jaskij[m]it supports configuring socketcan interfaces15:58
jaskij[m]networkd specifically does15:58
sveinsehaha, sorry, got a little overexcited here. Yeah, that makes sense. Good to know. We're using CAN15:58
*** manuel1985 <manuel1985!~manuel198@> has quit IRC (Quit: Leaving)15:59
sveinseI need to see if I can find an overview of the minimal kernel version of the respective systemd releases16:00
jaskij[m]it's in the README in the repo iirc16:01
jaskij[m]that's for `main`16:02
jaskij[m]urgh, my messages got reordered16:02
* jaskij[m] sent a code block:
sveinseYes, thats for *that* release, and then you need to plot a matrix across previous systemd releases16:03
sveinse...which you can use to map against specific yocto releases :P16:03
jaskij[m]Dunfell has systemd 24416:04
jaskij[m]I tried Hardknott and promptly noped out16:04
jaskij[m]too much work, for not enough benefit right now16:05
jaskij[m]mostly around i.MX8X support16:05
*** frieder <frieder!> has quit IRC (Remote host closed the connection)16:05
sveinseTesting 5.10.1 on hardnott on imx6 and it seems ok. No graphics on this device fortunately16:06
jaskij[m]imx6 is easier, no vendor firmware16:06
jaskij[m]we're using SoMs, so there's one more place in the support chain to keep you outdated16:06
sveinseaha, that's interesting. So you need properitary things to run on imx8?16:06
jaskij[m]imx8 all have that Cortex-M4, right?16:07
jaskij[m]it needs firmware which, if you're using a SoM, is provided by your SoM vendor16:07
sveinsewe're prospecting a new architecture, as imx6 is, what 2012 tech, and imx8 has been proposed16:07
*** mckoan is now known as mckoan|away16:07
jaskij[m]this firmware needs to match version with the security firmware16:08
jaskij[m]and iirc both talk with the kernel16:08
sveinsethere are some interesting stuff in the semi-pro world, like the CM4 from RaspberrPi trading16:08
jaskij[m]in my case one of the two is causing an issue when moving to 5.4 mainline and the device simply refuses to boot16:09
jaskij[m]I don't even get serial output16:09
jaskij[m]sveinse: you kinda lost me there16:10
jaskij[m]I know of Pi CM4, but the last two words completely confuse in the context16:10
sveinsejaskij[m]: We're exploring if the cm4 from raspberry pi is anything at all, or if it just is a toy16:10
sveinseas a replacement to the imx6 board we have16:11
jaskij[m]because of the low availability, we've settled on using SoMs using the SMARC standard16:11
jaskij[m]kinda bulky, but we don't mind and at least we're not tied to one SoM vendor16:11
sveinsei got to go, but this has been very interesting. Thanks. See you around.16:12
jaskij[m]see you16:12
sveinse(we need a good forum/chat for this, but HW-ppl dislike IRC it seems)16:12
jaskij[m]sveinse: first of all, CM4 doesn't have built-in CAN, and using an external controller is always a mild PITA16:13
sveinsejaskij[m]: yep, I am aware. Major drawback16:14
jaskij[m]I'm not sure about Pi4, but the bcm283x in Pi1 to Pi3 is basically a settop SoC16:15
jaskij[m]there's i.MX9 around the corner too16:15
jaskij[m]they've already announced it, but haven't shown any SoCs yet16:15
jaskij[m]yeah, seems like Pi4 doesn't improve much in the peripheral department16:18
sveinsebiggest advantage with the cm4 is the huge package/distro community. It's extremely well supported16:23
jaskij[m]guessing by you being here, you'll be running Yocto/OE anyway?16:23
jaskij[m]so that advantage doesn't exist then, does it?16:24
sveinseTo be honest don't know. We had one product for 5 years on ubuntu (armhf) and decided that it wasn't worth the stretch to customize it the way we needed it to, enter Yocto. However Yocto is hard for many and it requires tremendous investment in build frameworks16:25
sveinseWe're run yocto for 6 years or so16:25
*** roussinm <roussinm!> has joined #yocto16:27
sveinseThe more I use Yocto, the more I enjoy it16:28
jaskij[m]yeah, Yocto will draw out every issue in build systems16:28
jaskij[m]that too16:28
jaskij[m]I've spent what, two weeks? trying to build SciPy16:28
jaskij[m]I don't like some of the stuff in meta-scipy, such as a lack of an optimized BLAS16:29
sveinseBut it does have a curve, and engineers with yocto experience is very hard to get by. I've tried many times on delegating my tasks to others (as I am manager), internal and external looking16:29
jaskij[m]I've got no plans to move rn, but last time I looked there was little job offers mentioning Yocto16:30
jonmasonJPEW today, zeddii tomorrow.  Lots of good heckling over the next few days at ELC16:30
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 245 seconds)16:39
*** camus <camus!~Instantbi@> has joined #yocto16:39
*** florian <florian!> has quit IRC (Quit: Ex-Chat)16:45
*** amitk <amitk!~amit@> has joined #yocto16:47
*** goliath <goliath!~goliath@user/goliath> has joined #yocto16:47
perdmannqschulz: the problem was the way i made BBLAYERS relative...17:00
tlwoernerrelatives can often be the source of issues…17:04
*** oobitots <oobitots!> has quit IRC (Quit: Client closed)17:15
*** rfuentess <rfuentess!> has quit IRC (Quit: donde está el mezcal? DONDE?!)17:18
*** florian <florian!> has joined #yocto17:29
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Quit: ZNC 1.8.2 -
*** florian <florian!> has quit IRC (Ping timeout: 245 seconds)17:40
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto17:42
*** nerdboy <nerdboy!~nerdboy@gentoo/developer/nerdboy> has quit IRC (Ping timeout: 265 seconds)17:44
vddoes d.getVar('FOOBAR') return false if FOOBAR = ""?17:55
*** nerdboy <nerdboy!~nerdboy@> has joined #yocto17:56
jaskij[m]hmm.... I'm packaging something that's screwing up install paths somewhere... do I just fix it in `do_install_append` or patch CMakeLists.txt?17:56
kergothvd: it returns the empty string if it's set to the empty string, or None if it hasn't been set to anything anywhere at all. both are considered false in an if block in python17:59
vdkergoth: thank you18:01
arrGood afternoon folks. I have a weird issue. A recipe foo-image depends on another recipe/package bar. If I run -c cleansstate for bar and then run bitbake on foo-image, bitbake understands that foo-image depends on bar package and rebuilds it (runs compile, install, package etc tasks including do_package_write_ipk) but it won't run rootfs and image tasks for foo-image. Any ideas why?18:03
arrfoo-image has "IMAGE_INSTALL = bar" entry in .bb file18:03
khemjaskij: usually its better to fix the component build system in your case cmake and also submit upstream to make it cross compile friendly, second option would be to tweak it in do_install18:04
khemarr: did anything change in the package bar build after rebuilding ?18:05
khemperhaps it found the signatures to be exact and hence did not rebuild image18:05
arrkhem, yes, there were changes18:05
khemok did these changes result in output of build18:06
arrThe package bar downloads a binary file as source and simply tars it up as compile step. The binary file changed for sure.18:07
arrBut the versions and other metadata for the file didn't change.18:08
khemwell it sounds like its sneaking in things under the nose of bitbake, if tarball changed I wonder why SRC_URI checksums did not change18:09
arrThe .ipk file produced at the end of write_package_ipk has new file, so output of bar is correct18:09
khemI think you could change recipe for bar to explicitly download the tarball via SRC_URI and things will fall into place18:10
*** davidinux <davidinux!> has quit IRC (Ping timeout: 245 seconds)18:11
arrkhem, Ah. I will try that. Thanks.18:12
vdis there a mechanism similar to IMAGE_BOOT_FILES = "some_artifiact;different_name" but for the rootfs?18:14
*** pgowda <pgowda!> has quit IRC (Quit: Connection closed for inactivity)18:16
khemvd: what usecase are you looking for ?18:17
*** whuang0389 <whuang0389!> has joined #yocto18:17
vdkhem: I'm embedded several images in my rootfs, for example an initrd, an overlay image, application container images, and the process could be generic: do_rootfs[depends] += "${MY_ROOTFS_DEPENDS}" and a bunch of files copied into ${IMAGE_ROOTFS} from a ROOTFS_POSTPROCESS_COMMAND function. If I could fill a variable with the "from;to" syntax, I18:20
vdcould make a generic post process function.18:20
khemhmmm, I guess this are all super image functions perhaps18:23
vdkhem: so from the recipe or a configuration file I could do for example: MY_ROOTFS_EXTRADEPENDS += "core-image-minimal:do_image_complete" and MY_ROOTFS_EXTRAFILES += "core-image-minimal.squashfs;/var/lib/machines/app.img"18:28
*** GillesM <GillesM!> has joined #yocto18:32
*** GillesM <GillesM!> has quit IRC (Client Quit)18:32
*** GillesM <GillesM!> has joined #yocto18:33
khemyou could do this via a recipe for a new super image18:39
*** wwilly <wwilly!> has quit IRC (Ping timeout: 240 seconds)18:43
*** otavio_ <otavio_!> has quit IRC (Ping timeout: 252 seconds)18:44
*** otavio <otavio!> has joined #yocto18:46
yatesis there a overall log of a bitbake build stashed somewhere, perhaps in build/tmp? i'm not referring to the individual build/tmp/.../temp logs18:47
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 265 seconds)18:48
*** camus <camus!~Instantbi@> has joined #yocto18:49
khemyates: look into build/tmp/log18:49
khemespecially cooker folder contains the build logs18:49
yatesaha! Beautiful, khem!18:51
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)18:59
jaskij[m]khem: after looking around, seems like at least one path variable is used both for tests and as installation path, and it's altogether a complicated issue19:01
jaskij[m]so no upstream patches from me, unfortunately19:01
jaskij[m]Plus, it's entirely possible I'm passing wrong paths to the script19:04
Xagenwhen doing a build from toaster, can you force the checkout for a specific layer to be at a specific tag/commit-id instead of a branch?19:06
*** wwilly <wwilly!> has joined #yocto19:12
*** davidinux <davidinux!> has joined #yocto19:14
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 265 seconds)19:16
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:2a3:1764:1ba:5e89> has quit IRC (Ping timeout: 245 seconds)19:17
*** kiran_ <kiran_!~kiran@2607:fea8:5a80:ea0:61af:b0e5:dc3f:b04d> has joined #yocto19:17
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)19:32
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto19:37
*** GillesM <GillesM!> has quit IRC (Quit: Leaving)19:46
*** florian <florian!> has joined #yocto19:54
*** sakoman <sakoman!> has joined #yocto20:23
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto20:57
*** whuang0389 <whuang0389!> has quit IRC (Quit: Client closed)21:13
*** xmn <xmn!> has joined #yocto21:34
*** jwillikers <jwillikers!> has joined #yocto21:50
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Quit: Textual IRC Client:
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Remote host closed the connection)21:55
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto21:55
*** jonesv[m] <jonesv[m]!~jonesvmat@2001:470:69fc:105::4616> has joined #yocto21:56
*** ecdhe <ecdhe!> has quit IRC (Read error: Connection reset by peer)22:02
*** ecdhe <ecdhe!> has joined #yocto22:02
*** user_123 <user_123!~user@> has quit IRC (Remote host closed the connection)22:03
*** user_123 <user_123!~user@> has joined #yocto22:04
*** alex88 <alex88!> has quit IRC (Quit: ZNC 1.7.3 -
*** alex88 <alex88!> has joined #yocto22:05
*** roussinm <roussinm!> has quit IRC (Ping timeout: 246 seconds)22:06
*** alejandrohs <alejandrohs!~alejandro@user/alejandrohs> has quit IRC (Ping timeout: 264 seconds)22:07
*** alejandrohs <alejandrohs!~alejandro@user/alejandrohs> has joined #yocto22:07
*** roussinm <roussinm!> has joined #yocto22:07
*** vd <vd!> has quit IRC (Quit: Client closed)22:10
*** jonesv[m] <jonesv[m]!~jonesvmat@2001:470:69fc:105::4616> has quit IRC (Quit: Reconnecting)22:10
*** jonesv[m] <jonesv[m]!~jonesv@2001:470:69fc:105::4616> has joined #yocto22:11
*** jwillikers <jwillikers!> has quit IRC (Remote host closed the connection)22:18
*** arr <arr!~ar@> has quit IRC (Ping timeout: 252 seconds)22:18
RPJPEW: I suspect you're busy/distracted so this can with until later if so but depressingly I've discovered a problem with native sstate hashequiv :(22:40
JPEWRP: sad. We can talk at the meeting tomorrow22:43
RPJPEW: I thought that was cancelled?22:43
JPEWOh was it?22:43
RPdue to ELC22:43
*** florian <florian!> has quit IRC (Ping timeout: 252 seconds)22:44
JPEWEither way I'm free tomorrow morning (ELC doesn't start till 11 local time)22:45
RPJPEW: ok, cool thanks22:46
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has quit IRC (Ping timeout: 264 seconds)23:07
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has joined #yocto23:08
*** zmoment <zmoment!> has joined #yocto23:10
*** azstevep[m] <azstevep[m]!~azstevepm@2001:470:69fc:105::1:3b7> has joined #yocto23:12
*** zmoment <zmoment!> has left #yocto ( - Chat comfortably. Anywhere.)23:13
*** ramprakash[m] <ramprakash[m]!~ramprakas@2001:470:69fc:105::fbfe> has quit IRC (Ping timeout: 246 seconds)23:31
*** xicopitz[m] <xicopitz[m]!~xicopitzm@2001:470:69fc:105::4869> has quit IRC (Ping timeout: 246 seconds)23:31
*** Nate[m]1 <Nate[m]1!~nsdrudema@2001:470:69fc:105::f855> has quit IRC (Ping timeout: 246 seconds)23:31
*** coldspark29[m] <coldspark29[m]!~coldspar_@2001:470:69fc:105::db09> has quit IRC (Ping timeout: 246 seconds)23:31
*** Alban[m] <Alban[m]!~albeugaen@2001:470:69fc:105::34b4> has quit IRC (Ping timeout: 246 seconds)23:31
*** etam[m] <etam[m]!~etam@user/etam> has quit IRC (Ping timeout: 246 seconds)23:31
*** azstevep[m] <azstevep[m]!~azstevepm@2001:470:69fc:105::1:3b7> has quit IRC (Ping timeout: 250 seconds)23:31
*** cryptollision[m] <cryptollision[m]!~cryptolli@2001:470:69fc:105::f778> has quit IRC (Ping timeout: 250 seconds)23:31
*** meck[m] <meck[m]!~meckmeckd@2001:470:69fc:105::3a51> has quit IRC (Ping timeout: 250 seconds)23:31
*** WadeBerrier[m] <WadeBerrier[m]!~wberrierm@2001:470:69fc:105::3f0e> has quit IRC (Ping timeout: 250 seconds)23:31
*** dwagenk <dwagenk!~dwagenk@2001:470:69fc:105::103d> has quit IRC (Ping timeout: 246 seconds)23:31
*** jwillikers[m] <jwillikers[m]!~jwilliker@2001:470:69fc:105::626a> has quit IRC (Ping timeout: 246 seconds)23:31
*** saYco[m] <saYco[m]!~saycomatr@2001:470:69fc:105::1:2a0> has quit IRC (Ping timeout: 264 seconds)23:31
*** ejoerns[m] <ejoerns[m]!~ejoernsma@2001:470:69fc:105::252> has quit IRC (Ping timeout: 246 seconds)23:32
*** jordemort <jordemort!~jordemort@2001:470:69fc:105::2d9> has quit IRC (Ping timeout: 246 seconds)23:32
*** agherzan <agherzan!~agherzan@2001:470:69fc:105::e1fe> has quit IRC (Ping timeout: 268 seconds)23:32
*** coldspark29[m] <coldspark29[m]!~coldspar_@2001:470:69fc:105::db09> has joined #yocto23:33
*** vd <vd!> has joined #yocto23:33
*** Alban[m] <Alban[m]!~albeugaen@2001:470:69fc:105::34b4> has joined #yocto23:34
*** Nate[m]1 <Nate[m]1!~nsdrudema@2001:470:69fc:105::f855> has joined #yocto23:34
*** ramprakash[m] <ramprakash[m]!~ramprakas@2001:470:69fc:105::fbfe> has joined #yocto23:34
*** etam[m] <etam[m]!~etam@user/etam> has joined #yocto23:34
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 252 seconds)23:37
*** camus <camus!~Instantbi@> has joined #yocto23:37
*** WadeBerrier[m] <WadeBerrier[m]!~wberrierm@2001:470:69fc:105::3f0e> has joined #yocto23:37
*** azstevep[m] <azstevep[m]!~azstevepm@2001:470:69fc:105::1:3b7> has joined #yocto23:37
*** cryptollision[m] <cryptollision[m]!~cryptolli@2001:470:69fc:105::f778> has joined #yocto23:39
*** dwagenk <dwagenk!~dwagenk@2001:470:69fc:105::103d> has joined #yocto23:42
*** jwillikers[m] <jwillikers[m]!~jwilliker@2001:470:69fc:105::626a> has joined #yocto23:42
*** saYco[m] <saYco[m]!~saycomatr@2001:470:69fc:105::1:2a0> has joined #yocto23:44
*** agherzan <agherzan!~agherzan@2001:470:69fc:105::e1fe> has joined #yocto23:47
*** ejoerns[m] <ejoerns[m]!~ejoernsma@2001:470:69fc:105::252> has joined #yocto23:48
*** xicopitz[m] <xicopitz[m]!~xicopitzm@2001:470:69fc:105::4869> has joined #yocto23:58
*** meck[m] <meck[m]!~meckmeckd@2001:470:69fc:105::3a51> has joined #yocto23:59

Generated by 2.17.2 by Marius Gedminas - find it at!