=== yofel_ is now known as yofel === Meths_ is now known as Meths === doko__ is now known as doko [16:37] are the maverick buildd's messed up? I'm getting failures like this that I can't reproduce locally - https://launchpad.net/~xorg-edgers/+archive/ppa/+build/2081191/+files/buildlog_ubuntu-maverick-amd64.xserver-xorg-video-intel_2%3A2.13.901%2Bgit20101205.c2fac6ca-0ubuntu0sarvatt2~maverick_FAILEDTOBUILD.txt.gz [16:37] checking how to run the C preprocessor... /lib/cpp [16:37] configure: error: in `/build/buildd/xserver-xorg-video-intel-2.13.901+git20101205.c2fac6ca/build': [16:37] configure: error: C preprocessor "/lib/cpp" fails sanity check [16:40] was ok about 12 hours ago, affecting multiple X driver packages just on maverick [16:47] can you modify the package to output config.log if configure fails to see the exact reason? [16:48] gcc-4.5 didn't change for over a week now [16:49] ah, maverick and not natty, sorry; but getting config.log will help to see where exactly it fails in configure [16:49] it's using 4.4 on maverick and just started in the last 12 hours where the same packages built fine. trying to figure out how to do that now [16:52] adding " || cat config.log" to the configure call in debian/rules should do it [16:54] uploaded, will show up https://launchpad.net/~xorg-edgers/+archive/ppa/+builds?build_text=&build_state=all soon [16:55] (all the input driver failures there are different and expected) [17:04] http://launchpadlibrarian.net/60149920/buildlog_ubuntu-maverick-i386.xserver-xorg-video-intel_2%3A2.13.901%2Bgit20101205.c2fac6ca-0ubuntu0sarvatt3~maverick_FAILEDTOBUILD.txt.gz [17:06] for x-x-v-savage that failed the same way the only change in the past 14 hours since it succeeded was a version bump in configure.ac [17:07] /usr/include/bits/local_lim.h:39: fatal error: linux/limits.h: No such file or directory [17:08] that seems to be the problem [17:12] hmm maybe linux-libc-dev is screwed up in the PPA [17:13] the official maverick linux build contains that file in linux-libc-dev [17:13] 2.6.37-8.20 was copied into the PPA about the same time the failures started, looks like the problem is in there. thanks geser [17:22] yep 2.6.37-8's linux-libc-dev is screwed up, that was it [17:25] thanks for finding this bug === habnabit is now known as _habnabit [18:53] "You are over quota on people.ubuntu.com", is there a way to get an extension? i use that space mostly to pass files to security sponsors and to upstream [18:55] fta: per the wiki, I believe you have to mail rt at ubuntu dot com for this [18:56] micahg, ok, thanks [19:42] https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+build/2075614 no build log? [19:43] fta: ah, I think theres a bug about that. [19:44] wgrant: ^ ftbfs with no build log [19:45] fta: I'd search in launchpad-project bugs for that [19:48] morning [20:42] Would some launchpad person please see if they can find the link to the build log for https://launchpad.net/ubuntu/+source/qt4-x11/4:4.7.1-0ubuntu4/+build/2052893 [20:42] It just says failed to build, but no log. [20:43] wgrant: ^^^? [20:43] fta just mentione a similar issue for a PPA [20:44] (for a native ppa, not sure if it matters though) [20:44] jelmer: ^ [20:45] lifeless: thanks, looking [20:52] fta: what was your build? [20:53] https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+build/2075614 === Pici` is now known as Pici [21:04] ScottK, fta, lifeless: it looks like there were some temporary issues scanning builders late yesterday. I'm going to file a bug about this and retry the problematic (half a dozen) builds. [21:05] ack [21:32] hey all [21:32] do you have a plugin or what not if code is hosted on git? === thewrathjr is now known as thewrath [23:16] thewrath: git repositories can be imported into bzr, but launchpad does not host git natively [23:17] thumper, so i would have to import them manually then? [23:17] thewrath: no, launchpad has an import service [23:17] and the git one is quite good [23:17] as long as it doesn't use submodules [23:17] not that i am aware :)