**** BEGIN LOGGING AT Tue Jun 10 02:59:59 2014 Jun 10 08:09:52 good morning Jun 10 08:14:19 hi mckoan Jun 10 08:20:17 hi guys Jun 10 08:24:20 hi hrw Jun 10 08:26:34 hi woglinde, hrw Jun 10 08:32:57 morning Jun 10 08:34:05 hi kroon Jun 10 08:35:52 woglinde, nice work on perf Jun 10 08:40:05 thanks kroon Jun 10 08:40:15 and it was not this hard Jun 10 08:40:29 morning woglinde, kroon, all Jun 10 08:40:29 just looking what perl and python and bash is used for Jun 10 08:42:03 hi bluelightning Jun 10 08:42:12 woglinde: have you tried running perf test for self-tests ? Jun 10 08:42:24 suihkulokki nope as I said Jun 10 08:42:34 aehm I meant written Jun 10 08:42:40 I tested only perf top Jun 10 08:42:53 with the perf-core package Jun 10 08:42:58 ok Jun 10 09:07:35 http://www.angstrom-distribution.org/ looks beefed up Jun 10 11:38:36 hi. anyone using raspberry pi bsp? it's been fetching bcm2835-bootfiles for almost an hour Jun 10 13:04:29 is there a bitbake command to delete old stuff from the images folder? Jun 10 13:04:53 and maybe a way to say that I do not need to keep/timestamp every image I build? Jun 10 13:06:35 how about a general cleanup command Jun 10 13:06:45 that quickly redeems space Jun 10 13:06:52 tasslehoff: set RM_OLD_IMAGE = "1" Jun 10 13:07:02 always when the shit hits the fan I also run out of diskspace Jun 10 13:07:31 I Jun 10 13:07:33 the build system does have a way of checking and warning before disk space runs out... Jun 10 13:08:32 I am having a super bizarre oebb.sh issue... Jun 10 13:08:44 BB_DISKMON_* Jun 10 13:09:26 every time I do a oebb.sh update I end up with strange merge conflicts Jun 10 13:09:35 anyone seen that? Jun 10 13:09:44 on one file Jun 10 13:09:50 I just cannot understand why Jun 10 13:09:54 bluelightning: thanks :) Jun 10 13:10:08 diskmon is setup here, so that "saved me" Jun 10 13:10:48 pompomJuice: I'm not sure, but despite what its name might suggest, oebb.sh is an angstrom thing not OE or BitBake Jun 10 13:10:56 bluelightning: are you after pre-2003 OE commits? Jun 10 13:10:57 aah yea Jun 10 13:11:01 koen: yes Jun 10 13:11:39 koen: I did have a look at buildroot-oz but whilst interesting that doesn't seem to have the history I'm looking for Jun 10 13:11:44 I think those were at sf.net, but I'm not sure Jun 10 13:11:49 "before my time" Jun 10 13:11:56 The situation is bizarre, my company layer is ends up with a file in conflict even though if you do a git pull manually nothing happens and the oebb update says the layer was up to date Jun 10 13:11:58 didn't think I'd ever say that :) Jun 10 13:12:21 koen: heh Jun 10 13:12:21 pompomJuice: 'git status' ? Jun 10 13:12:40 already up to date Jun 10 13:12:44 this is bizarre Jun 10 13:12:47 koen: well, it doesn't seem like there are any repos in the OE project on sf.net now at least... I'll poke kergoth when he gets online Jun 10 13:13:04 it has suddenly started happening with this one patch Jun 10 13:13:34 bluelightning: I remember that a few old things were delete to stop confusing people Jun 10 13:13:35 after the UU it contains the text <<<<<<< Updated upstream Jun 10 13:13:41 but again, note 100% sure Jun 10 13:13:54 -e Jun 10 13:15:58 wow this is even more bizarre Jun 10 13:20:59 On branch impedo-duo-yocto1.6 Jun 10 13:20:59 # Unmerged paths: Jun 10 13:20:59 # (use "git reset HEAD ..." to unstage) Jun 10 13:20:59 # (use "git add/rm ..." as appropriate to mark resolution) Jun 10 13:20:59 # Jun 10 13:20:59 # both modified: patches/bitbake-fetch-accurev.patch Jun 10 13:22:13 every time I change the file to what it needs to be the error goes away Jun 10 13:22:37 git pull does nothing Jun 10 13:23:01 but ./oebb.sh update somehow brings back that status... even though it reports that layer being up to date Jun 10 13:23:42 and its on my buils server, I do not edit files there or commit them Jun 10 13:24:51 git push & git pull says everything is up to date Jun 10 13:25:20 oebb update somehow does not think so, brings back the UU on that file. Jun 10 18:57:14 ok Jun 10 22:48:27 What is the meta-openembedded/meta-oe layer? Is it special? Jun 10 22:49:01 it is just a collection of reciupes with no other home Jun 10 22:49:13 Ok Jun 10 22:49:14 no more special than any other layer Jun 10 22:49:38 I was confused by a guide, so it seemed that due to "metaness" or something I would not need to include other OE layers Jun 10 22:50:00 you start with oe-core/meta and add from there Jun 10 22:50:01 But adding meta-openembedded/meta-filesystems fixed my fuse issue Jun 10 22:50:05 cool Jun 10 22:50:13 I assume fuse is in therer? Jun 10 22:50:23 do not forget to turn on fuse in the kconfig Jun 10 22:50:56 yep Jun 10 22:50:58 kconfig? Jun 10 22:51:10 wait, kconfig ? Jun 10 22:51:12 kernel config Jun 10 22:51:22 do we do that by hand ? Jun 10 22:51:48 i'm hoping that has already been taking care of, since i'm using a layer which provides me recipes for complete images Jun 10 22:52:14 (fixing a dependency issue, not adding fuse from scratch) Jun 10 22:52:15 just something to worry about :) **** ENDING LOGGING AT Wed Jun 11 02:59:58 2014