[05:41] infinity: hey, do you have any idea when the SRU will be review for the unity stack in raring? [05:41] infinity: I hope we can finally get those netbook for who unity is not working fixed, as the fix was ready for a month and half === mmrazik is now known as mmrazik|afk === mmrazik|afk is now known as mmrazik === mmrazik is now known as mmrazik|afk === doko_ is now known as doko [09:31] I thought we had a chat about DIF at the vUDS session [09:32] Guess I could go and review the video [09:32] already loading it up [09:32] Be my guest :) [09:33] if I can bear to see myself on video, that is [09:34] oh no, that's the one I missed :-) [09:39] cjwatson: https://www.youtube.com/watch?v=Re9HfnTifaY&feature=player_embedded - the two of you discussing decided-ish on week 12 but pending an ubuntu-release discussion [09:39] guess that is this [09:39] Laney: can you give that link with minute/second offset ? [09:39] 10:30 [09:40] k, I shall refrain from enduring listening to myself since you have kindly summarised [09:40] the discussion starts at 06:30 [09:40] xnox: I don't know how [09:40] Laney: click share tab, tick start at: http://youtu.be/Re9HfnTifaY?t=6m30s [09:40] (mental self-image of voice does not have the same accent or pitch as actual voice) [09:40] there you go, even using youtu.be short url. [09:40] my hero [09:41] cjwatson: the actual voice sounds better than mental self-image of voice?! right?! [09:42] god no [09:42] never does [09:43] * Laney has a sexy radio 4 continuity announcer style voice [09:43] right guys? [09:43] * xnox must sound hideous then, since i don't like the mental projection of mine much..... [09:44] Laney: you don't speak much anyways =)))))) [09:44] righto :P [09:45] * xnox wants the voice of danny o'donoghue [09:46] anyway [09:46] 12 or 13 would be fine by me [10:23] Hi! [10:23] Is there anyone from the SRU team around? [10:23] sil2100, you better state your question than wait for an answer to that ;-) [10:25] So, Brandon prepared some unity+nux fixes for those bugs for raring: LP: #983254, LP: #1043627, LP: #1112044 [10:25] Launchpad bug 983254 in Unity 5.0 "Support input methods beside ibus" [High,In progress] https://launchpad.net/bugs/983254 [10:25] Launchpad bug 1043627 in Nux 2.0 "Add XIM Support to Nux" [High,In progress] https://launchpad.net/bugs/1043627 [10:25] Launchpad bug 1112044 in Nux 2.0 "Fcitx can't input word group more than 6 Chinese characters in Dash. Causes a crash if entering to many characters." [High,In progress] https://launchpad.net/bugs/1112044 [10:26] It's hard to say if those are bugs or features, so I wanted to get a confirmation if those are SRUable - the priority for those is rather high, as it affects many asian-language countries [10:26] The fixes are ready, reviewed and waiting to get merged === mmrazik|afk is now known as mmrazik [11:57] cjwatson: hi! Maybe you would have a moment to give a quick look and comment? ;) ^ [12:04] I think it'd be better to be somebody with more desktop clue than I do [12:59] cjwatson: [cjwatson] suggest moving DIF to week 12 (18 July) on -release [13:01] Either week 12 or 13 is fine by me, don't feel strongly [13:02] But thanks for the reminder :) [13:04] cjwatson: week 13 sounds better, as it will be Alpha2 again, just like in raring. That's like two releases in a row ;-) [13:05] (as if that's any kind of an argument for week 13 vs week 12) === mmrazik is now known as mmrazik|afk [20:59] https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule has a header of "Do not edit", but it seems you've moved DIF, mind updating there or if I do? [21:05] TheDrums: I was assuming cjwatson would do it once his "complain now or I'll move it" deadline is passed (Tuesday IIRC) [21:05] Cool, I'll shutup. :) [21:30] TheDrums: That's sort if why it has the "do not edit" header, so people don't randomly change things without concensus, or mistake a discussion for a decision. :) [21:30] (I wouldn't have edited it anyway, just an excuse to ask about it in here.) [21:32] Laney: still here? [22:27] autopkgtest for eglibc 2.17-0ubuntu5: RUNNING [22:27] autopkgtest for linux 3.9.0.7.8: RUNNING [22:27] ^-- Why do I have a feeling that's going to take a Very Long Time? [22:34] Spare a thought for glib2.0 [22:34] autopkgtest for firefox 22.0~b6+build1-0ubuntu1: RUNNING [22:34] autopkgtest for libreoffice 1:4.0.2-0ubuntu5: RUNNING [22:34] autopkgtest for pango1.0 1.32.5-5ubuntu1: RUNNING [22:34] autopkgtest for ubiquity 2.15.7: RUNNING [22:42] cjwatson: So, out of curiosity, do we even have remotely enough resources to run all these tests before tomorrow? :) [22:43] * infinity wonders how beefy jibel's infrastructure is. [22:47] Sounds like rather a personal question. [22:47] ScottK: There's a reason I avoided the word "equipment". [22:48] I guess we'll find out [22:48] Given how many times management has asked me about this work I expect I might have some leverage if it turns out to be prohibitively expensive [22:50] cjwatson: Yeah. It just stands to reason that, as test coverage increases (or for awful rdep cases like glibc and glib), the autopkgtest QA will take orders of magnitude longer than the actual builds do. [22:50] cjwatson: So, if that can be parallelised out very, very well, yay, but it could take a whole lot of machines. [22:50] (Or, we have to pare down some of the scarier rdep trees) [22:51] Well, as I've said, there are always force-autopkgtest hints in special cases if need be. [22:51] But, yes, I expect the rdep analysis may need to get a bit subtler. [22:51] Yeah, but I want to avoid using those as a general rule. [22:51] I had the impression there were quite a few Jenkins slaves, but I don't know the details. [22:52] Well, hopefully we're keeping some stats (or just a decent request/response logfile) so we can do some analysis later. [22:53] Not in a very pleasant form, but it's mostly logged. I was going to clean that up a bit soon. [22:53] * infinity wonders if he should brave the outside world for food, or if it's better to avoid being dragged away in a flood, and just find something in his house. [22:53] Right now I'm in one-more-upload-then-bed mode though ... [22:53] cjwatson: Pleasntness is less important than in/out timestamps. :) [22:53] cjwatson: Computers are awfully good at reading files I can't make sense of. [22:54] I'm not totally sure the results are properly logged other than in excuses. I'll check next time I'm in there. [22:54] With the exception of the Canterbury Tales. [22:54] Did I ever tell you about my stepson's experience with the Canterbury Tales when he was little? [22:55] He had recently learned how to read and was doing fairly well [22:56] Then he came in one evening holding a book, quite upset, saying "mummy, I've forgotten how to read" [22:56] ... it was Chaucer [22:56] Hah. [22:56] Well, time to teach him some Middle English. [22:56] Mine is pretty piss-poor these days. [22:56] I used to be passably alright. [22:57] Given some of the Tales it's probably best for them to be encoded in a child-safe form. :-) [22:57] Meh, they're not THAT raunchy, really. [22:57] And at least they're well-written. [22:57] * cjwatson reads about the floods. Yikes. Bring stilts? [22:57] God forbid children stumble on literary abortions like 50 Shades. [22:58] Not because of the content, but because it would teach them some terrible style and grammar. [22:59] I highly recommend "Mark Reads 50 Shades" (youtube search it, I'm not going to link it), for work background noise. [22:59] I've so far avoided the source material. [23:00] Well done. But Mark Reads is a whole different story. [23:00] In fact, nearly any of his segments are good, but the 50 Shades one is great just to get a feel for how awful the source material really is. [23:01] Like, the author ending narrative sentences in ", or something." [23:02] I've read a few fairly blistering written criticisms/satires of it. [23:02] But, yeah, fanfic goes straight to publication without the benefit of a whole lot of editing in between, I gather [23:03] My ex made the mistake of reading it and spent several DAYS complaining to me about how awful it was. [23:56] Does proposed-migration/autopkgtest require the test to succeed or to not go from successful→failure? [23:56] * Laney is concerned about the LO autopkgtest ...