**** BEGIN LOGGING AT Wed Jun 22 02:59:57 2011
Jun 22 14:49:01 <pidge> morning all
Jun 22 14:50:18 <bluelightning> hi pidge
Jun 22 14:51:31 <pidge> morning bluelightning. I'm going to test that patch out on the ab, see if things are fixed. ty for the work on that btw.
Jun 22 14:52:18 <bluelightning> pidge: no worries. FWIW I tested it with my login on ab03 and bitbake -p was able to run through successfully
Jun 22 14:52:50 <pidge> bluelightning: excellent.
Jun 22 15:01:55 * RP__ is trying to get around to patch mergin
Jun 22 15:02:04 <RP__> other things just keep getting in the way
Jun 22 15:10:13 * pidge will send RP__ cookies and beer if he merges in http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=paule/fix-uboot-srcrev
Jun 22 15:13:39 * RP__ ponders the ethics of holding patches for ransom :)
Jun 22 15:20:47 * pidge ponders the meaning of this new term "ethics"? *rushes for a dictionary*
Jun 22 15:23:07 <RP__> pidge: that patch is in
Jun 22 15:23:31 <pidge> woot. thank you. my autobuilder is happy now.
Jun 22 15:36:59 <bluelightning> pidge: some say it's a county northeast of london
Jun 22 15:37:53 <pidge> bluelightning: nice.....
Jun 22 16:09:07 <khem> RP__: ping
Jun 22 16:09:31 <RP__> khem: pong
Jun 22 16:09:49 <khem> RP__: should we use PV = "4.6.0+svn" or do you prefere 4.6.0+svnr{SRCPV}
Jun 22 16:10:06 <khem> RP__: SRCPV is also in PR
Jun 22 16:10:19 <RP__> khem: Why is SRCPV in PR?
Jun 22 16:10:33 <RP__> Can we just put it in PV like everything else?
Jun 22 16:10:51 <khem> RP__: its easier to just say version in PREFERRED_VERSION
Jun 22 16:11:11 <khem> otherwise the pinning is to be changed every time srcrev is bumped
Jun 22 16:11:13 <RP__> khem: You know that % acts as a wildcard in PREFERRED_VERSION?
Jun 22 16:11:18 <khem> but I guess we could use %
Jun 22 16:11:21 <khem> yep
Jun 22 16:11:22 <khem> :)
Jun 22 16:11:29 <RP__> I'd suggest doing that
Jun 22 16:11:33 <khem> ok
Jun 22 16:13:01 <khem> so about PV
Jun 22 16:13:14 <khem> what is better
Jun 22 16:13:25 <khem> just 4.6.0+svn
Jun 22 16:13:35 <khem> and then we increment it as the release happens
Jun 22 16:13:41 <RP__> I think we might as well include the revision
Jun 22 16:13:51 <khem> 4.6.0+svnr{SRCPV}
Jun 22 16:13:51 <RP__> Its not like its a meaningless git hash :)
Jun 22 16:13:59 <khem> yeah heh its svn
Jun 22 16:15:21 <khem> PV = "4.6.0+svnr${SRCPV}"
Jun 22 16:15:26 <khem> it is then
Jun 22 16:28:09 <khem> RP__: another option is to use 4.6+svnr${SRCPV}
Jun 22 16:28:44 <khem> RP__: that would make sure that we dont have to bother about minor releases happening from 4.6 branch
Jun 22 16:28:55 <khem> especially in distro pinnings
Jun 22 16:29:40 <khem> or may be I can use GCCVERSION ?= "4.6%"
Jun 22 16:30:38 <RP__> khem: you can
Jun 22 16:30:49 <RP__> I'd really like to see the minor number in there
Jun 22 16:30:59 <khem> ok so let me keep PV as we discussed
Jun 22 16:31:08 <khem> and use GCCVERSION ?= "4.6%"
Jun 22 16:32:56 <khem> I will rebuild the toolchain for all arches with thischange and resubmit later when that finishes
Jun 22 18:18:51 <holoturoide> Hi, anybody use yocto with TI AM180x?
Jun 22 19:26:40 <zeddii> fray. was it you that had a eglibc issue ?
Jun 22 19:29:18 <zeddii> was it this ? | ERROR: Function 'localedef returned an error' failed
Jun 22 19:35:54 <fray> yes
Jun 22 22:03:15 <Jay7> RP__: ping
Jun 22 22:03:27 <RP__> Jay7: pong
Jun 22 22:04:05 <Jay7> RP__: I'll talk with your LF fellow spirit :)
Jun 22 22:04:44 <Jay7> we have event here in Russia - Chaos Constructions
Jun 22 22:04:59 <Jay7> I think it's good place to present yocto project here
Jun 22 22:05:17 <Jay7> it's true geek's event :)
Jun 22 22:05:31 <RP__> sounds reasonable :)
Jun 22 22:05:56 <Jay7> I'm not sure I'll go CC this year, my finances are weak :)
Jun 22 22:06:17 <Jay7> but please consider this event :)
Jun 22 22:06:42 <RP__> Jay7: Consider it for who?
Jun 22 22:06:51 <RP__> Jay7: You mean me or someone from the project?
Jun 22 22:07:06 <Jay7>  http://cc.org.ru/inenglish.txt - that's all they have in english :)
Jun 22 22:07:17 <Jay7> RP__: Yocto project and LF mostly :)
Jun 22 22:07:40 <RP__> Jay7: I was going to say, it appears hard to even find information in a language I can read :/
Jun 22 22:08:01 <Jay7> I can help with contacts at least
Jun 22 22:08:37 <RP__> Jay7: There is the advocacy group for Yocto who you could ask about this but I think for this there would need to be someone more native involved
Jun 22 22:09:05 <Jay7> sure
Jun 22 22:09:27 * Jay7 scratching his head
Jun 22 22:10:19 <Jay7> iirc, Sergey Laping and Dmitry Eremin-Soleynikov are from St.Petersburg
Jun 22 22:10:32 <Jay7> may be good idea to ask them
Jun 22 22:10:43 <Jefro> Jay7  - thanks for the suggestion! I will make sure our advocacy group knows about it, but our finances are pretty stretched as well
Jun 22 22:11:02 <Jay7> Jefro: known situation :)
Jun 22 22:11:37 <Jay7> if you need more info or some contacts inside this event feel free to bother me :)
Jun 22 22:12:37 <Jefro> Jay7 will do, thanks
Jun 22 22:13:21 <dvhart> jefferai, ping
Jun 22 22:13:30 <dvhart> jefferai, beagleboard refresh has hit master
Jun 22 22:13:59 <dvhart> Jefro, you said you had an xm rev other than A I believe?
Jun 22 22:14:08 <dvhart> Jefro, you up to kicking off a build ?
Jun 22 22:14:29 <Jefro> sure - need to download first, that could take a while
Jun 22 22:14:34 <Jefro> I have an xm rev B
Jun 22 22:15:11 <dvhart> Jefro, yeah, working with a local linux-yocto repository would be a good idea
Jun 22 22:15:29 <dvhart> but, easiest to just kick it off overnight and not worry about it ;)
Jun 22 22:15:33 <Jefro> I have one, it is just out of date
Jun 22 22:21:59 <Jefro> dvhart is it the build you need to test, or the image? if you have a prebuilt image I could just download that & smoke test
Jun 22 22:22:23 <dvhart> both please
Jun 22 22:23:37 <Jefro> ok.  results in the morning ok?  my build machine, it is teh slow
Jun 22 22:27:14 <Jefro> dvhart and I am guessing this is for the most recent nightly build
Jun 22 22:27:39 <dvhart> Jefro, no, this is for what was committed to master about an hour ago
Jun 22 22:27:59 <dvhart> Jefro, yeah, no rush, anytime this week would be fantastic
Jun 22 22:27:59 <Jefro> dvhart ok
Jun 22 22:31:27 <dvhart> shhhh.... boss is back
Jun 22 23:57:14 <jefferai> dvhart: ncie!
Jun 22 23:57:29 <jefferai> erm
Jun 22 23:57:29 <jefferai> nice
Jun 22 23:57:38 <jefferai> dvhart: so I don't need your contrib branches anymore?
Jun 22 23:57:43 <dvhart> jefferai, correct
Jun 22 23:57:47 <jefferai> cool
Jun 22 23:58:05 <dvhart> jefferai, if you build "MACHINE=beagleboard bitbake linux-yocto"
Jun 22 23:58:10 <dvhart> you will get the update
Jun 22 23:58:15 <jefferai> ok
Jun 22 23:58:18 <dvhart> (from master of course)
Jun 22 23:58:32 <jefferai> sweet
Jun 22 23:58:33 <dvhart> there was some eglibc trouble reported earlier today
Jun 22 23:58:48 <dvhart> so that might cause a problem, not sure if it has been resolved or not yet
Jun 22 23:59:02 <dvhart> unrelated to the kernel, but was reported on master:HEAD today
Jun 22 23:59:02 <jefferai> ok
Jun 22 23:59:14 <dvhart> please give it a spin and let me know how it goes
Jun 22 23:59:19 <jefferai> yep
Jun 22 23:59:40 <jefferai> within a couple weeks I should have a nice, fast new build machine
Jun 23 00:03:27 <dvhart> nice!
Jun 23 01:36:02 <jefferai> dvhart: building it from parts on newegg...with a desktop sandy bridge processor, but the case has room for a dual-socket server board for later upgrading when sandy bridge xeons come out...
Jun 23 01:36:11 <jefferai> two SATA3 SSDs, two spinny disks
Jun 23 01:36:14 <jefferai> should speed things up a lot
**** ENDING LOGGING AT Thu Jun 23 02:59:56 2011