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