**** BEGIN LOGGING AT Thu Mar 24 02:59:58 2016 Mar 24 17:49:09 http://marguskoiduste.eu/images/the_general_problem-974.png Mar 24 17:59:07 kergoth: :-) Mar 24 17:59:37 i used to have the one posted on my cubicle wall years ago Mar 24 18:00:07 nice Mar 24 18:49:37 kergoth: http://www.digi.com/resources/documentation/digidocs/90001945-13/default.htm#task/yocto/t_customize_root_file_system_yocto.htm%3FTocPath%3DDigi%2520Embedded%2520Yocto%7CSystem%2520development%7CFirst%2520steps%7C_____3 Mar 24 18:52:14 kergoth: that's what I'm talking about: Mar 24 18:52:43 If you want to add a package to your image, for example strace, add the following to your project’s conf/local.conf file: Mar 24 18:52:46 IMAGE_INSTALL_append = " strace" Mar 24 18:53:01 ah, interesting Mar 24 18:53:26 i didn't realize digi was using yocto. pretty amusing, since i was working in tech support for them while i was working on OZ and while we started OE :) Mar 24 18:55:43 I just wanted to check to see if I handled my request to oe-core correctly here: http://lists.openembedded.org/pipermail/openembedded-core/2016-March/119376.html Mar 24 18:55:52 I don't usually submit to OE Mar 24 18:56:14 also, not really sure what the policy is for updating past releases Mar 24 18:57:58 minor quibble, the fido bit should be in the subject of all the patches, via --subject-prefix (iirc), and i think the upstream-status should be above the From:, so it doesn't end up in the commit message if the patch is applied with git-am, but that's minor, they should accept it without that. the only real policy on past releases is that it's not so old it's unmaintained, and it's a bugfix, not a feature Mar 24 18:58:09 clearly that's a bugfix, so it should be appropriate. the fido maintainer would pull it in if appropriate Mar 24 18:58:20 afaik, anyway Mar 24 18:58:33 the policy is described there: https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance Mar 24 18:58:46 good call, forgot about that page Mar 24 18:58:52 kergoth: thanks, that makes sense to me, and I considered putting the fido bit in all of the patches, but didn't know for sure Mar 24 18:59:07 abelloni: thanks Mar 24 18:59:31 Well I had to dig it up to include the link in the slides for ELC Mar 24 18:59:40 ah, cool Mar 24 19:00:16 if I haven't heard anything for a bit, I'll resubmit fixing the minor things and making sure to include Joshua on the mailing Mar 24 19:00:18 thanks again Mar 24 19:00:30 if you submit with changes, change PATCH to PATCHv2 in the subject lines Mar 24 19:00:43 this, I know :D Mar 24 19:00:46 :) Mar 24 19:00:51 just checking Mar 24 19:02:50 PATCHv2 or "PATCH v2" ? :) Mar 24 19:13:05 please use "PATCH v2"!! :-) Mar 24 19:13:37 i have a bunch of gmail filters that separate out the discussions from the patches in the various OE mailing lists into separate folders Mar 24 19:14:21 but the filters can't seem to be able to filter on partial words so "PATCHv2" doesn't get caught in a filter for "PATCH" :-( Mar 24 19:14:35 besides, the guidelines specify the space, so please follow that ;-) Mar 24 19:15:37 space is indeed preferred, but folks often use both, might need to add some new filters :) Mar 24 19:16:19 yea, it's only a matter of time before i do, hopefully PATCHv5 or PATCHv6 is the most i'll need... for each mailing list... Mar 24 19:16:34 * kergoth chuckles Mar 24 19:41:58 Somehow when running bitbake core-image-minimal -c populate_sdk, it is giving me errors about do_compile in qtsvg. I have not even included qtsvg at all. I did include it in local.conf at one point but now I removed it. Mar 24 19:42:04 I tried running cleanall and it didnt help Mar 24 19:42:34 This is what I get in the log file: http://pastebin.com/M6zyPPuk Mar 24 19:55:42 riz___: use bitbake -g to figure out the dependency chain. Mar 24 19:56:49 so, "bitbake -g core-image-minimal"? Mar 24 19:57:33 bitbake -g -c populate_sdk core-image-minimal Mar 24 19:59:10 I've also found pawing through the environment construction leading up to the build (the "bitbake -e" option) can be helpful when trying to figure out why something is happening Mar 24 20:00:22 OK thanks Mar 24 20:01:08 I have always done bitbake core-image-minimal -c populate_sdk Mar 24 20:01:13 But I guess order doesnt matter Mar 24 20:01:16 IT worked anyway Mar 24 21:29:24 When I get bitbake errors that it cannot fetch files because the URL is broken what file can I alter so that it tries and fethes from the correct URL? Mar 24 21:30:37 the bb file Mar 24 21:31:44 So when it says "WARNING: Failed to fetch URL http://downloads.sourceforge.net/project/cdrtools/alpha/cdrtools-3.01a31.tar.bz2, attempting MIRRORS if available", what bb file is that coming from? Mar 24 21:32:05 How can I trace that? Mar 24 21:32:06 the cdrtools bb file Mar 24 21:36:15 Thanks Mar 24 21:50:53 did something happen to the ssh-server-openssh IMAGE_FEATURE recently? **** ENDING LOGGING AT Fri Mar 25 02:59:59 2016