[00:08] anyone around who would considering pushing https://code.launchpad.net/~psusi/ubuntu/precise/lm-sensors/merge/+merge/85044 ? I don't have perms to dput it. [00:19] hallyn: i'm hoping to have time to try and improve that upgrade path during my holiday break === arosales is now known as antonio_afk [00:45] broder: for schroot? cool - it's no big deal if documented, just took me awhiel (and looking through a patch you sent to debian :) to figure out where to tweak [00:46] the subdirs under /etc confounded me :) i was grepping in /etc/* [01:54] anyone heard from lifeless & other christchurch people in the past hour? there's been another big quake there :( === cdbs is now known as bilal [02:01] iHate changing nicks, but this is going to be my nick from now onwards. Plain and simple [02:04] elky, "only" 5.8 this time, hopefully only modest damage and no casualties [02:04] bilal, nice [02:06] bryceh, yeah, so far no reports of toppled buildings or death, but there has been reports of injury and cracking and liquefaction. Merry christmas, christchurch :( [02:06] great way to finish the year [02:13] ajmitch, yeah [02:20] :( [02:24] And ross is dead again. [02:24] powerpc may never catch up. [02:25] infinity: Any idea what's up with it (dunno if you can still look into such things)? [02:25] At least the third time today it's died. [02:27] ScottK: I can't, no. Gave up that access. [02:27] ScottK: I know people have been notified, however. [02:27] Thanks. [02:40] ScottK: ross lives. Of course, the firefox build that killed it might take out adare soon. ;) [02:41] It's been that same build it died on at least two of the times. [02:41] Of course it's a long build, so it may just be coincidence. [02:41] * infinity nods. [02:42] I suspect the Xserves will be infinitely happier when we can upgrade them to precise. [02:42] The older kernels we left them on weren't the happiest of pandas, if I recall. [02:42] At least, back when the machines were "mine". [02:43] Oh, no, I'm living in the past. They're lucid now. [02:43] It was hardy that they skipped. [02:44] Yep [02:44] IIRC they ran Karmic for a little while. === bkerensa is now known as bkerensa|AFK [03:05] doko_, in xmlrpc-c (1.16.32-0ubuntu2) you wrote: * Don't use the symbols files, renamed the library packages anyway. I assume this means you renamed the binary package to have -0 in the name. Why? I'm trying to install boxee and it depends on the non -0 version. Is there an abi breakage, or could adding a provides: for the non -0 fix this? [03:10] Which is preferred (it seems they both work fine): (qreal)foo or qreal(foo)? [03:10] ScottK, you talking about casting in C++? [03:10] yes. [03:10] Sorry. [03:11] well, the former works in C as well, in C++, I think the specific {static,dynamic}_cast<> is preferred [03:11] technically the latter form instantiates a new temporary [03:12] For Qt qreal is a double on all archs except armel/armhf so it's quite common for people to interleave doubles and qreals when they shouldn't. [03:17] psusi: I'm not sure if there was an ABI break, but the package should have the SOVER in the name regardless. Can boxee not be rebuilt to get the correct dep? [03:18] psusi: Oh, it's proprietary. Yay. [03:18] infinity, right.. so if there wasn't an actual abi breakage, adding a provides: for the old incorrect soname should fix things right? [03:18] psusi: If. You might want to check that. [03:19] It's still "wrong" from a "packaging libraries correctly" standpoint, but... [03:19] psusi: On the other hand, if doko had to disable checksymbols, that sort of points to ABI breakage. [03:20] @pilot out === udevbot changed the topic of #ubuntu-devel to: Archive: open | Development of Ubuntu (not support, not app development) | build failures -> http://bit.ly/or6CHJ | #ubuntu for support and general discussion for hardy -> oneiric | #ubuntu-app-devel for app development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: === Aaron_ is now known as TiMiDo [04:51] infinity: just noticed that libsmbclient doesn't have a SONAME in the package either [05:38] anyone know how the ubuntu core images are built? is it just a debootstrap? [06:18] jk-: It's essentially debootstrap --variant=minbase at the moment. [06:19] infinity: awesome, thanks. [08:03] good morning [09:18] infinity: can I get you to copy firefox (lucid/maverick) from ubuntu-security-proposed to {lucid,maverick}-proposed? === Quintasan_ is now known as Quintasan [11:12] tumbleweed: it seems that we have to live with the broken dh_install. do you have the patch for wrap-and-sort for me? [11:15] bdrung: :/ http://paste.debian.net/150005/ [11:16] tumbleweed: do you have a commit message for that change? === _salem is now known as salem_ [11:44] bdrung: no, I hadn't committed it locally === yofel_ is now known as yofel [12:44] tumbleweed: pushed slightly modified [14:02] doko_: do you know if that kernel fix is going to be deployed to the buildds any time soon? === doko_ is now known as doko [14:03] Laney, I assume first week of Jan, there's nobody around now, but the kernels are in -proposed and can age [14:03] great [14:04] wfm [14:04] and they are already tested [15:11] doko: hi! any idea why this could be happening? (unbound FTBFS on oneiric) http://paste.ubuntu.com/779905/ [15:11] doko: line 6301+ [15:11] doko: same package build fine on precise, and precise's package doesn't build on oneiric [15:12] mdeslaur, configure:14781: checking python extra libraries [15:12] configure:14788: result: -lssl -lcrypto -lssl -lcrypto -L/usr/lib -lz -lpthread -ldl -lutil [15:12] but then not linking with these ... [15:13] yeah, I tried adding -lssl -lcrypto...but I didn't add the other...thanks, I'll give it a try [15:14] mdeslaur, hmm, it shouldn't be necessary, the conftest.c doesn't use any of these [15:15] mdeslaur, does it work without -flto? [15:15] doko: let me check [15:16] mdeslaur, is this oneiric-security? [15:17] doko: yes, but I tried building with -updates too [15:17] hmm, it should be fixed in binutils from oneiric-updates [15:17] oh, interesting...ok, I'll try it again with -updates [15:18] thanks doko [15:29] doko: binutils worked, thanks! [15:47] mdeslaur, so maybe copy it to the -security pocket? [15:47] doko: yeah, I'm rebuilding it in -security now so we don't hit it again [15:55] sladen: guy on ubuntu-users asked for monospace fonts, you may want to check if he's tried ubuntu mono [16:02] Riddell, according to NBS, a kdevelop upload is missing ;) [16:21] doko: I'll try a rebuild locally and upload [18:17] doko: KDE core is now fully built on armhf in the archive. [19:21] SRU question. I need to re-submit an SRU that needs some code added and some removed. Should I prepare a new branch to be merged against the oneiric branch (replacing the first one), or just request a merge on the oneiric-proposed branch with the modified code? [19:22] * roadmr wonders if the question is understandable [19:22] roadmr: #ubuntu-devel or #ubuntu-motu would be better for this, but oneiric-proposed would be the place to propose a merge to [19:23] micahg: ok. [19:23] micahg: btw, thanks! you're always answering my dumb SRU questions, you must hate me by now :) [19:23] roadmr: oops, you're in the right channel :) [19:23] roadmr: I'm used to seeing you in #ubuntu-bugs [19:24] micahg: hehe well sorry if I've been asking devel stuff in -bugs, too many channels! argh [19:24] roadmr: there are no dumb questions :), we're all learning [19:26] micahg: ok so I'll branch the current oneiric-proposed, prepare my fixes and request a merge on that [19:27] roadmr: branching for the first SRU from the release branch is only out of necessity since the -proposed branch doesn't exist until the first SRU is uploaded [19:28] micahg: oh I see, well that makes sense - and subsequent SRUs, if needed, would go to -proposed then? [19:28] roadmr: right [19:28] awesome :) thanks [19:29] roadmr: just keep in mind, if there's a security update, you'll need to branch from -updates or -security to get the full history (sometimes you might have to rebase -proposed onto security if the security team is forced to drop a fix in their upload) [19:30] micahg: ok, I'll be careful with that if the need arises === salem_ is now known as _salem [20:59] micahg: Done. [21:00] infinity: ooh, thanks :) [21:05] infinity: can you copy {firefox,mozvoikko,ubufox}/natty from ubuntu-mozilla-security to natty-proposed please? [21:13] micahg: Done, done, and done. [21:13] infinity: thanks :) [21:26] infinity: can we copy for oneiric and permakill the powerpc firefox build before it hangs the buildd [21:30] infinity: I don't want to risk hanging one of the powerpc buildds over the weekend, so if we can't, then we'll wait until monday [21:31] does it hang 100% of the time on ppc? [21:32] Laney: ATM, it seems to, we're disabling the tests which should in theory "resolve" the issue, but I don't want to test that w/out a safety net (i.e. someone to push the power button) either [21:35] ah OK. I was going to suggest p-a-sing it at least for the buildds' sake, and investigating why it builds for Debian but not us. [21:35] oh, i don't know if Debian's running the tests, I got the FTBFS fix from them [21:39] I am trying to see but the build log killed my firefox :-) [21:40] can I use p-a-s on a stable release? [21:41] infinity knows [22:00] infinity: if you get a chance and you can permakill the powerpc build, please copy {firefox,mozvoikko,ubufox}/oneiric from ubuntu-mozilla-security to oneiric-proposed, if not, don't worry about it, I"ll look into it Monday [22:00] * micahg has to run === EyesIsServer is now known as EyesIsAsleep