[00:27] bryceh: yeah sorry, i haven't been putting keyboard into edgers which was the problem [00:27] i actually resurrected that dead package a few releases ago with a sync.. [00:27] it wasnt in lucid [00:32] * Sarvatt kicks self for https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-keyboard/+bug/680049 [00:32] Launchpad bug 680049 in xserver-xorg-input-keyboard (Ubuntu) "Sync xserver-xorg-input-keyboard 1:1.5.0-1 (universe) from Debian experimental (main)" [Wishlist,Fix released] [00:32] Who uses -keyboard, anyway? [00:33] nokidding [00:34] hurd? [00:34] :) [00:34] Does the doko's AC100 still use -keyboard, or has nvidia joined the evdev generation? [00:37] evdev was fine on that when i last used one in dublin [00:43] Sarvatt, https://launchpad.net/~thebernmeister/+archive/indicator-ppa-download-statistics [00:43] that supposedly is an indicator that provides ppa download numbers [00:44] so you can track edgers and w hatnot [00:54] bjsnider: holy crap, with how slow querying the info is off launchpad i'm scared to try it :) [00:55] 50% cpu usage for 2 hours at a time to update it ftw [00:55] giving it a shot now though, thanks for the heads up because it looks neat :) [00:55] to update what? [00:56] download statistics? [00:56] ok, that's a bit of a problem [00:58] i hope you report that to wgrant or somebody [00:58] whoops, he's actually in this channel [00:59] it was actually really fast [01:00] and xorg-edgers lost a crapton of users :) [01:03] 8k amd64 downloads of openchrome that hasnt been updated since feb and automatically installed, 7.7k on i386, was closer to 45k total in 10.10 [01:19] Sarvatt: 50% CPU usage!? [01:19] that doesn't sound like a Launchpad problem :) [01:20] nah was talking about a real old crappy script, sorry for the ping :) [01:20] Note that there's a hole in the download stats from May 21 to June 25 that will be filled in in the next couple of weeks. [01:34] You know what's not super-fast? An atom building mesa. [01:39] Sarvatt, any idea why the user count went down? [06:46] bryceh: heh, indeed [06:52] morning [06:53] RAOF: try an atom building x over nfs [06:58] on wireless :-) [07:55] hm, should the renamed version be oldversion~precise1 or oldversion-precise1, I can only do the former with --force-bad-version but I don't know if it will break anything or not.. [08:00] one way to find out I suppose [08:01] the latter would be newer than "oldversion" [08:01] which breaks upgrades [08:02] tjaalton: yeah but I don't know if anything will subtly break by resetting version to below the previous changelog entry [08:02] That happens all the time with backports [08:03] mlankhorst: no, it'll still upgrade from precise [08:03] that's how sru's are versioned too [08:03] ah k [08:03] hmm [08:04] yeah I don't expect to be able to upgrade from xorg q stack to q afterwards, but maybe r will be possible with q stack [08:04] maxb: what do you mean, having to use --force-bad-version? [08:05] wonder why that's needed tho, since it's a valid version [08:05] having changelog versions less than the previous [08:05] ah [08:05] yes, more common there than -updates [08:05] because of the policy [08:05] well dch won't complain if you do it by hand :-) [08:06] oh it's dch.. then ignore the warning :) [08:07] tjaalton: yeah using the xorg-pkg-tools rename scripts, fixed them to add ~precise1 to version instead of bumping it [08:07] yep, sounds about right [08:12] I should probably have to re-upload them all to fix it for all packages [08:12] you can't, if the version is older [08:12] not on the same ppa [08:12] even if deleted? [08:12] nope [08:13] why did wacom just say accepted then? [08:13] (although that build failed on all) [08:14] which versions? [08:14] the old & new [08:14] think original was 1:0.14.0-0ubuntu3+rename2.1, now 1:0.14.0-0ubuntu3~precise1 [08:16] hm, weird [08:16] maybe launchpad got updated then [08:17] because I'm certain that wasn't possible before [08:17] same [08:18] wgrant: hey, you should know ^ :) [08:18] else I wouldn't mind if the whole ppa was flushed out, I could just re-upload it [08:19] this is great news if it's true, since a simple mistake could render a package useless on a ppa [08:19] before, that is [08:20] tjaalton: If you wait a few hours after deleting you can upload an older version. [08:20] It's always been the case. [08:20] Although it used to take a day or so. [08:21] But you can still never upload the same version again. [08:21] oh [08:21] oh that's fine, I still have almost the full domain of natural numbers after ~precise1 :-) [08:22] don't waste them :) [08:22] You've got more; you've got the set of terminating decimals! [08:23] Technically that would be a ring. [08:23] (It's not closed under division, so it's not a field) [08:24] Which obviously means it's a proper subset of the rationals ;) [08:32] oh right testing frankendrm === Guest59153 is now known as kklimonda [08:41] xf86-video-nouveau with new nouveau works [08:54] RAOF: you weren't kidding about mesa hardcoding pkg-config calls.. eep [09:01] mesa seems to link with old nouveau abi [09:03] oh failure, something tries to link against new libdrm_nouveau.so [09:14] RAOF: at least.. MOST things were hardcoding drm_nouveau pkgconfig, others just did -ldrm_nouveau directly [12:12] sigh, does fglrx overwrite some part of X too? [12:14] glx [12:14] should be all [12:14] well and libGL [12:15] yeah looks like I'll have to reinstall precise on other system and test https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1009629 [12:15] Launchpad bug 1009629 in xorg-server (Ubuntu) "Xorg crashed with SIGSEGV in DeliverRawEvent()" [High,Fix committed] [12:17] I suspect user error but still [13:09] mlankhorst: let me check [13:10] mlankhorst: if users use the NVIDIA installer or the AMD installer (without generating deb packages) and overwrite our libraries, then yes, it can be a bit of a problem... [13:18] tseliot: yeah probably what's happening here, the annoying part is that the fglrx installer can create .deb files and most of the time they work [13:19] which would sidestep this [13:20] mlankhorst: yes, which is why I work on that part of the AMD installer... [14:11] tseliot: I just realized that I should see it as positive, more people testing than appearing on first sight. :) [14:16] heh === erappleman is now known as LLStarks === `rand` is now known as `rand`-AFK