**** BEGIN LOGGING AT Wed Oct 26 02:59:57 2011
Oct 26 07:08:14 <mckoan> good morning
Oct 26 09:56:24 <Snafflehog> I'm sure someone is aware, but the yocto site and repositories are down, RP__
Oct 26 10:45:58 <mckoan> Snafflehog: http://www.yoctoproject.org is working here
Oct 26 11:18:04 <Snafflehog> mckoan: it's back up now, just a minor glitch I imagine
Oct 26 18:15:47 <zeddii> sgw, around ?
Oct 26 19:43:13 <sgw> zeddii: around now, just back from the evening evnet
Oct 26 19:51:09 <zeddii> np. I was just trying to find out who I'd email for oe-core contrib access. But I sent the patch anyway with an explanation :)
Oct 26 19:51:48 <sgw> Ok, I think cbrake is who you need to send your pub git key to.
Oct 26 19:52:02 <zeddii> ok. thx.
Oct 26 20:10:06 <msm> what version of python is yocto/oe testing against?
Oct 26 20:12:16 <incandescant> mostly 2.7 I'd imagine
Oct 26 20:12:35 <JaMaOffELCE> 2.6.6 is in repository
Oct 26 20:12:48 <JaMaOffELCE> there are patches for 2.7.2 there are few issues to make it default
Oct 26 20:13:07 <msm> do you know what issues?
Oct 26 20:13:29 <JaMaOffELCE> yes I know and I've reported them on ML
Oct 26 20:13:35 <msm> ok ill look
Oct 26 22:14:02 <kmacleod> looking at the yocto docs I see the workflow for BSP and app where they get up to the point where you have a built image or app to load on the target, but no suggested workflow for saving the results in git or the intermediate binaries somewhere.  Did I miss it or is it simpler than I'm thinking it is?
Oct 26 22:26:54 <msm> kmacleod: are you trying to save something in particular?
Oct 27 01:52:11 <hrw> *** %n in writable segment detected ***
Oct 27 01:52:21 <hrw> I forgot what this mean
Oct 27 01:53:37 <seebs> I am not totally sure, but I'd assume it means that there's a %n format string in a hunk of memory that's writeable, which is nearly always bad.
**** ENDING LOGGING AT Thu Oct 27 02:59:58 2011