[08:57] <apw> moin
[09:24] <ppisati> :(
[09:25] <ppisati> the dnsmasq instance in my router, this morning stopped working
[09:25] <ppisati> for some still unknown reason
[09:25] <ppisati> maybe it's on strike...
[10:08] <apw> ppisati, i had total admin interface "what interface" behaviour from mine over night
[10:09] <apw> ppisati, it got a poke in the eye this morning for its trouble
[10:09] <ogra_> geez, you are so mean to your machines 
[10:09] <ppisati> apw: well, in my case it was my cock up
[10:10] <ppisati> apw: i modified the config file but forgot to reload
[10:10] <ppisati> apw: so when i restarted it for the first time it sucked in the modification
[10:10] <ppisati> apw: and that screwed it up
[10:10] <ppisati> :P
[10:11] <apw> hehe ... oops
[10:11] <ppisati> apw: btw, do you have a script/way/$something to detect that there is a new kernel available for a specific release?
[10:12] <ppisati> apw: i would like something that i can use in a script
[10:13] <smb> ppisati, beside of dist-upgrade on the system I assume. :-P
[10:13] <ppisati> smb: yeah
[10:13] <ppisati> smb: i'm running precise on this board, but i can shave a *LOT* of stuff from the config
[10:14] <ppisati> smb: so i would like some sort of tool that detects that a new kernel is available, git fetch it, applies my config diff and kicks a build
[10:15] <smb> ppisati, I guess you could either directly check the latest commit of a master branch in git or rmadison output
[10:15] <apw> ppisati, recipe build in a PPA ?
[10:15] <ppisati> apw: yeah
[10:15] <ppisati> smb: rmadison? uhm
[10:15] <apw> rmadison -a source linux
[10:15] <smb> Though I think the mainline builds mostly would do what you need
[10:16] <smb> ppisati, or the line from apw, probably excluding the proposed lines
[10:17] <apw> rmadison -a source linux | grep precise-updates | awk '{print $3}'
[10:18] <infinity> -s precise-updates... Querying all dists and grepping is abusive to the remote end. :P
[10:18] <infinity> (Plus, 'rmadison -s precise-updates -a source linux' should generally return much more quickly)
[10:19] <apw> heh, indeed, i guess i should read the manual page more often
[10:19] <ppisati> nice, that's what i was looking for
[10:19] <smb> infinity, True. It became a bit better after moving lots of other things from that machine
[10:20] <infinity> smb: Other way around, rmadison itself moved to snakefruit with the other archive stuff.
[10:20] <infinity> (But yes, splitting lillypilly's load almost exactly in half was a pleasant side-effect of us moving off)
[10:21] <smb> infinity, Ah... ok, something moved and I did not care for the details except that it stopped taking ages
[10:21] <infinity> smb: All of ~ubuntu-archive moved.  Anything you see at people.c.c/~ubuntu-archive is actually a transparent proxy to our new machine.
[10:22] <infinity> And that includes rmadison, but that was just a nice side-effect of the deal.  The real motivation was to get permission-sensitive stuff like proposed-migration off a massively shared machine.
[10:24] <smb> Quite sensible. And at least it felt like some of that got more or more complicated because the responsiveness of lillipilly really went down a lot at some point
[10:24] <infinity> Yeah, lillypilly wasn't in a happy place.
[10:25] <infinity> I used to spend a lot of time running around neutering ~desktop and ~kernel processes on lillypilly so the archive scripts wouldn't be starved for I/O and cycles.
[10:25] <infinity> Now I don't care, and you guys can battle it out. :P
[10:26] <infinity> (But it seems much better in general with archive off there anyway)
[10:26] <smb> Heh, yeah I guess shanky is running from there, too
[10:26] <infinity> Is it?  I thought shankbot ran from one of bjf's home machines.
[10:27] <smb> Hm, maybe I am wrong
[10:27] <infinity> I actually kinda hope it does, since it has his LP creds.
[10:27] <infinity> Which really shouldn't be sitting on a shared account on lillypilly. :P
[10:27] <smb> But kinda would add a lot to the "bus problem" if it does...
[10:28] <infinity> It probably *should* be run with a role account from a tightly-controlled kernel team machine somewhere.
[10:28] <infinity> Or something cloudy.
[10:28] <apw> infinity, yep, we even have a role account, the problem is getting that account the creds it needed, like nominate rights
[10:29] <infinity> Actually, a role account would reduce the scariness a lot, since it wouldn't need to have much in the way of permissions.
[10:29] <infinity> Where as bjf's account is actually a bit scary to share.
[10:29] <smb> Yeah, that would be best... hm... not sure I would trust cloudy stuff with that
[10:29] <infinity> apw: I can give it series nomination privs.
[10:29] <apw> infinity, but we do have one, and it should be sorted out
[10:29] <infinity> smb: When I say "cloudy", I mean "prodstack", which should be quite trustable.
[10:29] <apw> we have the kernel robot or something which was intended for that
[10:30] <infinity> apw: Point me at said robot, and I'll give it the same nomination privs I gave bjf.
[10:30] <smb> infinity, ok less cloudy in the whereabouts
[10:30] <apw> infinity, whne i can remember its name :)
[10:32] <infinity> apw: ~kernel-ppa perhaps, or something else?
[10:32] <infinity> Probably a bad choice, if that's what you were planning on anyway.
[10:33] <infinity> A "Kernel Team Bug Robot" that *only* has permissions to mangle bugs would be ideal for privsep.
[10:33]  * smb thought that was one older approach and as scary in getting shared
[10:33] <smb> (the kernel-ppa one)
[10:35] <apw> infinity, something else ubuntu-kernel-bot i am pretty sure
[10:35] <smb> infinity, Something named like that would also have the advantage of stopping people to reason with the robot in bug reports
[10:35] <apw> i should check that belongs to us still
[10:36] <infinity> ubuntu.kernel.bot@gmail.com ...
[10:37] <infinity> The email address doesn't inspire confidence. :P
[10:37] <infinity> But then again, the archive robot isn't any better.
[10:59] <apw> infinity, heheh that i believe we own, it was one of those things you cannot have two accounts with the same addy, so you have to make a new address, then add the mailing list as a second one, and make it a preferred one
[10:59] <apw> infinity, but before you give it any privs let me find the password and confirm
[11:00] <infinity> apw: I hope by "mailing list" you mean "private alias expansion" or something.
[11:01] <infinity> apw: Cause having an LP account with a public mailing list as the owner is obviously very bad. :)
[11:02] <apw> infinity, heh who knows any more, ... but i think the one we made was kernel-janitor ... confirming now
[11:03] <apw> well i would be if compiz handn't just crashed when it opened the dash, something i didn't want it to do i would add
[11:03] <apw> 200% cpu it is managing to use, ARRRG
[11:03] <infinity> https://launchpad.net/~kernel-janitor is  linux.kernel.janitor@gmail.com 
[11:04] <infinity> So, looks like you have two bots.  Maybe cause someone forgot and made a second. :P
[11:05]  * infinity breaks down and orders a Nexus 5.
[11:05] <apw> heh yeah likely so ... that is leann's way but i have the password for the second according to my records, and if i could run firefox i could confirm
[11:05] <apw> infinity, a 5?  for what
[11:05] <infinity> apw: To replace my ancient phone.
[11:05] <infinity> I played with my friend's 5 last night and it's... Really nice.
[11:06] <apw> oh dear .... trusty X sucks ass
[11:06] <apw> i have nice shiney display corruption
[11:11] <davmor2> apw: I don't believe you, it can't be a shiny display if it's corrupted it can only be a broken display :P
[11:18] <apw> davmor2, heh ... it is a good job i only speak in sarcasm
[11:20] <davmor2> apw: damn did I forget the sarcasm tabs again "My bag"
[11:20] <ogra_> use your babelfish ;)
[11:29] <apw> bablefish don't speak sarcasm either :)
[11:37] <davmor2> apw: you must still be using bablefish 1.0 (US version)  You need to update to bablefish 2.0 (UK version) It assumes sarcasm at all times and is terribly shocked when there is none
[11:56]  * ppisati -> out for lunch
[11:58] <apw> davmor2, heh point indeed
[12:25] <apw> RAOF, yo, who do i whine at if on saucy i am getting character corruptions
[12:25] <apw> RAOF, on intel kit
[12:30] <infinity> apw: I'd try mlankhorst or tjaalton.
[12:31] <infinity> The former never idles in this channel, which is irritating.
[12:34] <tjaalton> apw: there are some bugs about it (still), like lp#1222871
[12:50] <apw> bug #1222871
[12:50] <ubot2> Launchpad bug 1222871 in xserver-xorg-video-intel (Ubuntu) "[gm45] Corrupted painting of window surfaces (L-shape tiling corruption?)" [Medium,New] https://launchpad.net/bugs/1222871
[12:51] <apw> ubot2, can't you learn lp# format please
[12:51] <ubot2> apw: I am only a bot, please don't think I'm intelligent :)
[12:51] <apw> no s*it
[12:51] <apw> tjaalton, that souds remarkably like mine
[13:00] <tjaalton> you can also just open bug strings formatted like that on terminator ;)
[13:00] <tjaalton> hmm I thought g-t supported those too, but no
[13:01] <apw> i think its lp:1222871
[13:05] <apw> they are all inconsistant for sure
[13:31] <apw> tjaalton, is there an upstream bug on ths L thing, that should be linked to the lP bug ?
[13:36] <tjaalton> apw: i'm not sure.. perhaps not but ickle is on lp
[13:36] <apw> tjaalton, yeah i noticed that with supprise
[19:24] <trevorj> Sorry, I don't mean to spam across multiple channels, I just realised #ubuntu-kernel existed.
[19:24] <trevorj> Hi guys, I compile a custom flavor of the Ubuntu kernel for our boxen here based on Ubuntu's kernel git. I've been trying to figure out the proper way to create a source package that I can upload to an apt repo. Anyone have any experience with this?
[19:52] <melodie> hello
[19:53] <melodie> I would like to know wether the 3.8.x-generic series for Precise have PAE enabled or not enabled. Does someone know about that?
[19:55] <melodie> I have seen the 3.11 does, and the 3.2.x don't. But the latest 3.2.0-55 and -56 don't support zram-config (bug #1246664)
[19:55] <ubot2> Launchpad bug 1246664 in linux (Ubuntu Precise) ""Buffer I/O error on device zram0, logical block 515067"" [Medium,Fix committed] https://launchpad.net/bugs/1246664
[20:35] <melodie> Will the kernel series 3.2.0-x for Precise always be PAE free until 2017?
[20:48] <melodie> I got the answer
[20:48] <melodie> which is "yes, that is the idea"
[20:49] <melodie> does someone know when the fix done by henrix as per #1246664 will be integrated in the kernel? 
[22:59] <melodie> hi again
[23:00] <melodie> is there someone here who is in charge of the kernel 3.2.0-x for Precise, and who could say when the patch for zram will be integrated?
[23:00] <melodie> #1246664
[23:00] <melodie> bug #1246664
[23:00] <ubot2> Launchpad bug 1246664 in linux (Ubuntu Precise) ""Buffer I/O error on device zram0, logical block 515067"" [Medium,Fix committed] https://launchpad.net/bugs/1246664