[00:35] qt may be easier than I thought to forward port [00:35] I'm still not crazy about the patch, it's rather hairy due to a bunch of #ifdefs [00:35] but there really isn't that much that changed between the two implementations [00:36] and the bits that did change are easy to fix [00:37] * cnd is running a test build of qt on behemoth [00:44] Yay behemoth! [00:44] At least that quad core monstrosity is good for something :) [03:49] when I upgraded behemoth this morning, it installed a bunch of i386 packages [03:49] I have no idea why [03:50] Either breakage, or dependencies that dropped out of ia32-libs? [03:53] apt can now sometimes do that if something's uninstallable on amd64, but a multi-arch: foreign alternative is installable. [03:58] dunno [03:58] I've done a lot to behemoth [03:58] and I may have only ever wiped it once since I've had it [03:58] so there's bound to be a lot of cruft [03:58] on the plus side, I've got qt and multitouch working! [03:59] it was much easier than I thought it would be [03:59] Sweet! That was fast. [03:59] Hows about a synaptics that doesn't reset to (0,0) at infuriatingly frequent, yet seemingly random, intervals? :) [03:59] I'll be pushing it in a few mins [03:59] Or, even better, do you see that behaviour? [03:59] heh, you'll have to wait a bit on that [03:59] I don't even have a rebuilt synaptics installed yet [04:00] and because I partially upgraded qt on my system to test [04:00] You haven't upgraded from the staging PPA? [04:00] it would be easier for me to just try it tomorrow [04:00] apt-get is useless if it thinks your packages are in a broken state [04:00] it needs a "I know what I'm doing, just install these other packages please" option [04:01] Yeah, it's sucky that way. [04:02] The ppa is, at least, fully installable. [04:03] with the updated qt, unity-2d starts up [04:03] though I'm missing the dock [04:03] any ideas why that would be? [04:03] No idea - I *thought* that was missing geis, because that's what would happen with the non-multitouch frankenserver. [04:04] Is unity-2d-launcher spinning at 100% cpu still? [04:04] well, geis still won't work with this multitouch frankenserver [04:04] oh, it is [04:04] compiz does that too [04:04] so unity 3d is useless [04:04] and unity 2d's launcher is useless [04:05] gnome classic with effects is also useless due to the same compiz issue [04:05] GNOME Do, however, LIVES ON! [04:05] heh [04:05] I'm on vacation now though [04:05] I'll be back on the 3rd [04:06] Like essentially everyone else :) [04:06] I'm just uploading qt, and I'll send out an email to ubuntu-devel and ubuntu-x about the x-staging ppa [04:06] Doing anything interesting? [04:06] not much [04:06] Excellent! [04:06] heh [04:06] playing zelda skyward sword I guess [04:06] That can be the most fun. [04:06] yeah [04:06] less stress [04:07] urgh, the qt4-x11 tarball is huge [04:07] It's ~200MB, isn't it? [04:07] Don't try building it on a tmpfs :) [04:08] I'll be doing something similar, but with jml's bucks party, and running a one-shot D&D campaign while jml's here thrown into the middle :) [04:08] 215 MB [04:08] I have no clue what any of that is [04:08] I do know what a jml is :) [04:08] but the rest... [04:09] Buck's party not familiar to you? [04:10] I mean, it's not like *I* had one, but I thought they were pretty universal across UK/US-derived cultures. [04:11] no, I have no clue what a "Buck's party" is [04:11] oh, bachelor party! [04:11] yeah, I got it [04:13] Perhaps more commonly known as a "buck's night", to go with the feminine "hen's night". :) [04:14] yeah, those terms didn't make it across the atlantic [04:14] we have bachelor and bachelorette parties [04:14] don't know if I spelled the latter correctly [04:15] Heh. [04:26] RAOF, I'm getting this error: File qt4-x11_4.7.4.orig.tar.gz already exists in Primary Archive for Ubuntu, but uploaded version has different contents. [04:26] when I try to dput to the ppa [04:26] I tried downloading the exact orig tarball from precise [04:26] and then rebuilt the source package [04:26] it didn't even upload an orig.tar.gz, since the archive already has it [04:26] any ideas? [04:29] do -S -sd [04:29] bjsnider, what does that do? [04:30] it uploads without uploading the tarball [04:30] it assumes the tarball is already there [04:30] debuild -S -sd [04:30] yeah, the second time it didn't upload the tarball [04:30] the first time it did [04:30] * cnd wonders if the tarball is stuck in the ppa [04:31] what happened the second time? [04:31] same error came back [04:31] impossible [04:31] I have the emails :) [04:32] you did an -sd instead of an -sa, and dput the changes file, and got that error? [04:33] yeah [04:33] and you need to do the -sd against the tarball it's talking about, in precise, not your own tarball [04:33] correct [04:33] I downloaded the orig tarball from launchpad from the precise package overview page to be sure [04:33] that's one i have't seen before [04:34] I've seen weird issues like this before [04:34] I'm guessing it's a bug somewhere in soyuz, and someone may need to manually delete the tarball from the servers [04:34] did you ask in #launchpad? [04:35] I am right now :) [04:35] you could do a bit of trickery and add +0 to the version number, thus creating a unique tarball [04:36] but only if it's being superseded by a newer version soon enough [04:36] yeah, I'm not sure that will happen [04:36] ever in precise [04:47] bjsnider, it was still building against the bad tarball in ../build-area [04:47] I had only replaced the tarball in ../ [04:48] so it worked? [04:48] still building [04:50] uploading now [04:52] ok, it worked finally [04:53] cool [04:54] I don't like how bzr bd copies the orig tarball into the build-area [04:55] I can kinda see why they do it [04:55] but I think it just makes things more confusing when there are issues [04:55] they could just symlink and be done with it [04:55] anyways, I'm done [04:56] I'm off for the holidays, but I'll troll, as always :) [07:08] oh new qt didn't fix compiz [07:09] let's install gnome-shell then :) [07:15] yeah it works [07:16] cnd, hi [07:17] hi [07:17] tjaalton, new qt isn't finished building yet [07:17] but yeah, compiz seems borked [07:17] cnd, the inputstack of xserver git master and the 1.11+input2.2 should be "indentical", right? [07:18] that's the theory :) [07:18] cnd, could look at this https://launchpadlibrarian.net/88180194/buildlog_ubuntu-precise-amd64.xf86-input-wacom_1%3A0.12.0-0ubuntu3_FAILEDTOBUILD.txt.gz [07:18] it depends on whether you count the new InputOption API [07:18] yeah... [07:18] ricotz: wacom hasn't been ported [07:19] cnd, ah ok [07:19] that input option api was not backported from 1.12 [07:19] tjaalton, wacom worked fine with abi 15 [07:19] I couldn't be sure that it would not cause ABI/API issues with other drivers [07:19] cnd, i see [07:19] the whole option parsing API changed, IIRC [07:19] not just for input modules [07:20] cnd, wouldnt it be better the pull this in too rather than creating a "new" abi which isnt abi 16? [07:21] ricotz, we can't modify any ABI that would affect video drivers [07:21] i.e. the 1.11 nvidia and fglrx drivers must still work [07:21] I'm worried that the new option abi would conflict [07:21] alright [07:22] but the reported abi will be 16? [07:22] and, it's a little outside of the scope of what we really need to backport [07:22] yeah [07:22] ok [07:22] in wacom and one other driver (I think synaptics), we might have to dance around the input abi [07:22] synaptic works [07:23] https://launchpad.net/~ricotz/+archive/unstable/+packages [07:23] i havent rebuild them all yet [07:23] yeah, it might not be forward ported yet [07:23] ricotz: wacom d54d936146fa58fb10a1b6839e1413671f96f86e perhaps? [07:25] tjaalton, could be [07:25] probably all commits since 0.12 would be needed [07:33] oh strong work dude, removed the wrong disk from a live system :P [07:35] ah, no i didn't, thought the one would've been wd blue instead of black.. === yofel_ is now known as yofel === FernandoMiguel is now known as Fernando_xtmas === soreau_ is now known as soreau