**** BEGIN LOGGING AT Mon May 06 02:59:57 2019
May 06 13:14:17 <JPEW> RP: I take it the resulttool change looked like it would do what you want since you merged it?
May 06 13:21:32 <RP> JPEW: its in -next, not merged yet :)
May 06 13:24:14 <JPEW> RP: Ya.... I was more curious if you thought that would do what you needed :)
May 06 13:25:47 <RP> JPEW: it looked like it, I've not tested it yet
May 06 13:26:29 <JPEW> Ok. If you could also pull in master-next of meta-mingw next time you do a master-next build on the AB, I would appreciate it
May 06 13:29:14 <RP> JPEW: we can trigger a specific build if that is helpful?
May 06 13:30:18 <RP> JPEW: https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/568
May 06 13:30:53 <JPEW> excellent. Thank you
May 06 13:39:28 <tlwoerner> LetoThe2nd: "PS: Yes, its actually *ME* writing that." <-- lol
May 06 13:40:38 <bl4ckb0ne> is there documentation about running the image from the deploy folder without runqemu ?
May 06 13:40:55 <bl4ckb0ne> i have a weird setup and paths are different from my container
May 06 13:42:13 <Crofton> tlwoerner, sadly I agree with LetoThe2nd
May 06 13:43:01 <tlwoerner> Crofton: absolutely! me too i agree. it's humourous he felt it necessary to add the PS at the end ;-)
May 06 13:44:22 <Crofton> otherwise no on ewould have believed him
May 06 13:48:19 <paulbarker> The coffee is always required, the alcohol is only required when builds fail
May 06 14:09:36 <tlwoerner> paulbarker: haha, true :-)
May 06 14:17:29 <erakis> Hi, what is the best way to set opkg server address in opkg.conf ? A bbappend of 'meta/recipes-devtools/opkg/opkg/opkg.conf' ?
May 06 14:18:46 <bjobjo> have you tried distro-feed-configs? It may do what you want
May 06 14:18:55 <bjobjo> https://layers.openembedded.org/layerindex/recipe/1132/
May 06 14:20:09 <bjobjo> alternatively, you could manually create the -feed files and install them in a separate recipe in one of your layers
May 06 14:42:58 <erakis> bjobjo: Thank you, I'm looking at it now. Hope it work with Fido branch.
May 06 15:15:59 <LetoThe2nd> tlwoerner: :-)
May 06 15:16:44 <LetoThe2nd> tlwoerner: i felt like i should step up and say something along those line, as i feared that somebody would misinterpret the "excessively appreciated" beers
May 06 15:18:43 <LetoThe2nd> Crofton: tlwoerner: in fact it was paul and me working on the last beers there. which was a good thing (TM), but for those who do not know me good enough it might easily be misunderstood as being representative for YP/OE folks.. and thats what i certainly should *NOT* be
May 06 16:35:08 <erakis> Hi, what is the proper protocol to use for custom (closed source) opkg feed (http, https, ssh, etc...) ? Currently, I'm using the https protocol with the form `src/gz all https:<user>:<passw>@myserver.com/all`.
May 06 17:27:49 <dfrey> Is there a bitbake command to figure out where in the filesystem  a recipe is defined?
May 06 17:28:51 <kergoth> bitbake -e somerecipe | grep FILE=
May 06 17:29:04 <kergoth> the 'FILE' variable holds the path to the recipe (technically, the parsed file)
May 06 17:40:26 <dfrey> kergoth: Thanks
May 06 17:40:47 <kergoth> np
May 06 17:45:05 <prosper0> Hi everyone. I'm wondering how company/people manage u-boot changes for multiple platform/machine as they add more projects. Fork U-boot repo vs bbappends? Copy existing board vs modification existing board?
May 06 17:47:14 <Crofton> bbappends and upstream everything you can?
May 06 17:50:28 <JPEW> prosper0: For anything COTS (e.g. raspberry pi), bbappends (and upstream if relevant). Anything custom in house, a u-boot fork. We always end up making a new board to get some of the particulars about our software updates to work.
May 06 17:59:37 <prosper0> Hmm i suppose by creating your own you are trading off getting automatic fix from the original board maintainer. Is that right JPEW?
May 06 18:14:05 <JPEW> prosper0: Right, thats not usually to much of an issue in those cases since we are building up our own board around the SOC. We start with the SOC vendor u-boot and have to make a lot of modifications from there
May 06 18:15:00 <JPEW> Which is why we try to use the upstream u-boot as much as possible for COTS stuff... that way we get the latest and greatest more easily
May 06 18:18:44 <JPEW> Also, you are generally having a bad day if you have to update u-boot in the field ;)
May 06 18:31:21 <prosper0> field update will suck. But i was thinking more in line of a new project base on the same board
May 06 18:38:57 <prosper0> Are there modifications, that isn't upstream material, but is common to all your boards? If so how are those modification applied?
May 06 18:42:17 <JPEW> Yes, for our SW update support we have a custom u-boot command we have to run as part of the boot sequence. Its a patch in a bbappend for the COTS and committed in the forked u-boot for the customs platforms.
May 06 18:42:56 <JPEW> I should probably clarify that we only use COTS for internal prototyping, so that sort of thing is deemed acceptable to be able to keep upstream more easily
May 06 20:08:23 <yocti> New news from stackoverflow: Unable to start bitbake server <https://stackoverflow.com/questions/48132054/unable-to-start-bitbake-server>
May 06 20:38:29 <yocti> New news from stackoverflow: How can I installed a python module that doesn't have it's own recipe? <https://stackoverflow.com/questions/56012106/how-can-i-installed-a-python-module-that-doesnt-have-its-own-recipe>
May 06 21:08:34 <yocti> New news from stackoverflow: How can I install a python module that doesn't have it's own recipe? <https://stackoverflow.com/questions/56012106/how-can-i-install-a-python-module-that-doesnt-have-its-own-recipe>
May 06 23:07:50 <prosper0> Thanks to JPEW for answering my questions!
**** ENDING LOGGING AT Tue May 07 02:59:57 2019