[15:01] <rsalveti> ndec: vstehle: call?
[15:01] <ndec> rsalveti: i am coming
[15:10] <rsalveti> ndec: https://blueprints.launchpad.net/ubuntu/+spec/other-dx-n-2d-experience-fallback
[15:14] <rbelem> the surgery is starting
[15:15] <rbelem> rsalveti
[15:15] <rbelem> my baby boy is about to born
[15:16] <rsalveti> rbelem: holy! :-)
[15:16] <rsalveti> rbelem: good luck man!
[15:17] <rbelem> thank you rsalveti :D
[17:32] <rsalveti> GrueMaster: a new network-manager package should be in the archive soon
[17:33] <GrueMaster> cool.  I'll keep an eye out for it.
[17: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.
[17:34] <GrueMaster> I just use apt-get update to wade through and keep testing.
[18:50] <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.
[19:45] <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.
[19:46] <topfs2> added a -Wall in one of them perhaps?
[19:46] <topfs2> just fix the warning otherwise, shouldn't be mixing those :)
[19:46] <sveinse> No, its the same code on both.
[19:47] <topfs2> I said -Wall as in compiler argument
[19:47] <sveinse> Well, its from google's protobuf included header...
[19:48] <topfs2> are they comparing in the header?
[19:49] <sveinse> Yes. Inlined code. And c++
[19:50] <topfs2> ick
[19:50] <topfs2> at any rate, it complaining is afaik usually via -wall
[19:51] <sveinse> Perhaps the specfile for ARM contains -Wall while the native dont
[19:53] <sveinse> I suppose hrw can answer, but it seems he's away
[19:56] <hrw> sveinse: cross one in archive is old
[19:56] <hrw> updates are queued
[19:57] <sveinse> Ah. I'll retry everything then
[19:58] <sveinse> Are the updated/fixed libc cross also queued?
[19:59] <sveinse> hrw: BTW Do you have the url to the build queue?
[20:01] <sveinse> found it
[20:02] <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.
[20:02] <rsalveti> GrueMaster: I saw that there was a problem with gdm
[20:02] <rsalveti> so that could be your case
[20:02] <GrueMaster> I did notice that the failing system pulled in mutter-common on updating.
[20:03] <rsalveti> and that is fixed at the archive already
[20:03] <GrueMaster> No, the failing system didn't pull gdm.
[20:03] <rsalveti> hm
[20:03] <rsalveti> well, if it's working now then we're happy :-)
[20:03] <GrueMaster> But since I can't reproduce it on two systems, I'm moving on.
[20:03] <GrueMaster> yep
[20:03] <rsalveti> ok
[20:17] <rsalveti> GrueMaster: just finished: https://launchpad.net/ubuntu/+source/network-manager/0.8.3+git.20101209t061929.638fb18-0ubuntu1/+build/2091214
[20:17] <rsalveti> should be available at the archive soon
[20:18]  * GrueMaster waits with baited breath.