[00:21]  * Fudge enjoys reading your conversations guys
[04:44] <hdon> 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] <RAOF> 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] <hdon> RAOF, perfect answer. thanks!
[04:48] <RAOF> 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] <ScottK> The syntax is correct.
[04:59] <lifeless> 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] <lifeless> slangasek: it might be nice if we can collaborate somehow
[05:29] <slangasek> lifeless: perhaps you could discuss with stgraber next week during UDS?  (If those times work)
[05:29] <lifeless> slangasek: I'll try, I'm in CA next week, so it may work well...
[05:31] <lifeless> slangasek: if I can't I'll get someone else on the team to chat
[05:31] <slangasek> lifeless: great :)
[05:34] <lifeless> slangasek: where is the schedule ?
[05:36] <slangasek> lifeless: http://summit.ubuntu.com/uds-1305/; the foundations track for some reason hasn't autoscheduled yet though, looking at this now
[05:37] <lifeless> kk
[05:37] <lifeless> slangasek: I can't do monday, as I fly in on Monday
[05:37] <slangasek> the sessions are Tue-Thu anyway
[05:39] <slangasek> ah, evidently I misread and there's no autoscheduling
[05:39] <slangasek> hand-scheduling it is, then
[05:41] <slangasek> lifeless: provisionally scheduled for Tuesday, if that's ok
[05:41] <lifeless> slangasek: cool; what time?
[05:42] <slangasek> lifeless: 1800UTC
[05:44] <lifeless> slangasek: so, 11am in CA I think?
[05:44] <slangasek> yes
[05:44] <lifeless> slangasek: cool, I should be able to do that.
[05:44] <lifeless> \o/
[05:52] <infinity> slangasek: Hrm, if you're manually scheduling, can you do specless meetings too?
[05:52] <slangasek> infinity: technically yes, but at the moment I'm heading to bed.  Shoot me an email with details? Or create a spec? :)
[05:52] <infinity> 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] <infinity> slangasek: I'll email.
[05:53] <infinity> slangasek: Done.
[06:13] <lifeless> smoser: where is the right place to report bugs on cloud images?
[06:16] <smoser> lifeless, if its not a pakcage, file just in ubuntu and tag a s 'cloud-images'
[06:16] <smoser> and subscribe utlemming and i
[06:17] <lifeless> smoser: thanks. the thing is that 'vga=normal nomodeset' is needed on the kernel command line to not break ILO's.
[06:17] <lifeless> smoser: I consider unbreakme options bugs :>
[06:18] <smoser> i think you dont need vga=normal
[06:18] <smoser> i think the nomodeset is enough
[06:28] <lifeless> smoser: what package would need to change to make nomodeset not be needed on Ubuntu server?
[06:28] <lifeless> by default, not by grub setting it.
[06:32] <lifeless> smoser: filed https://bugs.launchpad.net/ubuntu/+bug/1178115 for you
[06:32] <lifeless> smoser: enjoy :)
[06:43] <mitya57> pitti: FYI, I've just uploaded mathjax 2.1 to sid (so calibre is no longer blocked)
[06:49] <zyga> cjwatson: hi
[07:57] <mitya57> hi Mirv, is that expected that we don't have a qtbase5-doc package?
[11:25] <zyga> cjwatson: lots of interesting feedback on your proposal so far
[11:27] <cjwatson> Yes
[12:20] <zequence> stgraber: I suppose you are the guy who makes this happen? http://people.canonical.com/~stgraber/package_sets/saucy/ubuntustudio
[12:22] <zequence> 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] <zequence> 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] <cjwatson> if automake1.7 is there it's because something in ubuntustudio is (directly or indirectly) using it, but the core system isn't.
[13:07] <mitz> t
[14:00] <mitya57> Mirv: ping (if around)
[14:12] <jdstrand> jodh: hi! what is the status of cgroups in upstart?
[14:13] <tseliot> 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] <jodh> jdstrand: still at the consideration stage. do you have a use-case?
[14:20] <jdstrand> 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] <jdstrand> jodh: if apps are launched via users like this, that provides a place for resource monitoring and controls
[14:21] <jdstrand> jodh: which the application lifecycle guys are likely interested in
[14:23] <jdstrand> 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] <jodh> 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] <stgraber> 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
[14:25] <jdstrand> jodh, stgraber: ack, thanks
[14:49] <cjwatson> 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] <cjwatson> I'm sort of guessing that at one point it broke MoM, but I don't actually know
[14:50] <jdstrand> 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] <jdstrand> err merges.ubuntu.com
[14:50] <cjwatson> Yeah, that's what I thought
[14:51] <cjwatson> I've kicked it out now, so with any luck it'll appear on merges.u.c in the next run
[14:51] <jdstrand> cool, thanks :)
[14:51] <cjwatson> (or else it'll crash and I'll cry)
[14:51] <jdstrand> heh
[15:36] <sonne> just wondering: any reason why there isn't a package for libxenapi?
[15:36] <Riddell> 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] <cjohnston> edit meeting to subscribe people, and ask the track lead for scheduling
[15:37] <Laney> does it need to be client-s-?
[15:38] <Laney> or whatever the prefix is
[15:38] <sonne> libxenserver, pardon
[15:38] <cjohnston> since it was created in summit and not as a blueprint, no
[15:39] <Laney> sweet
[16:03] <Riddell> cjohnston: what if the people don't appear in the people list?
[16:03] <cjohnston> Riddell: then tell them to register
[16:04] <Riddell> cjohnston: how do I find out the track lead?
[16:05] <cjohnston> the emails that have been sent out, summit, fridge, planet, etc
[16:08] <Riddell> cjohnston: how come the track lead for foundations is on holiday during uds?
[16:08] <cjohnston> I don't make the rules
[16:08] <Riddell> 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] <cjohnston> slangasek: if your on vacation next week, should we have another track lead?
[16:15] <slangasek> 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] <slangasek> Riddell: scheduled for Wednesday
[16:18] <Riddell> slangasek: thanks
[16:18] <Riddell> cjwatson: are you registered for UDS?  I didn't see you in the people I could subscribe
[16:18] <cjohnston> slangasek: neither are registered.
[16:19] <slangasek> cjohnston: they have to be registered to be made the track lead?
[16:19] <cjohnston> yu
[16:19] <cjwatson> Riddell: yeah, I just remembered from the above conversation that I needed to ...
[16:19] <cjohnston> p
[16:19] <slangasek> yeesh
[16:19] <slangasek> bdmurray: ^^ please register for UDS :)
[16:19] <bdmurray> slangasek: done
[16:19] <cjwatson> clearly we suck
[16:20] <cjwatson> Riddell: FWIW the problems you blogged about look awfully like the ones that Steve McIntyre fixed at the 11th hour before wheezy
[16:20] <Riddell> cjwatson: uefi ones?
[16:20] <cjwatson> Yeah, specifically Debian #698914
[16:21] <cjwatson> I pulled half that fix into saucy today - other half is bug 1178072 and should be soon
[16:21] <cjwatson> slangasek,cjohnston: registered now
[16:21] <cjohnston> ack
[16:22] <Riddell> 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/
[16:23] <cjohnston> the same way as last time..
[16:24] <cjohnston> cjwatson has been added as a lead, I'll add bdmurray when it imports
[16:35] <bdmurray> 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] <bdmurray> Its showing up as a new bucket for zenity version 3.4.0-0ubuntu4
[16:36] <bdmurray> however, we can see it was reported about 3.4.0-0ubuntu2
[16:36] <bdmurray> its just that 3.4.0-0ubuntu3 had no reports of this crash
[16:37] <bdmurray> and our query uses previous_version=3.4.0-0ubuntu3 and new_version=3.4.0-0ubuntu4
[16:37] <bdmurray> I guess there is a possibility it was fixed in 0ubuntu3 and then unfixed in 0ubuntu4
[16:46] <mitya57> bdmurray: the diff looks clean to me, is that bug 968534?
[16:46] <mitya57> bdmurray: nevermind, that probably happens because -0ubuntu3 was never released
[16:47] <bdmurray> mitya57: never released?
[16:47] <mitya57> the difference between two versions is just 6 days
[16:48] <bdmurray> hrm, I couldn't find anything the source package publishing history in the launchpad api indicating it was not published
[16:48] <slangasek> bdmurray: hmmm, interesting
[16:48] <slangasek> bdmurray: I can't think of a good way to automatically distinguish this case from the case of a genuine regression
[16:48] <mitya57> https://launchpad.net/ubuntu/+source/zenity/3.4.0-0ubuntu3/+publishinghistory doesn't have any "Published" entry
[16:49] <bdmurray> mitya57: ah, thanks I'll poke some more then
[16:49] <bdmurray> slangasek: yeah, I was thinking this may happen with packages that are quickly superseded
[16:49] <mitya57> and your guess is also wrong because the only bug fixed in -0ubuntu3 was #968534
[16:50] <bdmurray> mitya57: what guess are you referring to?
 I guess there is a possibility it was fixed in 0ubuntu3 and then unfixed in 0ubuntu4
[16:51] <bdmurray> right that was very hypothetical
[16:56] <bdmurray> zenity 3.4.0-0ubuntu3 was released - you can see that on the precise changes mailing list
[17:00] <roaksoax> slangasek: howdy! So I was thinking... would it be possible to automate SRU processes using autopkgtests?
[17:03] <mitya57> bdmurray: ah right
[17:03] <mitya57> -0ubuntu3: Mon May 7
[17:03] <mitya57> -0ubuntu4: Fri May 11
[17:03] <mitya57> so there's still a little change someone could trigger that bug in just 4 days
[17:22] <slangasek> roaksoax: automate in what sense?
[17:22] <slangasek> 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] <slangasek> but most packages aren't there
[17:23] <roaksoax> 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] <roaksoax> 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] <slangasek> roaksoax: sure; the more automation the better
[17:25] <slangasek> this is largely what the security team does already, though not with the autopkgtest framework
[17:26] <roaksoax> 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] <kirkland> $ unity --reset
[17:27] <kirkland> ERROR: the reset option is now deprecated
[17:27] <kirkland> so how do I unfsck my desktop nowadays?
[17:33] <jtaylor> zul: why did you add ubuntu branding to nginx? its not even main
[17:33] <jtaylor> + it broke it: bug 1174158
[17:43] <mdeslaur> jtaylor: seems like adding branding to track market share is a good way to get it to main, no?
[17:45] <jtaylor> if that is stated in the changelog fine
[17:45] <jtaylor> neither the patch nor the changelog give any indication why this was done
[17:45] <jtaylor> I know now, so if you fix it I'm happy
[17:46] <mdeslaur> jtaylor: doesn't the patch in the bug fix it?
[17:46] <TheLordOfTime> mdeslaur:  there's only ONE patch in the bug
[17:47] <TheLordOfTime> and it's a reversal of the introduction of the branding
[17:47] <TheLordOfTime> introduced in comment 5
[17:47] <jtaylor> I don't know, probably, though it would be common courtesy if the person who broke it fixes it
[17:47] <infinity> TheLordOfTime: There's also my "verbal patch" in the bug.
[17:47] <TheLordOfTime> infinity:  which in -motu we'll test via a ppa
[17:48] <TheLordOfTime> 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] <mdeslaur> 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] <infinity> 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] <TheLordOfTime> infinity:  if you could upload it as a .patch to the bug that'd make my job easier
[17:49] <infinity> (Of course, just reverting entirely, and then trying different options later is also sane)
[17:52] <TheLordOfTime> infinity:  my thought is to drop the ubuntu-branding patch as is and recreate it using your verbal patch in comment 7
[17:52] <TheLordOfTime> at least for testing
[17:52]  * TheLordOfTime doesn't feel a need to add a new patch to fix the other patch
[17:52] <TheLordOfTime> if that works, i'll debdiff that and submit
[17:53] <infinity> TheLordOfTime: http://paste.ubuntu.com/5648561/
[17:53] <infinity> TheLordOfTime: Please test. :)
[17:53] <TheLordOfTime> that works too
[17:53] <infinity> Err.
[17:53] <infinity> Wait.
[17:53] <TheLordOfTime> infinity:  got to deploy my raring vm first.
[17:53] <TheLordOfTime> :P
[17:53] <infinity> Let me fix that with brackets.
[17:55] <infinity> TheLordOfTime: http://paste.ubuntu.com/5648563/ <-- There, that one.  I'll toss that at the bug too.  Still untested, mind you.
[17:55] <TheLordOfTime> 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] <TheLordOfTime> infinity:  this is why ppas can be useful :P
[17:55]  * TheLordOfTime has quite a few test PPAs
[17:56] <infinity> 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] <TheLordOfTime> infinity:  then thank goodness i'm here? :P
[17:57] <TheLordOfTime> actually, better, thank goodness I track all the nginx bugs :P
[17:57] <infinity> TheLordOfTime: But, if you can test this for me, I'll happily do the uploads and babysit it through.
[17:58] <TheLordOfTime> 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] <TheLordOfTime> anyways... lemme finish getting my VM up.
[17:58] <infinity> It at least built successfully here, so that's something. :P
[17:59]  * TheLordOfTime kicks the unity launcher
[17:59] <TheLordOfTime> try to open a terminal and it opens Skype...
[17:59] <TheLordOfTime> >.>
[18:00] <infinity> TheLordOfTime: Attached the debdiff to the bug too, for safekeeping.
[18:03] <TheLordOfTime> infinity:  ack
[18:04]  * infinity test locally because he's feeling pedantic.
[18:05] <TheLordOfTime> infinity:  heh
[18:05] <TheLordOfTime> hmm... this'll probably sit on the amd64 queue for a while...
[18:05] <TheLordOfTime> hmmm...
[18:05] <infinity> At least 'nginx -t' passes.
[18:05] <TheLordOfTime> wonder if I can get this bumped up in priority.
[18:05] <infinity> TheLordOfTime: Want my binaries? :P
[18:06] <TheLordOfTime> infinity:  please.
[18:06] <TheLordOfTime> but...
[18:06] <infinity> TheLordOfTime: (I can bump your builds too, but this is faster)
[18:06] <TheLordOfTime> put them somewhere I can wget
[18:06] <TheLordOfTime> :P
[18:06]  * TheLordOfTime is working off of a server VM so.... :P
[18:06] <infinity> TheLordOfTime: http://lucifer.0c3.net/~adconrad/nginx/
[18:08] <TheLordOfTime> got it, just finishing up the VM
[18:08] <TheLordOfTime> because the VM is being slow :/
[18:08] <TheLordOfTime> (can't test on this system i'm on because precise :/)
[18:11] <infinity> TheLordOfTime: So, testing here, nginx -t doesn't complain, and once started, the version string looks sane:
[18:11] <infinity> (base)adconrad@cthulhu:~/foo$ HEAD localhost | grep ^Server
[18:11] <infinity> Server: nginx/1.2.6 (Ubuntu)
[18:11] <TheLordOfTime> infinity:  lemme confirm, then if it works fine, i'll let you know.
[18:11]  * infinity nods.
[18:12] <infinity> 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] <nemo> So. Just spent an hour figuring out why our game didn't run in Ubuntu
[18:13] <nemo> Turns out it was badly packaged in 13.04 :(
[18:13] <nemo> (I mean, working w/ a user who said the game wasn't running for him)
[18:14] <nemo> 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] <mitya57> infinity: that will be nice, given that this is the only change in our delta (except for some temporary patch)
[18:15] <infinity> nemo: File a bug, for bonus points, attach a patch, and read https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
[18:15] <nemo> infinity: I already told him to do that
[18:15] <nemo> although it possibly should just be mentioned in the build bug
[18:15] <nemo> https://bugs.launchpad.net/ubuntu/+source/hedgewars/+bug/1073730  I assume
[18:16] <mitya57> maybe we should even make it append " (Debian)" on Debian...
[18:16] <nemo> infinity: as for patch, I have no clue as to .deb packaging
[18:19] <nemo> https://bugs.launchpad.net/ubuntu/+source/hedgewars/+bug/1073730/comments/44
[18:19] <debfx> nemo: it's already fixed but hasn't propagated to -updates yet
[18:19] <debfx> https://launchpad.net/ubuntu/+source/hedgewars/0.9.18-0.2ubuntu1.1
[18:19] <nemo> ok
[18:19] <nemo> thanks
[18:19] <infinity> debfx: Lovely.
[18:19] <infinity> (Shame no one fixed the FTBFS in the same SRU)
[18:20] <TheLordOfTime> gah, kernel updates... :/
[18:21] <infinity> "The Blue Systems sprint has spent a lot of time confirming this fix allows you to again play the game"
[18:21] <nemo> infinity: FTBFS  is some backport thingy?
[18:21] <infinity> Hahaha.
[18:21] <infinity> Riddell: Glad to see you're hard at work.
[18:21] <TheLordOfTime> FTBFS = fail to build from source
[18:21] <nemo> ah
[18:21] <nemo> huh...
[18:21] <TheLordOfTime> techie term for "WHOOPS YOU BROKE IT!"
[18:21] <nemo> is that our fault?
[18:21] <TheLordOfTime> (in a manner of speaking)
[18:21] <TheLordOfTime> um... i'll let someone else answer that one
[18:21] <nemo> our deps did change...
[18:21]  * TheLordOfTime goes back to stabbing nginx
[18:22] <infinity> 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] <nemo> oh. arm.
[18:22]  * infinity nods.
[18:22] <nemo> infinity: so, hopefully in a very very short period of time we'll have clobbered the final 0.9.19 bugs
[18:22] <nemo> and we'll get to go through the whole multimonth process w/ ubuntu all over again :D
[18:23] <nemo> usually is a minor miracle if ubuntu users are able to play other linux users/OSX/Windows ;)
[18:23] <infinity> nemo: I'm sure we can sort out clever ways to speed that up.
[18:23] <nemo> s/ubuntu/ubuntu|debian/
[18:23] <nemo> 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] <nemo> but we missed that window this time
[18:24] <nemo> and there was playdeb, but that shut down
[18:24] <infinity> 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] <infinity> 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] <TheLordOfTime> stupid computer
[18:26] <nemo> 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] <TheLordOfTime> infinity:  has anyone reported a problem with apt where it doesn't install dependencies?
[18:26] <nemo> 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] <nemo> infinity: hrm. correction date fail. .17 was released 11-19 and Evan had backport patch a mere 2 days later!
[18:28] <nemo> was the .16 release that was september
[18:28] <nemo> so. I think that was probably the fastest ubuntu turnaround ever. possibly faster than any other distro actually
[18:28] <TheLordOfTime> ah there we go
[18:30] <TheLordOfTime> infinity:  works
[18:30] <TheLordOfTime> infinity:  jtaylor: the latest patch/debdiff seems to correctly fix the situation
[18:31] <TheLordOfTime> so you should be OK to use that as a solution for Raring
[18:31] <TheLordOfTime> (for Bug 1174158)
[18:32] <infinity> TheLordOfTime: I'll just steal the bug and upload.
[18:32] <infinity> TheLordOfTime: Could you do me a huge favour and add the SRU boilerplate to the bug description?
[18:32] <TheLordOfTime> infinity:  the wha...
[18:32] <TheLordOfTime> oh you mean the template
[18:32] <TheLordOfTime> um... sure...
[18:32] <TheLordOfTime> if i had the link to it still
[18:32] <infinity> \o/
[18:33] <jtaylor> TheLordOfTime: https://wiki.ubuntu.com/StableReleaseUpdates
[18:33] <infinity> https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
[18:33] <infinity> Or https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template even.
[18:36] <infinity> TheLordOfTime: Uploaded to both saucy and raring.
[18:36] <TheLordOfTime> infinity:  adding the description shortly
[18:36] <TheLordOfTime> mitya57:  ping, update your merge stuff!
[18:37] <TheLordOfTime> infinity:  added SRU boilerplate
[18:39] <TheLordOfTime> infinity:  any way to skip -proposed for Raring on this?
[18:39] <TheLordOfTime> (or did you upload directly to -updates)
[18:39] <infinity> TheLordOfTime: Skip, no.  But I can expedite the SRU once it's been built and verified.
[18:40] <TheLordOfTime> awesome
[18:40] <infinity> 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] <TheLordOfTime> mmkay
[18:41] <infinity> 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] <bdmurray> infinity: sure give me a bit though
[18:43] <infinity> 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] <TheLordOfTime> infinity:  hehe
[18:45] <mitya57> err, infinity uploaded that? :(
[18:45] <infinity> mitya57: ?
[18:45] <mitya57> infinity: did you see https://code.launchpad.net/~mitya57/ubuntu/saucy/nginx/1.4.1 ?
[18:46] <mitya57> it was linked to that bug
[18:46] <infinity> mitya57: Ahh, well, feel free to upload 1.4.1, but please use the new branding patch instead of dropping it.
[18:47] <mitya57> ok, I'll rebase my branch that when your change hits the udd branch
[18:47] <mitya57> s/that/then/
[18:47] <infinity> Also:
[18:47] <infinity>   - Modify default site configuration file to correct a typo
[18:48] <infinity>     that prevented out-of-the-box usability (LP: #1162177).
[18:48] <infinity> ^-- Isn't that merged upstream correctly now?
[18:48] <infinity> s/upstream/with Debian/
[18:48] <TheLordOfTime> infinity:  i don't know yet i just saw a bug on that...
[18:48]  * TheLordOfTime opens his emails
[18:49] <mitya57> infinity: that is merged, but the correct parameter name is "ipv6only" (without "_")
[18:49] <TheLordOfTime> Debian Bug #707332
[18:49] <infinity> Well, their sites-available/default looks a lot like ours now.
[18:49] <TheLordOfTime> infinity:  then they didn't close their bug :P
[18:49] <infinity> Oh, nevermind.  I missed the underscore.
[18:49] <infinity> So, yeah, we still have that 1-char delta. :P
[18:50] <mitya57> TheLordOfTime: #707332 was filed by /me today's morning :)
[18:50] <TheLordOfTime> mitya57:  eheh
[18:50] <TheLordOfTime> yeah, so it's not fixed yet :P
[18:51] <infinity> TheLordOfTime: *nod*... I misread their adding the keyword as them having added it correctly. ;)
[18:54] <infinity> bdmurray: While I'm bugging you, I'm going to need your superpower to edit meta-release today.
[18:55] <bdmurray> infinity: okay, what SRU did you want looked at?
[18:56] <infinity> bdmurray: nginx/raring
[18:59] <hallyn_> stgraber: any discussion a tthe sprint about default cgroup config for users at login (i.e. for memory controls)?
[19:00] <stgraber> hallyn_: nope. We briefly discussed potential use of the freezer cgroup for apps but that's about it
[19:00] <hallyn_> ok, thanks
[19:39] <cjohnston> bdmurray: you are a track lead now
[19:43] <bdmurray> cjohnston: thanks
[21:10] <plars> thomi: ping
[21:10] <thomi> plars: hey
[21:10] <plars> 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] <thomi> plars: for raring?
[21:12] <plars> thomi: yes
[21:15] <thomi> 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] <thomi> plars: so, give it 10 minutes maybe
[21:15] <plars> thomi: ah, ok. That's where I was trying to pull from but it wasn't finding it
[21:15] <plars> thomi: thanks, will check back in a bit
[21:15] <thomi> plars: yeah, we switched the PPA, but since we haven't merged anything into trunk autolanding never triggered
[21:15] <plars> understande
[21:40] <zequence> 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] <stgraber> 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] <zequence> 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] <vertab7> good evening all from the UK
[21:47] <zequence> Just got the script make_report.py, and realized there may be LP API that can be used
[21:54] <stgraber> zequence: yeah, you can easily query through the API but there's no e-mail subscription for that part
[21:55] <stgraber> 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] <zequence> stgraber: Ah, thanks. I'll have a look :)
[22:11] <doko> directhex, ping
[22:25] <slangasek> cyphermox: hi, did you happen to see my follow-up on bug #1004775?
[22:26] <cyphermox> slangasek: argh, I hadn't seen it
[22:26] <cyphermox> you're obviously right, I forgot to re-apply this change
[22:31] <doko> barry, online?
[22:31] <barry> doko: yep