[00:00] <cjwatson> Pre-publishing now so it can mirror overnight
[00:14] <bdmurray> cjwatson: has anybody looked at bug 1240683?
[00:14] <ubot2> Launchpad bug 1240683 in ubiquity (Ubuntu) "Ubuntu one login during install hangs" [Undecided,Confirmed] https://launchpad.net/bugs/1240683
[05:22] <stgraber> I'm heading to bed now, just finished testing all of Edubuntu and all the Core images that I could (leaving arm64 to infinity)
[05:22] <stgraber> bug wise, the only new thing that got reported is bug 1240794
[05:22] <ubot2> Launchpad bug 1240794 in ubiquity (Ubuntu) "In partioner 'select something else' deleteing and adding a partition causes crash" [Undecided,New] https://launchpad.net/bugs/1240794
[05:22] <stgraber> I tried reproducing it quickly here but I don't have a VM that lets me do resize at the moment and any attempt to reproduce by directly using the manual partitioner failed (as in, it worked as expected)
[05:23] <stgraber> so maybe that's somehow related to resize or that's not a very reproducable issue, either way, doesn't seem world ending
[07:55]  * apw manages to trigger something which looks like bug #1240794
[07:55] <ubot2> Launchpad bug 1240794 in ubiquity (Ubuntu) "In partioner 'select something else' deleteing and adding a partition causes crash" [Undecided,New] https://launchpad.net/bugs/1240794
[08:58] <xnox> maybe let that into the archive ^ ? =)
[08:58] <smartboyhw> Question: I presume https://wiki.ubuntu.com/SaucySalamander/Beta2/UbuntuStudio should be changed to https://wiki.ubuntu.com/SaucySalamander/UbuntuStudio for the final release? (A template for all flavours)
[09:06] <cjwatson> apw: cf. bug 1060484
[09:06] <ubot2> Launchpad bug 1060484 in parted (Ubuntu) "When using gparted com.canonical.Unity.Devices blacklist is set back to Default of []" [Undecided,Fix released] https://launchpad.net/bugs/1060484
[09:10] <infinity> smartboyhw: Or SaucySalamander/ReleaseNotes/UbuntuStudio, or whatever.  There doesn't seem to be much agreement here about where to find them.  I'm having a hard time finding everyone's. :P
[09:10] <smartboyhw> infinity, OK, I will just do /ReleaseNotes/UbuntuStudio
[09:11] <infinity> Thankfully, it's a wiki, so people can add links to their notes in the primary notes after release if we can't find them all...
[09:15] <smartboyhw> infinity, how about the "Common infrastructure" thing again?
[09:21] <infinity> smartboyhw: No point in the CI thing.  Reproducing everything in 7 different-but-similar release notes is silly.
[09:22] <smartboyhw> infinity, so, what am I supposed to do?
[09:25] <smartboyhw> Riddell, ^ mark upgrades ready too probably?
[09:25] <infinity> smartboyhw: Honestly, I wouldn't worry about having that section at all.  You could have a "for more information about this Ubuntu release in general, see the Ubuntu release notes at: $link".
[09:26] <smartboyhw> infinity, -.- OK
[09:27] <Riddell> smartboyhw: waiting on valorie for that
[09:27] <infinity> Riddell: Can you link the Kubuntu release notes in the Kubuntu section in the primary notes?
[09:27] <smartboyhw> Riddell, OK, I thought the testcases all passed
[09:28] <smartboyhw> infinity, to notify you, Studio's release notes is at https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes/UbuntuStudio
[09:29] <infinity> smartboyhw: Great, thanks.
[09:30] <Riddell> infinity: can do, copying those over to the website now
[09:30] <smartboyhw> Not sure about release announcements though, I need to clarify something with zequence
[09:30] <infinity> Riddell: Or give me a link, whichever.
[09:30] <Riddell> infinity: http://www.kubuntu.org/news/kubuntu-13.10
[09:48] <infinity> Riddell: Is that the announce or the notes?  (or do you not have notes?)
[09:48] <Riddell> infinity: right, same thing for us
[09:48] <xnox> cjwatson: http://www.ubuntu.com/content/what%E2%80%99s-new-ubuntu-server-1204-lts
[09:48] <cjwatson> ta
[10:08] <ogra_> stgraber, already around ? i was wondering how our release process works for touch i assume you will make saucy a standlone dir and re-link devel to T ?
[10:32]  * utlemming marked cloud images as ready
[10:55] <xnox> cjwatson: apw: http://www.ubuntu.com/getubuntu/releasenotes
[11:00] <cjwatson> looks like most of the flavour release notes links in https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes need to be updated?
[11:01] <smartboyhw> I told infinity Studio's
[11:01]  * ogra_ waits for apw to stop sitting in the lock 
[11:02] <ogra_> s/in/on/
[11:04] <JackYu> I will update soon.
[11:06]  * ogra_ twiddles thumbs 
[11:06] <ogra_> apw, are you writing a novel ?
[11:09] <xnox> OGRA!
[11:09] <ogra_> yes, thats me !
[11:09] <apw> ogra_, i am ... and did you write over it any how?
[11:10] <ogra_> apw, nope
[11:10] <xnox> ogra_: yes, he is writing a novel fixing all the urls that point to beta-1 & 2 instead of final.
[11:10] <ogra_> i'm canceling all the time here
[11:10] <ogra_> ah, lovely
[11:11] <apw> ogra_, ok ... have a go now, and let me know when you are done so i can have another bash
[11:18] <ogra_> apw, heh, now didrocks stole the lock
[11:18]  * ogra_ knew that going to the restroom wasnt a good idea
[11:19] <didrocks> \o/
[11:19] <didrocks> finishing up copying the known issues
[11:19] <didrocks> but the wiki hanged…
[11:19] <ogra_> well i guess i'll better check then that you dont have my issues on it already
[11:21] <didrocks> lock released
[11:21] <didrocks> ogra_: apw: ^
[11:22] <ogra_> grabbed
[11:23] <smartboyhw> infinity, http://ubuntustudio.org/2013/10/ubuntu-studio-13-10-released/ (the release announcement)
[11:25] <cjwatson> Riddell: Could I move https://wiki.ubuntu.com/SaucySalamander/Final1/Kubuntu to https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes/Kubuntu to line it up with the other flavours?
[11:27] <cjwatson> highvoltage: Should we have a separate release notes page for Edubuntu, or do you just want to link to the master one in the installer?
[11:27] <Riddell> cjwatson: that page can be deleted, it's at kubuntu.org/news/kubuntu-13.10
[11:28] <cjwatson> Riddell: OK, so that's more like an announcement than release notes?  Where should the release notes link in the installer go though?
[11:28] <cjwatson> Riddell: Just the master release notes page?
[11:28] <Riddell> cjwatson: yeah
[11:28] <ogra_> saved feel free to take over
[11:29] <ogra_> didrocks, i added a "platform" section for us
[11:29] <ogra_> (added the upstart memleak and uevent spam bugs)
[11:29] <cjwatson> knome: Is https://wiki.ubuntu.com/SaucySalamander/Final/Xubuntu intended as release notes or as a staged announcement?
[11:29] <didrocks> ogra_: yeah, sounds good :)
[11:30] <knome> cjwatson, that would be the notes, but it is not final-final yet.
[11:30] <cjwatson> knome: If the former, can we move it to https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes/Xubuntu for uniformity with other flavours?
[11:30] <knome> cjwatson, that's fine :)
[11:30] <cjwatson> knome: That's fine, just trying to get the structure right so that the web team can do links
[11:30] <cjwatson> OK, great, will do
[11:30] <knome> cheers
[11:44] <pietro98-albini> Hello everybody
[11:44] <pietro98-albini> I'm pietro from the italian loco
[11:44] <pietro98-albini> In our site we have a box with the md5 of downloaded iso
[11:45] <pietro98-albini> Can someone give me saucy md5's asap?
[11:45] <cjwatson> Er, it's terrible to have md5s copied around lots of sites
[11:46] <cjwatson> Can't you just link to https://help.ubuntu.com/community/UbuntuHashes (which is still terrible, but at least centralises the terribleness)?
[11:46] <cjwatson> I'll update that shortly
[11:48] <pietro98-albini> cjwatson, ok
[11:51] <cjwatson> right, UbuntuHashes done, need a shower now :P
[11:52] <ogra_> heh
[12:58] <infinity> Does anyone have link to release announcements for Xubuntu, Edubuntu, Lubuntu, GNOME, and Kylin?
[13:05] <knome> infinity, xubuntu will be at http://xubuntu.org/news/saucy-salamander-final/
[13:09] <infinity> knome: Thanks.
[13:17] <smartboyhw> Released!
[13:18] <rtg> infinity, I thought tantric was nixed ?
[13:18] <infinity> rtg: This is me not knowing the real name yet. :P
[13:18] <wgrant> Awww
[13:18] <rtg> bummer
[13:18] <apw> who'd need a name, to like open the release
[13:19] <smartboyhw> infinity, please confirm it is released
[13:19] <apw> there will be an announcement, when it is
[13:19] <wgrant> Could just convince Mark to use t-series as the adjective, to make things easy now.
[13:19] <cjwatson> smartboyhw: it is
[13:19] <smartboyhw> cjwatson, ACK:)
[13:19] <cjwatson> the topic change is confirmation :P
[13:20] <smartboyhw> :P
[13:20] <cjwatson> (announcement is in the mod queue, James is getting the website sorted first)
[13:20] <smartboyhw> I got afraid of the "not not" stuff in #u-r-p
[13:20] <cjwatson> this channel is more authoritative than #u-r-p
[13:23] <stgraber> ogra_: there's no actual release actions for touch, everything stays as it's until we get the first T images. Once we do, I'll setup the channels for T and change the devel aliases to point to it
[13:24] <ogra_> and saucy points to anything ?
[13:24] <ogra_> or do we just leave it as saucy
[13:24] <ogra_> (i.e. will you introduce "stable" alongside devel)
[13:24] <stgraber> saucy-proposed will be updated whenever a new saucy image is published to cdimage, that's how we do post-release updates
[13:24] <stgraber> ogra_: we already have stable
[13:24] <knome> there is no CommonInfrastructure page for final?
[13:25] <stgraber> ogra_: and it's already pointing to saucy
[13:25] <ogra_> stgraber, we wont do any saucy images after release
[13:25] <cjwatson> https://lists.ubuntu.com/archives/ubuntu-announce/2013-October/000177.html
[13:25] <ogra_> the plan is to roll on top of distro
[13:25] <ogra_> WHEE !
[13:25] <stgraber> ogra_: phablet-flash actually defaults to stable I believe
[13:26] <stgraber> ogra_: hmm, not what we discussed last vUDS, we said we'd do a few saucy updates post release but not support for the whole 9 months
[13:26] <stgraber> ogra_: (so we can at least test the process for 14.04)
[13:27] <ogra_> stgraber, i think what we agreed on in recent landing team meetings is that we stay without image for a few days until we can spin the first T one
[13:27] <ogra_> and then move on in T
[13:27] <mdeslaur> congrats!
[13:27] <didrocks> congrats guys \o/
[13:27] <ogra_> mdeslaur, to you too !
[13:28] <didrocks> stgraber: ogra_: phablet-flash defaults to stable indeed
[13:28] <didrocks> stgraber: the planned changed
[13:28] <stgraber> ogra_: I think we really should be publishing a couple of updated saucy ones (even if we do so after the switch to T) so we can make sure this process works
[13:28] <rickspencer3> nice job  with the release apw, cjwatson, infinity, xnox and anyone else who was in the office :)
[13:29] <infinity> rickspencer3: Be sure to visit the website 5000 times, so I win the betting pool.
[13:29] <rickspencer3> didrocks, stgraber my understanding was that we would release some update for any SRUs that happened to impact the phone or tablet images
[13:29] <rickspencer3> for about a month
[13:29] <rickspencer3> but we wouldn't necessarily make special updates
[13:30] <ogra_> hmpf
[13:30] <rickspencer3> infinity, ok, I'm working on my script now
[13:30]  * ogra_ would prefer we just move forward
[13:31] <popey> rickspencer3: can we get a public announce about that. it's still very vague
[13:31]  * ScottK isn't aware of any discussions with the SRU team about special SRU rules for phone.
[13:31] <ogra_> ... and concentrate on T instead of wasting resources on saucy ...
[13:32] <ogra_> that will make the first T image appear faster
[13:32] <rickspencer3> popey, so far as I know, nothing changed from vUDS
[13:32] <popey> rickspencer3: for those who weren't "at" vUDS
[13:32] <stgraber> ogra_: we're just talking about running the cdimage script a couple of times with -updates enabled to make sure the result is usable and that the system-image script import those fine
[13:32] <stgraber> ogra_: that can be done after devel is switched to T so I really don't see the harm
[13:33] <rickspencer3> popey, sure, let me synch with asac, et al
[13:33] <stgraber> ogra_: and I'd really rather we find any problem with saucy than with T
[13:33] <popey> cool
[13:33] <ogra_> stgraber, that still means the people will fiddle with SRUing stuff instead of working on T
[13:33] <ScottK> The SRU rules from the TB, not a UDS session.
[13:33] <stgraber> ogra_: nope
[13:33] <ScottK> ... rules are from ...
[13:33] <stgraber> ogra_: for all I care the only delta could be from standard distro (non-touch) SRUs
[13:33] <ScottK> Of course if we had a tech board, it would be nice.
[13:34] <infinity> stgraber: The plan was exactly that, to just take the distro SRUs as they come to test the system image machinery.
[13:34] <stgraber> right
[13:35] <ogra_> by SRU rules the uploads have to ripen for 2 weeks anyway before they can go to updates (or did that change)
[13:35] <ogra_> so what does an image buy us
[13:35] <stgraber> ogra_: 7 days, less if a SRU team member feels it's been sufficiently tested
[13:35] <ogra_> in 2 weeks we should also have our first T image
[13:35] <ogra_> which makes putting time into S a waste imho
[13:36] <stgraber> ogra_: do you even read what I'm writing? :) the whole point is to test post-release system-images, I also said I'm fine doing those after we switch people to T. The only time we're talking here is running a cdimage script to spin a new image, I really don't see the problem.
[13:36] <rickspencer3> ogra_, I thought the "not wasted" part was to test the update and upgrade logic
[13:36] <stgraber> (vs the time to fix T post-release because we didn't notice something was badly broken in saucy)
[13:36] <rickspencer3> sorry, I'm repeating stgraber
[13:36] <rickspencer3> how about this ...
[13:37] <rickspencer3> ew all chill out and enjoy Saucy today
[13:37] <ogra_> rickspencer3, why would updates from a stable channel be different than the ones in devel ?
[13:37] <rickspencer3> and figure it out tomorrow
[13:37] <ogra_> its just another name
[13:37] <ogra_> and we test devel every day
[13:37] <rickspencer3> ogra_, I'm just tellign you what was th decision as I understood it
[13:37] <rickspencer3> and was discussed in the session on this at UDS
[13:37] <rickspencer3> I don't think I want to argue about it now
[13:38] <rickspencer3> and if stgraber thinks something is a good idea, I usually trust that it is a good idea ;_)
[13:38] <ogra_> stgraber, the problem is that devs will focus on fixing S if that option is there
[13:38] <ogra_> instead of focusing fully on T
[13:39] <ogra_> which makes us waste precious resources
[13:39] <rickspencer3> ogra_, devs shoudl focus on fixing S if they are working on the desktop or server
[13:39] <ogra_> anyway, if this is set in stone it is set in stone and i wont bother further
[13:40] <rickspencer3> in the meantime ... WE ACTUALLY SHIPPING UBUNTU FOR PHONE
[13:40] <rickspencer3> :)
[13:40] <rickspencer3> and it's good
[13:40] <ogra_> :D
[13:40] <rickspencer3> and we brought forth image based updates
[13:40] <rickspencer3> and application isolation
[13:40] <rickspencer3> and Mir with Unity 8
[13:41] <rickspencer3> etc... :)
[13:42] <ogra_> yeah, it is pretty awesome what we can manage in 6 months
[13:44] <didrocks> ogra_: +1, it's insane to see the amount of changes that happened and how the result is :)
[13:45] <ogra_> yeah
[13:50] <med_> looks like openstack is stuck at RC for a bit.
[13:55] <jamespage> med_, fortunately all of the RC's landed in saucy before 13.10 released; so the updates are version number only
[14:11] <stgraber> infinity: I assume it's a bit late now, but http://www.edubuntu.org/news/13.10-release is the URL for Edubuntu
[14:24] <med_> jamespage, cool
[14:39] <infinity> stgraber: I'll be sure to go back in time and edit my email.
[14:39] <xnox> Tasty Takin
[14:46] <stgraber> FYI I'm planning on accepting the procps SRU to all releases and after testing it myself to release it directly to -updates
[14:46] <ogra_> Twiddly Thumbs
[14:46] <stgraber> as anyone using containers currently has a broken apt
[14:49] <jamespage> stgraber, thankyou - I have alot of those :-)
[14:49] <stgraber> yeah, got 150 containers just by myself plus a dozen angry people who sent me e-mails
[14:49] <stgraber> so I want that resolved SAAP
[14:49] <stgraber> *ASAP
[14:50] <mdeslaur> stgraber: what? I thought only the security team got the death threats? :)
[14:51] <stgraber> jamespage: feel free to help with validation (bug 1157643)
[14:51] <ubot2> Launchpad bug 1157643 in procps (Ubuntu T-series) "procps fail to start" [Undecided,Confirmed] https://launchpad.net/bugs/1157643
[14:51] <stgraber> mdeslaur: well, it turns out that people running thousands of containers using unattended-upgrade don't like you when all of a sudden they're all broken and require manual changes ;)
[14:51] <jamespage> stgraber, ack - I have at load of containers winging in our openstack test environment which is all 12.04
[14:52] <mdeslaur> stgraber: hehe :P
[14:52] <stgraber> jamespage: yeah, 12.04 is definitely the most urgent, most people using LXC tend to stick to LTS, the rest is still impotrant but slightly less urgent
[14:52] <jamespage> stgraber, great - as soon as it lands I'll give it a run
[15:08] <phillw> please note that both the upgrade lubuntu's are also good for release. the arm-ac100 has not been tested and therefore not being released.
[15:08] <ogra_> infinity, do we know what we pull from for T (unstable/testing) ?
[15:08] <ogra_> cjwatson, ^^^
[15:11] <cjwatson> ogra_: unstable
[15:11] <ogra_> thx !
[15:12] <cjwatson> we're doing our own testing effectively, so most of what we get from testing would be being slowed down
[15:12] <ogra_> yeah, i agree
[15:43] <Daviey> The SRU's for openstack final are merely rc3 to final version bump, ie re-tagged.  I'm not sure on the worth of it personally, but I can recognise that there is interest in being seen to hav the /final/ version.
[15:43] <Daviey> Does anyone in ~ubuntu-sru have views on this?
[15:48] <slangasek> stgraber: so the recent comments on bug #1157643 show an interesting regression potential I hadn't considered; I've added it to the bug description.  Since you accepted the package, I wonder if you have any thoughts on this.
[15:48] <ubot2> Launchpad bug 1157643 in procps (Ubuntu T-series) "procps fail to start" [Undecided,Fix committed] https://launchpad.net/bugs/1157643
[15:49] <stgraber> slangasek: looking
[15:49] <slangasek> Daviey: well, there's a provisional MRE for OpenStack; and you can't get more micro than a plain version bump.  I'm not thrilled about a rebuild that just changes the version number, but there is value in getting rid of the ~rc3 in the version string
[15:50] <stgraber> slangasek: good points. I don't think I'd be opposed to having sysctl failing when run as non-root, however this would just be a temporary hack since soon enough we may want it to work as non-root (user namespaces)
[15:50] <slangasek> (I would draw a distinction between "getting rid of the pre-release version number", which is something we've done for packages post-freeze from time to time, and "take an upload with new upstream version numbers so that the version numbers are in sync", which happened earlier with ubuntuone)
[15:51] <slangasek> stgraber: well, the /new/ regression potential is "sysctls now get applied that weren't applied previously, due to skipped errors"
[15:51] <Daviey> slangasek: Yeah, rbasak made a good point.. we've previously had users complaining they want the latest version number.. when it's of no consequence to the user
[15:51] <stgraber> slangasek: for the second case, it's right that this may cause a change in behaviour on some systems, though I think this should be considered as a bugfix more than anything else (any container user running a full distro with sysctl probably expected sysctl to work)
[15:52] <stgraber> slangasek: note that sysctl at least partly worked in containers before since things like the IPv6 privacy options were applied fine for me
[15:52] <slangasek> stgraber: examples given in the comments include "My networking is no longer working the way it was before"
[15:52] <slangasek> (comment #38 - he attributes it to iptables, though it probably has to do with route forwarding or something)
[15:53] <stgraber> that's odd since /proc/sys/net is namespace aware and writable in containers
[15:54] <stgraber> slangasek: also note that this is on OpenVZ so on a non-standard kernel
[15:54] <stgraber> using a unofficial openvz template which does extra changes to a bunch of system files
[15:55] <slangasek> stgraber: so I was thinking that this was because sysctl was exiting with an immediate failure before fully processing all of the entries; but I've read the code now and see that this is not what's done, sysctl attempts to apply all the settings and or's their return values
[15:56] <slangasek> in which case there doesn't seem to actually be a risk
[15:56] <stgraber> slangasek: yeah, just went and re-read the code too, so it's not causing an actual behaviour change, the only difference is the return code
[15:56] <slangasek> yep
[15:58] <stgraber> oh, that's annoying... I assumed I could just update a broken container to the new procps and all would be fine, but it's not
[15:58] <stgraber> apt still insists on running the old postinst fist...
[15:58] <stgraber> *first
[15:58] <slangasek> uhm?
[15:59] <slangasek> when running what command?
[15:59] <stgraber> slangasek: http://paste.ubuntu.com/6251720/
[16:00] <slangasek> Daviey: I hope you're going through and checking that each of these packages is indeed covered by the MRE, there have been gaps before
[16:00] <Daviey> slangasek: There are two which were not.. celiometer and heat.
[16:01] <slangasek> stgraber: that's just weird
[16:01] <slangasek> Daviey: ok, and those are https://lists.ubuntu.com/archives/technical-board/2013-October/001732.html
[16:01] <Daviey> slangasek: Would you consider this to need an MRE, http://launchpadlibrarian.net/153986728/ceilometer_2013.2~rc2-0ubuntu1_2013.2-0ubuntu1.diff.gz ?
[16:02] <slangasek> Daviey: any SRU needs either an MRE or a fine-toothed comb; since ceilometer and heat are now included in the provisional MRE, I'm not getting out my comb ;)
[16:02] <Daviey> Oh yes, i forgot sabdfl +1'd it.
[16:03] <stgraber> slangasek: yeah, I certainly wasn't expecting that behavior....
[16:04] <slangasek> stgraber: it's probably affected by apt's "immediate configuration" option
[16:04] <stgraber> (FWIW, same thing on dist-upgrade, I was expecting that but wanted to make sure)
[16:04] <slangasek> because this package is so low in the stack, apt wants it to be in working order before it goes on
[16:05] <slangasek> stgraber: so see if -oAPT::Immediate-Configure=no helps
[16:08] <stgraber> slangasek: no difference
[16:08] <stokachu> is tantric tarantula official or is that a joke
[16:09] <stokachu> infinity: is this your doing? :)
[16:10] <rtg> stokachu, its a joke
[16:10] <stokachu> haha
[16:10] <doko> xnox, might be worth to prepare the boost1.54 split for the t-series, if we want to open with it
[16:10] <rtg> unless it sticks
[16:10] <Laney> I still want turgid
[16:11] <Laney> that's the kind of message we want to convey for an LTS
[16:11] <stokachu> or tony's tiger
[16:11] <stokachu> haha
[16:11] <stokachu> 14.04: Thunder Tiger
[16:11] <stokachu> sounds badass
[16:13] <stgraber> slangasek: I'm going to quickly check that it works when applied manually to all supported releases, then sru-release it so anyone who didn't update will go straight to .2 and not get the issue
[16:18] <stgraber> slangasek: hmm, so I just did the same test in a clean container and it just worked, so maybe it's some weird config I've got or something caused by packages I have installed...
[16:19] <stgraber> anyway a clean precise container => update to .1 =. update to .2 works fine
[16:19] <stgraber> that or my laptop is buggy, re-testing and looking very carefully
[16:21] <bkerensa> why does http://cdimage.ubuntu.com/releases/13.10/release/ only have server?
[16:21] <stgraber> bkerensa: because cdimage is only for things that aren't on releases.u.c
[16:22] <bkerensa> :s
[16:22] <bkerensa> ok
[16:22] <stgraber> slangasek: hmm, .1 worked fine here so it's some local weirdness, I need to first get .1 to fail, then I can properly test the SRU on my machine
[16:22] <stgraber> I suspect I need a sysctl entry to actually differ for sysctl to try to do something
[16:26] <stgraber> ok, ignore me for now, looks like apparmor isn't working with my LXC locally (limited to the daily builds so not something to worry about for Ubuntu)
[18:17] <bkerensa> noticed that https://wiki.ubuntu.com/SaucySalamandar/ReleaseNotes/Credits/ is missing
[18:18] <bkerensa> should we still add in credits for this release?
[19:45] <slangasek> bkerensa: I didn't understand why we were trying to do that in the first place; trying to exhaustively list all the people involved in the release seems like busy work to me, and missing people out by accident is worse than not doing it at all
[19:47] <xnox> doko: i have it, and I would have uploaded it to https://launchpad.net/~ubuntu-toolchain-r/+members Can you please approve me?
[19:47] <xnox> doko: i'm using "devel" nickname so it works for uploading both now and in the future to saucy/t-series (as of when it opens)
[19:47] <bkerensa> slangasek: You raise very good points I guess for the most part it served only as a form of credit for contributors since it is unlikely users would look elsewhere like changelogs :)
[19:56] <ScottK> slangasek: +1
[19:57] <xnox> ... if only we had any Technical Board members to actually open the new series, even if deciding to override the name....
[20:00] <ScottK> The TB does have one member.  Someone could ask him to override the name thing.
[20:01] <xnox> ScottK: Error: StackOverflow recursion detected.
[20:02] <slangasek> snerk
[20:04]  * xnox reads dictionary "Verb or Noun: Small sound that is emitted through the nose and mouth, usually a compressed laugh or snort. Often accompanied with a small grin, smirk, or sneer. Usually a tone of either derision, (as when someone says something you find stupid) or innocent humor. (When someone tells you a funny joke and you are busy doing something else, so a full-fledged laugh is difficult.)Nice to use behind other's backs, as when they do 
[20:42] <roaksoax> Hi all! So /win 3
[21:00] <stgraber> cjwatson: when you have a minute, can you add the usual SRU bits to bug 1197766?
[21:00] <ubot2> Launchpad bug 1197766 in partman-auto (Ubuntu Precise) "Different partition layout after recovery with keep home partition" [High,In progress] https://launchpad.net/bugs/1197766
[21:01] <sil2100> Hi everyone! Can anyone from the SRU team take a look at https://bugs.launchpad.net/unity/+bug/1043627 and assess if we can release it as an SRU?
[21:01] <ubot2> Launchpad bug 1043627 in nux (Ubuntu Raring) "[SRU] Add XIM Support to Nux" [Undecided,Confirmed]
[21:01] <sil2100> (for precise)
[22:16] <med_> Timid Titmouse.
[22:17] <med_> ah Tenacious Tribbles
[22:22] <ScottK> Tardy Tiger
[23:33] <TheLordOfTime> Wubi wasn't readded for 13.10 was it?  I remember a discussion around the mailing lists around 13.04 where Wubi was dropped...
[23:48] <slangasek> TheLordOfTime: in the end, wubi did release with 13.04 after the community stepped up to maintain it, but it has been de-emphasized on the download pages
[23:50] <TheLordOfTime> slangasek, "after the community stepped up to maintain it"... does that mean it's still technically "unsupported" except by the community?  The main question about this is whether in #ubuntu and other locations it's considered "supported" or not
[23:50] <TheLordOfTime> slangasek, the wubi.exe isn't included on the ISOs, though, is it?
[23:50] <TheLordOfTime> (and it still suffers from the UEFI and Win8 incompatibilities, right?)
[23:51] <slangasek> yes, it still has incompatibilities with newer versions of Windows, which is why it's de-emphasized on the download pages
[23:51] <slangasek> it is present on the images
[23:51] <slangasek> and what does "supported" mean
[23:52] <TheLordOfTime> (exactly the issue)
[23:52] <TheLordOfTime> meh, the general question is answered, now, i might poke the relevant governance teams on whether or not a given support method covers Wubi in post-13.04
[23:55] <sarnold> cjwatson,slangasek,stgraber, is this expected? https://bugs.launchpad.net/ubuntu/+bug/1241251
[23:55] <ubot2> Launchpad bug 1241251 in Ubuntu "Some kernel modules are failing digital signature checks during boot - kernel is tainted." [Undecided,New]