=== sv is now known as discopig [00:21] * Fudge enjoys reading your conversations guys [04:44] hi all :) can anyone tell me how to get Ubuntu's patches for gcc 4.7 in ubuntu 12.10 ? i don't have ubuntu 12.10 i have ubuntu 12.04 [04:47] hdon: You can install the ubuntu-dev-tools package, which contains pull-lp-source, which you can run as “pull-lp-source gcc-4.7 quantal”, which will get you the source package for gcc-4.7 in 12.10. [04:48] RAOF, perfect answer. thanks! [04:48] I might have the order of the pull-lp-source arguments around the wrong way, but it should be fairly obvious if I've done that :) [04:54] The syntax is correct. [04:59] slangasek: https://blueprints.launchpad.net/ubuntu/+spec/foundations-1305-image-based-updates is very interesting to us (openstack-on-openstack) - we're heading that way anyway to do operations at scale. [04:59] slangasek: it might be nice if we can collaborate somehow [05:29] lifeless: perhaps you could discuss with stgraber next week during UDS? (If those times work) [05:29] slangasek: I'll try, I'm in CA next week, so it may work well... [05:31] slangasek: if I can't I'll get someone else on the team to chat [05:31] lifeless: great :) [05:34] slangasek: where is the schedule ? [05:36] lifeless: http://summit.ubuntu.com/uds-1305/; the foundations track for some reason hasn't autoscheduled yet though, looking at this now [05:37] kk [05:37] slangasek: I can't do monday, as I fly in on Monday [05:37] the sessions are Tue-Thu anyway [05:39] ah, evidently I misread and there's no autoscheduling [05:39] hand-scheduling it is, then [05:41] lifeless: provisionally scheduled for Tuesday, if that's ok [05:41] slangasek: cool; what time? [05:42] lifeless: 1800UTC [05:44] slangasek: so, 11am in CA I think? [05:44] yes [05:44] slangasek: cool, I should be able to do that. [05:44] \o/ [05:52] slangasek: Hrm, if you're manually scheduling, can you do specless meetings too? [05:52] infinity: technically yes, but at the moment I'm heading to bed. Shoot me an email with details? Or create a spec? :) [05:52] slangasek: I was going to register a pointless spec for "review the release schedule with flavor leads and interested parties", but since it's likely to generate zero work items, a meeting would be easier. [05:53] slangasek: I'll email. [05:53] slangasek: Done. [06:13] smoser: where is the right place to report bugs on cloud images? [06:16] lifeless, if its not a pakcage, file just in ubuntu and tag a s 'cloud-images' [06:16] and subscribe utlemming and i [06:17] smoser: thanks. the thing is that 'vga=normal nomodeset' is needed on the kernel command line to not break ILO's. [06:17] smoser: I consider unbreakme options bugs :> [06:18] i think you dont need vga=normal [06:18] i think the nomodeset is enough [06:28] smoser: what package would need to change to make nomodeset not be needed on Ubuntu server? [06:28] by default, not by grub setting it. [06:32] smoser: filed https://bugs.launchpad.net/ubuntu/+bug/1178115 for you [06:32] Launchpad bug 1178115 in Ubuntu "nomodeset is needed on server environments for ILO to be usable" [Undecided,New] [06:32] smoser: enjoy :) [06:43] pitti: FYI, I've just uploaded mathjax 2.1 to sid (so calibre is no longer blocked) [06:49] cjwatson: hi === megha is now known as baba === doko_ is now known as doko [07:57] hi Mirv, is that expected that we don't have a qtbase5-doc package? === Phonon is now known as Phonon5 === tkamppeter_ is now known as tkamppeter === mmrazik is now known as mmrazik|lunch === mmrazik|lunch is now known as mmrazik [11:25] cjwatson: lots of interesting feedback on your proposal so far [11:27] Yes === mmrazik is now known as mmrazik|afk [12:20] stgraber: I suppose you are the guy who makes this happen? http://people.canonical.com/~stgraber/package_sets/saucy/ubuntustudio [12:22] stgraber: I guess some packages don't need to be there, like automake1.7? No problem for me. But, everything we use otherwise should be there, right (i.e. nothing is missing)? [12:27] bwt, is there some place where flavor developers could put cron job scripts, to check up on things, and then if something interesting was found, mail that to a mail list? I'm thinking of setting things like this up for Ubuntu Studio [12:28] if automake1.7 is there it's because something in ubuntustudio is (directly or indirectly) using it, but the core system isn't. === _salem is now known as salem_ [13:07] t === mmrazik|afk is now known as mmrazik [14:00] Mirv: ping (if around) === kentb-out is now known as kentb [14:12] jodh: hi! what is the status of cgroups in upstart? [14:13] ogra_: I have updated nvidia-graphics-drivers-tegra3 and nvidia-tegra-codecs-cardhu to the latest release in this PPA (in case you want to upload them in saucy): https://launchpad.net/~canonical-x/+archive/x-staging [14:19] jdstrand: still at the consideration stage. do you have a use-case? [14:20] jodh: I think they might become quite interesting for application lifecycle. ted blogged about gould.cx/ted/blog/Application_Centric_User_Experience, which is something we can do immediately [14:21] jodh: if apps are launched via users like this, that provides a place for resource monitoring and controls [14:21] jodh: which the application lifecycle guys are likely interested in [14:23] jodh: I was more just curious. I saw something on the mailing from scott on how it might work and didn't know if anything came of it [14:24] jdstrand: right. The plan this cycle is to work on section 2.3 of https://lists.ubuntu.com/archives/upstart-devel/2011-August/001707.html. Have to see if we can stretch as far as 2.3.3 :-) [14:24] jdstrand: IIRC what we discussed back at the sprint is to simply have the pre-start stanza of the job create the new cgroup and move itself to it === francisco is now known as Guest49017 [14:25] jodh, stgraber: ack, thanks [14:49] jdstrand: iptables is in the merge-blacklist (a text file only on the merges.ubuntu.com master machine which causes it to silently ignore merges - I hate it, but haven't got rid of it yet), so it's well behind Debian. Do you have any idea if there's a particular reason it shouldn't normally be merged? [14:50] I'm sort of guessing that at one point it broke MoM, but I don't actually know [14:50] cjwatson: no, not otoh. there is definitely a delta that we want to keep, but I don't see why we would not want to include it in MoM [14:50] err merges.ubuntu.com [14:50] Yeah, that's what I thought [14:51] I've kicked it out now, so with any luck it'll appear on merges.u.c in the next run [14:51] cool, thanks :) [14:51] (or else it'll crash and I'll cry) [14:51] heh [15:36] just wondering: any reason why there isn't a package for libxenapi? [15:36] cjohnston: I made a session, how do I subscribe people and get it scheduled? http://summit.ubuntu.com/uds-1305/meeting/21779/kubuntu-and-uefi-and-lts-backports/ [15:37] edit meeting to subscribe people, and ask the track lead for scheduling [15:37] does it need to be client-s-? [15:38] or whatever the prefix is [15:38] libxenserver, pardon [15:38] since it was created in summit and not as a blueprint, no [15:39] sweet [16:03] cjohnston: what if the people don't appear in the people list? [16:03] Riddell: then tell them to register [16:04] cjohnston: how do I find out the track lead? [16:05] the emails that have been sent out, summit, fridge, planet, etc [16:08] cjohnston: how come the track lead for foundations is on holiday during uds? [16:08] I don't make the rules [16:08] slangasek: could you schedule http://summit.ubuntu.com/uds-1305/meeting/21779/kubuntu-and-uefi-and-lts-backports/ before 17:00UTC on any day? [16:09] slangasek: if your on vacation next week, should we have another track lead? [16:15] cjohnston: yes, I've already asked mhall119|away to make cjwatson and bdmurray the track leads, but it seems this isn't done yet - could you take care of it? [16:16] Riddell: scheduled for Wednesday [16:18] slangasek: thanks [16:18] cjwatson: are you registered for UDS? I didn't see you in the people I could subscribe [16:18] slangasek: neither are registered. [16:19] cjohnston: they have to be registered to be made the track lead? [16:19] yu [16:19] Riddell: yeah, I just remembered from the above conversation that I needed to ... [16:19] p [16:19] yeesh [16:19] bdmurray: ^^ please register for UDS :) [16:19] slangasek: done [16:19] clearly we suck [16:20] Riddell: FWIW the problems you blogged about look awfully like the ones that Steve McIntyre fixed at the 11th hour before wheezy [16:20] cjwatson: uefi ones? [16:20] Yeah, specifically Debian #698914 [16:20] Debian bug 698914 in grub-efi "grub-efi booting Windows 8 in UEFI mode" [Serious,Fixed] http://bugs.debian.org/698914 [16:21] I pulled half that fix into saucy today - other half is bug 1178072 and should be soon [16:21] bug 1178072 in os-prober (Ubuntu) "Update to 1.58" [Low,In progress] https://launchpad.net/bugs/1178072 === wedgwood_away is now known as wedgwood [16:21] slangasek,cjohnston: registered now [16:21] ack [16:22] cjohnston: how can I add cjwatson to my session? if I follow Review Attendeed I just get an empty page http://summit.ubuntu.com/uds-1305/attendee_review/21779/kubuntu-and-uefi-and-lts-backports/ === mmrazik is now known as mmrazik|afk [16:23] the same way as last time.. [16:24] cjwatson has been added as a lead, I'll add bdmurray when it imports [16:35] slangasek: so I'm working on this phased updates / regression detection stuff and ran across an interesting case in https://errors.ubuntu.com/problem/a6b1afd5be6decd8e488e35a98b69d1535246d83 [16:36] Its showing up as a new bucket for zenity version 3.4.0-0ubuntu4 [16:36] however, we can see it was reported about 3.4.0-0ubuntu2 [16:36] its just that 3.4.0-0ubuntu3 had no reports of this crash [16:37] and our query uses previous_version=3.4.0-0ubuntu3 and new_version=3.4.0-0ubuntu4 [16:37] I guess there is a possibility it was fixed in 0ubuntu3 and then unfixed in 0ubuntu4 [16:46] bdmurray: the diff looks clean to me, is that bug 968534? [16:46] bug 968534 in zenity (Arch Linux) "zenity crashed with SIGSEGV in zenity_tree_dialog_response()" [Undecided,New] https://launchpad.net/bugs/968534 [16:46] bdmurray: nevermind, that probably happens because -0ubuntu3 was never released [16:47] mitya57: never released? [16:47] the difference between two versions is just 6 days [16:48] hrm, I couldn't find anything the source package publishing history in the launchpad api indicating it was not published [16:48] bdmurray: hmmm, interesting [16:48] bdmurray: I can't think of a good way to automatically distinguish this case from the case of a genuine regression [16:48] https://launchpad.net/ubuntu/+source/zenity/3.4.0-0ubuntu3/+publishinghistory doesn't have any "Published" entry [16:49] mitya57: ah, thanks I'll poke some more then [16:49] slangasek: yeah, I was thinking this may happen with packages that are quickly superseded [16:49] and your guess is also wrong because the only bug fixed in -0ubuntu3 was #968534 [16:50] mitya57: what guess are you referring to? [16:50] I guess there is a possibility it was fixed in 0ubuntu3 and then unfixed in 0ubuntu4 [16:51] right that was very hypothetical [16:56] zenity 3.4.0-0ubuntu3 was released - you can see that on the precise changes mailing list [17:00] slangasek: howdy! So I was thinking... would it be possible to automate SRU processes using autopkgtests? [17:03] bdmurray: ah right [17:03] -0ubuntu3: Mon May 7 [17:03] -0ubuntu4: Fri May 11 [17:03] so there's still a little change someone could trigger that bug in just 4 days === wedgwood is now known as wedgwood_away === wedgwood_away is now known as wedgwood === wedgwood is now known as wedgwood_away [17:22] roaksoax: automate in what sense? [17:22] roaksoax: if you can provide autopkgtests for the bug being fixed in the SRU, *and* you have robust tests for the rest of the package, then the SRU verification could be almost entirely automated [17:22] but most packages aren't there [17:23] slangasek: yeah so that's exactly what I mean. There's going to be SRU bugs that are easily reproduceable, which we can write tests for and have the whole process automated [17:24] slangasek: that would hugely improve the whole process, and I believe it would also free engineering time that's being "lost". Also allowing us to reduce the time it takes to release the fixes [17:24] roaksoax: sure; the more automation the better [17:25] this is largely what the security team does already, though not with the autopkgtest framework [17:26] slangasek: right! Yeah I think if we are able to provide that for the SRU process, it would be great (My idea came from doing a theorical escenario of automating the SRU process for a class on Total Quality Management I took this past semester) [17:27] $ unity --reset [17:27] ERROR: the reset option is now deprecated [17:27] so how do I unfsck my desktop nowadays? [17:33] zul: why did you add ubuntu branding to nginx? its not even main [17:33] + it broke it: bug 1174158 [17:33] bug 1174158 in nginx (Ubuntu) "Nginx fails to start on 13.04" [Medium,In progress] https://launchpad.net/bugs/1174158 [17:43] jtaylor: seems like adding branding to track market share is a good way to get it to main, no? [17:45] if that is stated in the changelog fine [17:45] neither the patch nor the changelog give any indication why this was done [17:45] I know now, so if you fix it I'm happy [17:46] jtaylor: doesn't the patch in the bug fix it? [17:46] mdeslaur: there's only ONE patch in the bug [17:47] and it's a reversal of the introduction of the branding [17:47] introduced in comment 5 [17:47] I don't know, probably, though it would be common courtesy if the person who broke it fixes it [17:47] TheLordOfTime: There's also my "verbal patch" in the bug. [17:47] infinity: which in -motu we'll test via a ppa [17:48] if that doesn't fix it once I get my raring VM loaded again, then we're back at comment 5's fix [17:48] jtaylor: sure, ping zul and ask him to fix it...he's at a sprint this week I believe, so wait until he gets back, and I'm sure he'll be glad to fix it [17:48] TheLordOfTime: I would have just uploaded that define swapping patch of mine, but I don't use nginx, nor do I have a sane way to test it, so I figured I'd leave it to someone who does and can. [17:48] infinity: if you could upload it as a .patch to the bug that'd make my job easier [17:49] (Of course, just reverting entirely, and then trying different options later is also sane) [17:52] infinity: my thought is to drop the ubuntu-branding patch as is and recreate it using your verbal patch in comment 7 [17:52] at least for testing [17:52] * TheLordOfTime doesn't feel a need to add a new patch to fix the other patch [17:52] if that works, i'll debdiff that and submit [17:53] TheLordOfTime: http://paste.ubuntu.com/5648561/ [17:53] TheLordOfTime: Please test. :) [17:53] that works too [17:53] Err. [17:53] Wait. [17:53] infinity: got to deploy my raring vm first. [17:53] :P [17:53] Let me fix that with brackets. [17:55] TheLordOfTime: http://paste.ubuntu.com/5648563/ <-- There, that one. I'll toss that at the bug too. Still untested, mind you. [17:55] infinity: the testing is going to be done by me anyways [17:55] * infinity test builds that to make sure he didn't do sometihng dumb. [17:55] infinity: this is why ppas can be useful :P [17:55] * TheLordOfTime has quite a few test PPAs [17:56] TheLordOfTime: Well, test-building on my laptop is probably only a few minutes, it's testing the actual package that is a bit tougher for someone who's never used it. [17:57] infinity: then thank goodness i'm here? :P [17:57] actually, better, thank goodness I track all the nginx bugs :P [17:57] TheLordOfTime: But, if you can test this for me, I'll happily do the uploads and babysit it through. [17:58] infinity: that's the plan, the only time I don't test something is when it's an upstream diff that fixes the bug and is already built in Debian xD [17:58] anyways... lemme finish getting my VM up. [17:58] It at least built successfully here, so that's something. :P [17:59] * TheLordOfTime kicks the unity launcher [17:59] try to open a terminal and it opens Skype... [17:59] >.> [18:00] TheLordOfTime: Attached the debdiff to the bug too, for safekeeping. [18:03] infinity: ack [18:04] * infinity test locally because he's feeling pedantic. [18:05] infinity: heh [18:05] hmm... this'll probably sit on the amd64 queue for a while... [18:05] hmmm... [18:05] At least 'nginx -t' passes. [18:05] wonder if I can get this bumped up in priority. [18:05] TheLordOfTime: Want my binaries? :P [18:06] infinity: please. [18:06] but... [18:06] TheLordOfTime: (I can bump your builds too, but this is faster) [18:06] put them somewhere I can wget [18:06] :P [18:06] * TheLordOfTime is working off of a server VM so.... :P [18:06] TheLordOfTime: http://lucifer.0c3.net/~adconrad/nginx/ [18:08] got it, just finishing up the VM [18:08] because the VM is being slow :/ [18:08] (can't test on this system i'm on because precise :/) [18:11] TheLordOfTime: So, testing here, nginx -t doesn't complain, and once started, the version string looks sane: [18:11] (base)adconrad@cthulhu:~/foo$ HEAD localhost | grep ^Server [18:11] Server: nginx/1.2.6 (Ubuntu) [18:11] infinity: lemme confirm, then if it works fine, i'll let you know. [18:11] * infinity nods. [18:12] Now, I should push this to Debian to do something clever with dpkg-vendor, instead of us carrying a silly branding delta forever. [18:13] So. Just spent an hour figuring out why our game didn't run in Ubuntu [18:13] Turns out it was badly packaged in 13.04 :( [18:13] (I mean, working w/ a user who said the game wasn't running for him) [18:14] Specifically, has a dependency on freeglut3 in the build that ubuntu packaged (is an optional dep for video recording) that was not put in the dependency list :( [18:14] infinity: that will be nice, given that this is the only change in our delta (except for some temporary patch) [18:15] nemo: File a bug, for bonus points, attach a patch, and read https://wiki.ubuntu.com/StableReleaseUpdates#Procedure [18:15] infinity: I already told him to do that [18:15] although it possibly should just be mentioned in the build bug [18:15] https://bugs.launchpad.net/ubuntu/+source/hedgewars/+bug/1073730 I assume [18:15] Launchpad bug 1073730 in hedgewars (Ubuntu) "Hedgewars 0.9.18 FTBFS on 13.04" [Wishlist,Fix released] [18:16] maybe we should even make it append " (Debian)" on Debian... [18:16] infinity: as for patch, I have no clue as to .deb packaging [18:19] https://bugs.launchpad.net/ubuntu/+source/hedgewars/+bug/1073730/comments/44 [18:19] Launchpad bug 1073730 in hedgewars (Ubuntu) "Hedgewars 0.9.18 FTBFS on 13.04" [Wishlist,Fix released] [18:19] nemo: it's already fixed but hasn't propagated to -updates yet [18:19] https://launchpad.net/ubuntu/+source/hedgewars/0.9.18-0.2ubuntu1.1 [18:19] ok [18:19] thanks [18:19] debfx: Lovely. [18:19] (Shame no one fixed the FTBFS in the same SRU) [18:20] gah, kernel updates... :/ [18:21] "The Blue Systems sprint has spent a lot of time confirming this fix allows you to again play the game" [18:21] infinity: FTBFS is some backport thingy? [18:21] Hahaha. [18:21] Riddell: Glad to see you're hard at work. [18:21] FTBFS = fail to build from source [18:21] ah [18:21] huh... [18:21] techie term for "WHOOPS YOU BROKE IT!" [18:21] is that our fault? [18:21] (in a manner of speaking) [18:21] um... i'll let someone else answer that one [18:21] our deps did change... [18:21] * TheLordOfTime goes back to stabbing nginx [18:22] nemo: I believe you provided us with a patch to fix the build on arm/powerpc, we just didn't apply it yet. [18:22] oh. arm. [18:22] * infinity nods. [18:22] infinity: so, hopefully in a very very short period of time we'll have clobbered the final 0.9.19 bugs [18:22] and we'll get to go through the whole multimonth process w/ ubuntu all over again :D [18:23] usually is a minor miracle if ubuntu users are able to play other linux users/OSX/Windows ;) [18:23] nemo: I'm sure we can sort out clever ways to speed that up. [18:23] s/ubuntu/ubuntu|debian/ [18:23] if we are lucky enough to time our release juuuust before the ubuntu release we can usually get at least some ubuntu users (full upgraded ones) on it [18:24] but we missed that window this time [18:24] and there was playdeb, but that shut down [18:24] If the package is cleanly backportable, it would be trivial to just update in the development release and backport to other supported releases. [18:25] If that's not the case today, I suspect you might be able to talk someone into helping make it so (Riddell appears to play the game, he may have an interest in being helpful, for instance) [18:25] * TheLordOfTime groans [18:25] stupid computer [18:26] infinity: 0.9.17 wasn't cleanly backportable but Evan got it patched and out the door a mere 2 months after release, which is "quite fast" for ubuntu ;) [18:26] infinity: has anyone reported a problem with apt where it doesn't install dependencies? [18:26] infinity: although even for current version would be nice. and usually that seems to take months. not so for gentoo/opensuse/bsd/fedora/whatever [18:28] infinity: hrm. correction date fail. .17 was released 11-19 and Evan had backport patch a mere 2 days later! [18:28] was the .16 release that was september [18:28] so. I think that was probably the fastest ubuntu turnaround ever. possibly faster than any other distro actually [18:28] ah there we go [18:30] infinity: works [18:30] infinity: jtaylor: the latest patch/debdiff seems to correctly fix the situation [18:31] so you should be OK to use that as a solution for Raring [18:31] (for Bug 1174158) [18:31] bug 1174158 in nginx (Ubuntu Raring) "Nginx fails to start on 13.04" [Medium,Triaged] https://launchpad.net/bugs/1174158 [18:32] TheLordOfTime: I'll just steal the bug and upload. [18:32] TheLordOfTime: Could you do me a huge favour and add the SRU boilerplate to the bug description? [18:32] infinity: the wha... [18:32] oh you mean the template [18:32] um... sure... [18:32] if i had the link to it still [18:32] \o/ [18:33] TheLordOfTime: https://wiki.ubuntu.com/StableReleaseUpdates [18:33] https://wiki.ubuntu.com/StableReleaseUpdates#Procedure [18:33] Or https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template even. [18:36] TheLordOfTime: Uploaded to both saucy and raring. [18:36] infinity: adding the description shortly [18:36] mitya57: ping, update your merge stuff! [18:37] infinity: added SRU boilerplate [18:39] infinity: any way to skip -proposed for Raring on this? [18:39] (or did you upload directly to -updates) [18:39] TheLordOfTime: Skip, no. But I can expedite the SRU once it's been built and verified. [18:40] awesome [18:40] TheLordOfTime: It doesn't need the 7-day baking period, given the current broken state, but I still want the final binaries tested at least once. [18:40] mmkay [18:41] bdmurray: Feel like being a charitable SRU team member, since it seems a bit silly for me to review/accept my own upload? :P [18:42] infinity: sure give me a bit though [18:43] Oh, hrm, I should have merged with Debian for saucy instead of uploading this version. La la la. [18:43] * mitya57 is looking [18:43] infinity: hehe [18:45] err, infinity uploaded that? :( [18:45] mitya57: ? [18:45] infinity: did you see https://code.launchpad.net/~mitya57/ubuntu/saucy/nginx/1.4.1 ? [18:46] it was linked to that bug [18:46] mitya57: Ahh, well, feel free to upload 1.4.1, but please use the new branding patch instead of dropping it. [18:47] ok, I'll rebase my branch that when your change hits the udd branch [18:47] s/that/then/ [18:47] Also: [18:47] - Modify default site configuration file to correct a typo [18:48] that prevented out-of-the-box usability (LP: #1162177). [18:48] Launchpad bug 1162177 in nginx (Ubuntu) "nginx-light: invalid parameter "ipv6_only=on"" [High,Fix released] https://launchpad.net/bugs/1162177 [18:48] ^-- Isn't that merged upstream correctly now? [18:48] s/upstream/with Debian/ [18:48] infinity: i don't know yet i just saw a bug on that... [18:48] * TheLordOfTime opens his emails [18:49] infinity: that is merged, but the correct parameter name is "ipv6only" (without "_") [18:49] Debian Bug #707332 [18:49] Debian bug 707332 in src:nginx-common "nginx-common: Typo in conf/sites-available/default" [Normal,Open] http://bugs.debian.org/707332 [18:49] Well, their sites-available/default looks a lot like ours now. [18:49] infinity: then they didn't close their bug :P [18:49] Oh, nevermind. I missed the underscore. [18:49] So, yeah, we still have that 1-char delta. :P [18:50] TheLordOfTime: #707332 was filed by /me today's morning :) [18:50] mitya57: eheh [18:50] yeah, so it's not fixed yet :P [18:51] TheLordOfTime: *nod*... I misread their adding the keyword as them having added it correctly. ;) === wedgwood_away is now known as wedgwood === wedgwood is now known as wedgwood_away [18:54] bdmurray: While I'm bugging you, I'm going to need your superpower to edit meta-release today. [18:55] infinity: okay, what SRU did you want looked at? [18:56] bdmurray: nginx/raring [18:59] stgraber: any discussion a tthe sprint about default cgroup config for users at login (i.e. for memory controls)? [19:00] hallyn_: nope. We briefly discussed potential use of the freezer cgroup for apps but that's about it [19:00] ok, thanks === wedgwood_away is now known as wedgwood === wedgwood is now known as wedgwood_away [19:39] bdmurray: you are a track lead now [19:43] cjohnston: thanks === jono is now known as Guest61463 === megha is now known as baba === smb` is now known as smb [21:10] thomi: ping [21:10] plars: hey [21:10] thomi: I'm trying to install latest autopilot-touch and it wants python-ubuntu-platform-api, where's the best place to get it from? [21:11] plars: for raring? [21:12] thomi: yes [21:15] plars: ok, the best place is ppa:autopilot/ppa - but I just had to binary copy the package, since it hadn't landed since we switched PPAs [21:15] plars: so, give it 10 minutes maybe [21:15] thomi: ah, ok. That's where I was trying to pull from but it wasn't finding it [21:15] thomi: thanks, will check back in a bit [21:15] plars: yeah, we switched the PPA, but since we haven't merged anything into trunk autolanding never triggered [21:15] understande === salem_ is now known as _salem [21:40] Anyone know a nice way to be notified of changes in a package set, such as http://people.canonical.com/~stgraber/package_sets/saucy/ubuntustudio? [21:42] zequence: I can have queuebot join your IRC channel and announce the changes there. Note that any packageset change is also announced in #ubuntu-release by queuebot [21:46] stgraber: I was actually looking at forwarding to a mail list. Didn't think about IRC. I think that would be nice, if we were only alerted of our own package set [21:47] good evening all from the UK [21:47] Just got the script make_report.py, and realized there may be LP API that can be used [21:54] zequence: yeah, you can easily query through the API but there's no e-mail subscription for that part [21:55] zequence: I can have queuebot join your channel and just show changes related to your packageset or you can write your own script (you probably want to look at edit_acl query -P ubuntustudio -S saucy in lp:ubuntu-archive-tools) [22:01] stgraber: Ah, thanks. I'll have a look :) === kentb is now known as kentb-out [22:11] directhex, ping [22:25] cyphermox: hi, did you happen to see my follow-up on bug #1004775? [22:25] bug 1004775 in network-manager (Ubuntu Precise) "NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup" [High,In progress] https://launchpad.net/bugs/1004775 [22:26] slangasek: argh, I hadn't seen it [22:26] you're obviously right, I forgot to re-apply this change [22:31] barry, online? [22:31] doko: yep === francisco is now known as Guest79778 === _salem is now known as salem_ === salem_ is now known as _salem