**** BEGIN LOGGING AT Thu May 09 02:59:56 2019
May 09 06:50:04 <mckoan> good morning
May 09 07:31:55 * alessioigor waves all
May 09 09:18:48 <miwa> So.. the practice of making a recipe .inc-file that constructs the src uri from the package version, and then making a small recipe including that. I'm assuming this is to make it easier to make a recipe for a newer version but I tried that in my own layer and I'm having problems with the search path for file:// URIs. The recipe I'm working on is sysstat. Have I misunderstood the concept of .inc files like
May 09 09:18:54 <miwa> these?
May 09 09:24:27 <leitao> hi. I would like to send a patch to a poky receipt (meta/recipes-graphics/wayland/weston-init/weston-start). What is the most appropriate mailing list to send it to?
May 09 09:48:38 <kanavin_> leitao, openembedded-core list
May 09 09:48:46 <leitao> kanavin_ thanks
May 09 09:55:37 <rburton> miwa: unless you have a need (ie two versions of the same recipe) then splitting bb/inc is mostly overkill
May 09 09:55:58 <rburton> the search path remains the same, it will look in files/ and ${PN}
May 09 09:58:25 <miwa> rburton: the case here is that there is a version in poky/meta and I want to upgrade the version using a recipe in my own layer. The split is already made in poky and I was trying to make sense of it
May 09 09:59:57 <rburton> presumably your problem is that the .inc has patches and they're not being found because bitbake is looking alongside your recipe
May 09 10:00:22 <rburton> (example 1 of why the bb/inc split is a pain unless handled very well)
May 09 10:11:55 <miwa> rburton: yes, exactly. Now I rewrote the recipe because I didn't really need the patches and files included. Still, it's nice to know that this bb/inc split is not a common good-practice thing :)
May 09 10:12:21 <rburton> its historical from when oe used to ship e.g. three versions of a recipe
May 09 10:12:44 <rburton> but without that level of testing the inc just becomes specific to a single version, so there's no point
**** BEGIN LOGGING AT Thu May 09 12:03:25 2019
May 09 13:10:27 <JPEW> RP: No problem. I wrote an embarrsing number of ARM/Thumb symbol decoders for our in house RTOS :)
May 09 13:15:22 <sveinse> Is there some "generic" armv7 machine in Yocto? We're experimenting with running docker containers on our HW, even 3rd party containers. My impression is that there are a lot of variants under the arm umbrella, but I find to find what Docker assume by "armv7" machine.  I'm trying to determine what kind of MACHINE I need to use for these container images. Of course the container would be related to the
May 09 13:15:28 <sveinse> HW-specific kernel running on the host machine.
May 09 13:26:41 <RP> sveinse: qemuarm?
May 09 13:29:58 <sveinse> RP: yeah, let me try that. Thanks.
May 09 13:54:55 <JPEW> Is there a way to get python unittest to generate ptest compatible output?
May 09 13:57:25 <RP> JPEW: not sure. I'd guess the python recipes do that in their ptest?
May 09 13:57:53 <JPEW> Ok, I'll take a look
May 09 13:59:36 <RP> JPEW: think its just a sed :/
May 09 13:59:42 <JPEW> Ya, I saw that
May 09 14:20:03 <yocti> New news from stackoverflow: Bitbake build consumes more space <https://stackoverflow.com/questions/39953304/bitbake-build-consumes-more-space> || how to delete deploy/images/beaglebone dir in yocto <https://stackoverflow.com/questions/45627686/how-to-delete-deploy-images-beaglebone-dir-in-yocto>
May 09 14:32:11 * armpit gives all bugs to rburton 
May 09 14:32:21 <paulbarker> JPEW, RP: https://gitlab.com/b5/BetaTest/betatest/blob/master/betatest/amtest.py
May 09 14:32:45 <paulbarker> That's what I wrote a long time back that I still use
May 09 15:20:38 <armpit> RP, has anyone checked to see if the patchtest server is alive ?
May 09 15:21:09 <armpit> there have been no new changes to code for a long time
May 09 15:25:43 <RP> armpit: we know its running but not working
May 09 15:25:51 <armpit> k
May 09 15:28:10 <JPEW> paulbarker: Excellent. Thanks
May 09 15:29:19 <paulbarker> JPEW: It's on PYPI as part of https://pypi.org/project/betatest/.
May 09 15:29:32 <JPEW> paulbarker: Just installed it :)
May 09 15:29:52 <paulbarker> I need to push a new release, I've added a subtest wrapper and some more tests
May 09 15:43:41 <ab0oo> Hoping to get some help with Toaster:  When I run toaster from the command line, I get the button to add new projects and and actually set up builds.  When I run it through apache, no such button exists.  I've carefully followed the instructions at https://www.yoctoproject.org/docs/2.8/toaster-manual/toaster-manual.html
May 09 15:43:56 <ab0oo> if this is the wrong place to ask, please redirect me.
May 09 17:07:23 <milloni> hello yocto folks, i'm working with a build that I do not really understand, and I'm new to yocto
May 09 17:07:42 <milloni> i'm trying to remove a package from my build
May 09 17:08:19 <milloni> commenting out #IMAGE_INSTALL += "system-core-adbd" doesn't do anythin
May 09 17:08:32 <milloni> and neither does adding IMAGE_INSTALL_remove += "system-core-adbd"
May 09 17:09:10 <milloni> git grepping the repo for system-core-adbd only returns the above IMAGE_INSTALL line
May 09 17:09:15 <milloni> what am i missing?
May 09 17:19:47 <kroon> milloni, you can use "bitbake -e" to investigate
May 09 17:20:35 <kroon> milloni, it will tell you how variable values are constructed
May 09 17:29:44 <ab0oo> I'm sorry, my client died.  Did I miss a reply to my "I can set up builds with toaster when run from the command line, but not from apache" question?
May 09 17:58:13 <jrypkec> Hi, I'm repackaging an old app to be built by oe_runmake. These two errors seem very contradictory to me. Yocto indicates that it knows about my libName but then complains it can't find it.   ELF binary '/mypath/usr/lib/libName.so.1' has relocations in .text ERROR: myapp do_package_qa: QA Issue: /usr/bin/otherApp contained in package appPackage requires libName.so, but no providers found in RDEPENDS_myapp? [file-rdeps]
May 09 18:01:39 <rburton> it probably doesn't know that libname.so.1 has the soname libName.so because you're linking it wrong
May 09 18:13:43 <jrypkec> Thanks rburton! objdump shows that libName doesn't have an soname
May 09 19:23:45 <dburnsii> Hello everyone, my team and I are interested in using Yocto as an embedded linux solution, and are looking to bring someone in for a few days of training for the team. Does anyone have suggestions for trainers, particularly for targeting x86?
May 09 19:25:03 <milloni> dburnsii: linux foundation has yocto courses afaik
May 09 19:25:29 <milloni> https://training.linuxfoundation.org/training/embedded-linux-development-with-yocto-project/
May 09 19:29:54 <dburnsii> Didn't see the corporate solutions link until just now, that'll work, thanks!
May 09 19:30:02 <LetoThe2nd> dburnsii: obvious places to start looking are https://www.yoctoproject.org/community/ambassadors/ and https://www.yoctoproject.org/community/consultants/
May 09 19:30:14 <LetoThe2nd> dburnsii: especially the latter :)
May 09 19:35:36 <dburnsii> I was also told that Windriver is the main contributor and maintainer of the project, but my understanding was that they were just one of many?
May 09 19:36:54 <LetoThe2nd> dburnsii: they are certainly one of the top contributors and their folks do a lot of tedious work.
May 09 19:37:44 <LetoThe2nd> dburnsii: "main contributor"... thats a big word. i wouldn't say there is one. at least not right now.
May 09 19:40:36 <dburnsii> That does make sense. Thank you guys for pointing me in the right direction
May 09 19:40:52 <LetoThe2nd> have fun.
May 09 19:54:00 <dreyna> ab0oo : for Toaster questions please go ahead and send email to toaster@yoctoproject.org
May 09 20:21:13 <yocti> New news from stackoverflow: How can we pass a ${BASEWORK} directory from Bitbake recipe to CMAKE for using find library function from CMAKE? <https://stackoverflow.com/questions/56066878/how-can-we-pass-a-basework-directory-from-bitbake-recipe-to-cmake-for-using-f>
May 10 00:02:03 <black_13> is it possible to run the yocto tools on native osx or via virtualization
**** ENDING LOGGING AT Fri May 10 03:01:14 2019