**** BEGIN LOGGING AT Fri Dec 10 02:59:57 2010
Dec 10 15:02:04 <rsalveti> ndec: vstehle: call?
Dec 10 15:02:15 <ndec> rsalveti: i am coming
Dec 10 15:10:50 <rsalveti> ndec: https://blueprints.launchpad.net/ubuntu/+spec/other-dx-n-2d-experience-fallback
Dec 10 15:15:18 <rbelem> the surgery is starting
Dec 10 15:16:08 <rbelem> rsalveti
Dec 10 15:16:21 <rbelem> my baby boy is about to born
Dec 10 15:16:54 <rsalveti> rbelem: holy! :-)
Dec 10 15:17:00 <rsalveti> rbelem: good luck man!
Dec 10 15:17:25 <rbelem> thank you rsalveti :D
Dec 10 17:33:17 <rsalveti> GrueMaster: a new network-manager package should be in the archive soon
Dec 10 17:33:35 <GrueMaster> cool.  I'll keep an eye out for it.
Dec 10 17:34:34 <GrueMaster> As to the image build failures, I am actually getting used to it.  One program or library gets an update, and a huge chunk of the pool gets churned.
Dec 10 17:34:56 <GrueMaster> I just use apt-get update to wade through and keep testing.
Dec 10 18:50:27 <GrueMaster> Grrr.  Now I can't reproduce the issue I saw.  Ran apt-get -d upgrade to pull all of the packages local, then apt-get install on batches between reboots.  Fully updated, system still works.
Dec 10 19:46:07 <sveinse> Are there some differences between the native gcc and the ARM cross gcc config? I keep getting "comparison between signed and unsigned integer expressions" from the cross compiler, which I dont on the native.
Dec 10 19:46:48 <topfs2> added a -Wall in one of them perhaps?
Dec 10 19:47:03 <topfs2> just fix the warning otherwise, shouldn't be mixing those :)
Dec 10 19:47:11 <sveinse> No, its the same code on both.
Dec 10 19:47:27 <topfs2> I said -Wall as in compiler argument
Dec 10 19:47:33 <sveinse> Well, its from google's protobuf included header...
Dec 10 19:49:06 <topfs2> are they comparing in the header?
Dec 10 19:50:20 <sveinse> Yes. Inlined code. And c++
Dec 10 19:51:09 <topfs2> ick
Dec 10 19:51:25 <topfs2> at any rate, it complaining is afaik usually via -wall
Dec 10 19:51:51 <sveinse> Perhaps the specfile for ARM contains -Wall while the native dont
Dec 10 19:53:30 <sveinse> I suppose hrw can answer, but it seems he's away
Dec 10 19:56:45 <hrw> sveinse: cross one in archive is old
Dec 10 19:57:01 <hrw> updates are queued
Dec 10 19:58:16 <sveinse> Ah. I'll retry everything then
Dec 10 19:58:35 <sveinse> Are the updated/fixed libc cross also queued?
Dec 10 20:00:00 <sveinse> hrw: BTW Do you have the url to the build queue?
Dec 10 20:02:01 <sveinse> found it
Dec 10 20:02:47 <GrueMaster> rsalveti: Well, after taking my second system from 20101206 to current in batches, I couldn't reproduce the X failure.  I then updated the failing system, and it now works.  Sigh.
Dec 10 20:03:15 <rsalveti> GrueMaster: I saw that there was a problem with gdm
Dec 10 20:03:20 <rsalveti> so that could be your case
Dec 10 20:03:25 <GrueMaster> I did notice that the failing system pulled in mutter-common on updating.
Dec 10 20:03:26 <rsalveti> and that is fixed at the archive already
Dec 10 20:03:43 <GrueMaster> No, the failing system didn't pull gdm.
Dec 10 20:03:52 <rsalveti> hm
Dec 10 20:04:01 <rsalveti> well, if it's working now then we're happy :-)
Dec 10 20:04:14 <GrueMaster> But since I can't reproduce it on two systems, I'm moving on.
Dec 10 20:04:20 <GrueMaster> yep
Dec 10 20:04:20 <rsalveti> ok
Dec 10 20:18:03 <rsalveti> GrueMaster: just finished: https://launchpad.net/ubuntu/+source/network-manager/0.8.3+git.20101209t061929.638fb18-0ubuntu1/+build/2091214
Dec 10 20:18:10 <rsalveti> should be available at the archive soon
Dec 10 20:18:28 * GrueMaster waits with baited breath.
**** ENDING LOGGING AT Sat Dec 11 02:59:57 2010