[00:04] <ToyKeeper> It'd be nice if freenode wouldn't freak out when I change the host connected to my proxy...  as I'm about to do.  Probably gonna get flood-kicked in a moment.
[00:07] <sergiusens> popey my znc is all confused it seems :-P
[01:07] <Wellark> good "evening" all
[01:16] <tedg> Wellark, Are you testing silo 19?
[01:16] <Wellark> tedg: which one is that?
[01:16] <Wellark> tedg: ...
[01:17]  * Wellark goes to get a clue
[01:17] <tedg> Wellark, connectivity api singleton
[01:17] <Wellark> oh, that
[01:17] <Wellark> just land it
[01:17] <Wellark> if it compiles, and tests pass it's fine
[01:18] <Wellark> same for silo 11
[01:18] <Wellark> that can be landed as well
[01:18] <tedg> Wellark, Is no one using connectivity api that we should check?
[01:19] <Wellark> tedg: not yet
[01:19] <Wellark> I landed it like on Friday
[01:19] <Wellark> and have not announced it on the ubuntu-phone ml yet
[01:19] <Wellark> will do it when silo 19 lands
[01:19] <tedg> k
[01:19] <Wellark> tedg: so, please mark both silos "Testing Done"
[01:20] <Wellark> wtf.. it's 4am already..
[01:20]  * Wellark sometimes wonders what is the meaning of life
[01:22] <tedg> Wellark, It seems that 11 should be installed on a device and made sure it's sane, we're definitely using indicator-network.
[01:22] <ToyKeeper> dobey: Around?  The ubuntuone-credentials test plan seems to be out of date.
[01:23] <Wellark> tedg: it's sane
[01:23] <Wellark> trustme
[01:24] <Wellark> it's just a try {} catch {}
[01:24] <Wellark> nothing more
[01:24] <Wellark> try{} does not have side effects
[01:24] <tedg> Wellark, Sure, but that can easily break something.It could catch something that went through and was used before elsewhere.
[01:24] <Wellark> and it will fix the #1 crasher on touch devices
[01:25] <Wellark> tedg: trust me. it's a precision WMD
[01:26] <tedg> I'm going to be trying to land some other silos tonight so I'll be flashing, I can test that one too.
[01:26] <Wellark> tedg: ok, thanks
[01:26] <Wellark> tedg: the only "test" there is that indicator-network keeps running
[01:27] <Wellark> tedg: and you can connect to an accesspoint using it
[01:27] <tedg> Wellark, K
[01:30] <Wellark> trainguards: please publish silo 19 ASAP
[01:30] <Wellark> it's an API break on a new QML module and we need it to land before users emerge
[01:31] <Wellark> and I can't send an announcement email to the ML before it's landed
[01:31] <Wellark> that's critical piece of API for the developers
[01:40] <robru> Wellark: will do, just afk now
[01:41] <tedg> robru, You need to put it in language Wellark understands: "had an emergency, ran out of beer, getting more, be back soon" :-)
[01:42] <Wellark> XD
[01:43] <Wellark> and don't know if it's sad or funny, but that is just so true...
[01:48] <kgunn> ToyKeeper: copy/paste worked for me...from browser to notepad
[01:48] <kgunn> i found an issue with msg app last week and had filed a bug
[01:49] <kgunn> seemed specific to msg app
[01:49] <kgunn> also notepad-to-notepad seems fine
[01:50] <ToyKeeper> kgunn: From what I found, long-tap in the browser acts like a double tap, simply selecting the current word.  I couldn't get the context menu to come up at all.
[01:50] <ToyKeeper> kgunn: Then I tried copy from notepad to SMS.  I could select text, copy it, then long-tap in the SMS entry showed 'paste' greyed out.
[01:50] <kgunn> right...the greyed out paste is the bug
[01:51] <ToyKeeper> Okay, the test plan didn't note anything about that case failing.
[01:52] <ToyKeeper> kgunn: Any ideas what happened with the browser's context menu?
[01:52] <kgunn> also, the browser is really fickle...but you can get copy to come up
[01:52] <kgunn> i mean i can (on multiple devices too)
[01:53] <ToyKeeper> The silo is approved since it fixes something and doesn't appear to break anything, but now there's a possible regression to track down.
[01:53] <kgunn> ToyKeeper: whats the regression ?
[01:54] <kgunn> https://bugs.launchpad.net/messaging-app/+bug/1360429
[01:54] <kgunn> https://bugs.launchpad.net/platform-api/+bug/1322238
[01:54] <ToyKeeper> kgunn: The browser's context menu on highlighted text used to work...  not sure when it broke.
[01:55] <ToyKeeper> (triple-click a paragraph to select it, tap-and-hold to bring up a context menu, and instead it just reduces the selection to the current word)
[01:57] <ToyKeeper> I can get it to copy a link, but it's supposed to be able to copy regular text, right?
[01:57] <kgunn> ToyKeeper: oh, honestly, not sure about that....i've only ever copied like whole paragraphs
[01:58] <ToyKeeper> In any case, it looks like this isn't a mir issue.  I originally thought it was because none of the copy/paste cases worked, but it seems to be individual app issues instead.
[01:59] <ToyKeeper> The SMS bug is known, and it seems the browser needs a bug filed too.
[01:59] <kgunn> ToyKeeper: yeah for sure...it really is fickle
[01:59] <kgunn> i see what you mean now too
[01:59] <ToyKeeper> kgunn: Any chance you could update the mir test plan with notes about expected failures and/or more specific steps known to work?
[01:59] <kgunn> it has drag handles
[02:00] <kgunn> and you can't really drag to a smaller amount of text
[02:00] <kgunn> sure
[02:02] <tedg> Thanks robru!
[02:02] <ToyKeeper> Heh, I haven't been able to invoke the drag handle in the browser at all today, and in other places it's really really finicky.
[02:02] <robru> tedg: you're welcome!
[02:03] <ToyKeeper> Then again invoking the drag handles on Android is usually difficult too.
[02:03] <tedg> robru, If you're back at a keyboard I'd love a couple of silos as well please.
[02:03] <robru> tedg: sure just a sec, I'm doing your RTM one for 19
[02:04] <tedg> robru, Cool
[02:04] <robru> tedg: also you didn't specify a series for line 64
[02:04] <tedg> robru, Sorry, fixed.
[02:04] <robru> tedg: ok you got rtm2 for starters
[02:05] <imgbot> [02:05] <robru> thanks queuebot, you're the best friend a man could ask for.
[02:08] <robru> tedg: ok you got 12 and 14 for utopic
[02:08] <tedg> robru, Great, will build away.
[02:09] <tedg> charles, 14 is yours ^
[02:12] <robru> hold on to your butts, I'm gonna run the archive job, bot might freak out (but it really shouldn't!!)
[02:16] <dobey> ToyKeeper: sorry, the online-accounts trusted session stuff landing caused some visible changes, but the plan itself is basically the same. i've updated it
[02:17] <robru> ok everything seems in order here
[02:18] <ToyKeeper> dobey: I got a little distracted mid-testing.  Mostly, I just noticed that some "<" back buttons aren't there any more, and the 'add account' thing is gone too.
[02:19] <ToyKeeper> dobey: And, er, is there a way to test account creation on staging?  I'd prefer if I don't have to delete accounts from production after each test.
[02:23] <ToyKeeper> dobey: I've also noticed issues getting to the account settings or to U1 accounts after going back, but it's not consistent and it's not just with the silo.  Are there any known bugs about that at the moment?
[02:23] <dobey> ToyKeeper: yes. the easiest way is to run the "setup-staging.sh" script that is included in the pay-service package
[02:23] <ToyKeeper> Like, tapping U1 then cancel repeatedly tends to make it stop working.
[02:24] <robru> alright, I am out. I may respond to pings later but no guarantees
[02:25] <dobey> ToyKeeper: i don't know if there are specific bugs filed or not. with online-accounts using trusted sessions now, there have been some behavioral changes as a result. but all those changes are in online-accounts itself
[02:26] <dobey> ToyKeeper: if you find bugs where system-settings or online-accounts stops responding or such, please file bugs against online-accounts for them
[02:26] <ToyKeeper> dobey: Just curious.  It's not a silo blocker (happens without the silo too), but it's an issue I was hoping someone already knew about.
[02:28] <dobey> ToyKeeper: mardy would be the person to ask about it. i suspect that issue isn't limited to the u1 account plug-in, and if you hit cancel repeatedly for twitter/google/etc it has the same results?
[02:28] <ToyKeeper> Haven't tried the other account types yet.
[02:29] <ToyKeeper> Got pulled away just after I found it, and haven't gotten back to it yet.
[03:12] <ToyKeeper> dobey: Approved.
[03:45] <imgbot> [03:45] <imgbot> [03:59] <Wellark> tedg: did you have time to test the $silo to get it landed+
[03:59] <tedg> Wellark, The indicator-network one?
[04:00] <Wellark> tedg: yeah
[04:00] <tedg> Wellark, Yup, merged and cleaned.
[04:02] <Wellark> tedg: thanks!
[04:02] <tedg> np
[04:05] <tedg> Thought I could run through these ubuntuuitoolkit tests, but I might fall asleep before they finish.
[04:06] <Mirv> Wellark: let's see
[04:07] <Mirv> looks like published
[04:08] <Mirv> indeed
[04:08] <Mirv> I think it slightly missed #209 image though
[04:09] <Mirv> Wellark: like, er, morning to you, or evening?
[04:13] <Wellark> Mirv: something like that
[04:13] <Wellark> or between
[04:15] <Mirv> o_O
[04:17] <Mirv> nice, a crasher fix
[04:17]  * Mirv updates mako
[04:18]  * Mirv goes crazy and will update new shiny Qt DPI support there too
[04:40] <ToyKeeper> Hmm, no thostr.
[04:42] <ToyKeeper> I wonder if anyone knows what bug is fixed in row 49 / rtm-013, "fix crash bug in network indicator".
[04:42] <ToyKeeper> It has no MP or bug attached.
[04:43] <Mirv> ToyKeeper: looking at the PPA contents, it's https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1343341
[04:43] <Mirv> something found from errors.ubuntu.com logs
[04:44] <ToyKeeper> Thanks!  I didn't think about looking in the PPA.
[05:08] <Mirv> hmm, ken is not online. anyway, that line 21 conflicts witch the Mir 0.7.0 landing which is also in rtm silo
[07:04] <asac> sil2100: hello :)
[07:07] <thostr_> sil2100: I'm confused about rtm landing silo 8
[07:08] <thostr_> sil2100: it says build fails because of missing libunity-scopes 0.6.3 which is exactly the version in pulls in...?
[07:11] <thostr_> sil2100: or, can I specify somehow that libunity is built before the shell?
[07:25] <pstolowski> sil2100, hey! if we get our stuff src-copied from u to rtm, do we also need to merge it intro rtm branches? or can we remove/disable these branches for now since we don't diverge from utopic?
[07:31] <sil2100> Hey!
[07:31] <thostr_> sil2100: good morning
[07:32] <sil2100> pstolowski: you don't need rtm branches then, since you just need to make sure you release everything into both more or less
[07:32] <thostr_> sil2100: how can I tell the builder to build the src packages in certain order?
[07:32] <sil2100> thostr_: hey! Let me take a look on what exactly is happening
[07:34] <Mirv> sil2100: we've a process question. bzoltan has run the usual 8h of tests on UITK on ubuntu. will he need to separately run the same 8h of test on ubuntu-rtm?
[07:36] <sil2100> Mirv: from my current understanding, the testing will have to be repeated... but I'm not sure if that's the final decision and if QA doesn't have any ideas on getting this better
[07:37] <sil2100> thostr_: ok, I kicked a rebuild of those packages... normally it would be stuck in a dep-wait, but I think the debian deps (maybe) weren't bumped
[07:38] <sil2100> thostr_: so it's really hard to force a specific build order without build-deps, we might just have to rebuild the packages in this case (which is not a big deal I think)
[07:39] <thostr_> sil2100: that's why we bumped the version to 0.6.3 to enforce the order... anyway, I keep my fingers crossed
[07:42] <Mirv> bzoltan: ^ dual testing for dual landings for now...
[07:42] <thostr_> sil2100: what did you rebuild? I cannot see it building
[07:42] <Mirv> and after that, QA signoff
[07:43] <sil2100> thostr_: now things build successfully from what I see - I kicked package builds in the PPA
[07:43] <bzoltan> Mirv:  OK, I charge my device and run the tests again
[07:43] <thostr_> sil2100: ah, ok, jenkins UI was slow
[07:45] <sil2100> thostr_: so, actually the problem that happened is that well, the ubuntu-rtm archive had currently the 0.6.3+14.10.20140820.is.0.6.1+14.10.20140809-0ubuntu1 version of the package (so the build-dep of 0.6.3 in packaging has been satisfied), but since this version is a revert it actually was 0.6.1... so there was no packaging dep wait, as the builder thought it's already satisfiable by the archive
[07:46] <sil2100> thostr_: that's a singular case, we rarely do reverts so such a thing should not happen again :)
[07:47] <thostr_> sil2100: yes, that was still fallout from rtm landing testing from last week
[08:01] <sil2100> brendand, davmor2: once you're up - there's a nifty list of QA sign-off tasks waiting for you :)
[08:03] <brendand> sil2100, so. many. signoffs
[08:03] <brendand> sil2100, i've still got silo 3 from yesterday. i'll probably sign it off in a minute and move on
[08:04] <sil2100> Excellent
[08:26] <davmor2> sil2100: I don't care :P
[08:27] <davmor2> sil2100: oSoMoN: did browser land in the end?
[08:27] <oSoMoN> davmor2, looks like it did, thanks!
[08:28] <davmor2> \o/
[08:32] <thostr_> sil2100: during the testing I got a crash, that's because mediascanner was now built before libunity... so, what we need to do is to combine the rtm silos 7 and 8 and rebuild the mediascanner part
[08:32] <brendand> sil2100, you need to remind people to set 'testing pass' even if they haven't done it
[08:33] <brendand> sil2100, otherwise it doesn't show up on the dashboard as requiring QA signoff
[08:37] <mandel> sil2100, morning! one question, I'd like to create a silo for location-service with two branches that should land in at least rtm (but would be nice to have it land on utopic too) what should I do?? I got lost with all those emails :-/
[08:38] <sil2100> mandel: one moment, I'll get back to you after the meeting
[08:38] <mandel> sil2100, awesome, thx
[08:44] <robru> mandel: make a regular utopic silo, basically sil will make the rtm silo and copy the packages for you.
[08:45] <mandel> robru, ok, thx
[08:46] <robru> sil2100: check your emails, i updated the rtm copy script with a fix from Ursinha that finds the dsc files for you, much less work that way
[08:47] <robru> (Unless your train solution is working yet ;-)
[08:47] <robru> mandel: you're welcome!
[08:50] <Mirv> robru: there'a also the simple copy-archive tool from ubuntu-archive-tools
[08:50] <Mirv> no dget/dput needed
[08:51] <robru> Mirv: does it work across distros? I wrote a script specifically to download from a PPA, change distro, then upload to different distro PPA
[08:51] <robru> Mirv: this was specifically for utopic to rtm
[08:53] <Mirv> robru: yes, it works across distros and PPA:s (Debian/Ubuntu/PPA:s), pitti mentioned it on the mailing list
[08:54] <Mirv> robru: https://code.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk
[08:55] <robru> Mirv: http://paste.ubuntu.com/8152711/ ;-)
[08:55] <robru> But thanks
[08:56] <Mirv> ./copy-package -d debian -s sid --to-distribution=ubuntu --to-suite=utopic --to-ppa=canonical-qt5-edgers --to-ppa-name=qt5-daily $1-opensource-src :)
[08:57] <Mirv> so that'd be probably -d ubuntu -s utopic --to-distribution=ubuntu-rtm --to-suite=14.09 --to-ppa=ci-train-ppa-service --to-ppa-name=landing-0xx
[08:57] <Mirv> so it's a LP operation and the copy happens immediately
[09:06] <brendand> sil2100, some lines don't have merge requests
[09:06] <brendand> sil2100, is that allowed?
[09:08] <Mirv> sil2100: on the latest rtm image I just got upgrade offer for Clock 3.1.69
[09:08] <sil2100> mandel: so!
[09:08] <Mirv> which is what I uploaded
[09:09] <sil2100> mandel: I see you already got an answer for your question ;)
[09:10] <sil2100> Mirv: oh, didn't know this tool actually worked for ppa's as well!
[09:10] <nik90> Mirv: so the next rtm image should have clock 3.1.69 by default instead of as an upgrade?
[09:10] <sil2100> brendand: which lines?
[09:10] <ogra_> nik90, yep
[09:10] <Mirv> sil2100: yeah, I've used for syncing from Debian to Qt landing PPA:s
[09:10] <Mirv> nik90: yes
[09:11] <mandel> sil2100, yes, I'll request the silo for utopic and then will do the testing, once that is done you take care of the rest, correct?
[09:11] <sergiusens> ogra_: sil2100 in case you want to type it down somewhere, snakefruit syncs run at :11' and :41'
[09:11] <Mirv> mandel: when ou request silo you get a silo for both utopic and rtm, and you'll need to currently test them both
[09:12] <sergiusens> http://people.canonical.com/~ubuntu-archive/click_packages/click_list already has the latest clock
[09:12] <ogra_> shrotly after the publisher then
[09:12] <ogra_> so lets build an image :)
[09:12] <sil2100> ogra_: can you build a new image?
[09:12] <sil2100> Right ;)
[09:12] <ogra_> on it :)
[09:12] <asac`> rtm?
[09:13] <thostr_> sil2100: but my last request on ice for time being
[09:13] <brendand> sil2100, lots of them at the bottom of the sheet
[09:13] <ogra_> asac`, utopic, then rtm
[09:14] <asac`> cool
[09:14] <sil2100> mandel: so, in a nutshell: you request a silo for utopic, we give you a silo for both, you build your merges for utopic, test it there and when you say that it's fine, we copy those packages to the ubuntu-rtm silo for you to do a quick double-check from the ubuntu-rtm side :)
[09:14]  * asac` waits for a new rtm image
[09:14] <ogra_> 3h from now
[09:14] <mandel> sil2100, got it
[09:14] <ogra_> well, a bit more since janis server takes time to sync
[09:15] <asac`> yo
[09:15] <asac`> maybe we have system-image before that
[09:15] <asac`> :)
[09:15] <ogra_> lol
[09:15] <ogra_> high hopes
[09:15]  * asac` hopes for a full moon night in porland
[09:15] <asac`> :P
[09:15] <ogra_> then they will just drink more
[09:15] <ogra_> and not work :P
[09:15] <asac`> hah. think stephane can do this in whatever state as long as he is awake :P
[09:16] <ogra_> haha
[09:16] <asac`> a pro
[09:16] <ogra_> bah, the SIM unlocking is totally messed up in 209
[09:16] <ogra_> (i just did an OTA)
[09:17] <ogra_> oh and the carousel is back
[09:18] <ogra_> (for music)
[09:20] <imgbot> [09:20] <Mirv> thostr_: your landing conflicts with ted's indicator-transfer landing, so not assigning a silo yet.
[09:21] <Mirv> unless that gets sorted out otherwise
[09:21] <Mirv> their landing doesn't have a description even, though
[09:22] <Mirv> I wonder if that https://code.launchpad.net/~charlesk/indicator-transfer/better-content-hub-use/+merge/232144 should be just taken to your landing
[09:44] <thostr_> jibel: when QA signing of silo 8 please make sure you test that together with silo 7 (or vice versa)
[10:00] <brendand> sil2100, did anyone else pick up reminders? elopio?
[10:00] <brendand> sil2100, i might have some breathing space from silos in a few minutes
[10:01] <sil2100> brendand: excellent! I didn't get any news from elopio, he was busy testing the clock up probably?
[10:01] <sil2100> So you can take a look at that
[10:03] <brendand> sil2100, ok once i finish with this silo
[10:06] <Mirv> mandel: ^ so there's the first double silo for you
[10:10] <ogra_> double plus good !
[10:10] <ogra_> :)
[10:17] <ogra_> looks like the utopic rootfs is done ... https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/utopic/ubuntu-touch
[10:17]  * ogra_ triggers an RTM build
[10:20] <ogra_> hmm, "starting in 26 minutes" ... :( ... https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch
[10:24] <cjwatson> ogra_: that was just a temporary glitch for some reason
[10:24] <cjwatson> it's building, there are plenty of free builders etc.
[10:25] <bzoltan> ogra_:  is the phablet-click-test-setup expected to work with the RTM images?
[10:25] <bzoltan> ogra_:  ssh_exchange_identification: Connection closed by remote host
[10:27] <brendand> sil2100, can i get an answer on the spreadsheet question?
[10:27] <sil2100> brendand: what's up?
[10:27] <brendand> sil2100, i was wondering why some silos don't have any MPs associated
[10:27] <brendand> sil2100, line 48 for example
[10:28] <sil2100> brendand: these are RTM silos so we do them as source-package only
[10:28] <sil2100> brendand: so we only push source-package copies there
[10:28] <sil2100> (no MRs are involved in this)
[10:28] <brendand> sil2100, it makes it difficult to know what we're actually testing
[10:29] <sil2100> brendand: you need to check the "Additional source packages to land" for a list of what to test
[10:29] <sil2100> brendand: yeah, sadly, the package changelog should give info on what has changed
[10:29] <mandel> Mirv, awesome, thx!
[10:30] <brendand> sil2100, yeah i guess i can look at the diff
[10:30] <ogra_> bzoltan, nothing changed between rtm or utopic images in that regard
[10:30] <ogra_> shoudl function exactly the same
[10:30] <brendand> sil2100, it's not as easy but oh well
[10:31] <bzoltan> ogra_: all right.. it stopped working after i flahes rtm image after 207
[10:31] <ogra_> bzoltan, did you use --bootstrap ?
[10:31] <bzoltan> ogra_:  not
[10:31] <ogra_> (to get an up to date recovery)
[10:32] <bzoltan> ogra_: phablet-click-test-setup --wipe seems to help
[10:33] <sergiusens> bzoltan: ssh_exchange_identification during a click-setup means bzr (if using over ssh, most likely case) has errored
[10:33] <bzoltan> sergiusens:  I figured that ...
[10:43] <bzoltan> sergiusens:  I git this earler and I got it now too -> http://pastebin.ubuntu.com/8158275/
[10:43] <sergiusens> bzoltan: update the clock app
[10:43] <sergiusens> bzoltan: that''s the same reason everything broke in ci
[10:44] <bzoltan> sergiusens: I see
[10:44] <bzoltan> sergiusens:  could the phablet-click-test-setup just skip the app and carry on with rest of tests instead of just failing?
[10:45] <sergiusens> bzoltan: not by default; this is more of a ci tool; we don't want silent fails
[10:46] <bzoltan> sergiusens:  it does not need to be silent... but it should not fail. And it is not just a CI tool.  We have no other way to verify landings before going to the CI.
[10:47] <sergiusens> bzoltan: well pitti has been working on it's replacement for autopackage tests
[10:47] <sergiusens> bzoltan: in that respect; you just have a broken image; your verification would be incomplete
[10:47] <sergiusens> bzoltan: ask balloons about adt for clicks when he gets up
[10:48] <bzoltan> sergiusens:  my verification takes 8-10 hours ... i could live that single 10 minutes app test to the end
[10:49] <bzoltan> sergiusens: anyway, how to update the ubuntu-clock-app?
[10:49] <sergiusens> bzoltan: system settings, check for updates?
[10:50] <imgbot> [10:50] <bzoltan> sergiusens: ahh.. UI
[10:50] <imgbot> [10:50] <ogra_> there we go
[10:50] <sergiusens> bzoltan: or install that image ^
[10:50]  * psivaa goes and kick a run
[10:50] <bzoltan> sergiusens:  is there an RTM image with the fix? I should test anyway on the latest image.
[10:50] <ogra_> psivaa, rtm should be ready in about 1h
[10:51] <sergiusens> bzoltan: wrt ogra_ would know
[10:51] <ogra_> no idea, what is that fix you are looking for ?
[10:51] <ogra_> https://lists.ubuntu.com/archives/rtm-14.09-changes/2014-August/thread.html has all rtm landings
[10:51] <bzoltan> ogra_: some clock app update what will unbreak the phablet-click-test-setup
[10:52] <sergiusens> bzoltan: anyway; I don't do click testing anymore; log a bug and someone from the ci team will look; or do like most of us and prepare an MP
[10:52] <ogra_> bzoltan, ah, yeah, thats the reason why we do all thae manually triggerd image builds atm
[10:52] <ogra_> you can watch the rootfs building if you are bored :) https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch
[10:52] <bzoltan> sergiusens:  All right, thanks for your help.
[10:53] <ogra_> (still takes about 45min til it becomes a system-image after it built though ... and another 20-30 for krillin to pick up on it)
[10:54] <bzoltan> ogra_: i think I will go with the manual update :)
[10:57] <psivaa> ogra_: ack, was going to start krillin tests, will do once 210 appears in utopic-proposed then
[11:03] <brendand> ogra_, do you know who'd be suitable to look at the add-apt-repository bug? it's really slowing down silo testing
[11:03] <brendand> ogra_, cjwatson is at debconf or something, right?
[11:07] <ogra_> brendand, it needs launchpad changes first ... and afaik wgrant is looking into that (cjwatson told me)
[11:08] <ogra_> for now you need to hack up the sources.list.d entry i fear
[11:08] <brendand> ogra_, yes - we're doing that
[11:08] <wgrant> Well, the trivial thing to do would pretty much be to just s/ubuntu/ubuntu-rtm/ in python3-software-properties' ppa.py in ubuntu-rtm.
[11:08] <wgrant> I hadn't realised citrain used add-apt-repository anywhere.
[11:08] <ogra_> everywhere :)
[11:08] <ogra_> well, not the train but the testers and tools
[11:30] <bzoltan> sergiusens:  I flashed the #8 rtm image, updated the clock app. Still the phablet-click-test-setup fails
[11:30] <ogra_> bzoltan, why did you flash the 8 image ?
[11:30] <ogra_> you want 9 once it has built
[11:31] <ogra_> 8 is old
[11:34] <bzoltan> ogra_: that is what i got when I flashed with --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed
[11:34] <ogra_> yes, because thats the latest
[11:34] <ogra_> read the backlog rtm will still take a while
[11:35] <ogra_> about 45min to 1h after the rootfs has built it becomes a system image ... for mako ...
[11:35] <ogra_> then it takes another 30min or so for krillin
[11:36] <ogra_> aaadn ... #8 for mako just showed up
[11:36]  * sil2100 lunch o/
[11:36] <ogra_> *aaand even
[11:36] <ogra_> err
[11:36] <ogra_> #9 for mako
[11:36] <ogra_> bzoltan, if you test on mako, you can now flash again
[11:37] <bzoltan> ogra_: nice, the 9 is coming
[11:37] <ogra_> :)
[11:40] <thostr_> is jibel around?
[11:40] <thostr_> or, who can I contact for QA sign off?
[11:50] <ogra_> asac`, looks like rtm #9 for krillin is ready ... happy testing
[11:51] <ogra_> psivaa, ^^^
[11:52] <ogra_> psivaa, also one mako doesnt seem to be so happy in rtm testing
[11:52] <ogra_> http://ci.ubuntu.com/smokeng/utopic/touch_stable/mako/20140827%20%3F/9984/
[11:53] <ogra_> looks like a bzr ssh issue on the server or so
[11:54] <psivaa> ogra_: yea, i restarted a few of those bzr ssh ones. let me take a look at this
[11:54] <psivaa> and will kick the krillin off now
[11:54] <ogra_> default and install-and-boot seems ot have failed on one device ... funnily other devices (or at least one) seems to run its tests just fine
[11:55] <ogra_> the versioning on the dashboard seems to have been messed up by that appraently
[11:59] <psivaa> ogra_: yes, i dash_ignored the touch ones, not touch_stable jobs. done and restarted those jobs too. things should look ok in a little bit
[12:02] <psivaa> ogra_: sil2100: so the lp:ubuntu-clock-app bzr versioning wasn't fixed in 210?
[12:03] <davmor2> sil2100: hmmm so it looks like the current rtm image might of got in some of the fixes from the ubuntu line a lot of the issues I was having are no longer affecting me,  but it might be the unity8 silo I'm testing that is making it all smoother ;)  I'll keep an eye on things and let you know though
[12:07] <psivaa> hmm weird.. http://q-jenkins.ubuntu-ci:8080/job/utopic-touch-mako-smoke-daily/786/console failed on clock click setup
[12:07] <Mirv> bzoltan: hmm, it looks like webbrowser would need similar unblocking, now that didn't get in to #209
[12:08] <bzoltan> Mirv:  hmm... yes, it was cjwatson who unblocked the uitk
[12:09] <Mirv> bzoltan: I'm asking generally over there, since I believe he has finally went to sleep
[12:34] <ogra_> psivaa, it wass supposed to ... we only built the images for this issue
[12:34] <ogra_> and looking it seems that 210 is just fine on both arches
[12:35] <ogra_> err, sorry 9 rtm that is
[13:33] <bfiller> sil2100: looks like a failure occured publishing rtm silo 3, do I just need to resync trunk with telephony-service branch? looks like a new version got released in ubuntu since the silo request
[13:34] <sil2100> bfiller: what failure happened?
[13:34] <sil2100> Something is missing?
[13:34] <bfiller> sil2100: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=landing-003
[13:35] <sil2100> Let me take a look at that
[13:36] <sil2100> bfiller: you used separate rtm branches for those, right?
[13:36] <sil2100> Like, bzr branches
[13:36] <sergiusens> yay, I'll keep making edits to the comments until it gets assigned :-P
[13:36] <sergiusens> err, description
[13:37] <sil2100> sergiusens: ;) One moment
[13:38] <sergiusens> sil2100: it was more of a joke :-)
[13:38] <bfiller> sil2100: yes
[13:38] <sergiusens> sil2100: I still want a silo though :-P
[13:38] <bfiller> sil2100: there are separate rtm branches
[13:38] <sil2100> bfiller: so, yeah, it seems that there was some release happening to ubuntu-rtm directly... most probably re-syncing that branch with trunk should do it
[13:38] <sil2100> bfiller: and then just rebuilding telephony-service should do the trick
[13:39] <bfiller> sil2100: ok, will do
[13:39] <sil2100> sergiusens: of course, you want an RTM counterpart as well, right? :)
[13:41] <sil2100> sergiusens: both assigned!
[13:56] <Mirv> Wellark: https://code.launchpad.net/~jpakkane/thumbnailer/embedded-album-art/+merge/231207 not approved
[13:56] <Mirv> Wellark: unping, wrong To:
[13:56] <brendand> thostr_, your silos are being tested
[13:58] <brendand> thostr_, 007 and 008
[14:00] <brendand> sil2100, please make sure to let people know about the trello board today
[14:00] <brendand> sil2100, and update the spreadsheet with a link
[14:06] <Saviq> robru, hey with some change that you did recently for citrain device-upgrade, I have to apt update before I can install unity8-autopilot
[14:07] <Saviq> robru, otherwise I get: http://pastebin.ubuntu.com/8159757/
[14:07] <Saviq> robru, is that expected/feature/bug?
[14:11] <sil2100> brendand: sure thing :)
[14:13] <brendand> thostr_, there is this trello board we have as well: https://trello.com/b/AE3swczu/silo-testing
[14:13] <brendand> thostr_, for more detail status on what we're doing
[14:20] <thostr_> brendand: ah, good to know. wasn't aware of this, was waiting for a ping as described by asac
[14:21] <brendand> thostr_, yes - and sorry about that not happening
[14:21] <asac`> brendand: can you try to do those pings? helps a lot keeping transparency up etc.
[14:21] <asac`> thanks
[14:21] <asac`> at least initially until folks have gotten a feel how this works and that they won't be forgotten :P
[14:22] <brendand> asac`, yes i think it's okay to do initially
[14:23] <brendand> asac`, but as with all manual processes it can be forgotten so i do feel it's a bit error prone
[14:23] <brendand> asac`, but until we find a better way
[14:24] <asac`> brendand: well, what i learned is that this is just hard to start; after peer encouraging folks for a few days it will become natural procedure
[14:24] <asac`> and wont be an issue at all
[14:24] <asac`> heh
[14:24] <asac`> anyway, yes, there can be misses, and hence i encouraged folks to ask early
[14:24] <asac`> rather than wait if they feel something isnt moving
[14:25] <brendand> asac`, yes people should be able to pull the info too
[14:25] <brendand> asac`, i feel the trello board once everyone is aware of it will serve that purpose best
[14:25] <asac`> right
[14:25] <brendand> asac`, but we can do proactive pings to landers as well
[14:26] <mterry> trainguards: can I get a silo for line 55 of the spreadsheet?  It would help reviewers to have easier testing
[14:26] <asac`> brendand: can the trello board show who is in charge of coordinating in case there are questions?
[14:26] <brendand> asac`, yeah absolutely
[14:27] <Mirv> mterry: you have not marked it as ready
[14:27] <mterry> Mirv, thanks, fixed
[14:28] <Mirv> mterry: assigning, and assigning RTM silo too
[14:29] <mterry> Mirv, ah awesome
[14:33] <sil2100> Mirv: thanks :)
[14:34] <Mirv> bfiller: ^ is because https://code.launchpad.net/~bfiller/telephony-service/rtm-14.09-sim-presence/+merge/231914 was already merged. if the PPA is completely fine like QA says it is, the only problems may arrive in the merge & clean stage (but it might be also just fine)
[14:34] <pmcgowan> sil2100, thanks for that list super helpful
[14:36] <sil2100> pmcgowan: yw! Hope it helps indeed, it might be a bit rough since it's auto-generated (to some extent) :)
[14:36] <pmcgowan> seems fine
[14:37] <bfiller> Mirv: anything I need to do to fix? looks like it's complaining about unapproved MR but I don't see it
[14:38] <Mirv> bfiller: I just published it. let's see later if there's a problem with M&C. so that MR was already "Merged" which != "Approved", that's why the complaint.
[14:38] <bfiller> Mirv: ah, ok. thanks
[14:54] <cyphermox> ^ already assigned, sorry
[14:55] <cyphermox> bah, nevermind
[14:55] <sil2100> Oh?
[14:55] <cyphermox> nah, I'm confused
[14:55] <cyphermox> I just woke up :)
[14:57] <alecu> trainguards, hi! I need to request a srccopy for the click scope into rtm, but also need to do another landing into devel+rtm. Should I do the landing on devel first and then request one srccopy, or should I ask for two separate srccopys?
[14:58] <sil2100> alecu: so, both are for unity-scope-click, right?
[14:58] <alecu> sil2100: yes
[14:58] <sil2100> alecu: if that's true, then it's enough that you request an ubuntu landing for the new thing - all previous changes will be pulled in if we do this for ubuntu-rtm
[14:59] <sil2100> alecu: so, request the new landings for ubuntu and we'll do the srccopy changes :)
[14:59] <alecu> great, I'll do it like that. thanks!
[14:59] <sil2100> And everything you had pilled up will land with it
[15:07] <Saviq> trainguards, icanhasreconfigure on silo 17 please
[15:07] <Saviq> added unity-notificaitons
[15:07] <sil2100> Saviq: yessir!
[15:09] <sil2100> Saviq: btw. you want a rtm silo for that?
[15:09] <sil2100> :)
[15:09] <Saviq> sil2100, I already have one in rtm-004
[15:09] <sil2100> Excellent
[15:09] <Saviq> sil2100, but
[15:09] <Saviq> sil2100, it has an old unity8
[15:09] <Saviq> and davmor2's looking through that now
[15:10]  * Saviq wonders if we want that still or shall we just skip the one currently in silo 4?
[15:10] <sil2100> Saviq: depends on how far davmor2 is with that
[15:11] <sil2100> Since if he's like almost done, then well, let's push this out and then prepare a new one for the new features
[15:11] <sil2100> Saviq: that's the previous ubuntu landing in 004, right?
[15:12] <Saviq> sil2100, yes
[15:12] <davmor2> sil2100, saviq I was close to finishing till the whole phone locked up
[15:15] <sil2100> Saviq: problems with reconfigure
[15:15] <Saviq> sil2100, lookin'
[15:15] <sil2100> Saviq: the last merge is wrong
[15:16] <sil2100> Missing one digit it seems :)
[15:16] <Saviq> sil2100, as usual
[15:16] <Saviq> sil2100, that's a gdoc bug
[15:16] <Saviq> and my ADHD bug
[15:16] <Saviq> compulsive something disorder
[15:16] <Saviq> sil2100, fixed
[15:16] <Saviq> sil2100, but check it out: you start editing a field, you're at the last line, empty, after all the other MPs
[15:17] <Saviq> sil2100, go backspace
[15:17] <Saviq> boom, newline *and* last digit gone
[15:17] <sil2100> hah, damn
[15:31] <cyphermox> sil2100: so I understand you guys now just sheperd things through to rtm ?
[15:32] <cyphermox> sil2100: I'm done testing the MTP silo (silo 2); this fixes the frequent crasher in errors.ubuntu.com ;)
[15:32] <sil2100> cyphermox: currently yes - once my changes are in CI Train, those will be moved to RTM with a version change - but for now it's a source copy
[15:32] <sil2100> cyphermox: that's music to my ears
[15:32] <sil2100> ;)
[15:32] <cyphermox> aye
[15:32] <cyphermox> hehe
[15:32] <cyphermox> so I don't need to touch line 36 I guess?
[15:35] <sil2100> cyphermox: no no, I'll assign that - it seems it got missed somehow :) Let me prepare all for you
[15:36] <sil2100> hmmm
[15:36] <sil2100> Actually a silo is already there, just the info seems corrupted again
[15:37] <sil2100> Ah
[15:37] <sil2100> Ok, I know why it's like that
[15:37] <sil2100> cyphermox: so, there's an RTM silo for the previous release already in CI Train
[15:38] <sil2100> cyphermox: so let's maybe do it like this - let me reassign it for your changes now, update the packages
[15:38] <sil2100> So then now we'll just sync 2 versions instead of one
[15:40]  * sil2100 copies the packages
[15:45] <cyphermox> aye
[15:46] <sil2100> cyphermox: copied, they're in the 002 rtm silo - I publish the ubuntu bits now
[15:47] <sil2100> If you could give those rtm ones a spin later on - if all is ok, set testing to DOne for that silo and QA will pick it up :)
[15:49] <kenvandine> sil2100, i have an old settings landing in silo 1 for ubuntu-rtm
[15:50] <kenvandine> sil2100, can i just change that line on the spreadsheet dropping the MP to request a package sync?
[15:50] <sil2100> kenvandine: sure thing :) Where should we sync from? Actually I'm just testing a feature where you can request syncs from selected places (like the archive or another PPA)
[15:51] <sil2100> So soon you'll be able to request that in CI Train without having to poke anyone
[15:51] <kenvandine> cool
[15:51] <kenvandine> just from utopic
[15:51] <sil2100> Ok, excellent
[15:51] <kenvandine> need me to do anything?
[15:51] <sil2100> kenvandine: no, I'll do everything needed now
[15:51] <kenvandine> thanks!
[15:52] <kenvandine> sil2100, note: the line number referenced in citrain doesn't match the spreadsheet from some reason
[15:53] <sil2100> Yeah, just noticed that o_O
[15:54] <sil2100> kenvandine: so...
[15:54] <sil2100> kenvandine: it seems your landing might not be required!
[15:55] <sil2100> kenvandine: I see silo 013 has ubuntu-system-settings in it
[15:55] <sil2100> kenvandine: since it's also a sync, then it will pull in your changes if those are in utopic
[15:55] <kenvandine> sil2100, cool
[15:56] <sil2100> kenvandine: I'll free up that silo
[15:57] <sil2100> cyphermox: is this merge approved by someone? https://code.launchpad.net/~mathieu-tl/mtp/greeter-crasher-fix/+merge/232317 ?
[16:02] <thostr_> sil2100: the landing of the network indicator crash bug in line 45, shouldn't that automatically synced all earlier features that haven't been in rtm?
[16:10] <davmor2> Saviq: unity8 on silo rtm004 is now passed I think sil2100 is publishing it now :)
[16:18] <Saviq> davmor2, awesomes, sil2100, we could use a srccopy from silo 17 then
[16:18] <Saviq> sil2100, we could hitch a rid with tedg's silo 14 if no one is looking at that yet
[16:18] <Saviq> *ride
[16:20] <davmor2> Saviq: I think 14 got failed due to the setting not being able to be raised by indicators
[16:21] <Saviq> davmor2, mhm
[16:22] <davmor2> Saviq: I think that is an old issue that victor might not of been aware of, so I'll catch up with him and double check
[16:23] <tedg> davmor2, Cool, thanks. I'm pretty certain it's not related to that silo, it can't really effect menu behavior.
[16:23] <Saviq> davmor2, it could've been bug #1362017
[16:23] <Saviq> davmor2, although Victor said he had the dash focused
[16:24] <Saviq> oh Ugo just filed bug #1362235
[16:28] <brendand> thostr_, finished testing the mediascanner silo
[16:39] <brendand> sil2100, oh - please mention the trello board in the landing email!
[16:39] <brendand> sil2100, please :)
[16:45] <balloons> so ogra_ re: community testing, do you think it's useful to switch to the rtm branch from devel-proposed on mako?
[16:45] <sil2100> brendand: this time for sure!
[16:45] <sil2100> (I hope!)
[16:45] <ogra_> balloons, no we will all do rtm testing anyway, but we will lack utopic testing
[16:45] <ogra_> balloons, thus my idea to ask the community for some help with that
[16:45] <balloons> ogra_, ahh, so that makes more sense :-)
[17:15] <Saviq> trainguards, silo 17 is ACK for release, can I have a corresponding silo for rtm please?
[17:15] <sil2100> Saviq: o/
[17:15] <sil2100> robru: handling that ^
[17:16] <robru> Saviq: one sec
[17:16] <sil2100> robru: thanks :)
[17:17] <robru> sil2100: you're welcome!
[17:18] <robru> sil2100: so i think my package-copy.sh script is better than copy-package... with copy-package you have to specify all kinds of ppa and package names on the commandline, it makes a long command to type. with mine you just type silo numbers and it copies the whole silo for you quickly ;-)
[17:18] <sil2100> hah ;)
[17:21] <robru> queuebot: done
[17:21] <robru> Saviq: uploaded unity8 to rtm-1
[17:22] <Saviq> robru, thank you
[17:22] <robru> Saviq: you're welcome!
[17:23] <robru> sil2100: something has gone horribly wrong in utopic-10, it's been cleaning for like 2 days
[17:26] <sil2100> robru: uh?
[17:26] <sil2100> Looking
[17:26] <sil2100> Grrrr
[17:26] <sil2100> Yeah, so I remember wgrant mentioning about this once
[17:27] <sil2100> Let me try finding it in the logs...
[17:27] <robru> sil2100: yeah I dunno... the ppa says it's empty but the citrain script is totally stuck on that
[17:28] <sil2100> robru: it's not entirely empty, I mean, the insides still say it's not empty sadly, and I wemember William mentioning somehting about that
[17:30] <sil2100> robru: since it's still listing something here http://ppa.launchpad.net/ci-train-ppa-service/landing-010/ubuntu/dists/utopic/main/binary-armhf/
[17:31] <robru> sil2100: I just requested another delete from the lp interface
[17:31] <sil2100> robru: that might help, wgrant mentioned it might have been a race with build completion and deletion
[17:31] <sil2100> And that a second delete should pick those up
[17:33] <davmor2> thostr_: I'm just starting silo008 on rtm
[17:33] <thostr_> davmor2: thanks
[17:34] <brendand> thostr_, i see you put a note about testing silo 008 and 007 together?
[17:34] <thostr_> brendand: yes, that would have eased up testing a little bit...
[17:34] <brendand> thostr_, but they should be independent
[17:35] <brendand> thostr_, thus 'silo'
[17:35] <thostr_> yeah
[17:35] <brendand> thostr_, can they be landed independently?
[17:35] <brendand> thostr_, i.e. testing them together is optional
[17:35] <charles> thostr_, thanks
[17:36] <thostr_> since you already tested silo 7 successfully that answers the question to yes :)
[17:36] <brendand> thostr_, that's why i asked :)
[17:36] <thostr_> anyway, either way is fine
[17:37] <thostr_> brendand: just to be sure: when we do a srccpy from utopic to rtm then we basically include all changes made in between, right?
[17:37] <davmor2> brendand: I can carry on then?
[17:37] <brendand> thostr_, sil2100 or robru can answer that
[17:38] <brendand> thostr_, it looks like 007 has a problem though
[17:38] <thostr_> which problem?
[17:39] <davmor2> thostr_: not building by the look of the silo page
[17:39] <davmor2> dashboard is the word I was after
[17:39] <thostr_> davmor2: was building earlier when we tested it...
[17:40] <davmor2> thostr_: Can't publish: Some projects (mediascanner2, unity-scope-mediascanner) that were in the silo configuration list were not built
[17:41] <thostr_> so, where do then the packages from ppa come from?
[17:41] <davmor2> robru: ^
[17:41] <robru> thostr_: what do you mean "changes made in between"? when I assign an RTM silo I do a verbatim copy from the utopic silo. it doesn't gain any changes made anywhere else.
[17:41] <davmor2> thostr_: all of that side is way out of my league :)
[17:42] <robru> sil2100: you know what we need? the stupid build job to realize when it's NOP'd itself and stop calling that a success.
[17:42] <thostr_> robru: the missing rtm changes mail  included a change to indicator-network. but tonight indicator-network was srccpied, see line 44 in ci sheet
[17:42] <davmor2> robru: I think the issue here is the packages built for qa sign off, that happened but now it can't be published
[17:43] <thostr_> robru: therefore I thought that all the changes made between rtm branching and that silo request are automatically  included, no?
[17:44] <robru> thostr_: what about line 44? it just says it's Landed.
[17:44] <robru> thostr_: also I have no idea what is a "missing rtm changes mail"
[17:44] <thostr_> robru: but target says rtm
[17:45] <robru> thostr_: I literally don't have the slightest clue what you're talking about
[17:45] <thostr_> robru: that was the mail sent by sil2100 "Landing team: convenience list of ubuntu landings not yet landed in ubuntu-rtm"
[17:46] <thostr_> robru: so, you're saying that line 44 does actually not mean that this change is landed in rtm?
[17:46] <sil2100> thostr_: let me make sure it did
[17:46] <sil2100> Maybe it landed in the archive, but it wasn't in an image yet
[17:46] <robru> thostr_: I'm not saying that? how do you read that from what I said?
[17:47] <robru> thostr_: line 44 claims indicator-network=0.5.1+14.10.20140826-0ubuntu1 was landed and https://launchpad.net/ubuntu-rtm/+source/indicator-network agrees with this
[17:47] <sil2100> thostr_: as mentioned in the e-mail, there might be some inconsistencies here and there as it was automated in generation, and the snapshot was made from the last ubuntu-rtm image
[17:47] <robru> thostr_: sil's mail says a different version
[17:47] <davmor2> tvoss: silo 011 on rtm have you tested it, and is it good to go?  I'm asking as you must not of set the spreadsheet tested part to true as there is no QA-signoff on it yet
[17:48] <thostr_> robru: sil2100: ok, then it might be a inconsitency
[17:49] <thostr_> sil2100: I just wanted to make sure that if we now srccpy things to RTM that all prior changes that means changes between RTM branches and the MP the silo was requested are actually included
[17:50] <sil2100> thostr_: yes, anything that you request an srccopy for now will include everything that it had in ubuntu already
[17:50] <thostr_> sil2100: ok, that means the change listed in your mail should be resolved with the latest indicator landing, so we're good
[17:50] <sil2100> thostr_: so for instance, if by some magical way there were 2 releases of package foo to ubuntu and then you request a sync for the second landing to ubuntu-rtm, all 2 changes will land in ubuntu-rtm
[17:50] <sil2100> thostr_: excellent :)
[17:55] <thostr_> robru: thanks for starting silo 3 build... I'm just wondering why I don't see the build log for the build I triggered 20 minutes ago...
[17:55] <thostr_> robru: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-003-1-build/4/console
[17:55] <alecu> trainguards, can I ask for a silo for landing 58?
[17:56] <alecu> I mean, for row 58
[17:56] <robru> thostr_: because you started it too soon, this is a known bug in citrain when it comes to manual source uploads like we are doing in RTM. it can't get the list of packages to watch, so it finds an empty list and reports "yep, this empty list built successfully!". I saw you did that so I had to recon the silo, wait for the PPA builds to finish, then re-run
[17:56] <robru> the build
[17:57] <thostr_> robru: ah, now this is also known to me
[17:57] <robru> thostr_: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-003-1-build/4/console here is the build you triggered. "Nothing happened... Success!"
[17:58] <thostr_> robru: stupid question part II: and where did it get the package from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-003
[17:59] <thostr_> robru: that package seems older then you when you triggered the build
[18:00] <robru> thostr_: I lovingly hand-plucked your packages from the utopic silo and painstakingly copied them into the PPA one by one. apologies if your packages are a little bit sweaty, it's hot down here in the salt mines
[18:01] <robru> thostr_: the build job only builds MPs, these aren't MPs, they're source copies. so you copy them in first, wait for them to build, and then the build job is just there to acknowledge that they've been built.
[18:01] <robru> or rather "*I* copy them in first..."
[18:02] <thostr_> ah, that explains
[18:04] <robru> thostr_: http://i.ytimg.com/vi/05agcR87bKo/hqdefault.jpg somebody took a picture of me transporting your package from the utopic silo to the rtm silo.
[18:04] <robru> ;-)
[18:04] <thostr_> now I'm feeling bad...
[18:05] <robru> thostr_: well, it's not  your fault...
[18:08] <balloons> can we get this into rtm as well? https://launchpad.net/ubuntu/utopic/+source/mediascanner2/0.104+14.10.20140825-0ubuntu1
[18:10] <robru> balloons: can you make a spreadsheet request for that? I'm getting to them slowly
[18:14] <balloons> robru, sure, not sure I know the proper spot; I don't have perms anymore for the CI Train sheet
[18:17] <robru> balloons: you don't have perms anymore? I'm not aware of any policy for revoking those....
[18:18] <balloons> to be fair, it's been awhile since I've had to request something
[18:19] <balloons> ty :-)
[18:19] <robru> balloons: ok, well I added you. just fill out the next available row and just leave the MPs blank, say the package name in the sources column, and in the comments just say "please sync from utopic archive" or something
[18:21] <balloons> done, ty robru
[18:22] <robru> balloons: you're welcome
[18:26] <tedg> Where does autopilot put its results?
[18:27] <ChrisGagnon> tedg: to stdout unless you specify -f
[18:27] <robru> balloons: oops, just noticed mediascanner2 was already in an rtm silo. published that one for you ;-)
[18:28] <tedg> ChrisGagnon, Oh, I thought there were more logs than that. Like attachments for each run. Is that something that's just done on the server?
[18:28] <balloons> silo-007 looks like it needs the new mediascanner package as well ;-)
[18:28] <balloons> robru, I just noticed the same, but ^^
[18:28] <ChrisGagnon> tedg: if you use subunit it will attach results, when the tests add attachments
[18:29] <balloons> +1 for subunit..
[18:29] <balloons> look at the artifacts
[18:29] <tedg> How do I use subunit?
[18:29] <robru> balloons: right, so once it hits rtm archive silo 7 should be fine
[18:29] <robru> balloons: no wait, what? silo 7 *has* the new mediascanner already. I confirmed the version numbers
[18:29] <ChrisGagnon> autopilot3 run -f subunit -o /tmp/mytest.subunit
[18:29] <robru> and that's the one I just published
[18:29] <balloons> robru, ok, I trust you then
[18:31] <balloons> there's also thomi's tool tedg .. https://launchpad.net/trv
[18:31] <ChrisGagnon> tedg: autopilot3 run --help will show you all the options.
[18:31] <tedg> Ah, okay. Thanks guys. That's what I need. Should be default :-)
[18:40] <robru> bfiller: conflicts with camera-app in silo 10
[18:40] <bfiller> robru: checking
[18:42] <bfiller> robru: I'll manage the conflicts if any occur and do rebuilds, etc..
[18:43] <ToyKeeper> robru: FWIW, I synced the current rtm silos to trello.  I'll probably do that each morning, and I think davmor2 is also doing that when he starts his day.
[18:43] <robru> ToyKeeper: cool thx
[18:43] <robru> bfiller: ok you got 18
[18:43] <bfiller> robru: thanks
[18:44] <robru> bfiller: you're welcome
[18:44] <ToyKeeper> Currently rtm 008 in progress, 001 claimed, 003/004/005/015 waiting.
[18:44] <ToyKeeper> ... and a format change as of just now, to disambiguate silos.
[18:44] <robru> ralsina: tvoss alecu boiko: only 2 silos available. ping me if you're actually around to test a silo i can potentially give you right now
[18:45] <ralsina> robru: mine I can test quick
[18:45] <robru> ralsina: sweet
[18:46] <robru> ralsina: ok you got 19
[18:46] <ralsina> robru: on it!
[18:48] <davmor2> ToyKeeper: no we, brendand and I are just updating as we go
[18:48] <robru> ralsina: thansk
[18:49] <brendand> ToyKeeper, no silo should ever be on the board twice, so the need for disambiguation isn't really there
[18:49] <brendand> ToyKeeper, it doesn't hurt to have the cards a bit more verbose though
[18:49] <davmor2> brendand: silo 008 got refilled after I finished testing it
[18:49] <brendand> ToyKeeper, but i like having the PPA url there because that's primarily what you need to get testing
[18:50] <ToyKeeper> brendand: The dashboard and trello have no automatic sync, so there are a lot of situations where the silo contents can change without trello noticing...  and then we have info about the wrong landing.  I'm planning to always include more info, to help avoid that.
[18:50] <davmor2> brendand: so you had 2 silo 008's on the board
[18:50] <brendand> davmor2, yeah - one in the Passed column though :)
[18:51] <brendand> ToyKeeper, davmor2 - anyway the new format is fine
[18:51] <ToyKeeper> brendand: Like, right now rtm/landing-014 is marked as failed, and I can't tell if it's the same packages that are currently in 014 or not.
[18:51] <brendand> ToyKeeper, yeah it's good to have that extra bit of certainty
[18:51] <brendand> just to cross check it
[18:51] <davmor2> brendand: but was that the one that was there now and I just forgot to mark it passed or was that another app in that silo and it was 004 not 008
[18:52] <robru> I'm glad to see such a vibrant software ecosystem growing up around ci train!
[18:52]  * robru sheds a single tear, so proud. so proud.
[18:52] <davmor2> brendand: before we just put the url for the silo so that can be anything ;)
[18:54] <brendand> robru, speaking of which - what do i need to use to hook into the spreadsheet? is python fine?
[18:54] <davmor2> brendand: ToyKeeper is going to take on silo001 so I can take the uitk one in the morning and free you up for the smaller ones or visa versa
[18:54] <robru> brendand: don't you touch my spreadsheet boi
[18:55] <robru> brendand: just kidding, what are you doing?
[18:55]  * davmor2 prods robru spreadsheet and runs
[18:55] <robru> I'll cut you!
[18:55] <brendand> robru, i'll cut you back
[18:56] <davmor2> robru: oh get you waving you're piece of paper....ouch paper cut.....okay you win
[18:56] <robru> davmor2: http://media.giphy.com/media/gmQNYr9nnbXxu/giphy.gif
[18:56] <brendand> robru, i want to automatically create cards on our board when a silo is set to Needs QA sign-off
[18:56] <robru> brendand: oh yeah, you can do that in python.
[18:56] <ToyKeeper> Saviq: I see 14 changes summarized on the unity8 silo's description (row 47), which is longer than the actual test plan.  Any chance of adding more info about what changed and how to test it?
[18:56] <brendand> robru, and the inverse, to set it to Granted when it goes in the Pass column
[18:57] <robru> brendand: yeah no, you can't poke data into the spreadsheet
[18:57] <robru> brendand: http://bazaar.launchpad.net/+branch/queuebot/view/head:/plugins/landing.py here's how we poll it in queuebot with python, it just gets a read-only CSV, hope that helps you
[18:59] <davmor2> robru: https://www.youtube.com/watch?v=kAGysJe_js0
[18:59] <alecu> robru: any silos left for me?
[19:05] <robru> davmor2: http://youtu.be/9Fvpyo2WuVY?t=2m59s
[19:06] <robru> alecu: sure
[19:06] <davmor2> robru: https://www.youtube.com/watch?v=01NHcTM5IA4 :)
[19:07] <robru> alecu: you got silo 6
[19:07] <alecu> yay
[19:08] <robru> woops, screwed up the timecode
[19:09] <robru> davmor2: http://youtu.be/9Fvpyo2WuVY?t=1m54s
[19:18] <bzoltan> is anybody from QA would be available for checking the UITK in silo5?
[19:19] <robru> bzoltan: you'd be looking for ToyKeeper or brendand I guess
[19:19] <robru> lunchtime! bbl
[19:19] <davmor2> bzoltan: that'll probably be me in the morning dude, ToyKeeper is hitting the unity8 silo
[19:20] <bzoltan> davmor2: thank you :) and good night for now
[19:20] <davmor2> bzoltan: indeed same to you dude :)
[19:21] <davmor2> bzoltan: You'll be able to check on the status here https://trello.com/b/AE3swczu/silo-testing
[19:21] <davmor2> bzoltan: https://trello.com/b/AE3swczu/silo-testing-for-questions-ping-eu-jibel-us-jfunk-nz-thomi-or-ubuntu-qa-on-ubuntu-ci-eng even
[19:21] <asac`> ok, iuf zoltan is out, maybe focus sign off on those that are still awake in that list?
[19:22] <asac`> think the other three would be cool
[19:22] <jfunk> ToyKeeper: it might make sense to do the short ones first
[19:23] <jfunk> since U8 is a long haul testsuite
[19:23] <brendand> ToyKeeper, perhaps tedg's indicator-transfer one
[19:24] <davmor2> jfunk: that was kinda why we wanted it out of the way.  with unity8 and uitk both being big it would mean mean and brendand would be out of action for most of the day
[19:24] <davmor2> s/mean mean/ mean me
[19:24] <brendand> ToyKeeper, clear that out first and then sort out the unity8 one
[19:24] <jfunk> davmor2: ack, but Selene starts late and can pick those up later on, during peak hours at the start of her day she should focus on the smaller ones
[19:25] <brendand> ToyKeeper, Saviq probably won't notice the difference :)
[19:25] <asac`> bzoltan: Q: did you test your silo against rtm?
[19:25] <bzoltan> asac`: yes
[19:25] <asac`> bzoltan: ok, thanks for confirming
[19:26] <bzoltan> asac`: strange, but the results were even better than against the 205-207 ubuntu images
[19:27] <pmcgowan> sil2100, you said in landing mail that all landings go through QA but in fact the traincon rules apply so only as needed
[19:28] <ToyKeeper> I'm perfectly okay with focusing on smaller silos.
[19:28] <ToyKeeper> Besides, I think the unity8 silo may have already failed.
[19:28] <davmor2> sil2100: so it looks like some of the fixes that landed in the unity8 silo from early are to blame for the bugs being fixed ;)  in the default image they are still there,  I assume that silo will land in the morning image thought right?
[19:29] <asac`> bzoltan: thats good news :)
[19:30] <asac`> bzoltan: means stabile branch is stabilizing more than we knew :)
[19:31] <asac`> davmor2: not sure i can parse your question
[19:31] <asac`> we want everything landed tonight that can be landed
[19:31] <asac`> at best i wake up and all the silos are empty or rejected :P
[19:31] <asac`> we want to bake a great image tomorrow for our milestone
[19:32] <kgunn> robru: yeah, i'm aware of row 55 conflict with the other 2...all of which i got my eye on
[19:32] <kgunn> but needing a silo to get a jump on it
[19:32]  * tedg counts and realizes kgunn has 3 eyes
[19:33] <davmor2> asac`: but it uitk and unity8 are still in place tomorrow they both take around 4 hours to test fully,  so if that is the case then not much would land tomorrow.   If ToyKeeper takes out the unity8 silo it means I am free to take on the uitk silo and brendand can take on the smaller ones similar to today or visa versa
[19:34] <asac`> davmor2: rigth
[19:34] <sil2100> pmcgowan: right! Yeah, true, this might have been not clarified there, the official announcement is right here
[19:34] <asac`> start with the light ones
[19:34] <asac`> davmor2: and continue with big ones after
[19:34] <asac`> davmor2: also check if the owner are online and take that that has someone committed to stay around while testing first
[19:35] <davmor2> asac`: indeed and that is what we settled on
[19:35] <ToyKeeper> davmor2: Unity8 is really not looking good so far, but I'm not sure if it's the silo or the base image yet.
[19:36] <ToyKeeper> In any case, I'm happy with focusing on smaller silos and/or silos with someone around to answer questions.
[19:36] <asac`> davmor2: yeah, key is checking with him that he is on and that he will stay on :)
[19:36] <plars> robru: sil2100: would it still be possible to get a silo for that MP I mentioned earlier in the call? It's in review still at this point, but mterry already took care of the comments I believe and I would like to get the process started.
[19:36] <asac`> if you need a priority decision :)
[19:37] <plars> robru: sil2100: it's #43
[19:38] <ralsina> robru: silo 19 tested, good to publish and srccopy into a rtm silo when you can
[19:51] <robru> kgunn: ok you got 2
[19:51] <kgunn> whoop!
[19:53] <robru> plars: I dunno dude there's like 3 other silos with unity8 in it already. the more of those we have going the harder it is to juggle (whenever a package gets published, any other silos containing that package need to get rebuilt, it's a tight dance to coordinate). can it wait a bit?
[19:53] <robru> plars: or maybe merge your MP into an existing unity8 silo, if you can coordinate that with somebody
[19:54] <plars> robru: I'm talking to Saviq and mterry about it. We can't wait too long but we have a little time. When ogra_ finishes up the stuff he's working on though, our autopilot tests will break without this if it doesn't land before the adbd as phablet user stuff
[19:55] <robru> ugh
[19:55] <plars> robru: he's well aware of that though
[19:55] <rsalveti> robru: hey, can we trigger a new image now?
[19:56] <rsalveti> a bunch of things landed
[19:56] <plars> robru: so let me continue to work through Saviq and mterry, maybe they have some recommendations for combining these so it doesn't create chaos
[19:56] <robru> rsalveti: go for it
[19:56] <rsalveti> robru: great
[19:56] <robru> plars: thanks
[19:59] <pmcgowan> thanks sil2100
[20:00] <ToyKeeper> robru: Do we have a log or list of what landed in rtm?  I found a regression since yesterday and don't know what caused it.
[20:01] <robru> ToyKeeper: ask ogra? he's got the script that reports what landed in the images.
[20:01] <robru> ToyKeeper: although I don't actually seean RTM version of that
[20:02] <ToyKeeper> I haven't seen anything like that either.  :(
[20:03] <robru> ToyKeeper: so... no. there's no changelog for what lands in rtm
[20:05] <imgbot> [20:05] <ToyKeeper> robru: That certainly makes regressions harder to track down...
[20:05] <sil2100> ToyKeeper, robru: yeah, currently there's no such thing :|
[20:06] <ToyKeeper> We might want to do something about taht.
[20:06] <ToyKeeper> that, even.
[20:06] <sil2100> ToyKeeper: ogra_ has more pending work to do - I could also modify my scripts to not depend on ogra's anymore, but I would also need time for that ;)
[20:06] <sil2100> While we're all busy busy with everything
[20:06] <ToyKeeper> Definitely.  So much to do, so little time...
[20:08] <balloons> sil2100, will rtm see a new image soon?
[20:08] <cyphermox> sil2100: can we land mtp in rtm now?
[20:10] <sil2100> balloons: depends if ogra_ kicked a new one - but there's a cronjob that does it once a day anyway
[20:10] <rsalveti> do you guys need a new rtm soon?
[20:10] <rsalveti> I guess I can trigger one
[20:10] <sil2100> cyphermox: did you test the packages in the ubuntu-rtm silo? Is this an bugfix-only release?
[20:11] <mterry> robru, plars: regarding unity8.  Looks like we can add the MP plars wants to my silo easily enough.  Other unity8 silos aren't ready yet
[20:11] <balloons> sil2100, ohh excellent. what time does it happen daily? I need a new rtm so I can push new apps to the store without breaking rtm
[20:11] <balloons> it's that rock and hard place between -proposed needing fixes vs things as they are in rtm
[20:11] <robru> mterry: can you update the spreadsheet and reconfig it? thanks
[20:12] <mterry> robru, sure can
[20:13] <robru> mterry: thanks!
[20:16] <ToyKeeper> Well, whatever changed, it worked in image 8 and broke in image 9.
[20:16] <mterry> robru, if I just delete a row in the spreadsheet, is that a problem?
[20:16] <robru> mterry: nope, that's how we roll ;-)
[20:19] <robru> ralsina: https://launchpadlibrarian.net/183311115/buildlog_ubuntu-rtm-14.09-armhf.ubuntu-push_0.63%2B14.10.20140827-0ubuntu1_FAILEDTOBUILD.txt.gz does this make any sense to you? your ubuntu-push landing from utopic failed to build after I put it in an rtm silo
[20:19] <ralsina> robru: not really! looking...
[20:19] <robru> ralsina: possible causes are: transient infrastructure error, or some necessary dependency is missing in rtm (although the failure is only on armhf, so that option is less likely).
[20:20] <ralsina> robru: looks like a tiny timeout
[20:20] <ralsina> robru: can you rebuild once?
[20:20] <robru> ralsina: yeah
[20:20] <ralsina> a test has to be done in 1.15 seconds and it took 1.151955 seconds
[20:21] <ToyKeeper> tedg, charles, rsalveti, tiagosh, pete-woods, Satoris: Anyone awake?  Deciding which silo to start next.
[20:22] <robru> ralsina: ah ok, could be the build server was overloaded or something. we'll solve it by triggering more builds!
[20:22] <ToyKeeper> At a guess, probably rtm-004, based purely on who is online now.
[20:22]  * tedg is awake, though curious what trouble admitting that gets him into :-)
[20:23]  * charles blames silo 002's merge conflict on tedg for being awake
[20:23] <tedg> ToyKeeper, What's up? Satoris and pete-woods are probably asleep.
[20:23] <ToyKeeper> tedg: Looks like I'll take rtm/landing-004 next, then (indicator-transfer).
[20:23]  * tedg goes to bed
[20:23] <charles> indicator-transfer would be a good one
[20:23] <ralsina> robru: trigering enough more builds we'll either fix it or break it again :-)
[20:24] <ToyKeeper> charles, tedg: Any testing at all done for rtm-004 on an RTM image, or was it just utopic?
[20:25] <charles> ToyKeeper, utopic image 210
[20:25] <sil2100> robru: yay! I think the preprod sync feature works \o/
[20:25] <ToyKeeper> charles, tedg: Okay.  I'll see what I can do; future RTM landings should be tested on an RTM image though.
[20:25] <sil2100> Too late for me to switch everything, but yeah, tomorrow might be a good day
[20:25] <charles> ToyKeeper, ack
[20:25] <sil2100> Less work for us (probably)
[20:26] <ToyKeeper> charles, tedg: Got a working URL for the test plan?  The URL in the spreadsheet is 404.
[20:26] <sil2100> robru: good luck in the meantime o/
[20:26] <ToyKeeper> Ah, found it.
[20:27] <robru> bfiller: you got silo 8
[20:28] <ToyKeeper> charles, tedg: I may have more questions while looking at the attached bugs, especially if the bugs aren't covered in the test plan and/or have no tests otherwise.
[20:29] <charles> ToyKeeper, unfortunately there's not a single concise answer for this, however
[20:29] <charles> ToyKeeper, the download-an-image test case at http://bazaar.launchpad.net/~indicator-applet-developers/indicator-transfer/trunk.14.10/view/head:/tests/manual handles several of these bugs
[20:29] <bfiller> thanks
[20:31] <kenvandine> mterry, you have system-settings in silo 9, how close is that to being ready to land?
[20:31] <charles> ToyKeeper, not handled there is the case of app updates and MMS messages should not appear in the transfer indicator, the steps to confirm that are exactly what you'd expect, though I'll make sure to add them to that list of tests for posterity
[20:31] <kenvandine> mterry, i have a bunch of branches i need to land :)
[20:31] <mterry> kenvandine, great question.  I need the two unity8 branches reviewed, but after that it can land
[20:32] <mterry> kenvandine, if you want to go now, go
[20:32] <mterry> kenvandine, I'll gladly rebase
[20:32] <ToyKeeper> charles: Thanks.  Just trying to make sure test plans are fairly complete to avoid regressions.
[20:32] <kenvandine> mterry, cool, thx
[20:33] <ToyKeeper> (though I can't say I've ever heard of a regression or any severe bugs for the transfer indicator)
[20:34] <charles> ToyKeeper, the other issue to be aware of is that there's currently a severe regression for the transfer indicator, bug #1350308
[20:34] <ToyKeeper> Heh, I stand corrected.  ;P
[20:34] <charles> ToyKeeper, until the rendering in unity8 gets fixed, even with the MP you're looking at now, the title, progressbar, and download status text are all missing
[20:34] <ogra_> ToyKeeper, http://paste.ubuntu.com/8162569/ save that as "compare-manifests" ... it will spit out the changes for you, but you need the rootfs versions for this ... i.e.: ./compare-manifests  20140827 20140827.1 would be for the diff between the last two rtm images
[20:34] <charles> ToyKeeper, but hey, the icon is correct now
[20:35] <ogra_> ToyKeeper, i'll get us automated changelogs tomorrw
[20:35] <ToyKeeper> ogra_: Thanks!
[20:41] <mterry> kenvandine, didn't you just land some USS silo today already?
[20:42] <kenvandine> last night
[20:42] <kenvandine> late
[20:44] <dbarth> o/
[20:46] <gatox> fginther, hi, do you know why approved branches are not landing? https://code.launchpad.net/~diegosarmentero/pay-ui/last-payment/+merge/232284
[20:47] <gatox> fginther, too recent or something wrong?
[20:47] <fginther> gatox, looking
[20:48] <fginther> gatox, it's building now
[20:48] <gatox> fginther, ack, thanks
[20:49] <pmcgowan> kenvandine, I turned pin on, hit cancel, then when I turn it off it still took me to the set pin popup
[20:50] <kenvandine> oh... cancel should have left it unchecked...
[20:52] <pmcgowan> kenvandine, what happens if I actually set a PIN, can I unset it?
[20:52] <kenvandine> you can unlock it
[20:52] <kenvandine> or change it
[20:52] <kenvandine> you can't add a PIN
[20:52] <kenvandine> only lock/unlock or change an existing PIN
[20:53] <pmcgowan> kenvandine, right and how to know what it is?
[20:53] <kenvandine> ha
[20:53] <kenvandine> in the US... googling :)
[20:53] <kenvandine> ATT is 1111
[20:54] <kenvandine> by default
[20:54] <pmcgowan> aha!
[20:54] <kenvandine> most people that don't know it... won't ever try this
[20:54] <kenvandine> but in europe it's big
[20:54] <pmcgowan> kenvandine, where is UI to change it
[20:54] <kenvandine> once it's locked
[20:54] <kenvandine> you see a button to change it
[20:55] <pmcgowan> kenvandine, I have to enable lock to change it?
[20:55] <kenvandine> yes... per the design
[20:55] <pmcgowan> uh oh 2 attemts left
[20:55] <pmcgowan> not 1111
[20:56] <kenvandine> whoops
[20:56] <sergiusens> adb reboot recovery
[20:56] <kenvandine> it was for me :)
[20:56] <ToyKeeper> There, log tail plus grep should help QA avoid ever missing a silo.  At least for now, until a bot does the work.
[20:56] <sergiusens> mount /dev/mmcblk0p6 somewhere
[20:56] <sergiusens> and mangle with /etc/shadow
[21:00] <pmcgowan> kenvandine, doooh, wrong phone it has a tmobile sim in it
[21:00] <kenvandine> i never figured out the t-mobile one
[21:01] <pmcgowan> 1234 says the internet
[21:01]  * pmcgowan uses his second try
[21:02] <pmcgowan> success
[21:05] <ToyKeeper> kenvandine: T-Mobile directly or via Straight Talk?  I've found that the AT&T APN settings work for T-Mobile if it's using Straight Talk.
[21:06] <kenvandine> t-mobile directly
[21:06] <kenvandine> it might be 1234... never tried that one :)
[21:06] <kenvandine> didn't want to hose my personal SIM :)
[21:07] <pmcgowan> kenvandine, was for me
[21:07] <pmcgowan> kenvandine, so I can lock, and change pin
[21:07] <pmcgowan> kenvandine, only issue I had was the uncheck
[21:08] <pmcgowan> kenvandine, any time you uncheck it it asks for pin
[21:08] <kenvandine> pmcgowan, fixing
[21:08] <kenvandine> just when you cancelled..
[21:09] <kenvandine> http://paste.ubuntu.com/8162831/
[21:09] <kenvandine> pmcgowan, grab that and push it to /usr/share/ubuntu/settings/system/qml-plugins/security-privacy/SimPin.qml
[21:09] <kenvandine> that should fix the cancel thing
[21:11] <kenvandine> http://paste.ubuntu.com/8162848/
[21:11] <kenvandine> pmcgowan, even better...  :)
[21:12] <ralsina> robru: can't get around to test ubuntu-push against rtm image but I am confident it's ok anyway
[21:12] <pmcgowan> kenvandine, oh man
[21:13] <pmcgowan> yeah first one not
[21:14] <pmcgowan> kenvandine, thats worse
[21:14] <kenvandine> ?
[21:14] <pmcgowan> now I cant uncheck at all, and still get the prompt
[21:14] <kenvandine> wait... did it actually locl?
[21:14] <kenvandine> lock?
[21:15] <pmcgowan> how would I know
[21:15] <pmcgowan> so you fixed the issue if I cancel, it disables it
[21:15] <kenvandine> so you quite settings
[21:15] <kenvandine> and went back in
[21:15] <kenvandine> right
[21:15] <pmcgowan> but now if its enabled and I want to uncheck it, does that require a PIN?
[21:15] <kenvandine> yes
[21:16] <pmcgowan> maybe I misunderstand the flow
[21:16] <pmcgowan> ok then fixed
[21:16] <kenvandine> you have to enter the PIN to unlock it
[21:16] <pmcgowan> kenvandine, vg then
[21:28] <ToyKeeper> Having some trouble finding files I can download which go slowly enough to see them in progress...
[21:29] <ToyKeeper> Mostly because the context menu for links doesn't include a "save link as..." function.
[21:30] <asac`> ToyKeeper: you can try downloading media samples
[21:30] <asac`> ToyKeeper: http://samplemedia.linaro.org/H264/
[21:30] <asac`> or anywhere on that server :)
[21:31] <asac`> some are a few megs, others hundreds, others GBs :)
[21:44] <ToyKeeper> asac`: Thanks.  It seems the UTouch browser lacks a function to actually download those though.  :(   (which is the issue I've been running into)
[21:45] <asac`> ToyKeeper: well, guess you can just upload some garbage .txt file or so to people.canonical.com etc.
[21:45] <ToyKeeper> Er, a function to save it anyway.
[21:45] <asac`> i dont know what the browser can save
[21:45] <asac`> knowing that will help finding or instrumenting test cases
[21:46] <ToyKeeper> asac`: I already have a local server full of useful files...  I just can't get the browser to download and save them unless it's already loaded into a page, in which case it's kind of already downloaded and the rest happens in a split second.
[21:47] <asac`> yeah no idea
[21:50] <imgbot> [21:50] <imgbot> [21:51] <alecu> ya
[21:51] <alecu> yay
[21:54] <alecu> that was quick (!)
[21:54] <alecu> trainguards: I just clicked on "build" for ubuntu-rtm/landing-008. But is that really needed when I asked for a srccopy?
[21:55] <robru> alecu: sure isn't!
[21:55] <alecu> robru: did I break something?
[21:55] <robru> alecu: no, sorry for the snark, it's not your fault
[21:56] <robru> alecu: the bot pings weren't designed with this crazy new RTM world in mind
[21:56] <robru> alecu: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-008-1-build/4/console this is what you did: precisely nothing.
[21:56] <robru> the fact that the status says 'Packages built' is a bug.
[21:56] <alecu> ah, great then. I'll stop trying to build when asking for srccopies, then :P
[21:57] <robru> alecu: source copies are done by me, by hand. I did it, and it's building in the PPA, you have to wait for that to finish before doing the jenkins build job
[21:57] <alecu> ack
[21:58] <robru> alecu: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-008/+packages you can watch here if you want to see it build
[21:58]  * alecu looks
[22:01] <robru> sergiusens: why does the binary package depend on dosfstools? https://ci-train.ubuntu.com/job/ubuntu-landing-012-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ciborium_0.2.11+14.10.20140827.2-0ubuntu1.diff I sort of get the build-depends on it...
[22:02] <robru> sergiusens: like, you want to ship dosfstools on our phone. really?
[22:02] <sergiusens> robru: yes I do
[22:02] <sergiusens> robru: we have a feature to format sdcards
[22:03] <robru> oh is that what that's for? grumble
[22:03] <sergiusens> robru: and udisks2 requires it; I thought I'd just add it myself as I need it
[22:03] <robru> sergiusens: oh so it was already being pulled in anyway?
[22:04] <sergiusens> robru: nope, it's not; it would be a newcomer
[22:04] <cyphermox> robru: could you look at line 24, whether it's still conflicting with something? it's definitely not conflicting with line 13, which is a different package entirely
[22:05] <robru> infinity: around? need a core dev ack on https://ci-train.ubuntu.com/job/ubuntu-landing-012-2-publish/19/
[22:05] <sergiusens> robru: just in case, rsalveti is also looking at the packaging ack
[22:05]  * rsalveti is looking at that
[22:05] <robru> rsalveti: thanks
[22:05] <rsalveti> I can publish when I'm happy with it :-)
[22:05] <robru> cyphermox: it conflicts with silo rtm 13.
[22:06] <cyphermox> argh
[22:06] <cyphermox> that's going to get really painful I think
[22:06] <cyphermox> unless you're syncing packages
[22:06] <ToyKeeper> charles: If you're still around, do you know why the wiki's test plan is different than the file on launchpad?
[22:06] <cyphermox> otherwise we could get one landing in ubuntu only, and the other in rtm only
[22:08] <cyphermox> robru: because I don't see the code landed in ubuntu (non-rtm) for silo rtm 13
[22:08] <robru> cyphermox: yep, I know, it's a total disaster. Total. Disaster.
[22:08] <cyphermox> well
[22:09] <cyphermox> you could land my stuff first, and then get the package rebuilt
[22:09] <cyphermox> assuming it hasn't already been tested
[22:09] <robru> cyphermox: I'm terrified to assign conflicting RTM silos because of the implications. one can revert the other, but by the time you discover it, the releases are already in utopic so it's too late to do anything about it
[22:09] <cyphermox> hmm
[22:09] <cyphermox> I know
[22:10] <charles> ToyKeeper, at a very quick glance, they look the same to me? <https://wiki.ubuntu.com/Process/Merges/Checklists/indicator-transfer>, <http://bazaar.launchpad.net/~indicator-applet-developers/indicator-transfer/trunk.14.10/view/head:/MERGE-REVIEW>
[22:10] <cyphermox> well, on the bright side mterry's hasn't built packages yet
[22:10] <robru> cyphermox: well, 13 hasn't been tested because it hasn't been built. I guess I can squeeze you in there first.
[22:10] <robru> cyphermox: but I'm gonna free 13 for good measure.
[22:10] <cyphermox> it might not actually be necessary to
[22:10] <cyphermox> hold on a sec
[22:11] <robru> heh, too late
[22:11] <robru> whatever, it's trivial to reassign that one when mterry really needs it
[22:11] <cyphermox> ah, you couldn't even build it yet if you wanted to anyway
[22:11] <cyphermox> I think that landing was expected to be done by package copy as well
[22:11] <cyphermox> (ie. no merge requests)
[22:12] <ToyKeeper> charles: I'm comparing http://bazaar.launchpad.net/~indicator-applet-developers/indicator-transfer/trunk.14.10/view/head:/tests/manual  to  https://wiki.ubuntu.com/Process/Merges/TestPlan/indicator-transfer
[22:12] <cyphermox> so that implies having the packages built in ubuntu before
[22:13] <robru> cyphermox: yeah exactly, what happens if we package copy in there? we can't rebuild a package copy to include new stuff. package copies are notoriously terrible at resolving conflicts because you can't just rebuild the MP which automatically rebases on trunk.
[22:13] <robru> cyphermox: anyway you got rtm-12 now
[22:13] <cyphermox> ok
[22:13] <cyphermox> robru: well, that just means you need to follow the order in which things land in the ubuntu archive
[22:14] <cyphermox> so basically; if mterry's code had landed in ubuntu; you could have done just one package copy because his version would have superseded mine, and included the changes
[22:15] <cyphermox> in other words, if silo A and silo B are planned for Ubuntu; and silo A lands, followed by silo B; then you only really need to do an RTM landing for silo B; because it will include the code for both (still requires to be tested accordingly)
[22:16] <robru> You hope ;-)
[22:16] <robru> I think there's a crazy race condition between when silo B lands and when silo RTM-A is assigned. it terrifies me
[22:20] <ToyKeeper> charles: In any case, simple-download.py seems to work (aside from known issues) pre-silo, but post-silo the screen shows no sign that any transfers are happening during the script run.  However, post-silo it does still show transfers the user initiated via browser.  Not sure what to think of that.
[22:21] <charles> ToyKeeper, I removed simple-download.py from the manual tests because it doesn't go through content-hub, which is now necessary in order for the transfer to show up. That's how other types of downloads, like system updates and mms downloads, are filtered out
[22:22] <charles> ToyKeeper, run the manual test indicator-transfer/simple-download-check
[22:23] <charles> ToyKeeper, because of the unity8 rendering bug I mentioned earlier, the title and progressbar still won't show up. However the gallery icon should appear correctly, and clicking the menuitem should launch the gallery
[22:24] <ToyKeeper> charles: Yes, that's as expected.  I haven't seen simple-download-check though...  don't normally need files from the source repo for testing.
[22:24] <ToyKeeper> Er, for manual testing anyway.
[22:26] <ToyKeeper> charles: Ah, not a source file.  That would be the content of the wiki page which refers to simple-download.py.  Okay.
[22:26] <charles> ahhhh, now I understand your confusion
[22:26] <ToyKeeper> charles: In any case, the package looks good aside from having trouble getting transfers to last long enough to see the progress.
[22:27] <charles> I removed simple-download.py from the manual tests, but didn't remove it from the wiki page. Sorry about that.
[22:38] <cyphermox> rockin'
[22:45] <ToyKeeper> charles: Thanks for all the help; any chance you could update the wiki's test plan since it's out of date?
[22:46] <charles> ToyKeeper, yes. I'll do it before I EOD here
[22:47] <charles> ToyKeeper, thanks for your patience; the test docs should have been in order before silo
[22:48] <ToyKeeper> charles: This is why we've started testing in order of who is still awake.  Almost every silo seems to have similar issues lately.
[22:48] <ToyKeeper> Once that sort of thing is in order, testing should go a lot faster.
[22:52] <robru> ToyKeeper: so what happens when you catch a regression? Seems to me like it's too late to do anything since the silo landed in utopic already
[22:52] <ToyKeeper> robru: I'm not sure yet.  Chase it down and work it through the process from the beginning, I guess.
[22:53] <robru> Awesome.
[22:53] <ToyKeeper> robru: In this particular case, the ability to configure the time zone broke somewhere between rtm-8 and rtm-9.
[22:54] <robru> Yeah, "somewhere" is the awesome part.
[23:15] <ToyKeeper> ralsina: You around?  I'm looking at rtm/landing-007 (ubuntu-push) and am wondering what image it was tested on.
[23:16] <robru> ToyKeeper: he told me he didn't test rtm but it was a small enough landing it should be fine. Not sure what image specifically
[23:16] <ToyKeeper> ralsina: Also wondering how to test the change in this silo.  No bug or MP is attached, and the manual test plan is just "run the autopilot tests".
[23:28] <sergiusens> rsalveti: ready with the changes you asked for
[23:33] <sergiusens> robru: what's the thing with http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=ciborium ?
[23:33] <sergiusens> I'm not in a hurry, I plan to go to bed ASAP; curiosity only
[23:33] <robru> sergiusens: looks like the packages didn't get copied
[23:34] <robru> sergiusens: i can do it in a bit
[23:34] <sergiusens> robru: yeah, but it refers to unity8 and ciborium in the spreadsheet
[23:34] <sergiusens> unless that status is stale
[23:35] <sergiusens> might be, the ppa is empty
[23:38] <kenvandine> robru, what do i need to do now if i want landing 19 to also go to ubuntu-rtm?
[23:39] <kenvandine> robru, add a new row to the spreadsheet for package only?
[23:46] <sergiusens> kenvandine: it's done "automatically" now
[23:46] <sergiusens> by the trainguard elves
[23:46] <kenvandine> sergiusens, ? automatically?  ubuntu-rtm is pretty outdated for ubuntu-system-settings
[23:46] <kenvandine> i added it to line 51 as a SRCCOPY based what i saw others do :)
[23:46] <sergiusens> kenvandine: the silo reservation is automatic
[23:47] <kenvandine> robru, ^^
[23:47] <sergiusens> the testing by dev + testing by qa is manual
[23:47] <kenvandine> yeah


[00:15] <duanedesign> evening all
[00:18] <sense> evening duanedesign
[00:20] <duanedesign> sense: you going to the happy hour tonight?
[00:21] <sense> duanedesign: I think we'll be out for dinner then.
[00:21] <duanedesign> ahh
[00:22] <duanedesign> sense: you getting adjusted yet to the time zone difference :)
[00:22] <duanedesign> i woke up early yesterday and walked around and I saw all our friends from across the pond were up and about
[00:23] <duanedesign> :)
[00:24] <sense> I sleep long enough, don't get up early. I guess I'm tired enough to keep sleeping. ;)
[00:25] <duanedesign> :)
[00:33] <sense> jcastro: https://blueprints.launchpad.net/ubuntu/+spec/appdevs-n-upstream-contacts needs a series, otherwise its work-items will not show up on the burn-down charts.
[04:14] <doctormo> jcastro: paultag said to let you know you're crap.
[04:14] <doctormo> Don't ask me why
[04:14] <paultag> That's not what I said at all!
[04:15] <paultag> doctormo, I said to go to the bar and tell him he *sucks*.  No real announcements would come as a normal public message. They would come as global notices and/or on the site/blog
[04:33] <Technoviking> thought so
[04:34] <nhandler> The unidentified user without a staff cloak getting killed for posting the message is also a good hint ;)
[04:35] <nigelb> heh
[06:02] <nigelb> morning AlanBell :)
[06:59] <czajkowski> aloha
[08:29] <AlanBell> morning
[08:34] <nigelb> AlanBell: hey
[08:34] <nigelb> AlanBell: How did the drinking game go? ;)
[08:45] <AlanBell> I got 18 words
[08:45] <AlanBell> it was a bit early in the day so I was playing with coffee
[09:19] <duanedesign> morning all
[09:20] <kim0> o/ everyone :)
[09:42] <nigelb> dammit kim0 , have you no sleep?
[09:42] <nigelb> duanedesign: ^^ you too
[09:42]  * kim0 not at UDS
[09:43]  * nigelb hugs kim0
[09:43]  * kim0 hugs nigelb :)
[10:17] <nisshh> akgraner, shame about your house :(
[10:31] <popey> yikes! Sorry to hear that akgraner
[11:13] <duanedesign> akgraner:  what happened :o
[11:13] <duanedesign> nigelb!!
[11:14] <duanedesign> nigelb: are you going to be able to remote participate today?
[11:16] <popey> duanedesign: http://akgraner.com/?p=763
[11:24] <nigelb> duanedesign: doubtful, have a packed schedule today
[11:34] <duanedesign> nigelb: ok. wish you were here, Alan too. :)
[11:43] <czajkowski> aloha
[11:46] <nigelb> morning czajkowski :)
[11:47] <cjohnston> mornin
[11:47]  * nigelb waves to cjohnston
[11:47] <nigelb> cjohnston: Did you find floor space to sleep?
[11:49] <cjohnston> no
[11:49] <cjohnston> lol
[11:52] <nigelb> haha
[11:52] <nigelb> cjohnston: did ya try bribing Daviey with caffeine stock for 6 months? :p
[11:53] <cjohnston> no
[11:53] <cjohnston> heh
[11:54] <duanedesign> morning cjohnston
[11:54] <cjohnston> hey duanedesign
[11:59] <czajkowski> TEAM REPORTS REMINDER!
[12:40] <nhandler> Bleh, I need a new computer. My current one is starting to fail one part at a time on me. It now won't even stay powered on through the night while plugged in.
[12:42] <czajkowski> :(
[12:42] <czajkowski> nhandler: pimping reports at sessions
[12:43] <Pendulum> nhandler: she's a good pimp too. Very vocal and very persuasive :P
[12:43] <nigelb> hahahaha
[12:43] <nhandler> czajkowski: Are any details of the discussions available anywhere? I saw a mere bullet on some blueprint mentioning it
[12:43] <czajkowski> yesterday in round table
[12:43] <czajkowski> so some folks still find it hard to create a wiki...
[12:43] <Pendulum> you could look at the gobby doc
[12:43] <czajkowski> *sigh*
[12:44] <czajkowski> so we;re gonna come up with a cheat sheet for it
[12:44] <czajkowski> and also get thet team reporting page translated
[12:46] <nhandler> czajkowski: That might be the case for some people (especially some LoCo teams), but I still think the key reason many people despise them is that it requires sitting down and thinking about what the team has done during the month and writing it down (which takes some time and is boring). I'm going to look back at the team-reports stats script (now that I think we have team report headings that match up with ...
[12:46] <nhandler> ... LP). Maybe getting a box on the HoF or somewhere might make this more interesting by adding a small element of competition
[12:46] <nigelb> nhandler: +1
[12:46] <nhandler> That is assuming my computer remains functional
[12:46] <nigelb> hrm, I should get around to classroom team reports
[12:46] <nigelb> and accesibility
[12:47] <nhandler> nigelb: The classroom report is usually pretty easy. Normally, it is just going through our calendar
[12:47] <nigelb> thankfully
[12:47] <nigelb> accessibility is challenging
[12:48] <Pendulum> nigelb: I know there's a page up already
[12:49] <nigelb> Pendulum: I saw, I want to add a few
[12:49] <Pendulum> *nods*
[12:50] <Pendulum> nigelb: also, you may want to liase with charlie-tca on some of the bug-related stuff
[12:50] <nigelb> Pendulum: I should, waiting for my laptop return again :/
[12:50] <Pendulum> yeah, no worries.
[12:54] <AlanBell> czajkowski: we talked about replacing gobby with etherpad before, is there any plan to do so?
[12:56] <AlanBell> one of the issues was that gobby was more accessible than etherpad, however gobby 0.5 is not accessible, the edit window is silent
[12:57] <nhandler> Having our own gobby server for the UDS stuff is also nice for people who want to go back later in the cycle to look at the discussions (pretty easy to find them there)
[12:57] <AlanBell> I am pretty sure that etherpad can be made to be accessible
[12:57] <AlanBell> nhandler: how is that different to etherpad?
[12:58] <AlanBell> if we set up pad.ubuntu.com then there would be a much better history of changes, no random deletions and a server that stays up given enough ram
[12:58] <nhandler> AlanBell: If they were to setup pad.ubuntu.com (or something similar), it would probably be used for much more than UDS (which isn't a bad thing)
[12:58] <AlanBell> probably, yes
[12:59] <AlanBell> but if the summit schedule had a pad URL on each session that would be the index to it all
[12:59] <nhandler> It is nice having only the UDS stuff on the current gobby. So basically, I am in favor of setting up pad.ubuntu.com, but I still like gobby for UDS
[13:00] <nhandler> AlanBell: The summit schedule is a PITA (due to being so large). The links would be nice for during UDS, but I'm not sure how long they would stay up afterwards
[13:01] <AlanBell> slap them all in a wiki page or even a pad document
[13:02] <nhandler> IMO, the best place for them would be in the comment section of the relevant blueprint. That way, you have the discussion and the resulting action items
[13:03] <AlanBell> even better
[13:04] <AlanBell> there is a url link on the blueprints already, just point that to an etherpad server, job done
[13:05] <AlanBell> e.g. http://pad.ubuntu-uk.org/packageselection-dx-n-unity-a11y
[13:06] <nhandler> AlanBell: The URL (I think you are talking about) is for a detailed Spec. Re-using it for the discussion stuff might get confusing
[13:06] <AlanBell> hmm, possibly
[13:06] <popey> etherpad > gobby
[13:06] <popey> in almost every single way
[13:07] <AlanBell> but just matching the blueprint name with etherpad URL as above would work fine
[13:10] <AlanBell> now that the gobby accessibility is broken I am unaware of any valid reason for sticking with it
[13:11] <popey> problem is nobody thinks about this issue until UDS itself
[13:12] <AlanBell> well the *only* reason I didn't push for it this cycle is because Luke Yelavich asked me not to because gobby was accessible
[13:17] <popey> whats luke doing this cycle?
[13:17] <popey> given he's there, and he must be involved in sessions
[13:19] <AlanBell> he is doing a lot on Unity accessibility and maybe some work on the installer
[13:19] <AlanBell> he is involved in sessions
[13:20] <popey> no, thats not what I meant
[13:21] <popey> I meant, what is he doing to enable his involvement if gobby is broken from an a11y perspective?
[13:51] <AlanBell> I am scribing in the accessibility sessions
[13:53] <AlanBell> I would assume he is taking his own notes, but with gobby down more than it is up I don't think he is bothering with it
[14:03] <czajkowski> AlanBell: problem with etherpad is one swift move and the document is deleted
[14:03] <AlanBell> whut?
[14:03] <AlanBell> that is the problem with gobby
[14:04] <AlanBell> not etherpad
[14:04] <AlanBell> I have no idea how to delete an etherpad document
[14:04] <czajkowski> selecting it all and deleting it
[14:04] <czajkowski> removes it there is no undo
[14:05] <czajkowski> also being able to save gobby remotely is good
[14:05] <czajkowski> problem atm with gobby is it wont stay up
[14:13] <popey> czajkowski: lies
[14:13] <popey> there is undo
[14:13] <czajkowski> really...
[14:13] <popey> yes
[14:13] <czajkowski> hmm
[14:13] <popey> thats kinda the whole point
[14:14] <popey> you can roll back any change
[14:14] <czajkowski> I knew I could save
[14:14] <czajkowski> thanks
[14:37] <AlanBell> https://blueprints.launchpad.net/ubuntu/+spec/ubuntutheproject-community-n-etherpad-for-uds
[14:40] <sense> AlanBell: Will it really take a whole session to decide to switch?
[14:41] <AlanBell> well yes, it will take a bit of discussion of the merits, and plan out who is going to do what to make it happen
[14:41] <AlanBell> could be done in another session perhaps if there is one appropriate
[14:41] <AlanBell> but it is going to need action items for implementation and might need server resources
[14:42] <AlanBell> easier to get that stuff if there is a clear decision at UDS to do it
[18:33] <czajkowski> paultag: grrrrrrr missing channel
[18:34] <cjohnston> lol
[19:14] <czajkowski> Pici: ping
[19:15] <Pici> czajkowski: pong
[19:15] <czajkowski> Pici: can you poke nafallo he's looking to talk re bots
[19:15] <czajkowski> please
[19:16] <Pici> czajkowski: sure.  Now?
[19:18] <czajkowski> yes in pm
[19:19] <czajkowski> or else near the stand at uds
[19:20] <jcastro> kim0: nice job on the blogging!
[19:20] <Pici> czajkowski: I'd like to listen to the next plenary, so I'm in there.  I've sent him a pm.
[19:20] <kim0> jcastro: hey thanks ;)
[20:11] <Technoviking> afternoon all
[20:31] <kim0> afternoon
[20:32] <Technoviking> kim0: howdy
[20:32] <kim0> going good :)
[20:32] <kim0> How about you
[20:32] <Technoviking> doing well
[20:34] <kim0> cool
[20:36] <Pendulum> hiya kim0
[20:37] <kim0> Pendulum: hey how's it going
[20:38] <dholbach> hey kim0
[20:38] <Pendulum> kim0: not bad. you?
[20:38] <kim0> dholbach: hey daniel :)
[20:38] <kim0> Pendulum: going good too :)
[20:38] <kim0> dholbach: I actually miss our team call :)
[20:40]  * dholbach hugs kim0
[20:40]  * kim0 hugs dholbach back
[20:40] <cjohnston> bug 644817
[20:40] <ubot2> Launchpad bug 644817 in loco-directory "Global Event Page should list the team name and the event name (affects: 1) (heat: 4)" [Wishlist,Triaged] https://launchpad.net/bugs/644817
[21:11] <nhandler> AlanBell: To answer your question from earlier, technically, the team reports are for Ubuntu teams. There is nothing stopping Canonical teams from using them, but I think in most cases, they try and utilize the most similar Ubuntu team's report.
[21:44] <Technoviking> jono: ping-a-ling
[21:45] <czajkowski> Technoviking: he's not so much on irc..
[21:46] <Technoviking> dholbach: ping
[21:47] <dholbach> Technoviking, pong
[21:47] <Technoviking> dholbach: I'm trying to get a session at UDS added for Ubuntu Forums upgrade, can you help?
[21:47] <dholbach> Technoviking, jcastro's your man
[21:48] <dholbach> Technoviking, do you have a blueprint in launchpad for it?
[21:48] <Technoviking> dholbach: yes I do
[21:48] <dholbach> Technoviking, give him the name of it and it should be fine
[21:48] <dholbach> ... I guess :)
[21:48] <Technoviking> :)
[21:48] <jono> Technoviking, hey
[21:48] <jono> oh its all sorted
[21:49] <Technoviking> jono: yep
[21:49] <jono> cool :)
[21:49] <jono> biab
[22:15] <sense> vish: Where are you?
[22:15] <sense> We need you here!
[22:15] <sense> Bug Squad Documentation review.
[22:17] <vish> sense: where?
[22:17] <sense> vish: BOnaire 5
[22:18] <vish> sense: i'm in the china design review session..
[22:18] <vish> chineese even..
[22:18] <sense> ok
[22:18] <vish> oh goody, 5min break..
[22:18] <sense> vish: What are you doing?
[22:18] <vish> coming there for 5mins.. :)
[22:19] <sense> yay!


[12:37] <holser_> smoser: Hi
[15:05] <smoser> holser_, hey.
[15:06] <holser_> I’ve submitted 2 reviews for mcollective https://code.launchpad.net/~sgolovatiuk
[15:06] <holser_> smoser: your feedback is welcomed
[15:10] <smoser> six doesn't cover BytesIO ?
[15:11] <smoser> holser_,
[15:11] <smoser> $ for p in python2 python3; do echo $p; $p -c 'from six import BytesIO; print(BytesIO)'; done
[15:11] <smoser> python2
[15:11] <smoser> StringIO.StringIO
[15:11] <smoser> python3
[15:11] <smoser> <class '_io.BytesIO'>
[15:11] <smoser> smoser@milhouse:~/src/cirros/trunk$
[15:11] <smoser> seems to work
[15:11] <smoser> but i'm guessin gyou tried that
[15:12] <holser_> yeah I tried
[15:12] <smoser> must be older version of six
[15:12] <smoser> that you have
[15:12] <smoser> what a pita
[15:12] <holser_> I use the default version in 16.04
[15:12] <smoser> its got to be in there.
[15:12] <holser_> fresh 16.04
[15:12] <holser_> anyway, I gave the exact steps in bug
[15:13] <holser_> so you can try them with your six
[15:14] <smoser> python3 on 16.04 most certainly can do: from six import BytesIO
[15:14] <holser_> I can do that way
[15:14] <holser_> without try:
[15:14] <holser_> just from six import BytesIO
[15:16] <smoser> see if that works on python2 though
[15:16] <smoser> its posisble configobj in python2 will not like that it gets bytes
[15:17] <waldi> possible. why do you want that?
[15:18] <smoser> why do i want python2?
[15:18] <waldi> wait. python2 does not have bytes
[15:18] <smoser> well, some pytho2 do
[15:18] <waldi> >>> bytes
[15:18] <waldi> <type 'str'>
[15:18] <waldi> so no, no bytes, only str
[15:18] <smoser> right. ok.
[15:19] <smoser> could you add unit test for this ?
[15:19] <smoser> you can rip the section out of 'handle' that does:
[15:19] <smoser>  if 'conf' in mcollective_cfg:
[15:19] <smoser>  ....
[15:20] <smoser> and just put that in a fuction that has 2 inputs.
[15:20] <smoser>  config and output file
[15:20] <smoser> then unit test that the file gets what you expected
[15:20] <smoser> or even that just returns a string (which you can pass to util.write_file())
[15:23] <smoser> i think if you re-factor that code a bit, it will be more easy for you do do the other mp too.
[15:23] <smoser> oh. i see that the method i mentioned would have other htings too PUBCERT_FILE, and such.
[19:11] <Wulf> Hoping to get a more satisfying answer today:  I'm using cloud-init on aws ec2. I've seen in the source code, that retrieving ec2 meta data is supported. I would like to access the meta data from a userdata script written in python. Is it possible to access it without having to reinvent the wheel?
[19:17] <smoser> Wulf,
[19:17] <smoser>  from cloudinit import ec2_utils
[19:17] <smoser> ec2_utils.get_instance_metadata()
[19:18] <Wulf> smoser: and that is considered a public interface?
[19:19] <smoser> that will work for 14.04 and 16.04
[19:19] <Wulf> Good enough for me, thank you!
[19:19] <Wulf> Now I only need to find out why I'm getting wrong data from AWS :-)
[19:25] <Wulf> Odd_Bloke: and thanks to you too
[22:37] <harlowja> btw, how far along is the networkd stuff for supporting systems?
[22:39] <holser_> smoser: I’ve updated review, added unit test
[22:45] <copumpkin> does cloud-init ignore everything before #cloud-config in ec2 userdata?
[22:45] <copumpkin> I see a lot of people describe it as #cloud-config needs to be on the first line
[23:37] <harlowja> arg, why do when i go to rebuild a cloud-init rpm and look at what redhat rpm has in it do i always find little surprises that never seemed toget upstreamed
[23:38] <harlowja> (where surprises == patches)


[00:20] <BobJonkman> Tomorrow at this time we should be having the IRC meeting. https://wiki.ubuntu.com/CanadianTeam/Meetings/2012-12-13
[00:21] <BobJonkman> And in the Kitchener Waterloo area we'll be sliming our keyboards with the juice of Egg Roll sauce: http://loco.ubuntu.com/events/ubuntu-ca/2127/detail/
[04:10] <blbe> anybody here familiar with javascript?
[23:28] <BobJonkman1> On my way to ERK, may be a little late...
[23:50] <dscassel> I'm here!
[23:51] <dscassel> Meeting in 10.
[23:56] <mcpherrin> This is probably not the best place to ask, but what non-ubuntu distributions do people use?
[23:57] <mcpherrin> A few people I know are evaluationg options, given the current unusability of the ubuntu stock config
[23:57] <mcpherrin> (For non-single-user machines)