[05:18] <ianorlin> hmm are debian installer images at the first bootslpash supposed to revert to normal mode if you change the mode and then move on to the menu and select check disk for defects then go back over to install on server or alternate installers?
[09:48] <rhuddie> fgimenez, hello, good morning.
[09:48] <fgimenez> hi rhuddie good morning
[09:49] <rhuddie> fgimenez, I noticed that you have removed the MultipleSignalReactor from your branch
[09:50] <fgimenez> rhuddie, yes, sorry are you using it? i can put it back
[09:50] <rhuddie> rhuddie, I used that in my wait-for-download branch, so wondered if I should just move it onto that branch?
[09:50] <rhuddie> either way is fine.
[09:51] <rhuddie> If you weren't using it on your branch, maybe it makes more sense to include it on my one?
[09:51] <fgimenez> rhuddie, in the apply update branch it doesn't make much sense, there's only one signal expected
[09:51] <rhuddie> fgimenez, ok. I'll add it to mine, using the base class that you have defined.
[09:52] <fgimenez> rhuddie, ok, thanks, i've also introduced some changes suggested by veebers in the test_services file, have you seen them?
[09:53] <rhuddie> fgimenez, no, not yet. I'll look through the changes
[10:13] <rhuddie> fgimenez, it seems to me that there is not much difference between the single and multi signal reactor, just how the signals get returned by the run function
[10:14] <rhuddie> fgimenez, so, how about just returning self.signals? then let the calling code check how many records there are etc?
[10:14] <rhuddie> that way you would only need 1 class for single and multi signals
[10:15] <fgimenez> rhuddie, that's right, barry pointed out that when more than one signal may arise you cannot only return the first one
[10:15] <rhuddie> fgimenez, for the download case, there are multiple signals, and in the reactor I just return the full list
[10:15] <rhuddie> then the calling code can check through them, or just look at the last one (which is what I actually do)
[10:17] <fgimenez> rhuddie, if it works for you go ahead with  it, i tried to dig in si code and was not sure of how the signals array was actually filled with more than one signal
[10:18] <rhuddie> fgimenez, it's just an array which gets a new record added for every callback it gets. you can see what I have here: https://code.launchpad.net/~canonical-platform-qa/ubuntu-ota-tests/wait-for-download/+merge/252759
[10:19] <rhuddie> fgimenez, so I think we could probably do away with the single and multi array classes, just make BaseReactor run() return self.signals
[10:20] <rhuddie> fgimenez, let me try that out
[10:20] <fgimenez> rhuddie, of course :)
[10:23] <rhuddie> fgimenez, yes that works fine for my multisignal case
[10:23] <fgimenez> rhuddie, ok perfect then :)
[10:24] <fgimenez> the only thing, imo given the asynchronous nature of the process we shouldn't assume any order when multiple signals may come
[10:28] <rhuddie> fgimenez, great, yes. Well, in that case the reactor is just passing the list of received signals back. the caller could then check the order if necessary? Or you could add a derived run() method to check the order?
[10:29] <fgimenez> rhuddie, yes the caller should check, maybe the happy-path  signal is not even in the array
[10:31] <rhuddie> fgimenez, I'll add my comments then to your mp about returning self.signals from base class run () and removing SingleSignalReactor
[10:33] <fgimenez> rhuddie, ok thanks, probably barry can tell us if there may be any corner case not covered by this approach
[11:24] <fgimenez> rhuddie, i'm not sure if calling self.quit in the _do_ methods of the reactor is right in the multiple signal case
[11:24] <fgimenez> rhuddie, see http://bazaar.launchpad.net/~ubuntu-system-image/ubuntu-system-image/client/view/head:/systemimage/reactor.py#L98
[11:26] <fgimenez> rhuddie, ok, i've seen that you removed it from _do_UpdateProgress
[11:36] <rhuddie> fgimenez, yes, I just left it in the case where the operation had either failed or succeeded
[14:45] <balloons> ubuntu-qa, autopilot3 appears to be broke on vivid atm. I'm assuming an update to vivid broke it, and autopilot2 remains unaffected.
[14:45] <rvr> Hmm
[14:45] <brendand_> balloons, i'm vanguard today i believe
[14:45] <brendand_> balloons, do elaborate
[14:46] <balloons> brendand_, I'll get you a log and I'm digging in myself atm
[14:46] <balloons> brendand_, http://paste.ubuntu.com/10610073/
[14:46] <balloons> I've tried calendar and clock and both fail this way..
[14:47] <balloons> I'm surprised the backend code is really that different, but we'll see
[14:47] <brendand_> balloons, on device or desktop?
[14:47] <balloons> brendand_, desktop
[14:47] <brendand_> balloons, okay can you put your exact repro steps as well
[14:51] <balloons> brendand_, sure, since this isn't a known thing. But more or less try and run any autopilot3 test on the desktop. They all seem to fail trying to instantiate a backend
[14:52] <brendand_> balloons, did you install an -autopilot package or run from source?
[14:53] <balloons> brendand_, here's a full reproduction: http://paste.ubuntu.com/10610117/
[14:53] <brendand_> balloons, dpkg -l | grep autopilot would be good too
[14:53] <balloons> brendand_, let me add that
[14:54] <brendand_> balloons, although it does list the version in your log, but anyway
[14:54] <balloons> right
[14:54] <balloons> it's sad the vivid testrunner hasn't been running recently, could have pinpointed when this broke
[14:57] <balloons> http://paste.ubuntu.com/10610145/
[14:59] <brendand> balloons, dunno about you but trying to run that just crashed my session
[14:59] <balloons> brendand, heh, fun times
[14:59] <balloons> I'd like to try on device now
[15:00] <brendand> balloons, afaik everything is fine on the device, folks have been running sanity tests today
[15:00] <balloons> right, I would assume so, and it's backend stuff anyway
[15:03] <balloons> brendand, ohh the python-autopilot package wasn't updated, so that's why it still works. Makes sense now as the backend code is the same
[15:03] <brendand> balloons, is that from looking at dpkg -l | grep autopilot?
[15:05] <balloons> brendand, yes and looking at the source it's different. A new version was not pushed
[15:05] <brendand> balloons, can you paste it?
[15:06] <elopio> good mmorning.
[15:07] <balloons> morning elopio ! elopio since I have you, I'm interested in talking QA for scopes. Who's the best person to talk to about that? I want to get some docs of the best practices on developer.u.c and I need an example scope and tests to do it
[15:08] <brendand> balloons, ahem, vanguard :P
[15:09] <balloons> brendand, ohh I get to bug you for that too? brillant
[15:09] <balloons> brendand, what did you want me to paste anyway?
[15:09] <brendand> balloons, yeah - we just want to get out of the habit of elopio being the bottleneck for all qa requests
[15:09] <brendand> balloons, dpkg -l | grep autopilot
[15:10] <balloons> brendand, right it's in the paste above
[15:10] <balloons> http://paste.ubuntu.com/10610145/
[15:11] <brendand> balloons, ah i missed that one - session crashy remember :)
[15:11] <balloons> ahh right, sorry mate
[15:12]  * balloons suspects https://bugs.launchpad.net/autopilot/+bug/1297595
[15:14] <brendand> balloons, open a bug and veebers can have a look later today
[15:15] <brendand> balloons, as for the scopes thing, elopio probably does know best there (cop out i know)
[15:15] <balloons> brendand, I will just gathering some more data.
[15:15] <balloons> thanks for the scopes answer :-) I'll await Leo
[15:22] <elopio> balloons: hello
[15:22] <elopio> balloons: we need to get together with pete-woods to define those things.
[15:23] <elopio> balloons: do you want to set up a meeting? somebody from qa, pete, and yourself
[15:23] <balloons> elopio, sure can. Who might you recommend from qa? ask jfunk ?
[15:24] <elopio> balloons: yes, invite jfunk and he'll take somebody else if he thinks it would be good.
[15:24] <elopio> thanks.
[15:24] <balloons> elopio, ty yt
[15:24] <elopio> dkessel: https://github.com/magne4000/quassel-webserver
[15:24] <elopio> this looks promising for using quassel on the phone.
[15:25] <elopio> brendand: balloons: I can't reproduce the autopilot issue on my updated vivid.
[15:25] <elopio> I see a comment on my branch from veebers who says he was going to ask about it to CI.
[15:26] <balloons> elopio, oh really?
[15:28] <balloons> filed https://bugs.launchpad.net/autopilot/+bug/1432700
[15:41] <elfy> hey balloons - quick one ... question of course :p
[15:41] <elfy> http://cdimage.ubuntu.com/daily-live/current/
[15:41] <elfy> does that look right to you ... am I missing something
[15:41] <balloons> pretty slick there eh?
[15:42] <balloons> it's correct insomuch as the new builds all fail automated testing
[15:42] <elfy> aaah
[15:42] <knome> slick... as in slickymaster?
[15:43] <balloons> I don't think slickymaster had anything to do with it..
[15:43] <balloons> now knome on the other hand :-)
[15:43] <elfy> right - so one's you could grab from tracker as daily are ok - but as it's failing auto testing - the daily there isn't updating - is that right?
[15:44] <knome> would i ever break anything?
[15:45] <elfy> balloons: so - that is expected from that link? just need to answer some people
[15:48] <balloons> elfy, -pending images don't get linked to the tracker as the are completely broken and useless for testing. However, 10 days is quite a long time to not have a new image
[15:48] <balloons> normally you might see a day or 2 gap in the image if something like that happens
[15:48] <balloons> sometimes it's as simple as making a .1, and you never get the .0
[15:49] <balloons> elfy, and yes you are correct. the tracker lists the last good image to test and won't update until a new good image is produced
[15:54] <elfy> balloons: so thew tracker is listing today - that direct current shows the 6th
[15:57] <balloons> yep
[15:57] <balloons> ohh
[15:58] <balloons> ahh I see.. well that does make more sense for it not to be 10 days old, but . . .
[16:11] <elfy> balloons: yea - bit broken there
[16:11] <elfy> balloons: also - is -release the right place to raise - umm chaps there's something wrong with the dailies?
[16:14] <jfunk> ping project-team vanguard
[16:15] <balloons> elfy, yes they are a good place to start
[16:15] <elfy> thanks balloons :)
[16:16] <balloons> ty!
[16:16] <elfy> so - back to that link - not roight? should be same as tracker?
[16:17] <balloons> elfy, it's a bit weird.. what I explained to you is correct, but indeed it doesn't match what we see
[16:18] <elfy> ok - I'll post in the +1 thread for them then :)
[16:27] <elopio> fgimenez: it's your turn on the vanguard, right?
[16:28] <fgimenez> elopio, i think that brendand took over, the rotation's been messed up after the friday
[16:29] <elopio> brendand: jfunk pinged ^
[16:29] <brendand> jfunk, hey
[16:30] <jfunk> seems like vanguard notification needs a little work
[16:30] <jfunk> brendand: there's a bug https://launchpad.net/bugs/1427439
[16:30] <jfunk> which I think we need to add a test for
[16:30] <jfunk> it should be simple enough
[16:31] <brendand> jfunk, well - to be fair it's in the channel topic - ping ubuntu-qa. if you don't think that's right suggestions are welcome, we can change it
[16:32] <brendand> jfunk, i suppose the flight mode sanity test ought to catch that
[16:33] <jibel> brendand, no, because we test only once
[16:33] <brendand> jibel, we enable, then disable. do we need to do that again in order to trigger it?
[16:34] <jibel> brendand, yeah, we'd want to do it like 100 times
[16:34] <brendand> jibel, oh it's a race condition (seems to be from reading the description though not 100% clear)
[16:35] <elopio> what we need is a regression test for the issue, at the low level. First they need to find the cause, and make a scenario to reproduce it.
[16:36] <brendand> elopio, well that, yes
[16:36] <jibel> elopio, agreed. But we can also test the other direction for issues that are not known
[16:38] <elopio> jibel: we can, but we need to think about the suites we will automate, make sure they are covering holes left by the low level suites.
[16:38] <elopio> if they fix this issue, and make a regression test for it, we will waste 100 cycles because all the runs will be green.
[16:38] <elopio> a long running test with common tasks that a user would do sounds nice.
[16:39] <elopio> but for that to work, first we need to make the random long running test to work.
[16:39] <jfunk> elopio: I guess I am worried that this problem could get out to users and want to get something in place to make sure we catch it
[16:40] <elopio> jfunk: they must make a test that catches it.
[16:40] <elopio> the issue has nothing to do with the indicator, so that test must not be through the UI.
[16:41] <jfunk> elopio: they can make a test that catches what they *think* causes it (as they already have) but I ran into it on my own, which proved they hadn't found all the causes of it
[16:41] <brendand> jfunk, automated testing is the perfect place for that, yes. whether it should be a sanity test... that depends
[16:42] <jfunk> elopio: right, I am not suggesting the test must be AP on the UI, only that the test must run regularly as part of regular testing
[16:42] <elopio> jfunk: right. But in order to write a good test, we first need to have a good scenario to reproduce the issue. That's where they must spend their time first, before writing the test.
[16:42] <brendand> jfunk, we'd have to get the balance between frequency/number of times run and severity
[16:43] <brendand> jfunk, if we ran it 100 times every image that would add a lot of time to the sanity run
[16:43] <elopio> if we know with 90% certainty that the issue will occur if the action is repeated 100 times, that's not good enough to get good automation out of it.
[16:43] <elopio> we caan use that knowledge to collect more knowledge.
[16:45] <elopio> add logs, debug, until the problem is understood.
[16:46] <elopio> then it will be easy to write a single test that when run only once will catch any regression of the same problem.
[16:47] <brendand> jfunk, by all means add a card to the backlog so we don't forget about it
[16:54] <rhuddie> brendand, should I add a task for looking at the sanity failures?
[17:23] <elopio> brendand or rhuddie: this needs one more review: https://code.launchpad.net/~canonical-platform-qa/autopilot/fix1266601-Pointer-pressed-move-2/+merge/252932
[17:37] <rhuddie> elopio, I can take a look, but it will have to wait until later as it seems quite large
[18:32]  * knome stares at om26er who changed their nick for 15 minutes to tell they were away
[18:32] <knome> (O.O)
[18:32] <om26er> knome, heh, it was a really quick dinner
[18:33] <knome> well i'm really surprised that there really isn't any other way to tell you are away than changing your nick
[18:33] <knome> oh but there is, /away ! :P
[18:35] <knome> roadmr_afk, et tu, brute?
[18:39] <ToyKeeper> /away is far less visible, and depends on the client to notice and ... grey out the nick or something...  a nick change is immediate and hard not to notice (especially if tab-completing a name)
[18:39] <knome> ToyKeeper, but why would you want to know if everybody is away or not?
[18:40] <knome> for example, why would you care if i'm away or not if you don't have anything to discuss with me?
[18:40] <knome> if you have something to discuss with me, why couldn't you see my away message?
[18:41] <ToyKeeper> In general, /away status tends not to mean much (especially auto-away), and /away messages tend not to get seen by anyone.
[18:41] <knome> fwiw, it's even on the ubuntu IRC channel guidelines:
[18:41] <knome> !away
[18:41] <knome> ToyKeeper, i couldn't disagree more...
[18:42] <ToyKeeper> But it depends on the person.  I don't generally set away messages, others do.
[18:42] <ToyKeeper> The nick change tends to bug me because it can make logs weird or break privmsg sessions.
[18:42] <knome> i don't mind if you do or not (i can probably see if you are away or not judging by the idle time)
[18:43] <knome> but i do care about awaynicks because i most often do not need to have the immediate information that you are eating lunch...
[18:44] <ToyKeeper> I also think one should never ping without data (i.e., just ask the question, don't ping first), but I have trouble convincing others to do the same.
[18:45] <ToyKeeper> What I'm getting at is ... I can't change human nature, so I choose not to get upset about it.
[18:45] <knome> well, what i'm getting at is that setting an awaynick is actually just as much work than an awaymessage...
[18:49] <ToyKeeper> Yes, but one can't fight every battle.  :)
[18:50] <knome> but i can win this battle ;)
[18:50] <dobey> knome: i'm going to go drink a gallon of water and /nick every 5 minutes to let you know i had to go use the toilet :P
[18:53] <dobey> knome: what you should do, is every time someone uses a nick change to show their status, pipe an !away to them
[18:54] <dobey> you could even write a bot to do it :)
[18:54] <knome> dobey, nah, it's better to leave a disturbing, shameful, public personal message ;)
[18:54] <dobey> eh, shame is for the weak :P
[18:55] <knome> :P
[19:21] <balloons> la_juyis, have you taken a look at what the help app looks like so far? would you like to?
[19:22] <knome> hullo balloons, what's up?
[19:23] <balloons> hey knome.. Trying to get work for the week all sorted, yourself? monday is in the books for you, I'm jealous
[19:23] <knome> kicking up the action again after a long weekend too
[19:24] <knome> and continuing with personal projects on the evening :P
[19:45] <veebers> balloons: ping hey I saw your bug go past in my email. I'll be looking at that today, once I get a VM up.
[19:45] <veebers> I suspect a new vivid something is happening
[19:48] <balloons> veebers, aye me too. Sadly the jenkins testing bot hasn't had a run this month (seems most things are running on utopic again for some reason)
[19:48] <balloons> that would have made it easy to see when it stopped working :-(
[19:51] <veebers> balloons: yeah, a little annoying. Oh well.
[20:11] <Letozaf_> balloons, hey :)
[20:11] <balloons> Letozaf_, buonasera
[20:12] <Letozaf_> balloons, I am having problems with autopilot3, I get errors running tests on filemanager app and calendar app, are there any issues or is it just me ?
[20:15] <Letozaf_> balloons, http://paste.ubuntu.com/10611753/
[20:16] <Letozaf_> balloons, http://paste.ubuntu.com/10611758/
[20:17] <balloons> Letozaf_, you are hitting the lovely bug: https://bugs.launchpad.net/autopilot/+bug/1432700
[20:17] <balloons> just found it this morning
[20:18] <Letozaf_> balloons, ah! ok thanks, so I am stuck :P
[20:18] <Letozaf_> balloons, but can I use autopilot2 ?
[20:19] <balloons> Letozaf_, yes you can, if the testcase supports it
[20:19] <Letozaf_> balloons, how do I find out ?
[20:26] <balloons> Letozaf_, by trying it :-) no harm in running it with autopilot
[20:26] <balloons> the only one I know of that won't work is reminders and calendar
[20:26] <Letozaf_> balloons, :) yes just found out that filemanager app does not run also with autopilot2
[20:31] <balloons> Letozaf_, ahh.. plugin issues?
[20:32] <balloons> Letozaf_, you can also install the old version
[20:32] <roadmr> knome: I've disabled my nick changer, but not because of your attempt at shaming me (can hardly be ashamed of something so widely done) but because you're right that it's in the channel guidelines. Plus I'm not important enough that I need to broadcast the fact that I'm away :)
[20:32] <nuclearbob> ubuntu-qa: I'm having some trouble with adt-run failing to find fakeroot: http://pastebin.ubuntu.com/10611845/ The package builds on my computer
[20:33]  * knome offers roadmr cookies and milk
[20:33] <roadmr> knome: thanks :)
[20:34] <Letozaf_> balloons, the old version of autopilot ? or what ?
[20:35] <balloons> Letozaf_, yes. http://mirrors.kernel.org/ubuntu/pool/universe/a/autopilot/python3-autopilot_1.5.0+14.10.20140812-0ubuntu1_all.deb
[20:36] <Letozaf_> balloons, ok thanks I will now
[20:36]  * balloons hasn't tried that just yet, so do give it a whirl :-)
[20:36]  * Letozaf_ is giving it a whirl :)
[20:36]  * balloons feels dizzy
[20:36] <balloons> round and round . . ..
[20:36] <Letozaf_> :D
[20:41] <Letozaf_> balloons, unfortunatly filemanager fails also with the older version: http://paste.ubuntu.com/10611904/
[20:42] <Letozaf_> balloons, also  calendar app: http://paste.ubuntu.com/10611911/
[20:43] <la_juyis> balloons, I have a pomodoro in 10' if you wish to talk about that :)
[20:43] <balloons> la_juyis, mmm..
[20:43] <Letozaf_> balloons, ?
[20:44] <Letozaf_> ohhh sorry la_juyis is a nik
[20:44] <Letozaf_> la_juyis, sorry :P
[20:44] <balloons> la_juyis, vi piace cibo di casa?
[20:44] <balloons> Letozaf_, :p
[20:44] <dobey> 10 minute tomatoes?
[20:44] <Letozaf_> la_juyis, balloons ohhh così la_juyis è Italiano
[20:45] <Letozaf_> balloons, si mi piace il cibo fatto in casa :D
[20:45] <balloons> Letozaf_, no, actually she isn't heh.. We have an Italian restaurant locally here called pomodoro, and that's there motto, so I was responding to her with it :-)
[20:46] <balloons> well.. cibo di casa is the motto anyway, heh
[20:46] <Letozaf_> balloons, oooh cool :D
[20:46] <Letozaf_> balloons, Italian food is the best :P
[20:46] <balloons> otherwise I don't know what pomodoro is :-)
[20:46] <Letozaf_> balloons, pomodoro is tomato
[20:46] <dobey> balloons: it's an app
[20:46] <dobey> balloons: http://pomodorotechnique.com/timer/
[20:47] <Letozaf_> dobey, mmm real tomatoes are better :P
[20:47] <dobey> oh, well, a "time management technique"
[20:47] <balloons> wild..
[20:47] <dobey> Letozaf_: only in marinara
[20:47] <dobey> or ketchup
[20:47] <Letozaf_> dobey, I also like tomato salad
[20:48] <dobey> beyond that, meh
[20:48] <Letozaf_> dobey, tomato sauce, we have tomato everywhere here in Italy
[20:48] <balloons> yea.. probably quite good.. not factory farmed under lights :-)
[20:48] <dobey> yeah
[20:48] <dobey> well, depends
[20:49] <dobey> and even the ones outdoors are farmed under lights :P
[20:49] <la_juyis> Letozaf_, :)
[20:49] <Letozaf_> :D
[20:49] <la_juyis> balloons, mi piace moltissimo!
[20:49] <dobey> it's just a very, very big light bulb that runs on fusion
[20:50] <la_juyis> :P
[20:50] <Letozaf_> la_juyis, ti piace moltissimo cosa ? il pomodoro ? :D
[20:50] <la_juyis> balloons, sorry, i though you'd knew the pomodoro tecnique :D
[20:50] <la_juyis> Letozaf_, anche!
[20:50] <dobey> la_juyis: it's more fun when they don't though :P
[20:50] <la_juyis> Letozaf_, ma il cibo fatto in casa. il cibo che faccio io :P
[20:50] <balloons> la_juyis, no, but all this food discussion is more fun eh?
[20:51] <Letozaf_> la_juyis, ma che cibo fai in casa? pasta al pomodoro ?
[20:51] <la_juyis> balloons, certainly :P
[20:51] <la_juyis> Letozaf_, tantissime cose! ieri ho fatto biscotti :D
[20:52] <Letozaf_> la_juyis, biscotti al pomodoro :P :D
[20:54] <Letozaf_> balloons, shorts app tests work with the older autopilot version
[20:55] <Letozaf_> balloons, sorry I mean with autopilot2 not autopilot3 older vers.
[20:55] <la_juyis> Letozaf_, hahaha ! per carita, no! biscotti di burro, mele e avena
[20:55] <Letozaf_> la_juyis, lol was just teasing :P
[20:55] <Letozaf_> la_juyis, mmm sound delicious
[20:56]  * balloons was worried Letozaf_ ate tomatoes with sugar
[20:56] <balloons> la_juyis, anyways; people.canonical.com/~nskaggs/help/index.html
[20:56] <Letozaf_> balloons, lol
[20:58] <Letozaf_> balloons, by the way there is a receipt for tomatoes with sugar : http://ricette.giallozafferano.it/Pomodori-confit.html
[20:58] <dobey> my italian is not as good as my spanish
[20:59] <Letozaf_> recipe not receipt :P
[20:59] <dobey> hmm, or maybe it is, if only talking about food
[20:59] <Letozaf_> dobey, unfortunatly I do not know Spanish :D
[21:00] <la_juyis> Letozaf_, i had a salad with those the other day. delicious!
[21:00] <la_juyis> balloons, how are you dealing with translations? :)
[21:01]  * Letozaf_ is starting to feel hungry
[21:01] <la_juyis> balloons, maybe it's worth noting that the FAQ and the Community pages are .en only?
[21:04] <balloons> la_juyis, launchpad for translations. We'll have a big push to get them done soon.
[21:05] <balloons> and la_juyis yes, only German has much in the way of translation at the moment.
[21:05] <balloons> But I thought I would share what the web pages look like atm.. The offline click app looks similar on the phone
[21:06] <balloons> Letozaf_, glad at least some of it can be worked around
[21:06] <la_juyis> balloons, sure, just asking :)
[21:07] <Letozaf_> balloons, yes I have a bug for shorts to fix so...
[21:07] <la_juyis> balloons, lmk if you need help with the spanish side of things
[21:18] <balloons> la_juyis, thank you. Do you have additional content (or vice versa, would you like some of this content?)?
[21:19] <la_juyis> balloons, did you add those to AU?
[21:21] <balloons> I'm not sure if you saw the embedded video; http://people.canonical.com/~nskaggs/help/settings.en-us.html
[21:21] <balloons> la_juyis, I was wondering if you had more things like that. And no, I didn't add anything to AU
[21:23] <knome> chihchun_afk, didn't we just talk about awaynicks today on the channel :P
[21:23]  * balloons notes knome is on the crusade!
[21:24] <knome> think as i do or get decapitated!
[21:25] <la_juyis> balloons, oh, I thought you'd be adding stuff there, and consuming the contents from there later
[21:27] <balloons> la_juyis, the idea was to get the basics into the app and link out to AU for harder questions or complex questions that might change rapidly
[21:28] <balloons> la_juyis, the idea to scrape from AU didn't work out.. partially because of translations (we can translate this app)
[21:48] <elopio> nuclearbob: you are probably missing -B
[21:48] <elopio> or --unbuilt-tree
[21:48] <elopio> or both.
[21:50] <veebers> nuclearbob, elopio: ugh sorry I missed the ping to u-qa :-\
[21:51] <elopio> nw
[23:26] <veebers> balloons: are you still around perchance?
[23:50] <veebers> barry: are you around? :-)