**** BEGIN LOGGING AT Thu Feb 07 02:59:58 2013 Feb 07 07:27:45 Hi everybody. Has anyone encountered problems compiling qt4-x11-free? It seems like during the configuration of the webkit, it's trying to use QtMobility from my host machine, leading to a compilation error afterwards Feb 07 07:29:05 cross-compiling always a huge source of fun... Feb 07 07:31:50 Indeed :) Feb 07 07:35:06 I seem to remember similar problems from years ago, but don't remember how I handled it Feb 07 08:01:58 good morning Feb 07 08:17:38 Hi all ! Feb 07 09:05:50 ls Feb 07 09:05:54 oups Feb 07 09:06:23 no files found Feb 07 09:07:02 :) Feb 07 09:36:40 is it possible, when in a devshell to execute commands such as do_configure do_whatever ? Feb 07 09:37:12 yes Feb 07 09:37:20 use the scripts located in temp Feb 07 09:39:05 ok. All the scripts are copied in temp at the beginning of the build, or do they add after beeing executed ? Feb 07 09:39:53 ? Feb 07 09:40:09 no they are created when the step will be executed Feb 07 09:40:23 ok Feb 07 09:40:32 for instance when compile is running the run.do_compile script is generated Feb 07 09:40:33 morning all Feb 07 09:40:37 hi bl Feb 07 09:40:41 Hi Feb 07 09:40:52 ok. Feb 07 09:41:31 And if I do bitbake -c listtasks sometarget, is the list in the order of task execution ? Feb 07 09:41:38 morning! Feb 07 09:41:55 good morning Feb 07 09:42:51 uhm Feb 07 09:43:01 never heard about listtasks yet Feb 07 09:46:13 it lists the tasks that will be ran to do the recipe. Feb 07 09:47:16 execpt for the task listtasks it self ... Feb 07 09:47:41 hm Feb 07 09:47:50 just try Feb 07 09:47:55 and you will see Feb 07 09:48:31 ascor_: listtasks is random order Feb 07 09:48:57 woglinde: listtasks is very old command Feb 07 09:49:07 just one of those less popular Feb 07 09:49:24 argl, it might be interested to have them in order ... Feb 07 09:49:29 how many of you remember "bitbake --interactive"? Feb 07 09:50:00 Never heard of it ! Feb 07 09:50:10 hrw intressting never needed it Feb 07 09:51:06 it was added in 2004-2006 iirc Feb 07 09:52:21 any of you know good place to have support in building qt5 with oe ? I'm going from fail to fail Feb 07 09:52:41 ascor_ pay someone? Feb 07 09:53:05 I'm already payed for that ;) Feb 07 09:53:40 oh intressting Feb 07 09:54:07 maybee was the wrong one Feb 07 09:54:14 yep Feb 07 09:54:18 I'm joking Feb 07 09:54:30 I am not payed for that Feb 07 09:54:40 ascor_: haha Feb 07 09:55:23 I just have to find a quick way to test a subcontractors job who began a developpment using qt5 Feb 07 09:55:50 intressting Feb 07 09:56:30 ascor_: grab any distro with qt5 packages and compile his soft? Feb 07 09:56:49 I found quite easy to get in buildroot, but openembedded is much harder Feb 07 09:56:52 hrw which distro has qt5 packages? Feb 07 09:56:53 * bluelightning would like to know the current state of the qt5 recipe efforts also Feb 07 09:56:58 my target is an embedded target Feb 07 09:57:55 okay till later Feb 07 09:58:35 woglinde: https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-proper - packages for ubuntu Feb 07 10:00:16 i made a recipe for a package that only contains php scripts, so i added "inherit allarch" but bitbake fails on (file: 'do_package_qa', lineno: 58, function: do_package_qa) with "KeyError: 'allarch'" Feb 07 10:00:17 any idea ? Feb 07 10:04:59 JaMa: have few minutes? Feb 07 10:05:06 apparently, it's denzil related Feb 07 10:05:22 JaMa: ping me when online Feb 07 10:13:14 hrw: ping Feb 07 10:14:17 JaMa: dwarfutils, google-glog, google-perftools, libmcrypt, libmemcached, libunwind, memcached, onig, tbb on a way to OE - prepare for discussion where to put them Feb 07 10:15:49 hrw: first idea was meta-webserver, but maybe not Feb 07 10:16:04 will see in a discussion Feb 07 10:23:59 afournier: that is definitely a bug Feb 07 10:40:14 Are all of those do_whaterver scripts python scripts ? Feb 07 10:41:08 hello Feb 07 10:41:39 Fortget my question, answer was on line 1 fo the file Feb 07 10:51:11 sent Feb 07 10:53:41 hi stefamn_schmidt Feb 07 10:54:44 moin woglinde Feb 07 12:23:25 stefan_schmidt_w, what are you up to these days/ Feb 07 12:28:44 bluelightning, my least favorite part of FOSDEM is the bit where I get sick afterwards :) Feb 07 12:29:02 mickeyl usde to have that problem Feb 07 12:30:36 lol Feb 07 12:30:53 I am getting sick now from school Feb 07 12:31:51 crofton how was fosdem this year? Feb 07 12:33:22 woglinde: :} Feb 07 12:33:33 he zecke Feb 07 12:33:51 I am reading no silver bullets at the moment Feb 07 12:33:57 what a nice timeless papaer Feb 07 12:35:01 Crofton|work: Doing good old coding work. Coding EFL for Samsung for Tizen more specifically. Feb 07 12:35:14 Crofton|work: I had to drive a car from Berlin to home as friend got terrible fosdem flu ;( Feb 07 12:35:15 stefan nice Feb 07 12:35:34 hrw not so nice Feb 07 12:35:39 heh, Daniel also came back with a cold from FOSDEM :) Feb 07 12:35:54 stefan_schmidt_w: I noticed recently that Tizen still exists - got 50$ amazon gift card due to some comment when they started in May 2012 Feb 07 12:36:17 #tizenallthethings Feb 07 12:36:29 yes! Feb 07 12:36:43 so you finished your degree OK? Feb 07 12:36:56 Crofton|work: ? Feb 07 12:36:59 It is somehow possible to change opkg tmpdir in opkg.conf? Feb 07 12:37:10 (for example, I want to download to /root not to /tmp) Feb 07 12:37:35 bluelightning: i think the bugs come from the bitbake including insane.bb for no reason Feb 07 12:37:43 the bug* Feb 07 12:38:31 Crofton|work: yeah, diplom computer science. Finished quite good actually to my surprise. :) And then moved to London to work for Samsung UK. Feb 07 12:45:41 very good Feb 07 12:46:28 we need to do more devleoper reruiting, everyone is getting jobs :) Feb 07 12:47:11 crofton who is we? Feb 07 12:49:38 OE Feb 07 12:50:12 We need to document that learning OE is a good path to getting work :) Feb 07 12:51:39 +1 Feb 07 12:52:31 basically, I want to make sure that we attract new people to the project Feb 07 12:53:33 hm Feb 07 12:54:14 sell mor products Feb 07 12:54:26 :) Feb 07 12:54:43 and get more BSP's out for entry level products Feb 07 13:11:53 guys - we do have xfce recipes but does someone has bootable xfce-image recipe? Feb 07 13:12:52 i understood the "KeyError: 'allarch'" thing, if you inherit allarch then don't leave any ELF in ${D}, two ELF got lost in my php repository Feb 07 13:15:38 afournier ;) Feb 07 13:20:04 Crofton|work: right, I received a couple of interesting offers, but I can't go abroad with the whole family Feb 07 13:23:34 I've just read "We need to document that learning OE is a good path to getting work :)", and I agree too ! Feb 07 14:11:14 JaMa: I am reading this chat log, from december, and I can read that you have worked on the meta-qt5. Did it work in the end ? Feb 07 14:12:05 ascor_: https://github.com/meta-qt5 Feb 07 14:12:54 Hmm I have it, but I can't make it work Feb 07 14:13:30 I just added it among my other meta. I still have qt4 tha build, can it interfere ? Feb 07 14:14:22 I'm quite busy, but what you mean by "I still have qt4 tha build"? It depends on what you ask bitbake to build Feb 07 14:15:48 There are still dependecies on qt4, so it still builds on my distribution. I wonder if some variables or configuration files may interfere between recipes Feb 07 14:16:42 But if you made it work, then I have my answer. Don't want to bother a busy person. Feb 07 14:16:51 if you're building something which depends on one of qt4* then it will still build qt4 too Feb 07 14:22:10 Since qt4 and qt5 are just libraries, they shouldn't interfere neither at build nor at run time. But since everything require deep and subtle understanding in OE, I have doubt. Feb 07 14:25:30 ascor_: btw - can I ask you for your real name? Feb 07 14:25:54 Of Course : Pierre Mazein Feb 07 14:26:13 ascor is part of the name of my client Feb 07 14:29:11 thx Feb 07 14:33:27 If you find my resume, you will understand why I have so much questions on oe ... Feb 07 15:04:42 ascor_: I dropped doing resume in favour of linkedin Feb 07 15:05:43 I have to maintain on line and off line resume. Feb 07 15:07:24 My online resume is on viadeo.com and apec.fr, in french Feb 07 15:14:14 hi Feb 07 15:15:33 viadeo is 'register to see' ;D Feb 07 15:16:30 ascor_: http://www.linkedin.com/in/marcinjuszkiewicz Feb 07 15:22:41 I have question which I can not google in an efficient way Feb 07 15:23:29 the question is that : Why every time I run bitbake the system is always parse all the recipes ? Feb 07 15:23:52 and not only that I gave in the command line Feb 07 15:25:05 sbela: cause your recipes depend on other recipes which depend on other recipes... Feb 07 15:25:22 and bitbake caches all data so next parsing is quick Feb 07 15:25:28 unless youchanged configuration Feb 07 15:28:40 lists.oe.org having issues today? 451 Error while writing spool file Feb 07 15:28:53 JaMa|Off: : seems to be broken yes Feb 07 15:29:19 urg Feb 07 15:29:23 pb_, ping Feb 07 15:30:01 hrw: thanks for the answer Feb 07 15:30:32 sbela: and what is recipe for 'virtual/kernel' for example? Feb 07 15:30:47 sbela: it is proper target but there is no recipe with this name Feb 07 15:30:53 this is how I use oe for busybox : MACHINE=at91rm9200iw ./oebb.sh bitbake busybox -c compile -f Feb 07 15:32:19 and the parsing is done every time for the busybox with this command line Feb 07 15:32:31 sbela: it's not possible for bitbake to resolve provides -> recipe filenames without parsing all the recipes to figure out what provides what. 90% of the time it's pulled from the cache, not parsed, though Feb 07 15:32:38 long time parsing? Feb 07 15:32:46 why do you use -c and -f? Feb 07 15:32:57 thats only recommend for developing Feb 07 15:33:06 parsing takes about 30-50 seconds Feb 07 15:33:29 woglinde: I am developing busybox Feb 07 15:33:47 o.O Feb 07 15:33:49 woglinde: creating a new module Feb 07 15:34:00 than I would not use oe Feb 07 15:34:06 sbela: bitbake busybox -cdevshell Feb 07 15:34:10 rather devshell Feb 07 15:34:14 or only toolchain Feb 07 15:34:22 | Running intercept scripts: Feb 07 15:34:22 | > Executing update_font_cache Feb 07 15:34:22 | ERROR: Function failed: do_rootfs (see /home/hrw/HDD/devel/canonical/aarch64/openembedded/build/tmp-eglibc/work/genericarmv8-oe-linux/linaro-image-sdk/1.0-r2/temp/log.do_rootfs.23211 for further information) Feb 07 15:34:28 why... Feb 07 15:34:36 and in the end I would make sure the recipe is working Feb 07 15:34:42 I amnew to oe I used buildroot before so this is why I do not know wht is devshell Feb 07 15:34:47 but I will google it Feb 07 15:34:49 :) Feb 07 15:35:05 oe is nice for building entire distros, but the overhead can be a little annoying during active development Feb 07 15:35:09 nature of the beast Feb 07 15:35:12 you dont will find much Feb 07 15:35:22 FUCK! Feb 07 15:35:29 hrw language Feb 07 15:35:30 haha Feb 07 15:35:34 fontcache.bbclass has HARDCODED qemu calls! Feb 07 15:35:39 red creepercard Feb 07 15:35:41 eep Feb 07 15:35:41 ARGERHG#$%@%$@#%!@#%@~!!!!!!!111!!!!eleven1 Feb 07 15:35:53 :) Feb 07 15:36:02 time to create empty bbclass for aarch64 Feb 07 15:36:07 and complain on ml ;( Feb 07 15:36:32 hrw: I had same build failure here Feb 07 15:36:32 wasnt fontcache jamas beast Feb 07 15:36:41 hrw: but I did a repo sync now and it worked Feb 07 15:37:13 hrw no qemu for aarch64 yet? Feb 07 15:37:57 woglinde: nope Feb 07 15:38:16 woglinde: some work on it just started Feb 07 15:39:30 ok, mail sent to ML Feb 07 15:40:44 time to calm down and food Feb 07 15:42:05 hrw && woglinde: this devshell mode is what I wanted as I read in the documentation, thank you very much Feb 07 15:42:29 sbela: you welcome Feb 07 15:43:04 sbela: other way (more useful) would be 'bitbake meta-toolchain', run tmp-eglibc/deploy/sdk/*.sh and use standalone toolchain Feb 07 15:43:11 hmm, three patchsets to send out and ML is broken :( Feb 07 15:44:34 and we have only one guy who can fixing it Feb 07 15:44:37 not good Feb 07 15:44:46 :( Feb 07 15:45:04 bus factor ;( Feb 07 15:45:13 why hasn't crofton or kergoth the rights? Feb 07 15:45:34 don't look at me, I don't do any admin stuff anymore :) Feb 07 15:45:39 okay Feb 07 15:46:18 so we have to wait for pb or ka6sox? Feb 07 15:46:49 florian? Feb 07 15:47:51 one good thing - for aarch64 we do not care about graphical output yet so less problems will be with OE classes and qemu Feb 07 15:48:07 hrw *g* Feb 07 15:48:51 lists are on ltg right? Feb 07 15:49:13 ha! I have to get rid of distcc Feb 07 15:49:25 no distcc, no gtk, no liberation-fonts Feb 07 15:50:39 cause distcc-dev catches gtk+-dev which catches libgtk-2.0 which wants liberation-fonts Feb 07 15:51:49 hrw cannt you rewrite the font class? Feb 07 15:52:23 woglinde: rewrite of packagegroup-core-sdk is easier Feb 07 15:52:30 I do not need distcc Feb 07 15:52:58 woglinde: and I would probably have to rewrite qemu.bbclass as well Feb 07 15:54:09 I never understood why distcc is included in that group. is it really that commonly used? Feb 07 15:54:57 I think the idea was faster on-target compilation for those that want it Feb 07 15:55:16 Zagor: years ago when arm926 at 400MHz was fast machine we added distcc to on-target-sdk Feb 07 15:55:39 as there were people who wanted to have native compilation Feb 07 15:55:52 ok Feb 07 15:56:31 I never understood the native-compile huggers either, but I guess we don't need to go there :-) Feb 07 15:56:40 today my main arm development platform is as fast as my conference laptop Feb 07 16:59:14 slightly off-topic, could someone tell me what these lines are called used by emacs (and vi?) so I can google them? "# ex:ts=4:sw=4:sts=4:et Feb 07 16:59:15 # -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-" Feb 07 17:02:13 didn't try hard enough. Found it. Feb 07 17:02:38 is that first line for emacs, too? Feb 07 17:05:02 Hmm the difficulty googling is that most people call that a modeling, but emacs calls it "File Variables" Feb 07 17:05:10 modeline Feb 07 17:05:20 damn OSX auto-correct Feb 07 17:31:41 moin Feb 07 19:16:19 woglinde: no my is update-fonts :) Feb 07 20:13:46 pb_, ping Feb 07 20:32:08 Any idea the status on the list serv? Feb 07 20:35:07 I haven't heard from the guys I know that have access Feb 07 20:48:21 zecke, do you have admin on ltg? Feb 07 20:56:40 Crofton|work: I don't think so. Feb 07 20:57:35 Crofton|work: I still have access to discovery but i am in no special group Feb 07 20:58:03 ok Feb 07 20:58:08 sorry Feb 07 21:01:45 np Feb 07 21:02:25 ok, got an email from florian Feb 07 21:02:35 it is out of disk space and he is looking for something to clean up Feb 07 22:01:57 Is it safe to send email to the oe-core list? or is it going to get lost once the problem is figured out? Feb 07 22:02:03 (does anyone know?) Feb 07 22:05:21 florian is aware Feb 07 22:06:07 this is a pretty rough situation Feb 07 22:06:31 we really need to do better about having other folks with administrative access for emergencies such as this Feb 07 22:06:48 bl I am saying this for years Feb 07 22:06:52 I thought this was unique because we didn't run the list servers Feb 07 22:07:06 florain had to buy a car Feb 07 22:07:10 when this has come up before, the answer has always been that the machines we control we have a couple of people who can manager them Feb 07 22:07:12 not sure where pb is Feb 07 22:07:52 I'm not blaming them for not being available, but this is not the first time these servers have had problems that couldn't be corrected for the best part of a day Feb 07 22:08:31 and full disk-space is poor administration Feb 07 22:08:47 ltg wears too many hats Feb 07 22:08:51 bluelightning: are the admins both EU based? I thought halstead has some admin privs, I guess not the list serv Feb 07 22:08:53 monitoring system is not that hard Feb 07 22:09:09 florian, you there? Feb 07 22:09:51 good nite Feb 07 22:09:52 sgw1: in order: yes; not for the linuxtogo.org servers Feb 07 22:10:14 is it all of linuxtogo or is it just OE? Feb 07 22:10:14 sgw1, The lists are managed by linuxtogo so I don't have access. Feb 07 22:10:17 * woglinde wonders why the ml wasnt switched over too Feb 07 22:10:25 bluelightning: figured Feb 07 22:10:36 woglinde I think because there was no reason to Feb 07 22:10:57 now we have the reason Feb 07 22:10:58 my immediate concern is getting them back, then we can worry about the future :) Feb 07 22:11:13 was not the first time in the last weeks Feb 07 22:11:30 ah no that other was patchwork Feb 07 22:12:01 so now really gone Feb 07 22:16:28 * fray will hold off sending patches to the list then.. Feb 07 22:17:03 * fray goes to get the kid from school.. back in a bit Feb 07 22:18:29 Crofton|work: yes Feb 07 22:19:20 any luck? Feb 07 22:20:42 yes, mailman should be back Feb 07 22:20:47 thanks Feb 07 22:21:16 would it make things easier of we looked at alternate list hosting? Feb 07 22:22:20 some more administrative power would be better :) Feb 07 22:24:10 well, we have access to admins, but they would likely want to use hw they are familiar with Feb 07 22:54:46 Crofton|work, florian OSUOSL can do the list hosting... Feb 07 22:54:46 they are good at that. Feb 07 23:00:09 okay, why would bitbake build a sudo package where /usr/bin/sudo is not setuid root Feb 07 23:02:10 hah Feb 07 23:04:16 i think i found it Feb 07 23:04:56 it's part of the package postinst and i'm trying to boot a read-only rootfs without a writable first-boot Feb 07 23:05:18 is that a vain/stupid goal in this case? Feb 07 23:13:57 kergoth: is there anything documented specifically on how the volatile and read-only root stuff in OE is supposed to work? Feb 07 23:15:24 not that i know of, just search the list archives for read-only-rootfs or postinst (lots of patchsets for do_rootfs time postinst stuff) Feb 07 23:15:41 i'm assuming you're buildng hte image with the read-only-rootfs in IMAGE_FEATURES? Feb 07 23:16:07 yeah, i integrated the Chen Qui patches and added that to my base image Feb 07 23:16:40 probably not spelling his name right... Feb 07 23:17:39 management seems to think we can do this without ever going through a first boot with a writable root Feb 07 23:17:50 I see mail flowing.. excellent! Feb 07 23:17:52 i'm starting to think not Feb 07 23:18:41 there are a number of people working on read-only first boot.. Feb 07 23:18:59 who in particular? Feb 07 23:19:02 but depending on what you need, it may be difficult (also master works a heck of a lot better then any of the previous releases) Feb 07 23:19:30 we're stuck with arago oe-dev stuff right now Feb 07 23:19:49 there seem to be a number of patch series hitting the mailing list for oe-core master for this sort of stuff. it's good to see attention going there Feb 07 23:19:53 Qhen Qi, Laurentiu Palcu, and others Feb 07 23:19:59 * kergoth nods Feb 07 23:20:04 i pulled in some nice patches from poky-contrib, but i'm still trying to wrap my head around the whole thing Feb 07 23:20:18 mr_science: i think pb's micro distro might ahve stuff in that direction also, as i know he's played iwth it over the years Feb 07 23:20:24 not sure though Feb 07 23:20:41 there are two issues you have to deal with.. operations that (for one reason or another) are easier done on the target, then during package build or install time.. Feb 07 23:20:46 yeah, i just pulled those patches from Qhen Qi Feb 07 23:20:48 and then problems with the boot scripting.. Feb 07 23:21:02 IMHO, initscript issues are bugs, pure and simple.. find and fix Feb 07 23:21:25 the other set, it's taking people to go through them one at a time to figure out why it has to run on the target, and to come up with an alternative.. Feb 07 23:21:30 but a lot of them aren't easy Feb 07 23:21:31 yeah, the rest is likely just getting links / bind mounts in place for whatever software you're running, and what you'll need to do will vary with what you have to run, obviously, since not all software writes to the same locations.. Feb 07 23:21:36 * kergoth nods Feb 07 23:22:06 I know the company I work for (and ChenQi works for) really want read-only root, first boot to work properly.. Feb 07 23:22:16 and without running any complex "temproary" stuff on every boot.. Feb 07 23:22:20 (i.e. no unionfs) Feb 07 23:22:27 so would i Feb 07 23:22:43 it's a common requirement, companies like the idea of the user not being able to hose the thing, or being able to easily revert to factory default quickly by wiping the rw partition(s), or whatever Feb 07 23:22:50 monolithic upgrades rather than package upgrades, .. Feb 07 23:22:53 heh Feb 07 23:23:04 the more people that find problems with the boot, the more likely it'll get fixed.. I think in the evolution of this work, we're finally at the point that -companies- developing diverse products are running into the problems Feb 07 23:23:19 (before it was primarily hobiests or contractors, and it's easier to do one-off fixes in those cases) Feb 07 23:23:23 yup Feb 07 23:23:42 so who do you guys work for? Feb 07 23:24:11 kergoth, ya.. field upgrade.. everyone things it's simple.. but to do it right you have to know how to do full system (image), package, file, and other odd ball things.. Feb 07 23:24:20 mr_science I work for Wind River Feb 07 23:24:31 ah Feb 07 23:24:46 * mr_science is now a medical device guy Feb 07 23:24:50 Mentor Graphics here, they do a yocto based product/distro, not unlike montavista Feb 07 23:25:06 from missle launch range to surgical cameras Feb 07 23:25:21 ya.. the three main OSVs have all moved to YP (oe-core based) to avoid duplication of effort Feb 07 23:25:28 mr_science: ah, interesting stuff, high availability Feb 07 23:25:44 add to that some of the primarily european OSVs (Enea for example) and most everyone is doing YP/OE-core now Feb 07 23:26:26 what about people tied more tightly to things like TI DSP hardware? Feb 07 23:26:47 back when I worked for MontaVista (around 2002) Guidant (now Boston Scientific) was just starting ot use Linux for pacemaker monitoring and programing.. very interesting Feb 07 23:26:49 It's pretty amazing how large oe/yocto have become. just look at the number of yocto-related talks at elc again this year Feb 07 23:26:49 does YP support omx/syslink/ti-codec-crap, etc? Feb 07 23:27:05 some of it.. through the angstrom/TI layers Feb 07 23:27:34 so it might be possible to migrate to YP/OE core? Feb 07 23:27:48 layers coming from the chip/board companies is just lovely Feb 07 23:27:55 or by "some of it" you really mean "not much" Feb 07 23:28:00 speaking as someone who doesn't want to have to maintain bsp layers, anwyay :) Feb 07 23:28:06 Yocto Project is the poky "meta-yocto" layer, bitbake and oe-core nicely packaged together... Feb 07 23:28:47 so, if you are familiar with oe (angstrom, oe-core) you should be able to migrate.. but there will be some learning curve.. Feb 07 23:29:06 if you are already familiar with oe-core... the curve is much smaller.. Feb 07 23:29:12 well, it looks like my rootfs_postprocess function can replace the sudo pkg_postinst Feb 07 23:29:26 it seems to have set the bit correctly Feb 07 23:29:33 cool.. mail server does seem to be working, I got my patches back.. ;) Feb 07 23:30:12 somehow i didn't think that work Feb 07 23:30:35 fray: nice, thats good to hear Feb 07 23:30:42 it's been eerily quiet Feb 07 23:30:56 if you haven't use oe-core before.. there is a newer tech called "pseudo".. it enables us to emulate a chroot capable, "fakeroot" style environment.. Feb 07 23:31:13 there are a number of things you can post process under pseudo control to help with this.. Feb 07 23:31:26 but you still can't just run the target binaries needed to generate caches and such.. Feb 07 23:33:03 * fray is happy to report all of his pending "upstream" submissions have now been sent "upstream".... Feb 07 23:33:07 one more TODO task off my plate Feb 07 23:33:57 congrats. i can't remember the last time i was at that point Feb 07 23:34:28 well, our guys are supposed to do it themselves.. but it's easy to let things fall through the cracks.. when it happens, I get to scope them up and fix it.. ;) Feb 07 23:34:34 I seem to get to do this about every 2 months or so Feb 07 23:42:22 jeez, putty sure shows its origins when you open the log file in gedit Feb 07 23:43:06 it puts in some weird crap header that totally makes it look non-text unless you delete the top two lines... **** ENDING LOGGING AT Fri Feb 08 02:59:59 2013