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