**** BEGIN LOGGING AT Wed Dec 28 02:59:57 2011
Dec 28 06:15:45 <Basith> i couldn't login in console-image.  i get the error: FAILED LOGIN (1) on '/dev/ttyS0' FOR 'root', Authentication failure . pls help me!
Dec 28 09:22:25 <bluelightning> morning all
Dec 28 09:22:35 <Jin^eLD> hi bluelightning 
Dec 28 09:51:07 <eFfeM> hi all
Dec 28 10:17:22 <bluelightning> hi eFfeM
Dec 28 10:20:30 <eFfeM> quiet morning
Dec 28 10:27:48 <bluelightning> eFfeM: indeed, I guess a lot of people are still on holiday
Dec 28 10:28:09 <eFfeM> yup (so am I)
Dec 28 19:19:05 <Jin^eLD> hmm why would locale-base-de-de list eglibc-binary-localedata-de-de in its "Provides"? as the result the binary locales are not put into the image
Dec 28 19:19:31 <Jin^eLD> is this on purpose, what would be the correct way?
Dec 28 19:34:56 <Jin^eLD> hmm, known bug, discussed in august by looks at the ml...
Dec 28 21:45:31 <GNUtoo> hi,
Dec 28 21:46:02 <GNUtoo> I've a kernel recipe which uses:
Dec 28 21:46:05 <GNUtoo>  * srcpv
Dec 28 21:46:07 <GNUtoo>  * git
Dec 28 21:46:28 <GNUtoo> I want to change the SRC_URI but the PV looks like this:
Dec 28 21:46:33 <GNUtoo> PV = "${KERNEL_RELEASE}+gitr${SRCPV}"
Dec 28 21:46:40 <GNUtoo> so bumping PR won't help
Dec 28 21:47:00 <GNUtoo> in fact it does that:
Dec 28 21:47:01 <GNUtoo> | ERROR: Package version for package kernel-headers went backwards which would break package feeds from (0:3.2+gitr5+38c76959e3209026c390a7a52e778e3e661a7214-r1 to 0:3.2+gitr1+d14022482bc7635d89efeb02637e439591119c1d-r3)
Dec 28 21:47:22 <GNUtoo> because of SRCPV?
Dec 28 21:47:25 <GNUtoo> s/?//
Dec 28 21:47:30 <GNUtoo> is PE the only option?
Dec 28 21:51:49 <GNUtoo> maybe I should ask in #yocto at this hour
Dec 28 23:13:50 <bluelightning> GNUtoo: seems we have a problem with our git versioning
Dec 28 23:14:12 <GNUtoo> ah?
Dec 28 23:15:02 <bluelightning> I'm not sure how we should handle this particular situation, but I think it's worth filing a bug
Dec 28 23:17:03 <bluelightning> either gitrX should not have reset, our version comparison code is wrong or we should somehow ignore this situation
Dec 28 23:19:26 * bluelightning -> sleep
**** ENDING LOGGING AT Thu Dec 29 02:59:57 2011