Wednesday, 2019-05-15

*** ab0oo <ab0oo!~Thunderbi@c-67-180-169-12.hsd1.ca.comcast.net> has quit IRC00:08
*** scottrif <scottrif!~scottrif@47.39.60.15> has left #yocto00:15
*** ab0oo <ab0oo!~Thunderbi@2601:647:4000:e050:d8ca:6e0:5624:135c> has joined #yocto00:21
*** vineela <vineela!vtummala@nat/intel/x-yqdralexvvruirpu> has joined #yocto00:24
*** vineela <vineela!vtummala@nat/intel/x-yqdralexvvruirpu> has quit IRC00:26
*** ab0oo1 <ab0oo1!~Thunderbi@c-67-180-169-12.hsd1.ca.comcast.net> has joined #yocto00:30
*** ab0oo <ab0oo!~Thunderbi@2601:647:4000:e050:d8ca:6e0:5624:135c> has quit IRC00:31
*** ab0oo1 is now known as ab0oo00:31
seebshttps://mdsattacks.com/ <-- this is sort of brilliant00:39
*** fitzsim <fitzsim!~user@69-165-165-189.dsl.teksavvy.com> has joined #yocto00:55
* armpit looks for his dunce cap to put on01:06
* armpit armpit go stand in the corner and think about it01:08
*** tprrt <tprrt!~tprrt@upc31-1-78-208-110-13.fbx.proxad.net> has quit IRC01:22
*** nslu2-log <nslu2-log!~nslu2-log@23.141.224.193> has quit IRC01:31
*** nslu2-log <nslu2-log!~nslu2-log@23.141.224.193> has joined #yocto01:32
*** nslu2-log_ <nslu2-log_!~nslu2-log@23.141.224.193> has joined #yocto01:42
*** nslu2-log <nslu2-log!~nslu2-log@23.141.224.193> has quit IRC01:42
*** nslu2-log_ is now known as nslu2-log01:43
*** nslu2-log_ <nslu2-log_!~nslu2-log@23.141.224.193> has joined #yocto01:52
*** nslu2-log <nslu2-log!~nslu2-log@23.141.224.193> has quit IRC01:52
*** nslu2-log_ is now known as nslu2-log01:53
*** kaspter <kaspter!~Instantbi@125.118.57.2> has joined #yocto01:54
*** ab0oo <ab0oo!~Thunderbi@c-67-180-169-12.hsd1.ca.comcast.net> has quit IRC01:54
*** rrerolle <rrerolle!~rrerolle@vps.neonex.fr> has quit IRC01:59
*** rrerolle6 <rrerolle6!~rrerolle@vps.neonex.fr> has joined #yocto01:59
*** nslu2-log <nslu2-log!~nslu2-log@23.141.224.193> has quit IRC02:01
*** nslu2-log <nslu2-log!~nslu2-log@23.141.224.193> has joined #yocto02:02
*** kaspter <kaspter!~Instantbi@125.118.57.2> has quit IRC02:11
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto03:07
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC03:11
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-xjrfwhqjtzttorqs> has quit IRC03:57
*** fatalhalt <fatalhalt!~fatalhalt@c-67-163-60-93.hsd1.il.comcast.net> has joined #yocto04:10
*** bjobjo <bjobjo!~bjobjo@2a01:79d:3e81:5208::9e6> has quit IRC04:38
*** fatalhalt <fatalhalt!~fatalhalt@c-67-163-60-93.hsd1.il.comcast.net> has quit IRC04:40
*** kaspter <kaspter!~Instantbi@2409:8928:e1a:6c1c:4df4:6aa0:12df:6525> has joined #yocto04:42
*** kaspter <kaspter!~Instantbi@2409:8928:e1a:6c1c:4df4:6aa0:12df:6525> has quit IRC04:52
*** kaspter <kaspter!~Instantbi@2409:8928:e1a:6c1c:4df4:6aa0:12df:6525> has joined #yocto04:52
*** tprrt <tprrt!~tprrt@upc31-1-78-208-110-13.fbx.proxad.net> has joined #yocto05:07
*** Klox3 <Klox3!~Klox@c-73-22-66-195.hsd1.il.comcast.net> has quit IRC05:10
*** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has joined #yocto05:13
*** xtron <xtron!~xtron@110.93.212.98> has joined #yocto05:19
*** xtron <xtron!~xtron@110.93.212.98> has quit IRC05:25
*** xtron <xtron!~xtron@110.93.212.98> has joined #yocto05:28
*** agust <agust!~agust@p508B6FD6.dip0.t-ipconnect.de> has joined #yocto05:40
*** tprrt <tprrt!~tprrt@upc31-1-78-208-110-13.fbx.proxad.net> has quit IRC05:48
*** kaspter <kaspter!~Instantbi@2409:8928:e1a:6c1c:4df4:6aa0:12df:6525> has quit IRC05:57
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto06:10
*** bjobjo <bjobjo!~bjobjo@2a01:79d:3e81:5208::9e6> has joined #yocto06:14
*** kaspter <kaspter!~Instantbi@2409:8928:e1a:6c1c:6940:211a:a269:4cd3> has joined #yocto06:15
*** frsc <frsc!~frsc@200116b82496c100a0090255879e121a.dip.versatel-1u1.de> has joined #yocto06:23
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:25
*** cvasilak <cvasilak!~cvasilak@2a02:587:8110:4000:3c63:9e53:70be:268e> has joined #yocto06:31
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC06:38
*** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has joined #yocto06:38
*** tijko <tijko!~tijko@unaffiliated/tijko> has quit IRC06:40
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has joined #yocto06:41
*** camus <camus!~Instantbi@223.104.246.2> has joined #yocto06:45
*** kaspter <kaspter!~Instantbi@2409:8928:e1a:6c1c:6940:211a:a269:4cd3> has quit IRC06:46
*** camus is now known as kaspter06:46
*** jku <jku!~jku@dyx9b8yyyyyyyyyyyyyct-3.rev.dnainternet.fi> has joined #yocto06:49
*** jeanba <jeanba!~jbl@77.243.63.34> has joined #yocto06:56
*** jeanba <jeanba!~jbl@77.243.63.34> has left #yocto06:57
*** tprrt <tprrt!~tprrt@217.114.201.133> has joined #yocto06:58
*** lukma <lukma!~lukma@85-222-111-42.dynamic.chello.pl> has joined #yocto07:10
*** malanecora <malanecora!b23cc82c@gateway/web/freenode/ip.178.60.200.44> has joined #yocto07:17
Ad0require ${@bb.utils.contains('DISTRO_FEATURES', 'virtualization', 'meta-virt-default-versions.inc', '', d)}07:17
Ad0 this fails, can't find the inc file. had to move them to the same directory07:17
Ad0http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/conf/layer.conf?h=thud07:18
*** yacar_ <yacar_!~yacar@80.215.109.48> has joined #yocto07:19
frayif it fails, then it sounds like something is wrong with the BBPATH.  the BBPATH will check the current directory first, and then fall back to searching the various locations..07:28
fraywhere is that file in the layer?  You may need to include the conf/... directory as well07:28
erboShouldn't the require line specify the "conf/distro/include/" part too? Like line 32 in the same file?07:35
frayIf it's in the same directory, then the line should just have the anem.. if it's in a different directory, then yes.. I usually include the full path from the root of the layer07:36
erboThe inc file is in a subdir, so not in the same dir. But it feels a bit weird that this is broken without anyone else noticing?07:37
*** Hodhr <Hodhr!~Hodhr@162.206.70.37.rev.sfr.net> has joined #yocto07:40
fraysubdirectory of the current dir, then it's:  include subdir/file.inc07:40
*** Hodhr <Hodhr!~Hodhr@162.206.70.37.rev.sfr.net> has left #yocto07:40
*** leitao <leitao!~leitao@2620:10d:c092:200::1:6842> has joined #yocto07:43
*** leitao <leitao!~leitao@2620:10d:c092:200::1:6842> has joined #yocto07:56
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has quit IRC08:00
*** kaspter <kaspter!~Instantbi@223.104.246.2> has quit IRC08:08
*** T_UNIX <T_UNIX!uid218288@gateway/web/irccloud.com/x-dqwsmalkmjfkwbyk> has joined #yocto08:10
Ad0fray, it's not in the same dir, it's in distro/include08:18
Ad0I am using this from toaster, maybe it does something with the paths that commandline builds don't08:18
Ad0sometimes I feel like I am the only person on earth that uses toaster08:19
frayconf/distro/include/....08:19
fraylet me look at an example quickly, just a second08:19
LetoThe2ndfray: now i totally misread that as conf/disco/include. and wondered. d'oh08:19
fraywrlinux-common.inc:require conf/distro/include/wrlinux-distro-settings.conf08:19
fraythat file is in conf/distro08:20
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has joined #yocto08:20
frayso yes something in conf/distro to include something in a further include directory needs a reltive path from the beginning of the layer...08:20
Ad0so meta-virtualization is quite central, and it even has it's own mailing list under yocto, and the code hasn't been changed in that file for ages in that area08:20
frayonly files in the same directory appear to not require a specific path08:20
Ad0so I am thinking it works somehow from cmdline08:21
Ad0http://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/conf?h=thud08:22
Ad0it does the full path elsewhere08:22
Ad0require conf/distro/include/virt_security_flags.inc08:23
Ad0 @ line 3208:23
Ad0so why doesn't it do it at line 41?08:23
frayAt one point that file was in that directory.. it's a bug..08:24
frayjust fix it08:24
Ad0ok! is this layer dead or should I use something else?08:25
Ad0since it's not pickedu p08:25
frayno.. meta-virtualization is definitely used.. heavily..08:26
fraythe change was made only a few weeks ago.. it may be that nobody has noticed, since they're not using the top of tree..08:26
fraybut it's a bug, the path in the layer.conf needs to have the distro/include part08:27
Ad0lol typical my luck08:27
Ad0thanks for helping, I thought I was insane08:27
Ad0btw, how is make menuconfig done on swupdate in a toaster build ?08:28
Ad0do I have to cd into whatever dir toaster has generated and do it there?08:28
Ad0hm my bad, seems like that's not related to yocto build08:30
*** eyalgal <eyalgal!~eyal@141.226.38.133> has joined #yocto08:48
* eyalgal say hi to all08:48
eyalgalanyone build a daemon service for yocto ? assuming i do not have systemd installed (RC scripts are used) how can i make sure my executable is respawn if it dies ?08:50
eyalgalwe tried /etc/inittab but it is problematic cause opther scripts on the way may hang it and i think it also didn't work.08:51
frayyou will need to either use the sysvinit inittab directly to monitor the resource, or you will have to have your own monitoring tool..08:51
fraythis is one of the reasons why systemd was created was to solve this problem08:51
LetoThe2ndfray: since you're around this time of the day, surprisingly... yesterday you suggested streaming on kernel dev etc. anything specifically you have in mind? configuration, working with upstream, patches... ?08:55
frayCustomer I'm currently visiting was interested in a presentation explaing how the Yocto Project handles it's kernel.. and then on a 'tour' of the linux-yocto(-dev), yocto-kernel-cache and the recieps that use them..08:56
fraythis is something I could do once I'm done with my current work trip..  kind of do an informal presentation, walk through08:56
fray(I'm in Finland right now.. next week in Ulm.. then finally back home)08:57
LetoThe2ndfray: ah, i get it. i was just trying to think along those lines, and while i'm happy to give it a shot its really not an area where i have significant expertise08:57
LetoThe2ndfray: ulm is nice :)08:57
frayI've already written the presnetaiton (about 10 slides), but it involves a lot of going out and showing things in context for people..08:58
frayya, I still need to book my hotel and get the DB tickets from Munich to Ulm and back.. :P08:58
frayDB tickets shouldn't be a problem, but the two hotels I've tried have been sold out so far08:58
* LetoThe2nd mentally pokes fray to get in front of a webcam and show it on twitch :)08:58
LetoThe2ndheh, then you actually pass by me in 45km distance08:58
frayremind me in two weeks.. I'd need to try to get OBS installed..08:58
LetoThe2ndfray: if you need assistance in ulm, i'm sure i can get some local information at least.08:59
frayI should be fine at this point, since work is paying Taxi's are 'easy'  :)09:00
frayI fly into Munich on Saturday afternoon, spend the night there, and then will get myself to Ulm on Sunday..  opposite on Friday of that week..09:00
fraythe other guy I'm meeting in Ulm is coming in from Stuttgart.. but that would have been a lot more expensive for the plane ticket.. :(09:00
frayotherwise he'll have a rental car09:01
*** mihai <mihai!~mihai@unaffiliated/mihai> has joined #yocto09:01
LetoThe2ndfray: yeah, german transportation is a bit different when it comes to flying vs. trains09:01
LetoThe2ndfray: sister of mine is dating a guy from the us, and when they went on weekend vacation with a like 3hr drive, he went "3hrs? why aren't we flying there?"09:02
LetoThe2ndfray: if you got spare time in ulm, get up the m√ľnster09:02
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC09:02
fraylast time I was there I drove by it a few times on the way to where I'm going.. ;)09:03
fraybut thats been as close as I've gotten.. ;)09:03
eyalgalfray: thanks09:03
LetoThe2ndfray: its really not super important. but nice if you want to be tourist for an hour, or so.09:04
LetoThe2ndfray: and, drink all the beers that are way too expensive in finland09:06
*** yacar_ <yacar_!~yacar@80.215.109.48> has quit IRC09:16
*** lusus <lusus!~lusus@62.91.23.180> has joined #yocto09:17
*** kroon <kroon!~kroon@213.185.29.22> has joined #yocto09:21
*** ak77 <ak77!c12e4b03@gateway/web/freenode/ip.193.46.75.3> has joined #yocto09:28
*** cvasilak <cvasilak!~cvasilak@2a02:587:8110:4000:3c63:9e53:70be:268e> has quit IRC09:29
*** fancer <fancer!fancer@gateway/web/irccloud.com/x-epipbmwbjhsiawtw> has joined #yocto09:35
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto09:36
*** leitao <leitao!~leitao@2620:10d:c092:200::1:6842> has quit IRC09:39
*** leitao <leitao!~leitao@2620:10d:c092:200::1:6842> has joined #yocto09:40
*** cvasilak <cvasilak!~cvasilak@2a02:587:8110:4000:1431:6b90:cc8a:e4d6> has joined #yocto09:43
*** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has quit IRC09:46
*** AndersD_ <AndersD_!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has joined #yocto09:46
*** timblechmann <timblechmann!~quassel@2001:e68:5420:2d94:cf8:dddd:e3ab:a5bd> has joined #yocto09:56
*** falstaff <falstaff!~quassel@2a02:169:34b6:0:38bf:a3ff:fe35:2815> has quit IRC09:56
*** falstaff <falstaff!~quassel@37.17.239.109> has joined #yocto09:56
Ad0the people at the toaster mailing list told me to make a defect but what's a defect, and in what system is it specified? bugzilla?09:57
frayAd0 if you are still here.. bugzilla.yoctoproject.org10:16
Ad0yes alive and kicking10:16
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto10:17
Ad0"Create a Toaster defect. I will create the patch, share that with the Toaster mailing list, and submit it to bitbake-dev.10:17
Ad0"10:17
frayyup.. that bugzilla is yoctoproject one10:17
Ad0thanks10:17
Ad0I will do the same for the meta-virtualization10:17
LetoThe2ndtodays todo: "create a toaster defect"10:17
fraythanks!10:17
* LetoThe2nd heads to the kitchen!10:18
Ad0_)10:18
Ad0https://www.youtube.com/watch?v=IPoJtt3X5SA10:18
frayIf you do create the meta-virtualization on, let me know the number and I'll comment on it10:18
Ad0kk10:18
fray(should have said this earlier.. if you create a patch and send it to the meta-virtualization mailing list, then there actually is no reason to open a bug... but a bug helps track the issue for us to work on if you are not otherwise able to.)10:25
*** ektor-5 <ektor-5!~ektor-5@94-255-191-177.cust.bredband2.com> has quit IRC10:25
Ad0ok, how should I send the patch, using the GIT method ?10:28
Ad0make a local commit and send it as a patch ?10:28
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC10:29
*** ektor-5 <ektor-5!~ektor-5@94-255-191-177.cust.bredband2.com> has joined #yocto10:30
fraytypically use git..10:31
frayso edit the file, git add <file> ; git commit -s ... fill out commit log..   then git format-patch ... and send the info to the mailing list10:32
fraymeta-virtualization list is:10:32
fraymeta-virtualization@yoctoproject.org10:32
Ad0I guess I have to subscribe first10:32
*** jku <jku!~jku@dyx9b8yyyyyyyyyyyyyct-3.rev.dnainternet.fi> has quit IRC10:32
fraynot sure.. you may have rto10:32
*** lusus <lusus!~lusus@62.91.23.180> has quit IRC10:33
Ad0ok will try tonight10:35
Ad0:)10:35
Ad0I have an issue understanding what's actually included in my yocto build, I want to include stuff from multiple layers, do I have to search for a package in a layer to explicitly include it? or does it magically get included?10:41
Ad0packages built = packages included?10:42
fraythink of each layer as a bucket of lego.  Collectively you have all of the buckets (listed in conf/bblayers) available to you.  Dependencies are what selets the pieces to use when you build..10:44
Ad0ok10:44
fraybitbake, like make, is dependeny based.. so if core-image-minimal requires busybox which requires glibc..  you must have something in that 'bucket' that provides glibc, and busybox..  but what is providing it doesn't really matter10:44
Ad0there are image recipes and software recipes10:45
frayall recipes are 'equal' from a dependency point of view.. what is different is their output format..10:45
frayimage recipes will generally NOT build software, but will output some type of image..  while a software recipe will usually build software and output a package..10:45
Ad0ok10:45
fraybut the dependencies between then remain the same10:45
Ad0I want to build an image with the meta-swupdate as the "master" image I guess since I want the partition layout of that for a 2 partition update10:46
fraymeta-swupdte is the bucket.. but the image is constructed from packages..  So your dependency (IMAGE_INSTALL) needs to specify some packages that meta-swupdate is capable of producing..10:47
frayI've not use meta-swupdate, so I'm not sure what specific packages you may need to include in your image10:48
Ad0I built swupdate-image but it produced no output, while core-image-full-cmdline produced image files etc.10:48
Ad0ok10:48
frayya, that is down to the layers and docs that come with it.  Sorry I can't help you more on that specific item10:48
Ad0thanks, no problem10:49
Ad0a lot of the configuration is set with bitbake vars. so I assume EXTRA_IMAGE_FEATURES in the Toaster web to append it, is EXTRA_IMAGE_FEATURES_append = " xxxx" ?10:52
Ad0seems like _append is used to do +=10:52
frayyes that should10:52
fray_append is a 'late' binding change to a variable.. after everything else has ben processed "do this"..10:53
frayi.e.10:53
frayA = 110:53
frayA = 210:53
*** timblechmann <timblechmann!~quassel@2001:e68:5420:2d94:cf8:dddd:e3ab:a5bd> has quit IRC10:53
frayat the end A equals 210:53
frayA = 110:53
frayA += 210:53
frayA = 210:53
frayagain A equals 210:53
frayA = 110:53
frayA_append = " 2"10:53
frayA = 210:53
frayA will be "2 2"10:53
Ad0right10:54
fraysince the _append is applied late10:54
Ad0I guess there is no other way to do += from within Toaster10:54
fraycorrect. since processing order is not ensured for various reasonable, you end up needing the _append to get what you usually want10:54
Ad0or is Toaster like you can do basic stuff there but you have to manually edit layer.conf as well10:54
Ad0right10:55
Ad0http://variwiki.com/index.php?title=Yocto_Build_Release&release=RELEASE_PYRO_V1.0_VAR-SOM-MX610:55
Ad0I wonder if it will accept something like this: SWUPDATE_IMAGES_FSTYPES[core-image-full-cmdline]10:58
Ad0nope10:59
Ad0just trying to follow this one - https://sbabic.github.io/swupdate/building-with-yocto.html11:00
*** cvasilak <cvasilak!~cvasilak@2a02:587:8110:4000:1431:6b90:cc8a:e4d6> has quit IRC11:10
*** jku <jku!~jku@dyx9b8yyyyyyyyyyyyyct-3.rev.dnainternet.fi> has joined #yocto11:11
Ad0maybe I have to make my own local layer and import it into toaster, and run it ?11:29
*** yacar_ <yacar_!~yacar@80.215.109.48> has joined #yocto11:36
*** jeanba <jeanba!~jbl@77.243.63.34> has joined #yocto11:48
*** jeanba <jeanba!~jbl@77.243.63.34> has left #yocto11:48
*** vmeson <vmeson!~rmacleod@24-52-238-240.cable.teksavvy.com> has quit IRC11:56
malanecoraHi guys!12:02
malanecoraI'm wondering which is the best way to manage several projects based on the same board from the Yocto point of view...12:03
LetoThe2ndmalanecora: sounds like the generic reason why one should have separate machine, distro and application layers :)12:04
malanecoraYeah, indeed12:06
LetoThe2ndso there is your answer!12:06
malanecoraBut I can't clearly see what should be separate from what12:07
malanecora:/12:08
LetoThe2ndmalanecora: the machine layer generally contains the kernel, bootloader, driver recipes that are tied to the hardware, plus the machine.conf12:08
LetoThe2ndmalanecora: you can share a distro layer if the applications bear some resemblance in software, or you can have two seperate distro layers, or mix that into the application layer, there it depends a bit on the actual projects.12:10
malanecoraLetoThe2nd: Hmmm...I see. So, even the slightest required modification in the kernel/device tree would force me to build up a new layer?12:12
*** berton <berton!~berton@181.220.86.53> has joined #yocto12:17
LetoThe2ndmalanecora: given a common board, such changes are rather rare once bring up is finished, right12:18
LetoThe2ndmalanecora: i mean, you explicitly stated "same board"12:18
malanecoraLetoThe2nd: You're right. I just wanted to know it...haha. Nevertheless, you may need to enable/disable some kernel modules or features for some project.12:21
LetoThe2ndmalanecora: you can always to that through an append, if needed.12:24
malanecoraLetoThe2nd: Suppose so12:26
malanecoraLetoThe2nd: Regarding the distro layer, would it make sense to have just different images (each image with different packages) and keep the same distro? Since the applications would be similar, someway. BTW, I'm not really sure if I totally understand which are the limits of the distro layer.12:27
*** ektor-5 <ektor-5!~ektor-5@94-255-191-177.cust.bredband2.com> has quit IRC12:27
LetoThe2ndmalanecora: it can be different images, technically of course. but then you'd have a commit in the repo if you modify one image, and see the commit for the other images too12:28
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto12:30
ndecmalanecora: distro and images are "orthogonal" concepts. in distro you configure 'behavior' for the entire build. you set variables that will impact every recipe that you build, or every image that you will build. in image recipe you only define which binary package you include. an image recipe doesn't impact how recipes are 'built'.12:47
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC13:09
*** eyalgal <eyalgal!~eyal@141.226.38.133> has quit IRC13:15
malanecoraLetoThe2nd, ndec : Thank you guys!13:20
malanecoraLetoThe2nd: The vory same would happen if I have several distros, wouldn't it?13:21
LetoThe2ndmalanecora: what doyou mean?13:26
*** lusus <lusus!~lusus@62.91.23.180> has joined #yocto13:34
*** rcw <rcw!~rcw@23.91.150.113> has joined #yocto13:38
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto13:42
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto13:52
*** AndersD_ <AndersD_!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has quit IRC13:54
*** tijko <tijko!~tijko@unaffiliated/tijko> has joined #yocto14:05
*** radsquirrel <radsquirrel!~bradleyb@mail.fuzziesquirrel.com> has quit IRC14:09
*** radsquirrel <radsquirrel!~bradleyb@mail.fuzziesquirrel.com> has joined #yocto14:09
*** jofr <jofr!~jof@90.184.86.154.1.fullrate.ninja> has joined #yocto14:13
jofr'lo! I'm having problems with "-c devshell".. I've set my OE_TERMINAL to "tmux-new-window" but when the new window is spawned it says "sort: cannot read: /dev/fd/63: No such file or directory" .. For this shell, the pseudo stuff is in /dev/fd/20 and 21.14:15
jofrAnyone come a across this problem?14:15
jofrIt's sumo, btw.14:15
*** dmoseley <dmoseley!~dmoseley@216.186.248.188> has joined #yocto14:16
*** kaspter <kaspter!~Instantbi@2409:8928:e1a:6c1c:7031:b3c4:fa36:36e4> has joined #yocto14:16
malanecoraLetoThe2nd: "but then you'd have a commit in the repo if you modify one image, and see the commit for the other images too"14:30
LetoThe2ndmalanecora: you would only share the distro across projects if the projects are suited for it. in that case, it would totally be fine if you see the commit everywhere.14:32
malanecoraLetoThe2nd: Oh, ok, I got it. I misunderstood the sentence. Thank you!14:33
*** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has quit IRC14:54
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC14:57
*** kroon <kroon!~kroon@213.185.29.22> has quit IRC14:59
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC15:00
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto15:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto15:04
*** malanecora <malanecora!b23cc82c@gateway/web/freenode/ip.178.60.200.44> has quit IRC15:06
*** frsc <frsc!~frsc@200116b82496c100a0090255879e121a.dip.versatel-1u1.de> has quit IRC15:07
*** rcw <rcw!~rcw@23.91.150.113> has quit IRC15:09
*** tprrt <tprrt!~tprrt@217.114.201.133> has quit IRC15:14
yoctiNew news from stackoverflow: Configuration of spi slave in device tree files for imx8 board <https://stackoverflow.com/questions/56152269/configuration-of-spi-slave-in-device-tree-files-for-imx8-board>15:15
* armpit sigh need to resubmit dropped patches15:22
RParmpit: ? :/15:23
armpitthere where a few more qa patches that got dropped when pybootchart hit the brakes15:24
armpitI think one needs to be re-factored as only part of the patch was taken15:25
armpitbtw, I figured out the ptest issue15:25
* armpit gives me a chance to double check and run on AB15:27
RParmpit: right, that patch needed major other work anyway :/15:28
RParmpit: they are on my todo list to come back to is/as/when I can15:29
armpitah, I am General Custer so I don't deal with Major stuff ; )15:29
RParmpit: ;-)15:30
armpitwell let me run through them again15:31
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC15:32
RParmpit: what was the ptest issue?15:32
armpitbtw. ptest, do we still wont one monolithic raw log or its it good enough that info is in the testimage.json?15:32
armpitptest: loop (ptest-runner) n- times... did not pass the test name15:33
RParmpit: currently we put the monolithic log and the individual logs in the json separately . I did plan to drop the monolithic log when we were sure we were getting sane results15:33
RPgetting sane ptest results has taken a bit of work :/15:33
armpitI am now saving raw logs on a per test bases15:34
armpiteasier to find errors15:35
erakisHi, it's probably a dumb question but if I call bitbake by setting first an environment variable `MY_VAR=1 && bitbake image`. How can I read the value of MY_VAR from a recipe ? xx = ${MY_VAR} ?15:39
*** Crofton <Crofton!~Crofton@mingus.hcro.org> has quit IRC15:47
RParmpit: the code splits the logs out per test15:47
RParmpit: you can likely just rely on that instead15:48
armpitRP, as parsed summary15:48
RParmpit: no, for ptest it wasn't a summary15:48
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC15:52
*** lusus <lusus!~lusus@62.91.23.180> has quit IRC15:53
armpithmm, the raw log has a bit more info in it other than pass/fail15:55
armpitFAILED:  wget--O-overrides--P15:55
armpitraw:15:55
armpitFAIL: wget--O-overrides--P15:56
armpit+ test x '!=' x15:56
armpit+ mkdir foo15:56
armpit+ busybox wget -q -O index.html -P foo http://www.example.org/15:56
armpitwget: bad address 'www.example.org'15:56
*** leitao <leitao!~leitao@2620:10d:c092:200::1:6842> has quit IRC15:56
armpitseems helpful to me15:57
*** leitao <leitao!~leitao@2620:10d:c092:200::1:6842> has joined #yocto15:57
armpitin anycase, dropping it from testimage.json seems like a good thing15:57
*** yacar_ <yacar_!~yacar@80.215.109.48> has quit IRC15:58
RParmpit: we need an overhaul of some of the logging in general :/15:59
armpittrue16:00
*** Crofton <Crofton!~Crofton@mingus.hcro.org> has joined #yocto16:02
armpitRP, do we want the ltp tests in Warrior?16:06
*** leitao <leitao!~leitao@2620:10d:c092:200::1:6842> has quit IRC16:08
*** comptroller <comptroller!~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net> has quit IRC16:09
*** kaspter <kaspter!~Instantbi@2409:8928:e1a:6c1c:7031:b3c4:fa36:36e4> has quit IRC16:10
*** leitao <leitao!~leitao@2620:10d:c092:200::1:6842> has joined #yocto16:11
RParmpit: probably not worth it?16:14
RParmpit: not sure16:14
*** Hodhr <Hodhr!~Hodhr@162.206.70.37.rev.sfr.net> has joined #yocto16:18
*** tprrt <tprrt!~tprrt@upc31-1-78-208-110-13.fbx.proxad.net> has joined #yocto16:19
*** rcw <rcw!~rcw@128.224.252.2> has joined #yocto16:21
*** jku <jku!~jku@dyx9b8yyyyyyyyyyyyyct-3.rev.dnainternet.fi> has quit IRC16:22
armpithmm, need to clarify QA then16:22
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC16:23
*** comptroller <comptroller!~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net> has joined #yocto16:27
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has quit IRC16:39
*** vineela <vineela!~vtummala@134.134.139.74> has joined #yocto16:42
*** pyrobby <pyrobby!~rob@cpc108965-cmbg20-2-0-cust775.5-4.cable.virginm.net> has joined #yocto16:44
RParmpit: I guess it if helps QA testing then yes, we should16:50
*** kapare <kapare!~kapare@38.127.66.236> has quit IRC16:51
RParmpit: loving the ptest results in https://autobuilder.yocto.io/pub/non-release/20190514-14/testresults/testresult-report.txt :)16:54
RP84/43000 failures16:54
*** AndersD <AndersD!~AndersD@h83-209-191-235.cust.a3fiber.se> has joined #yocto17:02
*** AndersD <AndersD!~AndersD@h83-209-191-235.cust.a3fiber.se> has quit IRC17:04
*** AndersD <AndersD!~AndersD@h83-209-191-235.cust.a3fiber.se> has joined #yocto17:04
*** AndersD_ <AndersD_!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has joined #yocto17:14
*** AndersD <AndersD!~AndersD@h83-209-191-235.cust.a3fiber.se> has quit IRC17:16
*** T_UNIX <T_UNIX!uid218288@gateway/web/irccloud.com/x-dqwsmalkmjfkwbyk> has quit IRC17:47
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC17:52
*** tprrt <tprrt!~tprrt@upc31-1-78-208-110-13.fbx.proxad.net> has quit IRC18:10
*** leitao <leitao!~leitao@2620:10d:c092:200::1:6842> has quit IRC18:11
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto18:15
*** AndersD_ <AndersD_!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has quit IRC18:21
*** Crofton <Crofton!~Crofton@mingus.hcro.org> has quit IRC18:25
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto18:30
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto18:31
*** Crofton <Crofton!~Crofton@mingus.hcro.org> has joined #yocto18:40
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC18:46
*** pyrobby <pyrobby!~rob@cpc108965-cmbg20-2-0-cust775.5-4.cable.virginm.net> has quit IRC18:53
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto18:54
*** berton <berton!~berton@181.220.86.53> has quit IRC19:02
*** berton_ <berton_!~berton@181.220.86.53> has joined #yocto19:02
*** berton <berton!~berton@181.220.86.53> has joined #yocto19:07
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC19:16
*** florian_kc is now known as florian19:16
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto19:17
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC19:22
*** aidanh_ <aidanh_!~aidanh@unaffiliated/aidanh> has joined #yocto19:28
*** aidanh <aidanh!~aidanh@unaffiliated/aidanh> has quit IRC19:28
*** aidanh_ is now known as aidanh19:28
*** berton_ <berton_!~berton@181.220.86.53> has joined #yocto19:36
*** berton <berton!~berton@181.220.86.53> has quit IRC19:38
*** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC19:39
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto19:42
Ad0fray, that meta-virtualization problem, people have been missing it for an entire year?19:53
*** tkoskine <tkoskine!tkoskine@kapsi.fi> has joined #yocto19:53
JPEWHmm.... I need a -native recipe to depend on a -cross recipe...20:08
RPJPEW: that sounds wrong20:09
JPEWYes, it does..... what I really want is diffoscope-native to be able to use the cross binutils as helpers20:10
RPJPEW: I suspect binutils-native might have enough cross-fu ?20:10
RPJPEW: at the back of my mind is the thought we may be able to have one binutils these days...20:11
RPJPEW: I guess I can't remember how we configure binutils-native20:11
JPEWhmm, ya maybe. binutils-native doesn't have the target named tools (e.g. "arm-linux-readelf")... maybe thats not so imporant with binutils these days and invoking the bare "readelf" is fine?20:12
RPJPEW: it depends which targets were configured into it20:12
* RP slowly seems to be simplifying the toolchain20:13
JPEWAh, --enable-targets=all in the -native case for binutils.... that will work20:14
RPJPEW: I had vague memories of writing that20:14
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC20:14
JPEWRP: Well, I have the test working now; of 4119 packages in core-image-minimal, 720 aren't reproducible20:15
JPEWMost of those seem to be -dbg packages20:16
RPJPEW: having numbers is a great start!20:19
RPJPEW: I'm a little surprised the dbg packages are showing issues, I thought we had that sorted :/20:19
JPEWRP: Ya, I haven't dug into to it too much. It wouldn't suprise me if it's some common core problem that fixes most of them.... trying to get diffoscope to decode the elf files will help significanly20:20
RPJPEW: you're using the reproducible  bbclass right?20:20
JPEWYep20:21
RPok. Hopefully something simple20:21
RPregardless, would be great to have tests and numbers20:21
*** berton <berton!~berton@181.220.86.53> has joined #yocto20:23
*** berton_ <berton_!~berton@181.220.86.53> has quit IRC20:25
kroonRP, JPEW, thats what I've seen too in my buildhistory, in particular e2fsprogs-dbg having some strange diff churn inbetween rebuilds20:26
kroona rename /sbin/.debug/mkfs.ext2.e2fsprogs -> ./sbin/.debug/mke2fs.e2fsprogs for no apparent reason20:28
JPEWkroon: On mine it apparently decided to rename /sbin/.debug/fsck.ext3 -> /sbin/.debug/fsck.ext220:39
RPkroon: the rename is probably just bad matching of the various symlinks or hardlinks20:39
RPthose should be the same file hardlinked20:40
RPprobably a determinism issue related to directory ordering in buildhistory?20:40
kroonJPEW, yeah, think I've seen that one too20:42
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto20:43
RPe2fsprogs is a little unique in that it has a load of files which are all hardlinked20:44
JPEWRP: ... but we split those hardlinks across multiple packages?20:48
JPEWSpecifically, e2fsck is in it's own package from fsck.ext220:48
JPEWOh, wait its not20:48
JPEWNevermind :)20:49
*** jofr <jofr!~jof@90.184.86.154.1.fullrate.ninja> has quit IRC21:07
aehs29has anyone figured out a way not to get cikced out of the room every now and then to authenticate again?21:08
aehs29or am I the only one with this problem21:08
aehs29kicked*21:08
JPEWHow often?21:08
aehs29about every week21:08
JPEWYa me too21:09
JPEWI usually attributed mine to my CPU being too loaded from doing an overnight build21:10
*** nate02 <nate02!~nate02@mail.validmanufacturing.com> has quit IRC21:10
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has quit IRC21:11
*** flying_sausages <flying_sausages!~flying_sa@static.88-198-40-49.clients.your-server.de> has quit IRC21:12
*** flying_sausages <flying_sausages!~flying_sa@static.88-198-40-49.clients.your-server.de> has joined #yocto21:15
*** berton <berton!~berton@181.220.86.53> has quit IRC21:15
*** rcw <rcw!~rcw@128.224.252.2> has quit IRC21:15
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC21:20
RPaehs29: my client has an auth plugin...21:26
aehs29RP: ok I'll look into that21:27
RPseebs: I pushed those SPDX headers fwiw21:34
RPseebs: we could probably simplify further and drop the COPYRIGHT files now if we wanted as things are simpler21:34
*** vmeson <vmeson!~rmacleod@24-52-238-240.cable.teksavvy.com> has joined #yocto21:44
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC21:47
*** tijko <tijko!~tijko@unaffiliated/tijko> has quit IRC21:51
*** agust <agust!~agust@p508B6FD6.dip0.t-ipconnect.de> has quit IRC21:55
*** ab0oo <ab0oo!~Thunderbi@2603:3024:18b5:e0e2:b44b:46d9:c3c3:6f06> has joined #yocto22:11
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-znahcuwgotyjgfua> has joined #yocto22:32
*** ab0oo <ab0oo!~Thunderbi@2603:3024:18b5:e0e2:b44b:46d9:c3c3:6f06> has quit IRC22:52
*** JaMa <JaMa!~martin@ip-217-030-068-212.aim-net.cz> has quit IRC23:11
*** JaMa <JaMa!~martin@ip-217-030-068-212.aim-net.cz> has joined #yocto23:23
*** nayfe <nayfe!uid259604@gateway/web/irccloud.com/x-qksuwvwgshkcpnqv> has quit IRC23:30
*** vineela <vineela!~vtummala@134.134.139.74> has quit IRC23:36
*** fatalhalt <fatalhalt!~fatalhalt@c-67-163-60-93.hsd1.il.comcast.net> has joined #yocto23:38
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC23:40
*** vineela <vineela!vtummala@nat/intel/x-zbwtyqtaboujryar> has joined #yocto23:47
*** armpit <armpit!~armpit@2601:202:4180:c33:d909:eb3d:d2ab:fd1d> has quit IRC23:59

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!