**** BEGIN LOGGING AT Thu May 09 02:59:58 2013
May 09 07:39:43 <mckoan> good morning
May 09 07:42:47 <ant_work> hello
May 09 07:59:35 <bluelightning> morning all
May 09 14:03:20 <Crofton> zeddii, do you have any advice for chasing my perf build failuer?
May 09 15:25:29 <sgw_> JaMa: did you see my note yesterday about building a plain oe-core with gcc-4.8 no problems.
May 09 15:28:22 <JaMa> yes, I'm trying to fix webkit-efl now to get better logs and then share them again
May 09 15:30:19 <sgw_> JaMa: ok, so where there other 4.8 issues for meta-oe that would prevent a version bump?
May 09 15:32:04 <JaMa> yes few more recipes were failing
May 09 15:35:35 <sgw_> JaMa: I would really like to get this update in sooner, can you deal with some breakage for now or are they critical recipes?  Or do you need one more round after the webkit-efl fix goes in?
May 09 15:37:16 <JaMa> I don't use master for anything important now so I don't mind if it gets broken
May 09 19:25:49 <evanp> I notice that there's some code in bitbake/lib/bb/utils.py which knows how PVs with 'alpha', 'beta', 'rc', 'pre' etc. should sort....but RPM's version comparison algorithm doesn't do it the same way, right? Or is there some magic somewhere when you enable RPM package management?
May 09 20:17:53 <fray> evanp -- RPM doesn't know anything about special cases of 'alpha', 'beta', etc..  I didn't even know OE did
May 09 20:20:06 <fray> I'd suggest a bug in the YP bugzilla, so it can be reconciled..  (there is a version bug already  see bug 256, might be reasonable to add to that)
May 09 20:20:07 <yocti> Bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=256 enhancement, Medium, 1.5, saul.wold, NEW , Sync up RPM version policy with rest of system (including support '~' in version strings)
May 09 20:41:24 <Jefro> You know what takes a long time? bitbake -c fetchall on a really lousy network connection. I want to start building & tweaking!
May 09 20:44:15 <fray> :)
May 09 21:36:15 <magno32> anyone able to help with a dtb/kernel question?
May 09 22:42:56 <kergoth> heh, that's two times now we've hit a bug related to bitbake's default when a function has no 'dirs' flag
May 09 22:43:41 <kergoth> it defaults to ${B}. which defaults to ${S}, which means it can be creating and cd'ing to a source tree even in cases where that's probematic (racing with cleandirs, or running before a git do_unpack (the git fetcher unpack chokes if the destination already exists)
May 09 22:43:59 <kergoth> bitbake really should have *zero* knowledge of ${S} or ${B}
May 09 22:44:04 <kergoth> so that's really inappropriate as a default
May 09 22:44:10 <kergoth> it should do ${TMPDIR} or something, or nothing at all
**** ENDING LOGGING AT Fri May 10 02:59:58 2013