[00:01] <rsalveti> yeah, not related
[00:07] <asac> cyphermox: what happened to your nm fix? :)
[00:07] <asac> did the merge go in?
[00:07] <asac> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1225393
[00:07] <asac> hi :)
[00:08] <cyphermox> asac: NM fix is in proposed waiting to be unblocked
[00:08] <asac> cyphermox: aha
[00:08] <asac> so no coordination :)?
[00:09] <asac> cyphermox: thought you wanted to put at least a log entry into the sheet
[00:09] <cyphermox> what do you mean no coordination?
[00:09] <cyphermox> asac: it's there
[00:09] <asac> cyphermox: where?
[00:09] <cyphermox> line 56
[00:09] <cyphermox> ok, so the status does need to be updated
[00:10] <asac> cyphermox: oh... so the idea is that you allocate a slot in the landing plan before uploading.
[00:10] <asac> cyphermox: anyway, ignore, just remind me that i do that tomorrow :)
[00:10] <asac> thanks
[00:10] <asac> i will explain more in depth maybe ... but this is in flux so i might not do :)
[00:11] <asac> hehe
[00:11] <kgunn> fginther: hey man
[00:12] <asac> cyphermox: you plan to get that through proposed before beta?
[00:12] <kgunn> fginther: realizing you might be eod
[00:12] <cyphermox> asac: beta is this thursday no?
[00:12] <kgunn> fginther: so, I was wondering...you know how you gave us a dedicated host to build on ?
[00:12] <cyphermox> asac: this is blocked *by* beta
[00:13] <asac> cyphermox: ok thanks
[00:13] <cyphermox> unless you mean you want to do a phone image beta
[00:13] <kgunn> fginther: can you make the ci runs on this https://code.launchpad.net/~mir-team/mir/development-branch branch use those ?
[00:13] <asac> cyphermox: i wondered if you tried to get it in saucy before thursday... seems thats not the case, so i have the date for fri
[00:14] <kgunn> fginther: in other words, we want the amd ci run on that to be treated just like lp:mir
[00:14] <cyphermox> asac: alright
[00:14] <asac> cyphermox: or do you plan to?
[00:14] <cjwatson> asac: Note that currently-blocked-by-beta packages will probably be flushed earlier than Friday.
[00:14] <asac> i am sure there are unhappy stakeholders :)
[00:14] <asac> cjwatson: right. you think its rather sometimes thu? would be nice
[00:14] <cjwatson> We normally try to block people for as short a time as possible, so we go through and flush anything not entirely inappropriate from the queue once we're past the point of no return on respins, or at the latest just after we release the beta.
[00:14] <asac> right
[00:14] <asac> ok
[00:14] <asac> thanks
[00:15] <cyphermox> asac: I'd personally prefer to have it landing earlier than later, but I can accept some people need a little stability in packages for milestones
[00:15] <asac> right
[00:15] <asac> lets leave it there unless someone comes along :)
[00:16] <cyphermox> in the meantime I got an issue reported by jason for a bug in MTP I want to look at
[00:16] <asac> sounds good. thanks
[00:17] <cyphermox> now, I'd land ubuntu-wallpapers, but that's in the same stack as upstart-app-launch, so I'll do some magic to avoid touching that one
[00:27] <cyphermox> robru: ^ wallpapers done...
[00:27] <robru> cyphermox, oh, cool. I watched the commit land earlier but forgot to actually build the package ;-)
[00:27] <cyphermox> np
[00:28] <cyphermox> I rebuilt it and published just that, it should show up in launchpad shortly I guess
[00:32] <jdstrand> asac: I do. I had that in there when I added it to the ask, but then later in the day that whole column seemed gone
[00:33] <jdstrand> asac: I see the notes in the landing plan
[00:38] <asac> jdstrand: i think 62 is now produced fwiw
[00:38] <asac> if you are happy and its tested and safe, go ahead and cross fingers :)
[00:40]  * asac off
[00:50] <ralsina> asac: maybe it got pulled in a previous landing, I guess but I am surprised, I waited until the previous one was INARCHIVE before opening trunk again
[00:53] <ralsina> asac: should all be in  click-update-manager 0.1+13.10.20130924.1-0ubuntu1 (revno 21 of lp:click-update-manager)
[00:57] <ralsina> asac: that's for #87. For #88 it's all in unity-scope-click  0.1+13.10.20130924.1-0ubuntu1 (revno 50)
[01:03] <ralsina> asac: which are both for early this morning when I put the asks in candidate status. Perhaps the previous related landings were still ongoing, in which case my fault (and hey, two things less to land)
[01:25] <plars> asac: we can do better than that actually... doanac has a change about to land that, among other things, will stop installing utah on the target (it wasn't being used anyway) and I can pull out the apt-get test from default tonight
[01:26] <plars> asac: this is what I suggested last time we talked about it, I think we should just go ahead and do it. The results will be more realistic then
[02:32] <cyphermox> rsalveti: poke. I reran tests for platform-api and they all passed; publishing now
[02:41] <cyphermox> rsalveti: actually, scratch that. I see in backlog you guys wanted to wait -- in any case, it's ready to land whenever we get the go.
[02:41]  * cyphermox logs off
[07:09] <asac> plars: ok lets check on that idea with you and doanac today
[07:09] <asac> and do it if all looks good
[07:31] <asac> line 99 in landing asks is too good to be true
[07:32] <didrocks> not merged yet ;)
[07:33] <asac> i am pretty confident... rsalveti was on it supportinng them and he sounded pretty confident that this is indeed fixing it as well :)... but yeah. you are right
[07:33] <asac> but again, it sounds too godo to be true
[07:33] <asac> hehe
[07:34] <didrocks> heh
[07:37] <asac> Mirv: what do you think about ui-toolkit? is that in good shape to try this morning?
[07:39]  * lool checks status of Mir landing
[07:39] <didrocks> lool: landed
[07:45] <lool> cool
[07:45] <lool> did we land unity8 too?
[07:46] <Mirv> asac: it just finished building, and I'm going to test that version with ui-toolkit + unity8 + apps (current version) autopilots. apps will rebuild them slightly later
[07:46] <didrocks> lool: yeah
[07:46] <lool> awesome
[07:46] <lool> so can I put line 41 as INARCHIVE?
[07:46] <Mirv> lool: yes
[07:47] <Mirv> I mean s/apps/phone/ will rebuild slightly later
[07:47] <lool> actually it's iINIMAGE it seems
[07:48] <Mirv> I guess line 72 platform-api as well?
[07:48] <Mirv> oh, that's probably still pending, even newer commit
[07:49] <lool> Mirv: click-package stack (;ine 74) is INIMAGE?
[07:50] <Mirv> no, I just published it a couple of hours ago
[07:50] <lool> thostr_: mir stack went in so unity8 stack went in image now late yesterday; see http://people.canonical.com/~ogra/touch-image-stats/20130924.1.changes
[07:51] <lool> Mirv: ok; thanks
[07:53] <thostr_> lool: I'm flashing right now and recheck what's actually in
[07:56] <lool> asac: so 62 has better pass rate than 61; could we consider promoting it at the standup?  then we can focus on landing things inarchive and in image build this afternoon/tonight
[07:56] <ogra_> image is building btw
[07:56] <lool> oh
[07:56] <ogra_> oh
[07:56] <ogra_> heh
[07:56] <lool> asac: can we promote 62?
[07:58] <thostr_> lool: do you think you can review https://code.launchpad.net/~ted/upstart-app-launch/fdo-application-open/+merge/186887
[08:00] <ogra_> 62 looks great
[08:02] <lool> thostr_: I can try
[08:02] <lool> ogra_: is it going to break numbering being in sync if we promote 62 after 63 is built?
[08:03] <ogra_> ?
[08:03] <ogra_> nope, that would be pretty awkward
[08:04] <ogra_> you can promote any number ... at least as long as it is bigger than the last promoted one ...
[08:04] <ogra_> not sure stgraber thought about rolling back ... well, he might, but not sure what the updater would do in that case
[08:20]  * ogra_ glares at the 350 next to his "merges" mailbox
[08:22] <StevenK> ogra_: That won't make it go down.
[08:23] <asac> lool: you know the rules ... ogra and popey sign off, then go
[08:23] <asac> :)
[08:26] <asac> mhr3: hi, can you check if http://people.canonical.com/~platform/cu2d/results has your crash fix?
[08:26] <asac> on home scope
[08:27] <asac> search for unity-scope-home
[08:27] <mhr3> asac, it does
[08:28] <vila> ogra_: Nope, shutting down won't make it go down either :-D
[08:29]  * ogra_ has some headset issues ... 
[08:30]  * popey flashes 62
[08:31] <asac> lool: coming or not?
[08:40]  * vila updates to 62 on air
[08:53] <popey> asac: ogra_ 62 looks good here
[08:54] <ogra_> popey, great, will test soon
[08:57] <lool> didrocks: this is not about skippping PPA, it's about returning to automatic mode, and corresponding the job of the autolander done when it's in proposed
[08:58] <lool> popey: how's music stuff working for you?
[08:58] <lool> popey: in 62 I can launch from music scope too  :-)
[08:58] <didrocks> lool: I don't have the metric on how many things we back out, do we really? If we don't, yeah, opening the gate, but I think we need to be coherent with the process we want in the future
[08:59] <lool> didrocks: I dont think we need to worry about post-13.10 no
[08:59] <lool> this is about getting 13.10 out  :-)
[08:59] <didrocks> lool: if we go with landing ask, then nothing, then landing asks again, it's not the right signal IMHO
[08:59] <lool> I dont want to stop landing asks
[08:59]  * ogra_ just wants to do the gating in a broader scope and later 
[08:59] <lool> without a landing ask, your stuff doesn't migrate from proposed to saucy
[09:00] <ogra_> and getting that in a shape to have testable image per landing set costs less than a day of work ...
[09:06] <lool> ogra_: so IIUC, after the call you will also check whether image 62 is good, and if it is promote it?  (just to confirm I got that right)
[09:07] <ogra_> lool, right
[09:07] <ogra_> i just dont have a phone around me, else i would have flashed already
[09:12] <popey> lool: oh excellent
[09:22]  * ogra_ twiddles thumbs
[09:33]  * ogra_ twiddles thumbs
[09:33] <ogra_> maguro flashing is soooooo slooow
[09:34] <ogra_> ah, at least it went into decompressing mode now ... so now its only another 30min
[09:34]  * ogra_ twiddles thumbs
[09:35] <didrocks> ogra_: how dare you! so much work, no time for twiddling thumbs :p
[09:35] <ogra_> haha
[09:35] <ogra_> well, given that we are blocked for most of our landings ...
[09:40] <thostr_> lool: ogra_: seems latest snapshot is missing the update of url-dispatcher and probably because of this no activation is working???
[09:41] <lool> thostr_: I have reviewed the upstart-app-launch branch, but I dont like the approach of matching app name + pid, I'd rather we match the full app_id minus version
[09:41] <ogra_> thostr_, hmm, i see a big rred entry on the spreadsheet for it
[09:42] <lool> thostr_: but I lack reference to the discussion where this was planned across components
[09:42] <ogra_> (not sure who marked it red)
[09:42] <ogra_> line 70b on "landing asks"
[09:42] <ogra_> *70
[09:43] <thostr_> I haven't marked it red.. mayb asac?
[09:45] <lool> thostr_: will check url-dispatcher when I'm back from school, gtg
[09:45] <thostr_> lool: thanks
[09:46] <thostr_> lool: btw what was now the latest status on the apps?
[09:46] <thostr_> basically the exec line, meaning do we need to update now all apps?
[10:25] <Mirv> lool: btw I've marked now "INARCHIVE" when it's in -proposed, is that fine or should I use something else?
[10:25] <Mirv> I'm just not clear how the proposal -> release works at the moment or who is doing it
[10:28] <cjwatson> that's INPROPOSED I believe
[10:29] <ogra_> yeah
[10:29] <cjwatson> -proposed => release is an automatic process although some packages are blocked until approved
[10:29] <cjwatson> if there's a block it'll show up on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[10:29] <ogra_> well, all packages are in beta freeze now, arent they ?
[10:29] <cjwatson> no
[10:29] <ogra_> ah, i thought so
[10:29] <cjwatson> the migration block for beta freeze is selective, for packages that are part of the beta images
[10:30] <Mirv> ah, I thought beta freeze affects these as well. then no problem.
[10:30] <cjwatson> Mirv: it may or may not.  which package?
[10:30] <Mirv> I'll inproposed anyway until I've checked that they have migrated
[10:31] <Mirv> cjwatson: ubuntu-ui-toolkit, indicators-sound, libusermetrics, address-book-app, dialer-app, history-service, address-book-service, ubuntu-download-manager
[10:31] <ogra_> indicators-sound  might be desktop too
[10:32] <cjwatson> none of those are blocked
[10:32] <cjwatson> however indicator-sound is
[10:32] <cjwatson> rather important to spell your package names correctly :)
[10:33] <cjwatson> so, assuming you've spelled the rest correctly, only indicator-sound is blocked
[10:33] <ogra_> yeah
[10:33] <Mirv> heh, yeah there's a typo
[10:33] <Mirv> ok, that was the (apparently much discussed) switch of Recommends between g-c-c and u-s-s
[10:33] <cjwatson> there are other checks apart from blocks, of course, so check that they actually migrate
[10:33] <ogra_> wasnt that also fixed in livecd-rootfs ?
[10:34] <ogra_> or was that just a corresponding fix
[10:34] <Mirv> I'll keep these marked as inproposed until it's sure they've migrated
[10:34] <cjwatson> I fixed one part of that in livecd-rootfs, but that doesn't mean the Recommends were correct as written
[10:34] <ogra_> no, but it wont harm us atm
[10:34] <cjwatson> Mirv: use rmadison to confirm migration
[10:34] <cjwatson> ogra_: indeed
[10:34] <lool> thostr_: on the apps I saw at least some apps go through
[10:34] <lool> thostr_: but more because we published tons of stacks in the last days
[10:35] <Mirv> ogra_: I don't know, I just heard that a lot of discussion occured on http://bazaar.launchpad.net/~indicator-applet-developers/indicator-sound/trunk.13.10/revision/379
[10:35] <ogra_> lool, popey asac 62 looks fine here
[10:35] <Mirv> cjwatson: ok
[10:35] <ogra_> Mirv, right, but colins fix makes sure it does no harm atm, so it isnt that urgent
[10:36] <popey> ogra_: lemme know when you hit the button and I'll mail
[10:36] <lool> thostr_: so url-dispatcher is seeded in Ubuntu, that's why it didn't go in
[10:36] <ogra_> popey, right, just waiting for feedback from asac and lool
[10:37] <lool> thostr_: but this is just the Bad URL fix
[10:37] <lool> thostr_: did you particularly care about this fix?
[10:38] <lool> it seemed like handling bad input to a component would actually bubble back the url
[10:38] <lool> ogra_: if it looks good and popey says it's good, you should promote it  :-)
[10:38] <ogra_> :)
[10:38] <ogra_> asac, ^^^ ?
[10:38] <lool> thostr_: unless it's critically urgent for url-dispatcher, we need to wait post Thursday / beta release to get it in
[10:39] <lool> thostr_: or they might have to reroll the candidate beta images
[10:42] <thostr_> lool: I mean currently activation is not working on phone at all
[10:42] <thostr_> lool: or is it just me?
[10:43] <lool> thostr_: weird, popey told me the same thing but it worked for me
[10:43] <lool> hmm my latest flash didn't have --no-backup, but I lost my music; anyway, reflashing 63 and I'll try putting music again
[10:43] <thostr_> lool: it's not working at all and I suspect the url-dispatcher... I'll do a manual upgrade and recheck
[10:44] <lool> thostr_: by activation, what do you mean exactly?
[10:44] <thostr_> clicking on an icon on dash e.g. music and by that launching the music player
[10:45] <lool> So I have: ii  url-dispatcher:armhf                                  0.1+13.10.20130919.3-0ubuntu1               armhf        service to allow sending of URLs and get handlers started
[10:45] <lool> and it works here
[10:46] <lool> oh I just broke unity
[10:47] <lool> what's the screenshot command again?
[10:48] <popey>  /system/bin/screencap
[10:48] <popey> lool: https://bazaar.launchpad.net/~popey/+junk/phablet-flash-wrapper/view/head:/screenshot.sh i use that
[10:48] <popey> which screencaps and then scp's somewhere so i can easily share them
[10:48] <popey> YMMV etc
[10:50] <lool> popey thostr_: just so that I save this glorious moment, I've recorded a video where you'll see me opening two music files from home and music scopes with a stock image   :-)
[10:51] <popey> ☻
[10:51] <thostr_> lool: I did a reboot and now I can launch music from home scope
[10:51] <thostr_> but not from music scope
[10:51] <thostr_> something is fishy here
[10:53] <lool> thostr_: is that with 62 or 63?
[10:53] <lool> or 61
[10:54] <thostr_> where can I see that number on image?
[10:54] <lool> thostr_: BTW apps >> I'm not too pressed to land all the X-Single-Instance things since I feel it doesn't work adequately right now; if we land the new fdo Open thing, it can go in
[10:54] <lool> thostr_: system-image-cli -i
[10:54] <thostr_> it's version 61
[10:55] <lool> I have 62 which has the music-scope fix
[10:55] <lool> thostr_: we're about to promote 62 I think
[10:55] <thostr_> so, it --pending also working for system-images?
[10:55] <lool> thostr_: --channel saucy-proposed
[10:55] <thostr_> ok, reflashing...
[10:56] <lool> thostr_: LP #1229468 is the single instance issue I mentioned
[10:57] <thostr_> lool: regarding apps: fine with me. Let's try to first get all upstart-app-launch (fdo) things in
[11:02] <asac> ogra_: yes!!!
[11:02] <lool> thostr_: do you know who's handling the other parts of it and where the design is?
[11:02]  * ogra_ does so then
[11:02] <asac> ogra_: thats simple... dont wait for me if all applies
[11:03] <asac> zero dashboard regression and ogra nd popey signoff is currently a 100% promote :)
[11:03]  * lool lunch &
[11:03]  * ogra_ wonders what these pling sounds from his mobile are and notices that he missed a hangout 
[11:03] <ogra_> :(
[11:03] <ogra_> sorry for that
[11:04]  * ogra_ would actually like to see some 63 results on the dashboard ... seems everything fell over on the utah side or some such
[11:04] <ogra_> (63 works fine as well in manual testing, i just reflashed right after testing)
[11:04] <thostr_> lool: handling which other parts?
[11:06] <ogra_> popey, asac, lool, promoted ... (20130924.1/62)
[11:08] <didrocks> \o/
[11:10] <popey> ogra_: nice one
[11:11] <popey> had to rummage under the desk yesterday to access the back of my PC.. glad we have a torch app! :D
[11:12] <asac> awesomey
[11:15] <popey> sent
[11:26] <ogra_> popey, torch only works on mako though
[11:26] <popey> oh ☹
[11:26] <popey> does the light work in the camera app ?
[11:27] <Mirv> ok we've been here before, but libusermetrics + click-update-manager stuck in -proposed because they earlier built for powerpc but now depend on qtdeclarative. who wants to raise a hand that "yes I'll fix that easily"? :)
[11:29] <cjwatson> I can have a look
[11:29] <cjwatson> I expect they just need archive removals
[11:31] <cjwatson> Mirv: fixed
[11:33] <lool> thostr_: the qtubuntu bits and such
[11:33] <lool> thostr_: I mean, I'm expecting we're providing something for apps to get notified
[11:33] <lool> thostr_: in the SDK runtime if you want
[11:34] <Mirv> cjwatson: I was thinking about you but I allowed anyone to volunteer. thanks!
[11:34] <thostr_> lool: AFAIK grayback working on that
[11:34] <thostr_> lool: I'll get the full update once Ted is here
[11:34] <lool> ok
[11:34] <lool> just missed him, he is probably out for lunch
[11:34] <cjwatson> Mirv: it's not always trivial but in this case there were no rdeps on powerpc so nothing else to clean up
[11:39] <ogra_> popey, yeah, it works when i force it on during taking pics
[11:43] <lool> changed all the INIMAGE 62 to DONE 62
[11:49] <didrocks> ogra_: from your description on landing ask line 100, it seems that not everything is ready (merged in trunk), yet, is it?
[11:50] <ogra_> didrocks, well, the systemd change falls under beta feeze anyway i think
[11:50] <ogra_> tehroretically everything should be ready, but not all branches got merged afaik
[11:51] <ogra_> i just updated the line right before you asked btw
[11:51] <didrocks> ogra_: so rather than Candidate, shouldn't the state be rather "Waiting for Code"?
[11:51] <ogra_> code is there
[11:51] <didrocks> we need maybe to change that terminology
[11:51] <ogra_> waiting for the "go" from us
[11:51] <didrocks> 'code not in trunk"
[11:51] <didrocks> maybe ;)
[11:51] <didrocks> ogra_: they want on us to merge to trunk?
[11:51] <lool> didrocks: just found some relatively old mps against cupstream2distro-config: https://code.launchpad.net/~cupstream2distro-maintainers/cupstream2distro-config/trunk/+activereviews would you think we can nuke the oldest ones?
[11:52] <ogra_> didrocks, no, but to nod it off
[11:52] <didrocks> ogra_: is that better this way?
[11:53] <didrocks> lool: I asked Mathieu to remove his ones
[11:53] <ogra_> didrocks, well, apart from the systemd upload all code is in trunk now
[11:53] <didrocks> the 2 WIP is from mmrazik
[11:53] <ogra_> and systemd doesnt use any bzr trees
[11:53] <ogra_> afaik
[11:53] <didrocks> ogra_: ok, please update "phablet-tools has a proposed fix for https://code.launchpad.net/~cwayne18/phablet-tools/phablet-timezone-setup/+merge/186891
[11:53] <didrocks> "
[11:53] <ogra_> so it should be Candidate now
[11:54] <didrocks> to a more accurate statement then ;)
[11:54] <didrocks> yeah
[11:54] <ogra_> phablet-tools is unrelated to the upload, just a side thing
[11:54] <didrocks> listing the merge would make think it's not in trunk yet
[11:54] <didrocks> it's still listed in this group, isn't it?
[11:54] <didrocks> (and mentionned ;))
[11:54] <didrocks> should that be 2 separate slots?
[11:54] <ogra_> it should get the fix too, but thats a separate thig, i only list it so we make sure it also lands
[11:54] <didrocks> lool: I think fghinter's and mmrazik's ones can be nuked
[11:55] <didrocks> ogra_: ok, so let's count it all that together
[11:55] <ogra_> its not a blocker for the rest
[11:55] <didrocks> so, as everything is in, let's put it all together
[11:55] <didrocks> ogra_: let's add it as soon as it's listed in http://people.canonical.com/~platform/cu2d/results
[11:55] <ogra_> right, but it needs a systemd upload that will get stuck in proposed
[11:56] <ogra_> didrocks, ??
[11:56] <ogra_> none of tehse packages will land there
[11:56] <didrocks> ogra_: phablet-tools? you still listed in this set, so it's expected that we validate this whole set :)
[11:56] <ogra_> they are all direct uploads
[11:57]  * ogra_ sighs and wipes phablet-tools 
[11:57] <ogra_> i'll blame you if we forget to do it though
[11:57] <didrocks> ogra_: why not waiting on phablet-tools to be ready and do everything in one shot?
[11:57] <didrocks> or just add another landing asks for phablet-tools to not forget it
[11:57] <didrocks> we should decouple when needed (like for Mir for instance)
[11:58] <ogra_> it was just a reminder that the p-t fis needs to go in later
[11:58] <didrocks> as long as it's merge to trunk and we got a landing ask for it, we won't forget it
[11:58] <didrocks> (but if we want it to land separately, let's separate the ask as well)
[12:02] <didrocks> ogra_: added
[12:03] <ogra_> thx
[12:06]  * ogra_ chacks what tail poppler-qml-plugin will drag in
[12:07] <ogra_> great, doesnt exist
[12:08] <ogra_> ah, nice
[12:08] <ogra_> The following NEW packages will be installed:
[12:08] <ogra_>   libpoppler-qt5-1 libpoppler43 qtdeclarative5-poppler-qml-plugin
[12:09] <ogra_> not as much as i feared
[12:09] <ogra_> (i thought it would drag ghostscript in or something)
[12:10] <didrocks> thostr_lunch: when you are back, can you define a little bit more indicator-bluetooth? We are thinking about landing system-settings, but I don't see any indicator-bluetooth staged in http://people.canonical.com/~platform/cu2d/results. Is that already in distro?
[12:10] <lool> So all the webapps stuff landed
[12:10] <lool> but I was waiting to add autopilots for these
[12:10] <ogra_> didrocks, what do you mean by 96E on landing asks ? the seed change wont go through CI
[12:10] <ogra_> and should be safe to land right now
[12:11] <didrocks> ogra_: I didn't change 96E
[12:11] <ogra_> ah, hmm, someone added it
[12:15]  * ogra_ sighs 
[12:15] <ogra_> asac, can we ask people to please use binary package names on the sheet, at least if seed changes are involved
[12:15] <ogra_> some package names seem even randomly made up
[12:15] <lool> ogra_: music-app whitelist for app lifecycle: put as INPPA
[12:15] <ogra_> great !
[12:16] <asac> ogra_: we should ask them for both
[12:16] <asac> two columns
[12:16] <asac> i want to see sources :)
[12:16] <ogra_> yeah, or that
[12:16] <ogra_> for seed changes sources are moot :)
[12:16] <asac> seems there is popular demand for binaries, so lets ask for both
[12:16] <asac> didrocks: ^^
[12:16] <ogra_> its always ubuntu-touch-meta
[12:16] <asac> ok?
[12:16] <ogra_> (and seeds onlt work on binary level)
[12:17] <ogra_> *only
[12:17] <didrocks> for seeding yeah
[12:18] <cjwatson> well, mostly only work on the binary level </pedantry>
[12:18] <cjwatson> (there's a %source syntax used in some special circumstances)
[12:19] <ogra_> heh
[12:19] <lool> didrocks: So I checked http://10.97.0.1:8080/job/cu2d-misc-saucy-1.0prepare/ and it didn't pick up ubuntu-touch-customization-hooks, why is that?
[12:19] <ogra_> lool, what happened to line 67 in landing asks ? i thinnk you were on that one
[12:19] <didrocks> lool: did anybody deploy the configuration change?
[12:20] <didrocks> as per the link I gave to you yesterday
[12:20] <didrocks> I asked Mirv to finish it IIRC
[12:20] <didrocks> also, not sure it's been preNEWed
[12:20] <lool> didrocks: Ah I thought the link recaped the addition, not the deployment
[12:20] <lool> didrocks: it's in archive already
[12:20] <ogra_> lool, and i think i saw 66 land in propoased today
[12:20] <lool> in INIMAGE even
[12:20] <didrocks> oh right, you told me that (in the archive already)
[12:20] <lool> ogra_: I'm not tracking landing asks, but will look
[12:21]  * ogra_ is just going through all seed changes
[12:21] <ogra_> since these will definitely not get stuck in beta freeze
[12:22] <Mirv> lool: it needs my branch to be merged still before I'll redeploy the stack
[12:22] <Mirv> to enable bzr split mode
[12:22] <didrocks> ah, this is still not merged upstream?
[12:22] <didrocks> there is no upstream merger setup?
[12:23] <Mirv> didrocks: there is merger setup, but my branch hasn't been approved yet after I rebased in top of mfisch's and lool's changes
[12:23] <lool> ogra_: I've added a landing plan entry for nexus 10 audio
[12:23] <ogra_> lool, heh, thanks
[12:23] <lool> ogra_: the last status was rsalveti wanted to test and sponsor
[12:23] <ogra_> right, i saw it on /changes
[12:23] <ogra_> -changes
[12:23] <ogra_> should be INPROPOSED
[12:24] <lool> alsa-lib was uploaded
[12:24] <lool> but not pulseaudio
[12:24] <didrocks> lool: mind finishing that up with Mirv then?
[12:24] <lool> didrocks: ok
[12:24] <Mirv> mfisch: lool: so when you have time check the https://code.launchpad.net/~timo-jyrinki/ubuntu-touch-customization-hooks/prep_for_daily_release/+merge/187220 and I'll enable the cu2d for it after that
[12:24] <Mirv> lool: preNEW check will be needed as well before it can be enabled
[12:25] <lool> Mirv: you've reverted some of my changes
[12:25] <lool> Mirv: like dropping homepage
[12:25] <lool> Mirv: the package is already in the image, no need to preNEW it?
[12:26] <Mirv> lool: that only I think, it's how it's instructed in the daily release wiki page and how we have it for others.
[12:26] <Mirv> lool: no, right, no preNEW needed as it's already there
[12:27] <didrocks> sil2100: hey!
[12:28] <didrocks> sil2100: so, I added you for request #20 and #26 (the latest is the easiest, so maybe doing it first?) for releasing today
[12:28] <lool> Mirv: also, you can use lp:xyz now
[12:28] <lool> Mirv: let me update the wiki with the new message and the new URL
[12:28] <lool> Mirv: BTW code.lp.net is always wrong in Vcs-Bzr as it's meant to be a bzr branchable URL
[12:29] <didrocks> sil2100: does this sound good to you?
[12:29] <lool> Mirv: oh it is branchable!  my bad
[12:29] <cjwatson> I was about to say :)
[12:30] <Mirv> lool: yeah either one is branchable. the severe downside to using lp: links in Vcs-Bzr instead of proper url is that vim colors it bright red!
[12:34] <cjwatson> we should fix our vim configuration :)
[12:34] <lool> Mirv: it's for you to easily find the branch when opening control!
[12:35] <Mirv> also we'd need to fix gnome-terminal to detect lp: links, another downside
[12:35] <lool> the upside is that it's short and stable
[12:37] <didrocks> sil2100: did we loose you? ;)
[12:39] <Mirv> lool: ok took your dailyrelease wiki page changes into account and updated the branch
[12:39] <lool> Mirv: ah I was preparing an updated branch
[12:39] <lool> looking
[12:39] <Mirv> didrocks: https://wiki.ubuntu.com/DailyRelease/InlinePackaging?action=diff&rev2=21&rev1=20 <- so no homepage would be added anymore for LP projects, and slightly different text
[12:39] <cjwatson> lool: It's not very discoverable, but you can use http://bazaar.launchpad.net/+branch/ubuntu-touch-customization-hooks
[12:39] <lool> Mirv: looks good
[12:39] <cjwatson> Which is not horribly much longer and is stable across changes in what the focus branch points to
[12:40] <lool> cjwatson: what's against lp:xyz?
[12:40] <lool> except perhaps people who manage to miss the lp plugin
[12:40] <sil2100> didrocks: in the middle of lunch ;) But reading up now
[12:40] <didrocks> Mirv: sounds good to me, thanks!
[12:40] <cjwatson> As Mirv said, some syntax highlighters fail on it
[12:40] <lool> Mirv: looks good
[12:40] <sil2100> didrocks: looking at the landing plan
[12:41] <lool> cjwatson: do you think we should allow for lp: urls in Vcs-Bzr, that is is it ok to require lp plugin to be there?
[12:41] <sil2100> didrocks: ok, dealing with those
[12:41] <didrocks> sil2100: thanks!
[12:42] <lool> I'm sure there are many lp: Vcs-Bzr, so I'd like to know whether we want to get rid of them, or whether we will update the syntax file to accept it
[12:42] <lool> this feels like a super trivial question though, sorry
[12:43] <cjwatson> lool: I guess I don't much mind
[12:43] <lool> I think the set of people who don't mind using bzr don't mind the lp: URLs or they've switched to git  :-)
[12:44] <lool> so we should update the vim syntax
[12:45] <lool> Mirv: mind reviewing https://code.launchpad.net/~lool/ubuntu-touch-customization-hooks/dh-flags/+merge/187495
[12:45] <lool> Mirv: you know for who this one is
[12:45] <sergiusens> fginther, hey, can you snoop at http://10.97.2.10:8080/view/click/job/notes-app-click/
[12:46] <sergiusens> fginther, I could use the pbuilderjenkins plugin there if it ignored the fact that it had a nesting conflict on the debian dir btw.. should be very streamable into upstream merger
[12:47] <Mirv> lool: done
[12:48] <ralsina> didrocks: hi! I am trying to figure out what happened with qtdeclarative5-ubuntu-click0.1 and click-update-manager I had them in a landing request, they are built in daily release but they seem not to have landed and asac couldn't find the changes to pull. I am guessing we slipped somehow... can we get them in the next image?
[12:48] <didrocks> ralsina: let me look for them
[12:48] <fginther> morning
[12:48] <ralsina> didrocks: awesome, thanks
[12:49] <didrocks> ralsina: this was "fixes for download service daemon and packages that use it"?
[12:49] <asac> ralsina: which landing plan entry is it? guess that would help didrocks to spot your ticket :)
[12:49] <didrocks> (line 57 of landing plan)
[12:49] <ralsina> asac, didrocks: no, this is 87
[12:49] <asac> ralsina: ask? or plan?
[12:49] <lool> Mirv: <3
[12:50] <ralsina> landing ask #87
[12:50] <asac> right
[12:50] <asac> that one i couldnt figure if we took it or if its in flight or stuck or whatever
[12:50] <didrocks> ralsina: ok, there is some packaging that are common with line 57, can you check if that one is still valid or not?
[12:50] <ralsina> didrocks: I think all of 57 is in
[12:50] <asac> didrocks: i think that one was done
[12:51] <asac> it was landing no. 1 ... and that is done
[12:51] <didrocks> ok, let's cross it then
[12:51] <asac> i didnt spot it during cleanup... will do
[12:51] <asac> for you (as debt :))
[12:51] <didrocks> so indeed, your changes are not staged
[12:51] <ralsina> I am going to start adding revnos to the asks, just in case :-)
[12:51] <didrocks> let me look if line 87 already landed
[12:51] <didrocks> asac: thanks ;)
[12:52] <didrocks> ralsina: if you look at your clickmanager-plugin trunk
[12:52] <didrocks> you see a merge back, right?
[12:52] <didrocks> with 0.1+13.10.20130924.1-0ubuntu1
[12:53] <ralsina> looking...
[12:53] <ralsina> didrocks: it seems that one is landed, and click-update-manager isnot
[12:53] <asac> didrocks: oh we did a manual publish and we might not have the merge back? ic
[12:53] <didrocks> (released from rev 21)
[12:53] <didrocks> ralsina: https://code.launchpad.net/~ubuntuone-hackers/click-update-manager/trunk
[12:53] <didrocks> asac: no, all is good is fine
[12:54] <ralsina> didrocks: yes, that one is good
[12:54] <asac> didrocks: so its already in?
[12:54] <didrocks> ralsina: so click-update-manager landed right? this is all you need?
[12:54] <asac> anyway... /me just moves out of discussion
[12:54] <didrocks> as the qt* is from this package
[12:54] <ralsina> weird
[12:54] <asac> http://people.canonical.com/~ogra/touch-image-stats/20130919.changes
[12:54] <asac> thats the last image that has something about click-update-manager
[12:54] <asac> everything after didnt touch it
[12:55] <asac> that was landing no. 1 afaik (ask 57)
[12:55] <ralsina> didrocks: in -proposed I see click-update-manager 0.1+13.10.20130919.2-0ubuntu1
[12:55] <asac> ralsina: proposed?
[12:55] <asac> image or the archive proposed?
[12:55] <didrocks> ralsina: yeah, I was looking at the image, it's not in
[12:55] <ralsina> asac: from the proposed image today
[12:55] <cjwatson> $ rmadison click-update-manager
[12:55] <cjwatson> click-update-manager | 0.1+13.10.20130924.1-0ubuntu1 | saucy/universe | source, amd64, armhf, i386
[12:55] <ralsina> ok, so it's in archive and not in image?
[12:55] <didrocks> click-update-manager | 0.1+13.10.20130924.1-0ubuntu1 | saucy/universe | source, amd64, armhf, i386
[12:55] <cjwatson> it's in the release pocket in the archive
[12:55] <asac> ralsina: its not in there afaict
[12:55] <ralsina> awesome then
[12:55] <cjwatson> (rmadison is fastish now, just use it)
[12:56] <didrocks> cjwatson: yeah, I start to like it again ;)
[12:56] <ralsina> so, next image?
[12:56] <didrocks> ralsina: let me check in which image this is in
[12:56] <didrocks> it should have been from the one from today
[12:56] <asac> click-update-manager0.1+13.10.20130919.2-0ubuntu1
[12:56] <asac> thajts the one that i see last ended up on the image
[12:56] <asac> it must be stuck somewhere or will be in the next image
[12:57] <asac> didrocks: oh there was a click stack landing this morning
[12:57] <asac> maybe Mirv did that and its all in the next image :)
[12:57] <didrocks> it should have been at least in http://people.canonical.com/~ogra/touch-image-stats/20130925.changes
[12:57] <asac> didrocks: right ... it was done by mirv today
[12:57] <asac> it was me not properly using the landing no.
[12:57] <lool> no, it migrated one hour ago
[12:57] <didrocks> asac: it landed to distro yesterday
[12:57] <asac> will update
[12:57] <didrocks> we are the 25, not 24, right?
[12:57] <lool> didrocks: it migrated one hour ago to release pocket
[12:58] <lool> https://launchpad.net/ubuntu/+source/click-update-manager
[12:58] <asac> didrocks: the commit says that, but we published it today afaict
[12:58] <didrocks> lool: ah, that makes sense, do we no why?
[12:58] <asac> didrocks: that explains why its not on the image
[12:58] <didrocks> asac: no, it entered yesterday midday to -proposed
[12:58] <didrocks> not sure why it took a day to migrate though
[12:58] <didrocks> ralsina: in short: yeah, next image ;)
[12:58] <asac> didrocks: ok i fix the bookkeeping and refer to the right landing here
[12:59] <cjwatson> didrocks: because it needed me to manually remove an unbuilt binary on powerpc, which Mirv asked for at 11:27 UTC today and I immediately did
[12:59] <didrocks> asac: ok, thanks
[12:59] <didrocks> cjwatson: ah, making sense, perfect
[12:59] <ralsina> didrocks: awesome, works for me :-)
[12:59] <asac> nice someone alreawdy said its in build #64 on the right :)
[12:59] <asac> not sure if after or before... next time we should read the comments ... hehe
[12:59] <asac> ralsina: ok all cleared
[12:59] <asac> nice one
[13:00] <asac> guess it wasnt build yesterday
[13:00] <asac> and was buld this morning so we took it
[13:00] <asac> didrocks: so is there anything in PROPOSED that we want?
[13:00] <ralsina> last comment I saw was "check 61 or 62" got all confused ;-)
[13:00] <didrocks> asac: I'm scanning regularly, nothing atm
[13:00] <asac> otherwise we should kick an image so we can start landing after standup
[13:00] <asac> we wanted to kick an image earlier :)
[13:00] <asac> just ask ogra if you feel its time
[13:00] <asac> lol
[13:01] <ogra_> asac, well, i kicked an image at 10am :P
[13:01] <asac> right
[13:01] <asac> but there was nothing in
[13:01] <asac> and we have good stuff now
[13:01] <asac> the results on dashboard look good enough
[13:01] <asac> to call it a good checkpoint
[13:01] <asac> let me double check
[13:01]  * ogra_ would like to do the bunch of seed changes for eth next image 
[13:01] <mfisch> Mirv: looking
[13:01] <ogra_> so we have thse off the plate
[13:01] <asac> ogra_: well, you can do it right after
[13:01] <didrocks> yeah, because if we add something now, we won't have time with the migration and so on
[13:01] <asac> so yeah. lets kicfk an image and dont release the current. thats good enough
[13:02] <didrocks> so yeah, ogra_ can do all the seeds changes
[13:02] <didrocks> and then, we kick the image
[13:02] <asac> before?
[13:02] <asac> didrocks: seed changes take 2 hours at least :)
[13:02] <ogra_> why hold tjem back ?
[13:02] <ogra_> is there anything urgent we need the image for ?
[13:02] <asac> yes
[13:02] <asac> we landed a bunch of good things
[13:02] <asac> we flushed low hanging fruit stacks
[13:02] <ogra_> and making pdf work isnt a good thing ?
[13:02] <asac> its good to checkpoint and then proceed on the bigger landings
[13:02] <asac> multimedia
[13:02] <ogra_> or making google account mgmt work
[13:02] <didrocks> asac: we do have click + sdk which are interesting
[13:03] <asac> didrocks: right
[13:03] <didrocks> (waiting)
[13:03] <didrocks> yeah, some services as well
[13:03] <asac> ogra_: just kick an image and upload your seed change if it has a landing slot
[13:03] <didrocks> can make sense to kick an image then
[13:03] <didrocks> (I didn't remember the sdk part)
[13:03] <asac> we hgave a good set. we wanted to go in smaller, but more frequent steps
[13:03] <ogra_> ok
[13:03] <asac> lets not forget and start waiting till everything is in. there will be a new image for the next shot
[13:03] <ogra_> running
[13:03] <asac> didrocks: so maybe think about what should be done for next shot for real then
[13:04] <asac> and discuss with all so all are happy :)
[13:04] <asac> hehe
[13:04] <asac> nice
[13:04] <Mirv> mfisch: was merged already, nothing anymore
[13:04] <asac> !!
[13:04] <asac> good team work
[13:04] <asac> fast and furioyus image production
[13:04] <didrocks> asac: right now, I assign them to sil2100 (+ ogra with the seed changes), so let's see when he's back from lunch
[13:04] <Mirv> asac: it was stuck and I got colin to unblock it. it was blocked because of powerpc.
[13:04] <didrocks> Mirv: we all figured it out, no worry ;)
[13:05] <didrocks> thanks for handling that!
[13:05] <mfisch> Mirv: ok
[13:05] <Mirv> yeah, ok
[13:05] <asac> didrocks: i dont know what seed chagne this is about. if its about multimedia stack landing, just triple check that we get everything and well testing
[13:05] <asac> tested
[13:05] <asac> but you will sort it
[13:05] <asac> Mirv: oh cool. nice one
[13:05] <ogra_> asac, no, its about a bunch of piled up sered change requests fro single packages
[13:05] <didrocks> asac: there are other seed changes that ogra_ wanted to do
[13:06] <ogra_> *seed
[13:06] <asac> ok if they are in spreadsheet etc. then its going to happen
[13:06] <asac> or not if there are good reasons :)
[13:06] <asac> lol
[13:06] <asac> ogra_: what i would like to know is where is lightdm and the multimedia stuff
[13:07] <asac> we have to pay extra pull on those
[13:07] <asac> to get them properly released and in shape i think
[13:07] <Mirv> lool (/asac): ok customization-hooks in http://10.97.0.1:8080/view/cu2d/view/Saucy/view/Misc/ and building (actually built already), if you want misc stack published when it has completed - seems like phablet-tools, upstart-app-launch, ubuntu-themes + ubuntu-touch-customization-hooks - ping didroc_ks, sil21_00, cypherm_ox or kenvandi_ne later in the evening
[13:07] <asac> didrocks: ^^
[13:07] <ogra_> lool, which reminds me, you didnt aswer about the cordiva stuff above (line 67 on landing asks) iirc, you were the one who blocked it due to broken or missing tests back then, can the seed change land now ?
[13:08] <ogra_> asac, lightdm sits in proposed and is supposed to fix all issues ... ubuntu-touch-session just needs the merge re-applied
[13:09] <lool> Mirv: I'm fine with upstart-app-launch and ubuntu-touch-customization-hooks; can't comment on ubuntu-themes, but that seems like it would stay in proposed?
[13:09] <lool> phablet-tools is fine I guess
[13:09] <ogra_> asac, for multimedia i dont know the status of the thumbnailing, that might take a while until we can fix it (needs a completely new function to be written for gst 1.0)
[13:09] <lool> ogra_: Yes, I've updated the ask and pinged dbarth about the tests again
[13:09] <didrocks> asac: those are the first listed in landing asks, right? (lightdm in particular)
[13:09] <didrocks> the multimedia, yeah, it seems touchy
[13:09] <lool> ogra_: I dont want to add a landing plan entry until we have a testing story working otherwise we wont have one
[13:09] <ogra_> asac, and without thumbnailing (even though everything else works flawless and has been 100 times tested) we cant land because it breaqks one test
[13:09] <asac> didrocks: lightdm is a very old landing ask, yes
[13:09] <lool> albeit technically, adding this has little chance of breaking our image
[13:09] <ogra_> lool, thats fine, just wanted to know where that stands
[13:10] <lool> I want us to be able to detect regressions of these bits
[13:10] <asac> bounced a few ties... i think there is even a landing plan slot projected in the hope they come along :)
[13:10] <didrocks> Mirv: lool: whitelist refreshed as per doc?
[13:10] <Mirv> lool: theme would be in proposed yes, phablet-tools "Adding in phablet-timezone-setup." (Chris Wayne)
[13:10] <asac> didrocks: it requires touch session and lightdm and we need to test the hell out of it
[13:10] <Mirv> didrocks: not checked, should be done, I was just about to write that it'll need to be done if not yet
[13:10] <ogra_> didrocks, mutimedia is fine, i dont think any feature ever got that much testing since we do the phone :) its just that we know there is no thumbnailing support during video playback which breaks one test
[13:10] <lool> ogra_: did you test the timezone stuff?
[13:11] <asac> didrocks: at best test that with utah command tools to ensure it doesnt break automation ... sergiusens has a setup to help
[13:11] <didrocks> ogra_: is there any plan to finish this thumbnailing before shipping?
[13:11] <ogra_> lool, nope, and i still wait for stgraber to appear ... it didnt feel like he was happy with the approach
[13:11] <didrocks> asac: right
[13:12] <ogra_> didrocks, well we try but our core dev for that is on vac, bfillers team is now helping out with that
[13:12] <didrocks> ogra_: ok, so it's still pending
[13:12] <ogra_> didrocks, i personally would just drop the test (temporary)
[13:12] <didrocks> let's see how it goes this week
[13:12] <didrocks> we can relax the constraint a little bit if we need to ship it ASAP, yeah
[13:13] <didrocks> so, let's give some more time and see
[13:13] <sil2100> didrocks: regarding the ubuntu-system-settings - there is mention about the bluetooth settings to test
[13:13] <didrocks> sil2100: yeah, you can check that one with seb128 I guess
[13:13] <didrocks> sil2100: indicator-bluetooth already landed
[13:13] <didrocks> we just need the -settings part
[13:14] <lool> ogra_: but hte lxc-android-config bits are in saucy already
[13:14] <didrocks> thostr_lunch should be able to help as well
[13:14] <ogra_> lool, huh ?
[13:14] <ogra_> lool, which ones
[13:14] <lool> https://launchpad.net/ubuntu/+source/lxc-android-config/0.101
[13:14] <lool> the timezone ones
[13:15] <sil2100> didrocks: I found the merge, but I'll poke seb128 about this
[13:15] <ogra_> lool, pittis change supersedes that
[13:15] <ogra_> thats a former commit that will have to be reworked
[13:16] <didrocks> sil2100: thanks!
[13:23] <Mirv> didrocks: can you refresh the whitelist for the misc stack release?
[13:24] <didrocks> Mirv: done
[13:24] <Mirv> didrocks: thanks
[13:25] <didrocks> yw
[13:25] <ChickenCutlass> didrocks, still working on the last details for Multimedia stack to land.  I will ping you when we are ready
[13:25] <lool> ogra_: so do we need to hold phablet-tools from going to archive?
[13:25] <didrocks> ChickenCutlass: excellent, thanks!
[13:26] <ogra_> lool, which merge is that ?
[13:27] <lool> ogra_: the one adding timezone-setup flag
[13:27] <lool> or binary rather
[13:27] <ogra_> lool, we should hold it back, yeah
[13:28] <ogra_> was it merged already ?
[13:28]  * ogra_ chacks
[13:28] <lool> it's in PPA
[13:28] <ogra_> (even without typo)
[13:28] <ogra_> ah, fine, keep it there then
[13:28] <lool> r194
[13:28] <lool> ogra_: I'd like us to land misc stack
[13:28] <lool> well, I just would like to land touch-customization-hooks for mfisch really
[13:29] <ogra_> lool, well, i think it will break the way it is in the PPA now
[13:29] <didrocks> lool: we can manually back out something from the publication if needed
[13:29] <sil2100> didrocks, asac: there seems to be a problem with the bluetooth system settings
[13:29] <ogra_> it will need pittis changes and some re-work
[13:29] <Mirv> ogra_: so the mere existence of the new script might hurt, even though no existing scripts were modified?
[13:29] <didrocks> (but it's a hack, it wasn't designed for that)
[13:29] <didrocks> sil2100: ah? it's not ready? does it regress what we have already or just non functional?
[13:30] <ogra_> Mirv, it wont do the right thing
[13:30] <ogra_> i dont think it will break
[13:30] <lool> didrocks, Mirv: So IIUC, we could run the misc stack with build parameters to just publish 3 out of 4?
[13:30] <plars> asac: one crash still on the unity tests: http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4440/unity8-autopilot/
[13:30] <Mirv> ogra_: lool: ok, I'll leave you to it (misc stack publishing), but it's now ready and didier refreshed the whitelist so any cu2d vanguard can publish it
[13:30] <plars> asac: unity-scope-home
[13:30] <lool> Mirv: thanks a lot
[13:31] <ogra_> lool, can we just trigger a new build of the same version ? if so, just delete it from the ppa
[13:31] <sil2100> didrocks: well, the problem is that due to a probable bug in indicator-bluetooth I won't be able to test the new features locally
[13:31] <sil2100> On my device I mean
[13:31] <didrocks> lool: no, that's not supported that way, we need to mess with the file system unfortunately
[13:32] <didrocks> sil2100: does it regress the current experience?
[13:32] <didrocks> (compared to current system-settings)
[13:32] <lool> ogra_: it will be detected when "check"ing the stack
[13:32] <sil2100> No ;)
[13:32] <plars> asac: no more apt-get updates too
[13:32] <didrocks> sil2100: ok, maybe let's publish system-settings if other things are working then, and open a bug on indicator-bluetooth?
[13:33] <ogra_> lool, then just let it in, iit will get a fix soon and i dont think it is actually used beyond the customization stuff
[13:33] <didrocks> seb128: it wasn't ready then? can you track that please? ^
[13:33] <seb128> didrocks, shrug, it's ready and works on some system, seems like sil is hitting /dev permissions issues that
[13:34] <seb128> - have nothing to do with system settings
[13:34] <lool> ogra_: I also dont think hurts
[13:34] <seb128> - concerns only on/off (you can still pair devices)
[13:34] <lool> Mirv, didrocks: Let's just publish misc stack then
[13:34] <seb128> - you really want to block important fixes because bluetooth (which is new) is not perfect?
[13:34] <seb128> didrocks, ^
[13:34] <didrocks> seb128: did you backlog? I told I won't block on this
[13:34] <didrocks> 15:32:58       didrocks | sil2100: ok, maybe let's publish system-settings if other things are working then, and open a bug on indicator-bluetooth?
[13:34] <didrocks> seb128: ^
[13:34] <seb128> didrocks, no, I read your "it wasn't ready then"
[13:35] <seb128> ok, thanks
[13:35] <didrocks> seb128: I'm just asking you as the feature was both listing indicator-bluetooth + system-settings if you can track this new bug to be fixed
[13:35] <seb128> didrocks, sure can
[13:35] <didrocks> thanks ;)
[13:35] <seb128> didrocks, we are discussing it with charles already
[13:35] <seb128> didrocks, thanks ;-)
[13:36] <didrocks> yw
[13:36] <didrocks> sil2100: so please go ahead and publish
[13:36] <didrocks> lool: fine for me to publish the whole stack
[13:36] <didrocks> with*
[13:37] <sil2100> ACK
[13:38] <asac> plars: you say from image 63 on we see the real thing?
[13:38] <asac> :)
[13:38] <asac> sil2100: bluetooth?
[13:38] <asac> wasnt that always broken?
[13:39] <plars> asac: yep
[13:39] <ogra_> lets unbreak it then :)
[13:39] <ogra_> it always worked ... from commandline
[13:40] <asac> ogra_: bluetooth is now busted in kernel?
[13:40] <lool> didrocks: So I'll try running it!
[13:40] <asac> you say?
[13:40] <ogra_> asac, no
[13:40] <didrocks> lool: sure!
[13:41] <ogra_> asac, BT always worked ... but had no UI
[13:41] <asac> wait... that means for me that bluez cmd line tools work
[13:41] <asac> but nothing else :)
[13:41] <ogra_> asac, you should be able to connect devices
[13:41] <ogra_> yeah
[13:41] <lool> cjwatson: just to confirm, I'll upload ubuntu-themes as part of that stack; I've not added any hint and the expectation is that it will remain in -proposed
[13:41] <asac> so rephrase if you mean something else
[13:41] <lool> until after beta is released
[13:41] <asac> ogra_: so either bluez changed or kernel
[13:41] <asac> did they?
[13:41] <cjwatson> lool: OK
[13:41] <cjwatson> infinity: ^-
[13:41] <asac> ogra_: or did we mess it up in android?
[13:42] <ogra_> asac, BT cmdline works since several weeks, nothing should have changed there ... but we never had any UI parts connected to that (BT indicator is a no-op)
[13:42] <sil2100> asac: yes, but it was supposed to be un-broken
[13:42] <sil2100> asac: seems that it's *not*
[13:42] <asac> sil2100: what exactly did we land/expect to land? can you shed some light on that :)
[13:42] <didrocks> lool: btw, how are you going to publish?
[13:43] <asac> sil2100: might be that its just in landing right now and not yet on the images
[13:44] <asac> check the spreadsheet i guess
[13:44] <ogra_> asac, BT indicator fixes to make the toggle work i think
[13:44] <asac> how can bt indicator break cmdline?
[13:45] <asac> ogra_: so you say its a bluetooth-indicator regression? or a fix we should fast path?
[13:45] <charles> to toggle, the bt indicator tries to write a block entry to /dev/rfkill
[13:45] <asac> iirc there was a bluetooth-indicator in the stack
[13:45] <ogra_> asac, reggression ?
[13:45] <charles> if /dev/rfkill isn't readable or writable, the bluetooth toggle in the indicator won't work at all
[13:45]  * ogra_ feels like he misses info
[13:45] <didrocks> asac: it was already published
[13:46] <charles> and, by extension, the same toggle in system-settings won't work either
[13:46] <ogra_> asac, so whjat exactly is broken now ?
[13:46] <didrocks> it seems that it's just a /dev perm issue, seb128 is tracking it
[13:46] <asac> ok so what i hear is that the system stetings landing didnt work as good as we thought
[13:46] <didrocks> so let's go on meanwhile, the settings don't regress bluetooth anyway, let's move :)
[13:46] <ogra_> asac, it cant, we dont have logind
[13:47] <asac> right. so i dont understand what the problem is really :)
[13:47] <ogra_> unless that was taken into account in the expectations
[13:47] <ogra_> we wont have permissions to change stuff
[13:47] <didrocks> asac: we thought it will bring bluetooth support working (as discussed with seb), but it seems it doesn't work everywhere
[13:47] <asac> right
[13:47] <asac> ok. seems we understand why and so be it :) ... wait for lightdm basically
[13:47] <ogra_> didrocks, where doesnt it ?
[13:47] <asac> lets ensure we dont miss an opportunmioty to land that WELL TESTED!!!
[13:47] <didrocks> ogra_: on sil2100's phone (mako) at least ;)
[13:47] <ogra_> didrocks, i know we used it durign the sprint
[13:47] <ogra_> on mako
[13:47] <seb128> asac, didrocks, ogra_: it brings bluetooth support (you can pair devices), it doesn't let you turn off bluetooth though
[13:48] <ogra_> seb128, aha
[13:48] <asac> right
[13:48] <asac> thats a polkit thing it feels
[13:48] <seb128> could be
[13:48] <seb128> charles, ^ do you use polkit to write to /dev?
[13:48] <asac> seb128: you could try by using the new ubuntu-touch-session
[13:48] <ogra_> seb128, thanks, the first informative sentence in that conversation :)
[13:48] <asac> seb128: this would give us more confidence and you would be unblocked
[13:48] <asac> but guess thats not in CI
[13:48] <asac> ogra_: can you put that in CI?
[13:48] <ogra_> charles, if you talk to the device directly we might need to adjust the udev rules
[13:49] <charles> seb128, ogra_: indicator-blueooth's talking to the device directly
[13:49] <ogra_> asac, not really keen to since rolling back is a lot harder then
[13:49] <ogra_> charles, ok
[13:49] <ogra_> root@ubuntu-phablet:/# ls -l /dev/rfkill
[13:49] <ogra_> crw-r--r-- 1 root root 10, 63 Sep 25 12:05 /dev/rfkill
[13:50] <ogra_> so we just need to update the udev rule
[13:50] <asac> ok. well, non CI stuff will get harder to get in over time... thats for sure
[13:50] <asac> :)
[13:50] <charles> ogra_: +1
[13:50] <ogra_> asac, willing to live with that :)
[13:50] <ogra_> charles, can you prove it works if you make the device 0777 ?
[13:50] <asac> ogra_: so please put your ubuntu-touch-session debs somewhere
[13:50] <asac> so we can test them
[13:50] <asac> before we promote
[13:50] <ogra_> asac, will do, one thing at a time :)
[13:51] <ogra_> (on a sidenote: the image is done)
[13:51] <asac> which image?
[13:51] <seb128> sil2100, ^ can you change the permission to 777 and test again?
[13:51] <asac> 64?
[13:52] <asac> ogra_: wait... rfkill. we had fixed the groups etc. there shouldnt be a problem
[13:52] <asac> oh wait... this needs to get a group set
[13:52] <asac> right
[13:52] <asac> nevermind
[13:54] <sil2100> seb128: will do
[13:54] <seb128> sil2100, thanks
[13:54] <dobey> what was the branch where the CI config lives?
[13:57] <sil2100> seb128: just give me a minute, need to finish testing something else
[13:57] <seb128> sil2100, sure, no hurry
[13:58] <charles> ogra_: I can't test with 0777 this minute, I'm about to be afk
[13:59] <ogra_> if someone can test it http://paste.ubuntu.com/6154560/ would be the fix
[14:00] <seb128> sil2100, ^
[14:00] <seb128> ogra_, sil2100 said he's going to give it a try
[14:00] <ogra_> yeah, saw that
[14:01]  * ogra_ isnt in a hurry and the fix is easy enough 
[14:01] <charles> sil2100, ty
[14:01] <ogra_> we just might need to back out pittis change since thats back to discussion status
[14:05] <sil2100> charles, seb128, ogra_: added 0777 to rfkill and now ubuntu-system-settings enables/disables bluetooth correctly, but the indicator still does not
[14:05] <sil2100> (strangeness)
[14:06] <didrocks> sil2100: you did restart the indicator?
[14:06] <sil2100> charles, seb128, ogra_: not sure if it's related, but unity8.log has this: file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Unity/Indicators/MenuItemFactory.qml:55: TypeError: Cannot read property 'ext' of null
[14:06] <sil2100> No
[14:06] <sil2100> Maybe indeed I should
[14:06] <ogra_> yeah
[14:07] <kgunn> fginther: thank you for all your help recently!!! it feels so good to wake up and actually see ci tests passing!
[14:08] <fginther> kgunn, your welcome. it also feels good to wake up and not have a dozen people pinging you :-)
[14:09] <kgunn> :))
[14:09] <kgunn> well i do appreciate it
[14:09] <didrocks> asac: sil2100: lool: ogra_: ok guys, feeling a little bit better, so will try to exercice a little bit, back in ~1 hour
[14:13] <ogra_> Mirv, i see you are also assigned to the timezone stuff from pitti. seems that needs to be rewritten forst
[14:13] <ogra_> *first
[14:14]  * lool runs misc stack
[14:19]  * ogra_ sets the timezone stuff to blocked
[14:19] <lool> oh it looks like someone had run misc stack already
[14:19] <lool> but at lsat I found how to do it
[14:19] <ogra_> Mirv did i think
[14:21] <lool> weird, it says 10.99.244.110
[14:21] <lool> but no login
[14:22] <lool> it sounds like someone using the command-line did it at least
[14:22] <lool> anyway
[14:22] <lool> so looking at platform stack now
[14:22] <fginther> sergiusens, for the click job, does there need to be a lp:~phablet-team/notes-app/click_wrapper branch for each app, or is that really generic?
[14:23] <lool> the tests rae running in platform stack
[14:23] <sergiusens> fginther, we can make a generic one once ogra_ gets xnox's changes to the seed in
[14:26] <lool> sil2100: I see yo uadded an entry for landing content-hub, cool; do you know where the gallery changes are if any?
[14:26] <sil2100> lool: I didn't add any entry, I think Didier added it - I'm in the middle of testing services now
[14:26] <ogra_> sergiusens, OH ! thanks for the reminder
[14:27] <sil2100> Sadly I don't see any working ubuntu-keyboard AP tests still
[14:27]  * ogra_ adds it to the spreadsheet, i totally forgot that one
[14:27] <sil2100> lool: not sure about any gallery changes sadly
[14:27] <lool> sil2100: let's ping Ken when he came up
[14:27] <lool> *comes
[14:28] <sil2100> lool: in the meantime I'll publish ubuntu-keyboard if all is ok
[14:29] <sil2100> If you don't mind
[14:29] <lool> I don't mind
[14:36] <lool> ogra_: any regression in 63 that would stop us from promoting it?
[14:36] <lool> I see 64 was built and is being tested
[14:37] <ogra_> lool, do you really want to publish each and every image ?
[14:37] <sil2100> asac, lool: do you guys know if we're running the ubuntu-keyboard tests as part of image testing?
[14:37] <lool> ogra_: if it passes  :-)
[14:37]  * ogra_ would wait for the last build of the day 
[14:37] <asac> sil2100: not yet... last we look they didnt pass at all
[14:37] <lool> sil2100: never seen that, check http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4439/ perhaps?
[14:37] <asac> we can start adding, but bfiller said they are not supposed to run right now
[14:38] <lool> asac: do you care to promote 63?
[14:38] <lool> or is that wasting popey's / ogra's time to confirm
[14:38] <asac> lool: its a backup, but not really has much content so thought we omit it
[14:38] <asac> and just go back in case something is busted :)
[14:39] <lool> ogra_: ^
[14:39] <popey> lool: i already have 63 on my device
[14:39] <lool> asac: yup fair enough
[14:39] <sil2100> Thanks
[14:39] <sil2100> I have been informed by Bill that they're working now, just need a special way of running - and they seem to be running right now
[14:39] <sil2100> On my machine at least
[14:40] <sil2100> So far so good
[14:40] <lool> sil2100: might want to ping plars to add them to the image tests
[14:40] <bfiller> asac: the ubuntu-keyboard autopilot tests are working now (as of last night) so they can be added to the daily image testing
[14:40] <lool> plars: ^
[14:40] <ogra_> lool, asac, i would say lets try to promote first and last build of a day as a rule of thumb
[14:41] <ogra_> promoting 6 of them just because we did 6 seem like a waste of tester time
[14:41] <sil2100> plars: ping
[14:41] <sil2100> All passed, publishing ubuntu-keyboard
[14:41] <plars> sil2100: hi
[14:42] <plars> sil2100: ubuntu-keyboard-autopilot right?
[14:42] <plars> sil2100: I'll take a look
[14:43] <asac> bfiller: nice
[14:43] <bfiller> plars: only thing is the way the test is requires unity8 to be stopped and maliit-server to be run with -testabiltiy
[14:43] <sil2100> plars: yes, ubuntu-keyboard-autopilot - all that is needed is to run maliit-server with -testability and shutting down unity8 beforehand
[14:43] <bfiller> plars: not sure how you guys set that up but won't pass unless that happens
[14:43] <sil2100> (as we do with unity8-autopilot already)
[14:44] <lool> rsalveti: https://launchpad.net/ubuntu/+source/android/20130924-2218-0ubuntu1 are the other half of the mir fix?
[14:44] <lool> looks like it's in saucy-release then
[14:44] <rsalveti> lool: yes, already updated the landing page
[14:45] <ogra_> rsalveti, wasnt there a kernel change too for this one ?
[14:45] <ogra_> or was that unrelated
[14:45] <lool> rsalveti: the ask or the landing itself?
[14:45] <lool> I'll clarify that android is INARCHIVE and mir needs a mp to land
[14:45] <rsalveti> lool: landing
[14:46] <rsalveti> lool: we already have 2 separated lines for them
[14:46] <rsalveti> lool: we should put it inarchive, why inflight?
[14:46] <rsalveti> as we're only covering the android side in there
[14:47] <rsalveti> we have a separated line for the mir one
[14:47] <lool> rsalveti: oh ok, I thought it was a single landing, i get it now
[14:47] <ogra_> inflight means "building"
[14:47] <lool> rsalveti: I've removed the reference to the merge proposal from the first landing
[14:48] <rsalveti> lool: ok, thanks
[14:48] <lool> rsalveti: can I put you as PoC for mir part?
[14:48] <rsalveti> lool: yes
[14:48] <sergiusens> bfiller, plars sil2100 since unity8 and maliit-server are upstart jobs can't we use the initctl set-env QT_TESTABILITY=1 flag? (need to confirm the exact var)
[14:50] <ogra_> sergiusens, we should put that into pre-start scripts for everything and make it switchable by touching a file in ~/
[14:50] <plars> that would be useful
[14:50] <sergiusens> ogra_, hmm, we made a lengths deal to avoid that due to security
[14:51] <ogra_> well, then put it into a place ony root can write to
[14:51] <ogra_> /userdata/.testable
[14:52] <ogra_> if a user has root you have lost anyway :)
[14:52] <sergiusens> ogra_, if jdstrand agrees, then I'm good
[14:52] <lool> rsalveti: so I think there was a pulseaudio part to diwic's fix, did you manage to test/upload this one?
[14:52] <sergiusens> unity7 exports it by default today I guess
[14:52] <rsalveti> lool: I'm testing another patch that diwic had first, but will upload in a bit
[14:54] <asac> ogra_: lets see what we can do ... at least 1 image per day i would say
[14:55] <asac> but make sense to throw out the last we have before we call it EOD
[14:55] <asac> ... even though i would like to figure how to have a longer day with west coast involvement etc.
[14:55] <asac> bfiller: can you talk to plars about enabling your keybord tests?
[14:55] <sil2100> asac, lool: testing content-hub doesn't seem possible, I guess we indeed need some additional changes in gallery-app to have this testable
[14:55] <asac> bfiller: we dont have a good process yet, so do some handwaving to him for now
[14:55] <sil2100> asac, lool: but I guess we can publish since it doesn't break anything for sure
[14:55] <plars> asac: we've already been discussing it :)
[14:56] <asac> sil2100: why cant we test content-hub and the gallery-app?
[14:56] <asac> i mean the existing gallery app?
[14:56] <asac> if that breaks we shouldnt push it, but rather wait for the gallery-app fix
[14:56] <asac> plars: ok good.
[14:56] <sil2100> asac: since gallery-app still doesn't start in the picker mode
[14:56] <asac> plars: i think we should wrap that all under one shared CIguard TODO list later on :)
[14:57] <sil2100> asac: last week it didn't start in picker mode as well, so no regression I guess? Or maybe it got fixed on Monday?
[14:57] <plars> asac: you mean something like: https://blueprints.launchpad.net/ubuntu/+spec/ci-s-add-image-testsuites
[14:57] <sil2100> Since due to my sickness I might have missed something
[14:57] <asac> sil2100: how about the autopilots?
[14:57] <sil2100> asac: content-hub has no autopilots
[14:57] <asac> sil2100: autopilots for gallery-app and unity8 run on top
[14:57] <sil2100> asac: it has one manual test for changing the background which cannot be performed ;)
[14:57] <asac> those we should at least try to protect them
[14:58] <sil2100> asac: ok, I can run those, but actually those don't really test content-hub
[14:58] <asac> people told me that content-hub can have side effects on those
[14:58] <asac> so in the absense of knowing more, i would do that rather than nothing.
[14:58] <sil2100> k
[14:59] <asac> for me unity8 is what we should always run in case we dchange something in the base system and dont know its potential effects
[14:59] <sil2100> didrocks: I'll perform unity8 + gallery-app autopilot tests and if those pass, I'll publish content-hub as well - just a heads up
[15:03] <lool> sil2100: the way to test would be to change your background, and that should popup gallery-app to pick one
[15:05] <lool> sil2100: so it worked for me with image 63
[15:05] <lool> sil2100: would be good to confirm that it didn't regress
[15:05] <lool> sil2100: not sure if there are other tests
[15:05] <lool> sil2100: I had to kill other instances of the app though
[15:06] <lool> sil2100: so a) kill all apps, b) launch camera-app take a picture c) kill all apps :-)  d) launch settings and tap the images at the top in "background"  e) gallery-app comes up, select an image  f) background is changed
[15:06] <sil2100> lool: on todays image with latest content-hub you can click on the image, it starts gallery-app but not in picker mode
[15:06] <lool> sil2100: it started in picker mode for me
[15:06] <sil2100> On a clean, fresh started system
[15:07] <mmcc> Hi, I need some assistance with the CI config for ubuntuone-credentials that fginther set up. the PS Jenkins bot is complaining about our branches because they're not native packages yet, but we've postponed using daily releases. Is there a way to turn off that check?
[15:07] <lool> sil2100: Yes, I just tried again
[15:08] <sil2100> lool: I'll downgrade to the old content-hub and check if it's the same here
[15:08] <fginther> mmcc, looking
[15:08] <mmcc> fginther: thanks
[15:09] <lool> sil2100: I'll upgrade and check whether it works, I'm just upgrading to image 64 now
[15:09] <lool> I was on 63
[15:09] <sil2100> lool: what version of content-hub and gallery-app do you have?
[15:09] <lool> sorry too late, but the ones from 63
[15:09] <lool> hand't fiddled with rw today
[15:10] <sil2100> How can I check what image I'm using? Since I use the one from 20130924.1
[15:11] <fginther> mmcc, is there a packaging branch?
[15:11] <lool> sil2100: worked with 64
[15:11] <lool> sil2100: system-image-cli -i
[15:12] <sil2100> heh, build number 0
[15:12] <mmcc> fginther: there's a separate branch for packaging, yes: https://code.launchpad.net/~ubuntuone-control-tower/ubuntuone-credentials/packaging-dailies
[15:12] <lool> sil2100: uh
[15:12] <lool> I have content-hub | 0.0+13.10.20130920-0ubuntu1 | http://ports.ubuntu.com/ubuntu-ports/ saucy/universe armhf Packages
[15:12] <sil2100> Using cdimage-touch - probably that's why?
[15:12] <lool> gallery-app | 0.0.67+13.10.20130924.1-0ubuntu1 | http://ports.ubuntu.com/ubuntu-ports/ saucy/universe armhf Packages
[15:12] <lool> sil2100: oh yes, you wanted ubuntu_system
[15:12] <lool> sil2100: shouldn't break this, but we're all testing system images
[15:13] <fginther> mmcc, that *should* fix the problem
[15:14] <fginther> mmcc, I'll give it a test and get back to you
[15:14] <mmcc> fginther: sorry, I don't follow - what should fix it?
[15:14] <sil2100> I'm using this as it's the easiest thing when developing I guess
[15:14] <sil2100> lool: downgraded content-hub and will try in a moment
[15:15] <fginther> mmcc, adding the packaging branch to the build configuraton. we can't build without being able to build a package
[15:15] <mmcc> aha, ok
[15:16] <sil2100> lool: strange, but it doesn't work on my device even with the old content-hub
[15:16] <sil2100> It starts gallery-app in normal mode, I can browse images
[15:19] <lool> sil2100: you don't a couple of buttons at bottom of the screen?
[15:19] <lool> I'm not even sure how it's started in either mode; I see:
[15:19] <lool> phablet   3141 36.7  2.7 227392 52752 ?        Ssl  15:19   0:01      \_ gallery-app --fullscreen  --desktop_file_hint=/usr/share/applications/gallery-app.desktop
[15:19]  * lool pulls content-hub
[15:19] <sil2100> lool: no, when I swipe from the bottom and bring the toolbar, I have select, camera etc. there, as with the standard app
[15:22] <lool> sil2100: the buttons just show up for me without doing any swiping
[15:22] <lool> sil2100: are you on mako?
[15:22] <sil2100> lool: yes
[15:25] <sil2100> lool: so it's working for you after upgrading normally?
[15:30] <lool> sil2100: slowly trying
[15:30] <lool> sil2100: content-hub + gallery-app binary packages are all I have to update?
[15:30] <sil2100> lool: I think so? That's what I didn, but actually there's no new gallery-app
[15:32] <didrocks> need any help (I'm on image 63)
[15:34] <sil2100> didrocks: could you upgrade content-hub and try to change your wallpaper? :D
[15:34] <sil2100> didrocks: since it doesn't work on my machine
[15:34] <didrocks> sil2100: it won't work even before, right?
[15:34] <didrocks> let me try without it to see the experience first ;)
[15:34] <didrocks> then I'll upgrade with content-hub
[15:35] <sil2100> didrocks: lool says it worked on his machine with 63
[15:35] <sil2100> didrocks: on my device it doesn't work even in the old versions...
[15:35] <didrocks> hum, I'm actually on 62
[15:35] <didrocks> it doesn't work with this one
[15:35] <sil2100> lool: ^
[15:35] <didrocks> lool: please remind me how to switch to the proposed channel for downloading 63
[15:35] <sil2100> lool: so it's as on my machine ^
[15:37] <didrocks> so, if I double click
[15:37] <didrocks> on the imag
[15:37] <didrocks> image
[15:37] <didrocks> I go to "events"
[15:39] <asac> didrocks: so 64 is an image we would like to release if validated etc.?
[15:39] <asac> plars: how is love going there?
[15:39] <didrocks> asac: indeed, seeing the number of yummi changes in it
[15:39] <asac> hmm
[15:39] <asac> didrocks: didnt the home-scope land?
[15:39] <sil2100> didrocks: same here
[15:39] <asac> seems there are still crashes
[15:40] <asac> didrocks: lets look after its finished... wouldnt block for sure as we managted to get rid of one crasher and see progress
[15:40] <plars> asac: well, looks like music-app is still failing
[15:40] <didrocks> asac: asac no, it didn't land, not sure if the staged changed is the crash fix
[15:40] <ogra_> and unity is still crashing
[15:40] <didrocks> thostr_: do you know if it's that one? ^
[15:40] <asac> didrocks: check with thostr_, yes.
[15:40] <didrocks>  Don't maintain own instances of cancellables. Use cancellable from
[15:40] <asac> didrocks: show him the changes that landed maybe :)
[15:40] <didrocks>     search context. (LP: #1228260)
[15:41] <asac> didrocks: or wehere to find it
[15:41] <asac> at best
[15:41] <didrocks> asac: I'll handle it, no worry ;)
[15:41] <didrocks> discussing as well of a possible urgency due to unity7/8 and edubuntu (AGAIN)
[15:41] <ogra_> what did you break ?
[15:41] <ogra_> think of the children !
[15:41] <ogra_> :)
[15:42] <didrocks> ogra_: see #ubuntu-unity, no dash for edubuntu :p
[15:42] <ogra_> ah, i'm not in there
[15:42] <ogra_> i didnt know they use unity :)
[15:42] <plars> asac: also still seeing a crash on unity
[15:43] <thostr_> plars: is there any stacktrace?
[15:43] <thostr_> plars: then we can check if this is because of a missing fix not landing or a different issue
[15:43] <plars> thostr_: there's a .crashfile for it - http://jenkins.qa.ubuntu.com/job/saucy-touch_ro-maguro-smoke-unity8-autopilot/89/artifact/clientlogs/_usr_lib_arm-linux-gnueabihf_unity-scope-home_unity-scope-home.32011.crash/*view*/
[15:43] <didrocks> thostr_: is bug #1228260 about the crash?
[15:45] <thostr_> didrocks: that is one of 3
[15:45] <didrocks> thostr_: so that one is staged, not released yet
[15:45] <thostr_> didrocks: and we need https://code.launchpad.net/~mhr3/libunity/fix-1199715/+merge/187172
[15:46] <didrocks> thostr_: ok, that one will be after beta2 freeze though
[15:46] <didrocks> (the 2 in fact)
[15:46] <fginther> mmcc, the packaging branch didn't resolve the issue because it's not in the expected format (it's actually looking for a /debian dir to nest inside the source branch). I can fix this with a custom job, but that will take a little bit of time
[15:46] <didrocks> but we can stage that to proposed
[15:46] <thostr_> that's line 78 in landing and is the number1 reason for the crashes
[15:47] <thostr_> plars: can you manually install what's in 78 and rerun? because that should fix the crash
[15:47] <mhr3> thostr_, asac showed me earlier today a list that had that included
[15:47] <mmcc> fginther: hmm, ok
[15:48] <mhr3> thostr_, http://people.canonical.com/~platform/cu2d/results
[15:48] <didrocks> thostr_: excellent! I have added the missing component in the landing plan
[15:48] <didrocks> thostr_: so yeah, we will push that to -proposed (but it will stay there until the end of beta2)
[15:48] <lool> sil2100: sorry, was reviewing a mp with Ted, back now
[15:49] <lool> sil2100: so I've installed latest content-hub and am rebootin
[15:49] <mmcc> fginther: can you say more about how much extra work that custom job is?
[15:49] <thostr_> didrocks: wait, something is strange, if we take http://people.canonical.com/~platform/cu2d/results then the fix seems in???
[15:50] <dobey> fginther: seems odd that it would expect something different than launchpad does
[15:50] <didrocks> thostr_: this is what is staged, not yet in proposed
[15:50] <thostr_> didrocks: ah, ok
[15:50] <didrocks> thostr_: it's in the ubuntu-unity/daily-build ppa
[15:50] <didrocks> so people can already test if they want ;)
[15:51] <lool> didrocks: to write the proposed image, just use --channel saucy-proposed
[15:51] <fginther> mmcc, it's about 30 minutes of work to get it setup and tested
[15:51] <didrocks> lool: hum, where? I'm in a command line ;)
[15:51] <cjwatson> lool: (devel-proposed, let's not get into habits we'll have to change in three weeks ;-) )
[15:52] <lool> ;-)
[15:52] <lool> didrocks: with phablet-flash
[15:52] <fginther> dobey, I'm not sure if the format has a name, but it expects a single branch with packaging and source together, we just strip out the packaging to apply to the new source branch
[15:52] <lool> didrocks: or you can change your /etc/system-image/channel.ini
[15:52] <didrocks> lool: ah? I have to reflash, no way to tell "please now for my image update use…"
[15:52] <lool> sil2100: so it worked with new content-hub
[15:52] <didrocks> ah, in /etc/system-image/channel.ini
[15:52]  * didrocks does
[15:53] <lool> sil2100: was no new gallery-app for me to update to
[15:53] <plars> I was wondering that actually... so devel-proposed == saucy-proposed == daily-proposed? (we did just remove all traces of daily-proposed from the image ci, and told stgraber it was fine from our end to remove)
[15:53] <didrocks> lool: how does it work? you click on an image and then?
[15:53] <lool> plars: currently
[15:53] <lool> plars: daily-proposed will go away
[15:53] <mmcc> fginther: ok, do you have that time today?
[15:53] <plars> I knew about daily and devel being equivilent, but wasn't sure about saucy-proposed and whether it had any differences
[15:53] <lool> didrocks: I click on the top left image, and it opens gallery
[15:53] <fginther> yeah, I should have time in about 2 horus
[15:54] <lool> sil2100, didrocks: Now I did find a bug before and after the content-hub update: when I go back to settings, one of the two top images uses the default image instead of the configured one (just after selecting a new image it's correct)
[15:54] <plars> thostr_: I can try to take a look soon, is there a package for it already?
[15:54] <lool> didrocks, sil2100: Note that I've arranged for pictures to be in my gallery-app first
[15:55] <lool> otherwise it doesn't work too well as it launches a new gallery-app from camera
[15:55] <lool> there's no "take a picture and return" mode it seems
[15:55] <mmcc> fginther: great, thanks
[15:55] <thostr_> plars: it's in daily build ppa, update libunity and unity-scope-home
[15:56] <sil2100> lool: I have pictures in my gallery if anything
[15:56] <sil2100> lool: well, fill in a ubuntu-system-settings bug for the background issue you mentioned and I'll pick it up tomorrow
[15:57] <ralsina> asac: can we land the landing ask #57 in the next round?
[15:57] <ralsina> asac: it has a candidate and everything
[15:57] <asac> ralsina: can you check with didrocks?
[15:58] <ralsina> asac: of course. didrocks ^+2
[15:58] <didrocks> ralsina: in the discussion we had before, didn't we say that already landed?
[15:58] <ralsina> didrocks: not that one. I have a number of asks, and they all end in 7 ;-)
[15:59] <asac> yeah #57 is in afaict
[15:59] <asac> please double check
[15:59] <asac> that was hooked to landing no. 1 and that one is done
[15:59] <ralsina> Argh, sory, my bad #58
[15:59] <asac> didrocks: can you show how ralsina can find out if his stuff is in?
[15:59] <didrocks> 14:54:47           asac | http://people.canonical.com/~ogra/touch-image-stats/20130919.changes
[15:59] <ralsina> didrocks: ^
[15:59] <didrocks> 14:54:54           asac | thats the last image that has something about click-update-manager
[15:59] <didrocks> 14:54:59           asac | everything after didnt touch it
[15:59] <asac> ah
[15:59] <asac> good
[15:59] <didrocks> 14:55:08           asac | that was landing no. 1 afaik (ask 57)
[15:59]  * didrocks has memory ;)
[15:59] <ralsina> yes, sorry, I was off by one.
[15:59] <asac> 58 is a new story :)
[15:59] <asac> hehe
[15:59] <didrocks> (and a good backlog :p)
[15:59] <didrocks> ah 58!
[15:59] <didrocks> ;)
[15:59] <asac> hehe
[15:59] <ralsina> So, didrocks this is about #58
[16:00] <asac> ralsina: dont confuse us :-P
[16:00] <didrocks> ok, let me look!
[16:00] <lool> sil2100: but I see no regression with content-hub, so you can land it if you like
[16:00] <asac> didrocks: i think we have a standup... will be right there :)
[16:01] <lool> sil2100: that's with 0.0+13.10.20130920-0ubuntu1
[16:01]  * ogra_ needs fresh coffee ... 
[16:01] <didrocks> asac: yeah, coming in one minute
[16:01] <ogra_> gimme a few
[16:01] <didrocks> ralsina: in fact, it's already in ;)
[16:01] <didrocks> we can see the huge power of asac tracking and updating :p
[16:02] <ralsina> didrocks: yay in any case!
[16:02] <didrocks> ralsina: should be in current promoted image (#62)
[16:02] <asac> to be fair those landings were done before we referernced the landing
[16:02] <asac> so it was a bit of a mental challenge to ensure i dont do mistakkes :)
[16:02] <asac> but the good news is that the landing ask owner cares and we learn how to find out :)
[16:02] <didrocks> yeah, I'm just kidding :)
[16:02] <didrocks> right
[16:03] <ralsina> asac: I am trying to be a good asker! ;-)
[16:03] <asac> thanks! :)
[16:05] <ralsina> didrocks: the current promoted image seems to have 0.2+13.10.20130924.1 and we want 24.2
[16:06] <didrocks> ralsina: yeah, .1 has partially your fix, #63 and soon #64 have it
[16:07] <ralsina> didrocks: ok, no problem then
[16:07] <sil2100> lool: ok, I ran unity8 tests so I'll publish
[16:11] <sil2100> didrocks: I published content-hub, and now I think I go warm my bed a bit to recover completely for tomorrow :)
[16:11] <sil2100> didrocks: how was your exercise btw.?
[16:11] <didrocks> sil2100: sure! thanks a lot for all the work dude :)
[16:11] <didrocks> sil2100: good, but my bike's tire exploded :/
[16:11] <didrocks> so had an unexpected stop
[16:11] <didrocks> :p
[16:12] <sil2100> uuuh, it sucks when that happens, especially when one is far away from home ;)
[16:12] <sil2100> See you tomorrow everyone!
[16:13] <lool> didrocks: so IIUC, platform stack is failing in check due to: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/2117/label=qa-nvidia-gtx660/testReport/junit/unity.tests.test_dash/DashScopeResultsTests/test_results_message/
[16:16] <plars> thostr_: ok, I'm provisioned locally, where's the ppa I need?
[16:16] <thostr_> plars: it's in daily-build
[16:17] <plars> thostr_: for... unity? link?
[16:18] <thostr_> plars: add-apt-repository ppa:ubuntu-unity/daily-build
[16:18] <plars> ppa:ubuntu-unity/daily-build I guess?
[16:18] <plars> got it,
[16:20] <plars> thostr_: unity-scope-home and libunity9? or does it need libunity-* also?
[16:21] <thostr_> mhr3 ^
[16:23] <mhr3> it needs libunity-protocol-private as well
[16:23] <mhr3> but that should be dep of libunity9
[16:24] <asac> robru: there?
[16:24] <asac> robru: wkae up we need you
[16:24] <mhr3> but perhaps stop super-cherrypicking, and take everything built from lp:libunity
[16:30] <rsalveti> lool: new pulse should be in proposed soon, and we'd also need to copy/publish telepathy-ofono, to fix bug 1226298
[16:31] <lool> rsalveti: do you have a landing slot for it or would you like me to add one?
[16:31] <rsalveti> lool: already added
[16:32] <lool> thanks
[16:33] <ogra_> rsalveti, pulse will get stuck
[16:33] <ogra_> (beta freeze)
[16:33] <rsalveti> ogra_: sure
[16:34] <rsalveti> who can copy telepathy-ofono from the ppa to the archive?
[16:34] <lool> rsalveti: which stack is this?
[16:34] <ogra_> rsalveti, btw, since you will be around when the US day ends, you have been voluntold to guide the MM landing :)
[16:34] <lool> network
[16:34] <lool> rsalveti: I think we can do that now
[16:34] <ogra_> rsalveti, i'll take over in the morning
[16:34] <lool> I might even be able to
[16:34] <rsalveti> ogra_: sure
[16:34] <rsalveti> lool: thanks
[16:35] <ogra_> it needs someone who knows about the stack ...
[16:35] <lool> rsalveti: keeping Didier on the hangout to make sure I do no mistake
[16:37] <rsalveti> cool
[16:37] <lool> rsalveti: running
[16:37] <rsalveti> thanks
[16:37]  * rsalveti lunch
[16:39] <lool> rsalveti: should be into -proposed in 5mn or so
[16:39] <ogra_> the latest phablet-flash changes need a build, can someone trigger one ?
[16:39] <ogra_> sergiusens, was there a spreadsheet entry for it i can refer to (else i'll add one)
[16:40] <sergiusens> ogra_, no, needs addition... it's a fix to the demo setup tool for ro and a new phablet-config tool to setup timezone
[16:41] <ogra_> sergiusens, the latter was just reverted in the image
[16:41] <ogra_> sergiusens, since stgraber didnt like the approach
[16:41] <ogra_> sergiusens, is antthing making use of that feature by default yet ?
[16:42] <sergiusens> ogra_, need to tell cwayne...
[16:42] <sergiusens> ogra_, nothing by default
[16:42] <ogra_> sergiusens, we have the three files still writable
[16:42] <lool> == Publishing stack mir ==
[16:42] <ogra_> but pitti wants to change that setup completely so i try to hold back anything related to it until the basics are solved
[16:43] <lool> just ubuntu-system-compositor (unseeded) against latest Mir, checked packaging changes
[16:45] <lool> rsalveti: telepathy-ofono is accepted, will soon be published to proposed
[16:45] <lool> should transition to archive after that
[17:05] <plars> thostr_: I'm running it a few more times to be sure, but so far no crash
[17:05] <plars> asac: ^
[17:05] <ogra_> robru, can you trigger a phablet-tools build  from recent trunk ?
[17:22] <didrocks> asac: okkk, so the landing spreasheet is up to date
[17:23] <didrocks> discussed with ricmm, it's under control
[17:23] <didrocks> I'm happy to discuss about it more tomorrow
[17:23] <didrocks> but I think we should have an image as well with just unity-mir + the android part if not in + mir (once the fix is merged to trunk)
[17:23] <didrocks> to assess of the quality of this on maguro
[17:23] <didrocks> and then, rediscuss the application management :)
[17:24] <ogra_> the android part should be in since a while
[17:25] <ogra_> so it shouldnt be to hard to test on maguro if someone can provide debs for the Mir part
[17:25] <ogra_> (and unity-mir)
[17:25] <didrocks> ogra_: yeah, I was checking this, it seems to be in
[17:25] <didrocks> right, there is hope to have that in the ppa tomorrow :)
[17:25] <ogra_> yeah
[17:25] <ogra_> that should make it possible to test without having an actual image
[17:25] <ogra_> i.e manually
[17:27] <didrocks> right
[17:30] <didrocks> ogra_: content-hub is in now, can we get a beautiful image? :)
[17:30] <didrocks> (one which will pass all AP tests of course ;))
[17:30] <ogra_> didrocks, can we wait until the seed changes landed that i just uploaded ?
[17:30] <ogra_> though they are not urgent
[17:30] <ogra_> i guess i can as well just build an image
[17:31] <didrocks> ogra_: if it's not urgent, we can maybe just stage it for tomorrow's image?
[17:31] <didrocks> let's try to get one first
[17:31] <asac> ogra_: build :)
[17:31] <asac> hehe
[17:31] <didrocks> so that you can to bed earlier :p
[17:31] <asac> i believe we want to obey our selfimposed deadlines is what we earlier actually were trying to say
[17:32] <asac> so lets not extend cut offs because there is just another inflight thing almost ready :)
[17:32] <asac> hehe
[17:32] <ogra_> running
[17:32] <didrocks> yeah, there is alway this last nice candy that would be nice to get in ;)
[17:32] <didrocks> thanks ogra_ \o/
[17:33]  * didrocks waves good evening, have sweet dreams
[17:33] <ogra_> didrocks, in this case it was some leftover from yesterday i had forgotten about :)
[17:33] <ogra_> but nobody complained today so it will all be fine if it lands tomorrow
[17:34] <didrocks> :)
[17:40] <lool> \o/
[17:40] <asac> lool: why so happy :)
[17:40] <lool> so now I can play different music files, and they keep playing in background
[17:40] <asac> really>
[17:40] <asac> ?
[17:40] <lool> even if I turn screen off, but that's probably because I'm attached with adb
[17:40] <asac> just locally or anywhere near an image?
[17:40] <lool> asac: yeah, with a) platform-api change
[17:40] <lool> b) upstart-app-launch fix that I just happroved to trunk
[17:41] <asac> nice
[17:41] <lool> ah it also needs a music-app change (.desktop key addition)
[17:41] <asac> guess friday morning this lands
[17:41] <asac> err is in image
[17:41] <asac> :)
[17:41] <lool> I think tonight!  :-)
[17:41] <asac> cowboy mode?
[17:41]  * infinity read "anywhere near an image" as "playing your music files on a device a few feet away from a phone with Ubuntu on it".
[17:41] <infinity> Why yes, yes, I can play music near an image!
[17:42] <asac> hehe
[17:43] <lool> lol
[17:43] <lool> asac: I was actually testing the platform-api changes earlier
[17:43] <lool> only package in this stack to publish
[17:43] <lool> and can land now
[17:43] <asac> didrocks planned out the whole night
[17:43] <lool> until we discussed the minor regression with you, and the fix was trivial, so tested it quickly
[17:44] <asac> if that was discussed before its surely in
[17:44] <lool> I discussed this with him after our call in a hangout
[17:44] <asac> kk
[17:44] <asac> he knows what he is doing i guess... just ensure you run autopilots :)
[17:44] <asac> lol
[17:44] <asac> lool: so i see it
[17:45] <asac> lool: its 35
[17:45] <lool> I've just added it, yes
[17:45] <asac> so thats good
[17:45] <asac> you added it?
[17:45] <ogra_> hey, didnt we say we keep clear for MM landings
[17:45] <asac> to the landing plan?
[17:45] <ogra_> stop cowboying !
[17:45] <lool> asac: just the upstart one
[17:45] <asac> yeah. lets go according to plan is the simple rule to stay focussed and stay alive :)
[17:45] <lool> asac: that's the "fix the regression" you wanted
[17:45] <asac> ok
[17:45] <ogra_> yeah
[17:46] <ogra_> we definitely want it ...
[17:46] <ogra_> and i'm inclined to say that music app is kind of MM related :P
[17:46] <lool> ogra_: landing 12: I tested and would like to push it, but after upstart-app-launch is pushed
[17:46] <lool> ogra_: it works fine  :-)
[17:46] <ogra_> lool, yeah, doit
[17:46] <lool> ogra_: updated all platform-api packages, restarted session, music-app now keeps running in bg
[17:46] <ogra_> yeah
[17:47] <lool> it will hurt battery life I'm sure given the code outputs stuff it's doing to the db every second
[17:47] <lool> but it will play music  :-)
[17:47] <asac> lool: i guess its fine if you give didrocks a heads up ... i believe it was really agreed and hence is just an oversight in the plan.
[17:47] <ogra_> :)
[17:47] <lool> asac: Yes, I confirmed the platform part with didrocks earlier, and I also updated him on the whole single instance story, music playback story
[17:48] <asac> but i dont see what else we missed. so what is there is the plan and afaik didrocks has robru and friends helping. lets see
[17:48] <lool> we're far from the clean solution still
[17:48]  * ogra_ whispers "proposed and bugs" 
[17:48] <asac> lool: right. i trust you, so its an oversight if you agreed to land this before the morning image
[17:49] <asac> ogra_: such extreme ideas have to bake slowly before coming to fruits :)
[17:49] <ogra_> haha
[17:49] <ogra_> extreme :0
[17:49] <ogra_> :)
[17:52] <lool> ogra_: haha
[17:52] <lool> I meant far from the clean solution for music playback
[17:52] <ogra_> ah
[17:52] <ogra_> *grin*
[17:52] <asac> we have a clean app
[17:53] <ogra_> glossy and polished :)
[17:53] <asac> its just not sterile :)
[17:53] <asac> so if we lower our standards a bit, its still a clean app imo :)
[17:53] <asac> lol
[17:53] <asac> ogra_: image done?
[17:54] <asac> is it true that our community apps got better?
[17:54] <asac> err core apps
[17:54] <asac> V
[17:54] <asac> http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4441/
[17:54] <asac> hmm. not everywhere. http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4442/
[17:54] <ogra_> asac, will be done "zur tagesschau"
[17:54] <ogra_> :P
[17:54] <asac> but maybe that run was still affected by us pulling stuff from archive
[17:54] <asac> ogra_: oh... still that early. nice
[17:55] <asac> thats fixed now btw
[17:56] <asac> plars: can you confirm that we still did update in 64?
[17:56] <lool> ogra_: tagesschau isn't at 7pm?
[17:56] <asac> plars: otherwise it feels odd that we see the difference imo
[17:56] <plars> asac: no, we did not
[17:56] <asac> hmm
[17:56]  * lool watched news pünktlich um sieben!
[17:56] <asac> thats odd then
[17:56] <ogra_> lool, 8pm
[17:56] <lool> tudududut tudududut
[17:56] <lool> tah dah dah dahhh
[17:56] <ogra_> haha
[17:56] <lool> zdf!
[17:56] <asac> plars: how can we be sure? can we grep through all logs>?
[17:56] <ogra_> LOL
[17:56] <lool> ah tagesschau is ard?
[17:56] <asac> maybe there is an apt-get update hidden somewhere lese
[17:56] <ogra_> lool, yeah
[17:57] <lool> I think that's the one I watch on the web, I dont get the zdf one
[17:57] <ogra_> yeah, its the more common one
[17:57] <ogra_> that should work after the MM landing btw :)
[17:57] <plars> asac: I'll keep looking but the only ones I could find have already been removed
[17:57] <lool> you know what would get ur pass rates up?
[17:57] <lool> adding more tests!
[17:58] <asac> plars: how is beta testing going btw? are there many respins?
[17:58] <asac> plars: yeah, still wonder how we could systematically find all
[17:58] <plars> asac: we're about to get a full respin of server/desktop
[17:58] <asac> and be certain :)
[17:58] <asac> we could also dumb the packagelist after the run as well
[17:58] <ogra_> oh, that might unleash some of our stuff !
[17:58] <plars> asac: we could also check the package version - which one is it you're concerned about in particular
[17:58] <ogra_> if desktop gets rebuilt
[17:59] <asac> plars: well, just want to ensure that we test what we want to test
[17:59] <asac> and nothing else
[17:59] <asac> guess a doanac thing maybe to sort that
[17:59] <ogra_> asac, well, a desktop respin usually means that the floodgates get opened (at least for a bit)
[17:59] <plars> asac: doanac already removed the installation of utah - which also removed the apt-get update that went along with it after installing the ppa
[18:00] <plars> asac: I removed the default test that ran apt-get update
[18:00] <asac> plars: you think that respin is last and we open archive again after?
[18:00] <ogra_> so packages helld back by desktop will flow in
[18:00] <asac> when would we know?
[18:00] <plars> asac: I hope so, but there could be 5 more for all I know - we don't usually know until it happens
[18:00] <asac> ok. lets talk about that in our 1-on-1 a bit more :)
[18:00] <plars> asac: and all tests have to be rerun every time
[18:01] <asac> plars: what is the test list again?
[18:01] <asac> do you have that somewhere on one page?
[18:01] <plars> asac: http://iso.qa.ubuntu.com/qatracker/milestones/303/builds
[18:01] <plars> asac: not on one page though
[18:06] <ogra_> asac, btw, tagesschau is on screen :)
[18:06]  * ogra_ is brave and tries Mir on maguro before flashing the next image
[18:07] <asac> ogra_: is RO out?
[18:07] <ogra_> asac, ah, not yet
[18:08] <ogra_> hmm
[18:08] <asac> doesnt sound good
[18:08] <asac> probably a problem
[18:08] <ogra_> nah
[18:09] <ogra_> it takes a while to repack them
[18:09] <plars> asac: just double-checked again - no more apt-get update anywhere in the ci scripts. Utah phablet-run wrapper has it in one function - the one that installs utah on the target, but this is turned OFF now from our ci scripts
[18:10] <asac> plars: can we retry those builds until they get the same results :)?
[18:10] <asac> one more time for now i gues
[18:10] <ogra_> wow, Mir is like a slap in the face on my maguro
[18:10] <ogra_> full brightness burns through my eyes
[18:11] <ogra_> wow ... thats slower than xfbdev over network !
[18:12] <ogra_> ah, and starting the browser just hardlocks it
[18:13] <ogra_> woah
[18:14] <ogra_> load average: 19.83, 8.87, 3.39
[18:15] <thostr_> ogra_: do we have a fixed url for landings in images similar to http://people.canonical.com/~platform/cu2d/results for daily?
[18:16] <ogra_> thostr_, only for after the build ... http://people.canonical.com/~ogra/touch-image-stats/
[18:16] <thostr_> ogra_: yes, that is what I'm looking for. thanks
[18:23] <plars> asac: psivaa restarted a lot of those already, but build 65 is out now, so those tests are now running
[18:24] <ogra_> maguro seems to always miss some
[18:54] <popey> ogra_: i have a bit of time now, want me to flash 65 and test on mako?
[18:58] <lool> soo
[18:58] <lool> misc stack won a new package update while I was waiting for upstart-app-launch to merge
[18:59] <lool> phablet-tools
[18:59] <lool> so I'll try to run the misc stack with just upstart-app-launch
[19:01] <lool> I see platform is currently building (along tons of other stuff) so will let that settle
[19:01] <lool> too bad platform seems to be getting another update
[19:18] <ogra_> popey, yeah, that would be great
[19:48] <lool> == publishing platform ==
[19:48] <lool> which just has the platform-api change I tested much earlier
[19:49] <lool> I wish I could have published the misc one, but phablet-tools got there and I'm not 100% sure I can land it, and I couldn't figure a sane way to publish just upstart-app-launch out of it
[19:49] <fginther> mmcc, the ubuntuone-credentials have been updated
[19:49] <fginther> mmcc, the ubuntuone-credentials *jobs* have been updated
[19:50] <mmcc> fginther: excellent, thanks for the help!
[19:51] <ogra_> lool, if phablet-tools is up to date, thats something i wait for
[19:51] <fginther> mmcc, you're welcome, sorry it took longer then expected
[19:51] <lool> ogra_: it has a couple of changes form tip
[19:51] <lool> ogra_: one from cwayne for your TZ stuff and one from doanac for some autopilot failure handling, as to keep colling logs
[19:52] <mmcc> fginther: no problem. it wasn't blocking us :)
[19:52] <ogra_> well, latest tip would be fine ... i pinged robru above for it, not sure he saw the ping
[19:52] <lool> ogra_: since that doesn't go in the image, if you can confirm it works as you want it, I can push to archive; would also need the ok from doanac I guess
[19:52] <ogra_> lool, sergiusens tested it
[19:53] <lool> ogra_: did you want it in PPA, or in archive?
[19:53] <lool> ogra_: this is what's in PPA https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages?field.name_filter=phablet-tools&field.status_filter=published&field.series_filter=saucy
[19:53] <ogra_> lool, hmm, i'm not sure how it gets promoted to the backport PPAs ...
[19:54] <ogra_> i would have said archive, but i kind of suspect the copying for the older releases happens from the PPA
[19:54] <lool> ogra_: it definitely got published with the cu2d stuff last time
[19:55] <lool> doanac: hey
[19:55] <lool> doanac: is latest phablet-tools tip good to go?  did you test it?
[19:55] <ogra_> lool, perfect, verified, i want both changes
[19:55] <doanac> lool: its working for me locally
[19:56] <lool> Ok; since it's just going to archive and you wanted robru to push it, and there's a landing slot for it, and you guys both tested it + sergio, it's ok  :-)
[19:56] <lool> doanac: it has no chance of breaking our autotesting infrastructure?
[19:57] <doanac> lool: i don't think so. if anything it should fix a regression
[19:58] <lool> == publishing misc ==
[19:58] <ogra_> :)
[19:59]  * ogra_ vanishes again
[20:05] <plars> another respin coming on the beta, I'm going to disappear for a bit too, back in a bit
[20:10] <robru> ogra_, sorry I've been sick today. just getting functional now. do you still need me to do phablet-tools or did you get somebody for it already?
[20:10] <sergiusens> ogra_, going from saucy to precise is automatic
[20:15] <thomi> hey fginther, got a second?
[20:16] <fginther> thomi, yes, what's up?
[20:17] <thomi> fginther: one of the autopilot functional tests is failing because 'dpkg-architecture' isn't installed  on the system.
[20:17] <thomi> fginther: My question is: should we make dpkg-dev a build-depends on autopilot, or a regular depends on python-autopilot-tests?
[20:17] <thomi> fginther: We don't (currently) run the functional tests during package builds, but if we did, I guess it'd need to be a build-depends.
[20:17] <thomi> fginther: But I don't know how the jenkins job works when it runs the functional tests.
[20:17] <thomi> does it install the python-autopilot-tests package and go from there, or run them from source?
[20:21] <fginther> thomi, the functional tests should be installed via the python-autopilot-tests package. I did just notice that wasn't installed when I ran your test yesterday
[20:22] <fginther> thomi, in the daily-release setup, it is using the python-autopilot-tests package
[20:22] <thomi> fginther: ok, so I'll it as a dependency on that package, and we should be down to one test failure :)
[20:22] <thomi> which looks like qmlscene borking for some reason
[20:22] <fginther> thomi, tes
[20:22] <fginther> yes
[20:22] <thomi> awesome, thanks fginther
[20:24] <ogra_> robru, seems what lool has there is fine
[20:24] <ogra_> robru, go to bed
[20:24] <robru> ogra_, hehe
[20:30] <ogra_> plars, gallery app on mako looks a little unhappy
[20:31] <ogra_> (in the 65 tests)
[20:34] <kgunn> fginther: hey, i've been watching this one...https://code.launchpad.net/~kdub/mir/fix-1215979/+merge/187346
[20:35] <kgunn> fginther: is there a way to prioritize it for a merge/ci run ?
[20:45] <popey> ogra_: 65 seems good to me!
[20:46] <dobey> popey: in bug #1227100 it's about the weird second button there, and not the 503 unavailable message itself, right?
[20:46] <popey> dobey: both really
[20:47] <popey> 503 means nothing to me, and *** download... is odd
[20:47] <dobey> maybe should be two bugs then
[20:47] <dobey> one for "error messages are too technical" and the other for "wtf is this weird button on the error page"
[20:47] <popey> ok, gimmie a mo and i will do it
[20:48] <dobey> because they are separate issues
[20:48] <dobey> sure
[20:48] <dobey> thanks :)
[20:51] <popey> dobey: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1231145
[20:52] <lool> kgunn: will run mir
[20:52] <dobey> thanks popey
[20:53] <lool> == building mir ==
[20:53] <lool> (not publishing)
[20:53] <lool> this is to get https://code.launchpad.net/~kdub/mir/fix-1215979/+merge/187346 built in PPA
[20:53] <kgunn> lool: cool
[20:54] <kgunn> lool: which ppa ?
[20:55] <lool> I thought it was the main one, but I guess I'm not looking at the right stuff
[20:56] <lool> 2013-09-25 20:54:10,424 INFO No new useful revision published since last daily push, no need to upload this component
[20:59] <lool> kgunn: actually I see the branch marked as merged, but it's not in lp:mir?
[21:00] <lool> aha development-branch
[21:01] <fginther> kgunn, the MP shows as 'merged'
[21:01] <kgunn> fginther: sweet...it knew i was complaining
[21:01] <kgunn> :)
[21:02] <lool> kgunn: so I don't know how to trigger a snapshot of the development-branch into $other PPA used for this
[21:02] <lool> kgunn: can only help with lp:mir
[21:02] <lool> gtg, 'night all
[21:18] <ogra_> popey, here too
[21:26] <jdstrand> fginther: hey-- I have a self-service upload. testing on 62 worked fine. is now ok to upload?
[21:26] <jdstrand> (line 76 of the landing plan)
[21:26] <fginther> jdstrand, let's figure out who can answer this
[21:26] <fginther> jdstrand, one moment
[21:27] <jdstrand> fginther: well, my question was just about getting in the way of 63
[21:27] <jdstrand> fginther: thanks
[21:28] <fginther> robru, are you the current domain expert on the landing plan?
[21:31] <fginther> cyphermox, maybe that's you? ^
[21:33] <robru> fginther, uhhhh, no ;-) but I can release something if you want me to
[21:34] <jdstrand> I was asked to make sure my upload came before 63
[21:35] <jdstrand> "self service after build #62 is available and before we cut #63 ... check to be safe"
[21:35]  * jdstrand is trying to be safe :)
[21:37] <thomi> Hello CI team - I'm getting bzr errors causing my branches to fail autolanding, for example: https://jenkins.qa.ubuntu.com/job/autopilot-1.3-saucy-armhf-autolanding/19/console
[21:37] <thomi> any ideas?
[21:39] <fginther> thomi, let me check to make sure nothings down
[21:40] <cjwatson> thomi: for the record, dpkg-dev is in build-essential, and therefore you shouldn't ever build-depend on it (unless it's a versioned build-dep to force something new enough).  Runtime depends are a different matter of course.
[21:40] <cjwatson> (re autopilot discussion earlier)
[21:40] <thomi> cjwatson: ahh, thanks
[21:40] <thomi> cjwatson: but it wouldn't hurt to build-dep on it, right? It would just be redundant?
[21:40] <cjwatson> It doesn't hurt, but you still shouldn't. :-)
[21:41] <thomi> sure
[21:41] <popey> ogra_: we publishing?
[21:50] <ogra_> popey, wanna mail ?
[21:50] <popey> sure thang ogra_
[21:51] <ogra_> popey, hmm, the gallery-app failures on mako dont make me feel comfortable
[21:51] <popey> what fails?
[21:51] <jdstrand> ogra_: hey, I have a self-service upload and was told: "self service after build #62 is available and before we cut #63 ... check to be safe"
[21:51] <ogra_> nearly everything
[21:51] <jdstrand> ogra_: is now safe?
[21:51] <ogra_> should be
[21:51]  * jdstrand uploads
[21:52] <ogra_> popey, http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4443/gallery-app-autopilot/
[21:52] <popey> oof
[21:52] <popey> QA looked at it?
[21:53]  * popey runs the tests locally
[21:54] <ogra_> i pinged plars but i dont think he saw it
[21:55] <ogra_> seems sensorservice was going wild during that test
[21:55] <popey> lets see if i can get a good run here
[21:56] <ogra_> https://jenkins.qa.ubuntu.com/job/saucy-touch_ro-mako-smoke-gallery-app-autopilot/108/artifact/clientlogs/top_before.log/*view*/
[21:56] <popey> nice
[21:56] <ogra_> sensorservice munches the cup
[21:56] <popey> hah
[21:56] <ogra_> err
[21:56] <ogra_> cpu
[21:56] <ogra_> :P
[21:56] <popey> i prefer cup
[21:56] <ogra_> heh
[21:57] <popey> I'm picturing a robot munching away on a polystyrene cup rather than drink the contents
[21:57] <ogra_> heh
[21:57] <popey> ok, running...
[22:01] <popey> every time I run the gallery app autopilot tests it makes me think of timo jyrinki because the avatar of the guy holding a phone is very similar to his G+ avatar. https://lh6.googleusercontent.com/-zx1-8TRxsMI/UOQT19iuDTI/AAAAAAAAAVk/Dyqo9PMXWjw/s679-no/avatar2.png
[22:02] <fginther> thomi, I found nothing obviously wrong with the build slave, now that retoaded is back online, I'll poke his brain
[22:02] <thomi> fginther: OK, well, I re-approved the MP, so we'll see what happens
[22:03] <ogra_> popey, hahaha
[22:06] <popey> ogra_: http://paste.ubuntu.com/6156394/
[22:08] <ogra_> popey, hmm
[22:08] <ogra_> i wonder what an error vs a failure is
[22:09] <popey>  phablet-test-run -o /tmp/gallery.txt -p gallery-app-autopilot gallery_app
[22:09] <popey> thats the command I used, that's right isn't it?
[22:10] <ogra_> yeah, i think so
[22:10] <ogra_> and you unlocked manually indeed
[22:11] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20130925.2.changes ...
[22:11] <ogra_> i dont think there is anything that touches gallery app in the changes
[22:12] <ogra_> hmm, does content-hub ?
[22:13] <ogra_> popey, i dont really feel like hunting that down tonight, lets skip this one
[22:13] <popey> ok
[22:13] <popey> Fine by me. Can always get someone to look first thing and release early tomorrow, before US wakes
[22:13] <ogra_> QA can re-run the test on the utah machine and we'll see then
[22:13] <ogra_> yeah
[22:18] <plars> ogra_: those are rerunning
[22:19] <plars> ogra_: we've seen that sensorservice eating cpu  before - just right after boot, seems to go away later
[22:19] <ogra_> yeah
[23:15] <thomi> fginther: is there any way to trigger the autopilot integration test suite early? or should I just wait up to 4h for it?
[23:34] <fginther> thomi, you can ask robru
[23:35] <robru> thomi, yes, i can trigger that. do you have a new trunk commit you want to test? or just want to re-run same build because of an infrastructure issue?
[23:35] <thomi> robru: there's a new trunk commit
[23:35] <robru> thomi, ok, and which project? lp:autopilot?
[23:35] <thomi> robru: well, technically it's the lp:autopilot/1.3 series, rather than trunk
[23:35] <thomi> yeah
[23:35] <robru> thomi, ok, let me check on that
[23:36] <thomi> thanks
[23:36] <robru> thomi, ok, good, we already have 1.3 branch configured for saucy ;-) I'll kick off a new build.
[23:36] <thomi> robru: awesome, thanks
[23:37] <robru> thomi, not sure how long that'll take to run, but probably less than 40mins
[23:37] <thomi> robru: awesome, thanks
[23:39] <robru> np