[00:08] <sil2100> I think all looks good with the image so far
[00:28] <sil2100> alesage: so, the image got imported to /ubuntu, so with the next publisher run the krillin and arale images should be available
[00:28] <sil2100> bfiller: ^
[00:29]  * sil2100 goes EOD now
[00:29] <sil2100> o/
[00:29] <bfiller> sil2100: just saw your email, thanks for theupdate
[00:29] <bfiller> good night
[00:29] <sil2100> yw, good night!
[05:18] <Mirv> heh, this is now interesting that I cross-check darkxst's PPU upload rights to those main packages that are part of the 016 landing. a bit more complicated than usual.
[05:19] <darkxst> Mirv, I have upload rights for all those
[05:20] <Mirv> darkxst: ok. via which rights? I've looked at http://people.canonical.com/~ubuntu-archive/packagesets/wily/desktop-extra and http://people.canonical.com/~ubuntu-archive/packagesets/wily/ubuntugnome so far
[05:20] <darkxst> Mirv, ubuntu-desktop
[05:20] <Mirv> ah, desktop!
[05:20] <Mirv> just a moment
[05:21] <Mirv> darkxst: correct, publishing, thanks!
[05:24] <darkxst> Mirv, thanks
[06:07] <bzoltan_> Mirv: I have a release candidate for fixing an OTA6 bug in the silo9... just FYI
[06:08] <bzoltan_> bfiller: ^ that is the emulator bug
[06:10] <Mirv> bzoltan_: ok. the gates are closed but it can be discussed in 2.5h - maybe for example let it in in a sense that a new emulator image can be created at a suitable point to have it fixed.
[06:11] <bzoltan_> Mirv: Yes. Also.. we do not have to land the main package :) All we actually need is the gles package.
[06:49] <Mirv> michi: I assume the 011 can't be "publish" since it only just built and cannot have been tested? you should reset the value in the request so that the silo doesn't accidentally get published
[06:50] <Mirv> michi: oh, also, it's a dual landing silo so that status shouldn't be ever set anyway
[06:50] <michi> Mirv: Sorry, you lost me there.
[06:50] <michi> What did I do wrong?
[06:50] <Mirv> michi: the UI could be better, but for wily only landings you should select "No QA needed" at first, and for dual landings you should select "QA Required" at first
[06:51] <michi> Aha, OK, thanks.
[06:51] <Mirv> michi: now you selected "Publish without QA" which the status to set wily-only silo to after it's ready
[06:51] <michi> So, what do I do now to fix it?
[06:51] <Mirv> michi: edi the line and set it to "QA Required". once it's ready and tested by you, the next step is to set it to "Ready for QA"
[06:51] <michi> Aha, OK, thanks!
[06:52] <Mirv> no problem. at some point there'll be UI improvements but currently one just to know those.
[06:52] <michi> Ah, looks like you set it to QA required already?
[06:52] <michi> Because that’s what I’m seeing after hitting “Edit"
[06:52] <michi> Ah, no… Wrong silo, my apologies.
[06:52] <Mirv> michi: hmm, no, are you looking at the above line?
[06:52] <Mirv> right..
[06:53] <michi> Bloody easy to edit the wrong silo by mistake.
[06:53] <Mirv> that's also an UI issue, the lines are not really well separated :)
[06:53] <michi> Maybe add an interlock with a warning?
[06:53] <michi> If someone other than the lander wants to edit, at least ask them whether they are maybe trying to edit the wrong line?
[06:54] <Mirv> michi: good idea, filing a bug to https://bugs.launchpad.net/bileto/ with that description
[06:54] <michi> About to do that.
[06:54] <Mirv> michi: ah, ok, feel free to do that.
[06:55] <michi> But submitted :)
[06:56] <Mirv> michi: thanks!
[07:03] <morphis> Mirv: time to do another upload for me?
[07:03] <Mirv> morphis: always!
[07:04] <morphis> Mirv: great!
[07:06] <morphis> Mirv: same one will follow in a bit for wily
[07:08] <Mirv> morphis: ok
[07:08] <morphis> but want to verify the vivid one first
[08:12]  * sil2100 disables the e-mail bot for a moment
[08:13] <sil2100> I wonder what happened that it started malfunctioning
[08:16] <davmor2> sil2100: blame ogra_ it's normally all his fault
[08:18] <sil2100> That's probably true!
[08:18] <sil2100> ogra_ and his reckless ways of hacking other people's stuff
[08:27] <ogra_> sil2100, not to mention me being the cassandra of ubuntu-phone nowadays, always bringing the bad news (like:: dont use wily)
[08:28] <sil2100> Yeah, let's hope we won't get on the news for this
[08:28] <sil2100> I can already see the phoronix news item:
[08:28] <ogra_> haha
[08:28] <sil2100> "Dave and Łukasz report that ogra is breaking other people's stuff!"
[08:29] <sil2100> ;)
[08:29] <ogra_> Canonical forbids developers the use of the developer images !
[08:29] <sil2100> How dare people use developer images
[08:30] <ogra_> "Canonical says developer images exclusive to Canonical employees"
[08:31] <sil2100> No no no, exclusive to ogra_!
[08:31] <ogra_> subtitle: "is the IP policy involved ?!?"
[08:32] <davmor2> Web exclusive: ogra_ says NO
[08:32] <ogra_> :)
[08:39] <sil2100> jibel: I fixed the e-mailing bot, we might have missed a few uploads since one of the uploads was causing it to crash (invalid bug ID in the changes) - all though be good now
[13:46] <kgunn_> sil2100: i understand you'll be copying in pkg's manually to the snapshot-overlay, i think it'd be good to ping me & bfiller when this happens
[13:47] <kgunn_> also, curious, can you make sure to keep the previous package(s) somewhere when you copy ? in case you need to roll back
[13:47] <kgunn_> (@ping at least until pat's back)
[13:47] <sil2100> kgunn_: the snapshot is now propagated with the state of the candidate image
[13:48] <sil2100> kgunn_: whenever I'll include some packages from the overlay once we open up, I'll do it on your guys request
[13:48] <kgunn_> awesome
[13:48] <sil2100> Sadly having previous versions is not really possible... the snapshot PPA is a normal PPA, so we can't upload older versions ;/ We would have to rebuild a revert
[13:48] <kgunn_> got it
[13:49] <kgunn_> sil2100: i was just thinking of copying off those "old" versions tho
[13:49] <kgunn_> just in case
[13:49] <kgunn_> i suppose it shouldn't be many so rebuild is not too bad
[13:50] <kgunn_> ....and ultimately safer
[13:50] <sil2100> We can get the state of any released rc-proposed image easily, I have a script for that - so in any moment of time we can run that to see what packages we had originally
[14:09] <sil2100> bfiller, kgunn_, jibel, robru: ^
[14:10] <sil2100> As per announcement, we can land things to the overlay now
[14:11] <sil2100> The daily auto-builds are still disabled though, I could basically enable those and switch them off (doing some channel magic) whenever we need a re-spin, but I don't want QA to get a sudden update notification during testing
[14:11] <sil2100> As they're using rc-proposed for tests
[14:12] <sil2100> We could think of some new channels for this purpose, but it's a bit complicated as we, for instance, have 2 different mako images right now
[14:12] <sil2100> Anyway
[14:12] <sil2100> jibel, davmor2: how's the testing so far?
[14:12] <sil2100> Anything we should be worried about?
[14:12] <davmor2> sil2100: you should always be worried
[14:13] <kgunn_> :)
[14:13] <sil2100> bfiller: any update regarding the camera-app fix? And did you see dbarth's media-hub/oxide bug e-mail?
[14:13] <bfiller> sil2100: that's a kgunn question (camer-app fix)
[14:14] <bfiller> sil2100: and yes saw dbarth's email, but it's not clear if we have a fix? need jhodapp support for that it sounds like
[14:15] <jhodapp> bfiller, I replied to dbarth but haven't heard back from him
[14:15] <jhodapp> is he off today?
[14:15] <bfiller> jhodapp: yes
[14:16] <jhodapp> bfiller, ok, from alex-abreu's reply though it sounded like there was no action to take
[14:16] <bfiller> alex-abreu: can you summarize what is left to have media-hub support for oxide including https?
[14:16] <alex-abreu> jhodapp, bfiller that was my impression too yesterday since the doors were closed and the mh bit was not ready apparently
[14:18] <bfiller> jhodapp: do we have a fix for https yet or not?
[14:18] <alex-abreu> bfiller, jhodapp David managed to make things work w/ the https mh fix a few hours ago, ...
[14:18] <jhodapp> bfiller alex-abreu: it seems from justinmcp's reply that silo 21 was working with media-hub support and that dbarth simply did not upgrade to the silo correctly when testing
[14:18] <jhodapp> so nothing was wrong with https from justinmcp's MR
[14:18] <alex-abreu> bfiller, jhodapp so the fix seems ok, but I am not sure about the status of the landing pipeline for ota6, my impression is that it was too late
[14:19] <jhodapp> so if we have a FFE, we can land that
[14:19] <alex-abreu> jhodapp, this is what I understood too
[14:19] <jhodapp> not sure there's anything for me to do
[14:21] <kgunn_> sil2100: @camera trusted prompt, i'm about to meet with team...it wasn't a straight fwd answer unfortunately
[14:21] <bfiller> jhodapp, alex-abreu: if it's deemed critical we'll be able to land it, the important thing is that the silo is tested and works. can you guys verify that please?
[14:21] <sil2100> kgunn_: ACK, thanks :)
[14:22] <alex-abreu> bfiller, the silo has been +1'd by david & justin
[14:22] <sil2100> jhodapp, alex-abreu, bfiller: ok, so the fix is in silo 21?
[14:22] <kgunn_> sil2100: question regarding frozen ppa & manual uploads, does this mean as things get propogated over....will it still be taken from trunk ? (i'm seeing a flaw in the ability to filter)
[14:22] <alex-abreu> sil2100, yes
[14:23] <sil2100> kgunn_: yes, from trunk, so if you release something besides the fix we need, we either have to release all of it, or try to rebuild it somewhere manually with just the fix cherry-picked and then uploading
[14:23] <jhodapp> alex-abreu: seems like you don't need me then
[14:23] <sil2100> Not much we can do here sadly, it's a risk we need t otake
[14:23] <kgunn_> sil2100: ack, up to teams i suppose
[14:23] <sil2100> *to take
[14:24] <alex-abreu> jhodapp, branch wise is everything ok ?
[14:24] <sil2100> Yeah, anyway, it's never a 'no way out' situation, as I said we can always take this single change and rebuild it in a silo and then manually copy
[14:24] <jhodapp> alex-abreu, yeah it's set to merge into the correct branch
[14:24] <jhodapp> and everything else
[14:25] <sil2100> alex-abreu: ok, so if it's good, please switch it to 'Ready for QA' so that someone from QA can take a look at it
[14:26] <jhodapp> alex-abreu, the one thing maybe you could do (or have justinmcp do) is, in a separate silo, propose this same change but against lp:media-hub for wily
[14:26] <sil2100> Once it lands I can copy it and re-spin
[14:26] <jhodapp> alex-abreu, it has to be separate because lp:media-hub and lp:media-hub/stable are fairly different right now, so dual landing is not possible
[14:26]  * sil2100 hugs jhodapp 
[14:26] <sil2100> jhodapp: thanks for keeping track of the wily parts!
[14:26] <alex-abreu> jhodapp, will do, ... I''ll drop justin a line
[14:26] <jhodapp> np
[14:28] <jhodapp> thanks alex-abreu
[14:40] <sil2100> alex-abreu, jhodapp: remember to mark the silo as 'Ready for QA' once it's ready
[14:40] <alex-abreu> sil2100, I did ...
[14:41] <sil2100> Ah, ok, it seems queuebot missed it somehow
[14:41] <sil2100> davmor2, jibel: once you guys have a moment, silo 21 is on the list of required fixes - could you assign someone to test it?
[14:42] <alex-abreu> jhodapp, do you have a proper test case for silo 21 btw ?
[14:42] <AlbertA> trainguards: for https://requests.ci-train.ubuntu.com/#/?req=81
[14:42] <AlbertA> trainguards: who can provide the archive admin review for it?
[15:02] <jhodapp> alex-abreu, no I don't, that would have been something for justinmcp to produce
[15:03] <jhodapp> alex-abreu, you could add to this for a manual test plan: https://wiki.ubuntu.com/Process/Merges/TestPlan/media-hub
[15:04] <alex-abreu> jhodapp, ack
[15:04] <jhodapp> alex-abreu, I'd add a new section for Oxide to that since it will increasingly start to use media-hub more and more
[15:05] <alex-abreu> right
[15:07] <Mirv> AlbertA: I've asked twice on #ubuntu-release, no reply yet
[15:07] <sil2100> Most are probably busy on DebConf right now
[15:07] <Mirv> last was 1.5h ago
[15:10] <AlbertA> Mirv: ack, thanks
[15:37] <jibel> alex-abreu, jhodapp re silo 21, the branch is not reviewed and not top approved
[15:38] <jhodapp> jibel, it was reviewed by me previously, not sure what happened
[15:39] <jibel> jhodapp, oh maybe it has been reset because it was a previous version. Anyway top approval is required
[15:39] <jhodapp> yeah one sec
[15:40] <jhodapp> jibel, done
[15:40] <jibel> thanks
[16:50] <rvr> jibel: Approving silo 21
[16:55] <sil2100> o/
[16:55] <sil2100> Publishing in that case
[16:57] <sil2100> Published, I'll copy it over to the snapshot later on
[17:00] <sil2100> morphis, bfiller, jibel: so, seeing the notes, we'll also need silo 17 for proper trust-store integration on mako and flo
[17:02] <sil2100> ARGH
[17:02] <sil2100> The silo wasn't set for the overlay
[17:02] <sil2100> Damn, could have checked that
[17:03] <jibel> sil2100, yeah, davmor2 just approved it
[17:05] <davmor2> sil2100: do keep up ;)
[17:05] <sil2100> jibel, davmor2: thanks guys!
[17:14] <sil2100> bfiller: hey! Since kgunn is not around, do you know by any chance how far are we from getting the final camera fixes? I saw the bug mentioning 2 hours ago that the branch is still in testing
[17:16] <sil2100> Would be great if we could have this as soon as possible, since the change is in unity8 so QA will have to retest a LOT
[17:21] <sil2100> jibel: hey! If we release silo 23, how much of the regression test suite will you guys have to re-run?
[17:25] <sil2100> ANyway, copying android and media-hub over to the snapshot PPA now
[17:30] <jibel> sil2100, as you said a LOT. this is a very large change and very risky to land it that late
[17:31] <sil2100> bfiller: ^
[17:31] <sil2100> Too bad Kevin is not here
[17:31] <jibel> sil2100, we don't have a unity/mir specific tests in the regression test suite and potentially everything is affected
[17:31] <sil2100> Not sure in what state we would be without that fix
[17:31] <sil2100> mzanetti: hey
[17:32] <mzanetti> sil2100, hey
[17:32] <jibel> sil2100, concretely without the fix the camera app doesn't work on first launch
[17:32] <sil2100> mzanetti: we have some questions regarding silo 23 - it seems it's the final piece to fix trust store integration with the camera? How bad would it be without it?
[17:32] <jibel> sil2100, when you get the trust store prompt
[17:32] <mzanetti> a one-time issue basically
[17:32] <sil2100> Since as you see, landing it now will require re running almost all tests...
[17:33] <mzanetti> yes. also I'm not sure about the quality of 23
[17:33] <mzanetti> seems it decreases rendering performance and is not good enough yet
[17:33] <mzanetti> it does fix the issue tho
[17:33] <sil2100> Then I would really prefer not landing it
[17:33] <mzanetti> but if you ask me we should not land it
[17:33] <sil2100> Can't we workaround the issue somehow?
[17:33] <mzanetti> looking now
[17:33] <sil2100> mzanetti: thanks ;)
[17:33] <mzanetti> we had another brnach with a workaround, but that wasn't reliable enough either
[18:03] <sil2100> mzanetti: give me a ping once you know if it can be somehow worked-aroound
[18:03] <sil2100> I'll go AFK for a bit
[18:03] <mzanetti> ack
[18:03] <mzanetti> kgunn, hey, mind installing 23 and give it a test?
[18:04] <kgunn> mzanetti: on it
[18:04] <kgunn> mzanetti: i was gonna start with mako
[18:04] <kgunn> any other device pref ?
[18:05] <mzanetti> kgunn, hmm... any of them is fine. have arale at hand?
[18:08] <kgunn> mzanetti: yes i do
[18:08] <kgunn> i can certainly do both
[18:13] <bfiller> sil2100, kgunn, mzanetti, jibel: if the fix is risky I'd vote for not including it and living with the bug in camera-app first time you record a video
[18:14] <kgunn> bfiller: i think we'd need to understand the impact for john-mcaleely
[18:14] <kgunn> e.g. customer engagement
[18:14] <kgunn> is it best to continue to release ?
[18:15] <kgunn> or delay release ?
[18:15] <mzanetti> bfiller, I for one would agree. but yes, as Kevin said. customer engagement might be a factor
[18:15] <bfiller> kgunn: +1 on getting john-mcaleely's take, think it will satisfy customer req even without the fix but he needs to confirm
[18:16] <kgunn> cool
[18:16] <kgunn> and sorry this wasn't simple
[18:16] <bfiller> kgunn: no worries, things not always easy
[18:17] <kgunn> at least we might fix the emulator.......finally :)
[18:17] <sil2100> Ok then, so we wait for john-mcaleely ;)
[18:17] <bfiller> kgunn: that's good, pat really wanted that one
[18:18] <kgunn> bfiller: sil2100 we'll keep testing and progressing in the meantime, as if johnmc can't wait
[18:18] <bfiller> ack
[18:19] <bfiller> I'm going to test without the fix on krillin and arale to make sure things work correctly after the first time
[18:19] <sil2100> Makes sense, but landing silo 23 will probably mean we'll have to shift the release
[18:26] <john-mcaleely> aha
[18:26] <john-mcaleely> context kgunn bfiller sil2100 ?
[18:27] <bfiller> john-mcaleely: trust session stuff
[18:27] <bfiller> john-mcaleely: proper fix potentially very risky
[18:27] <bfiller> contemplating going with what we have where camera-app won't work correctly for first recorded video
[18:28] <bfiller> john-mcaleely: would this be acceptable to customer
[18:28] <john-mcaleely> bfiller, it might be
[18:28] <john-mcaleely> bfiller, on the basis that the security works, and the camera app is just buggy
[18:29] <kgunn> right, security is there, it's just the hitting of record after accepting the trust
[18:57] <sil2100> john-mcaleely, bfiller: ok then, so we generally don't wait for 23 then, right?
[18:58] <john-mcaleely> sounds like it sil2100
[18:58] <sil2100> Should I kick a new image then? :)
[18:58] <john-mcaleely> that I don't know :-)
[19:00] <sil2100> bfiller: I think we should be good to kick another promotion candidate now then, right?
[19:00] <bfiller> sil2100: I think so
[19:05] <sil2100> Preparing p/
[19:19] <sil2100> ogra_, bfiller: I'll use the rc-proposed channel for building the image
[19:24] <sil2100> bfiller: image kicked
[19:24] <bfiller> sil2100: cool
[19:25] <sil2100> davmor2, jibel, alesage: the new snapshot based image with the new android (for mako/flo) and media-hub is now building and will appear in rc-proposed after it's done
[19:32] <sil2100> Ok guys, I'll have to log out now for a while - I'll be back in 2-3 hours to check if everything goes well
[19:32] <sil2100> o
[19:32] <sil2100> o/
[20:37] <dobey> hmm, kind of annoying that i can't actually see the in-progress dep 8 tests for the proposed migrations
[21:44] <sil2100> jibel, alesage, ToyKeeper, davmor2, bfiller: bq-aquaris.en channel has the new image - #104
[21:45] <alesage> sil2100, ack
[21:48] <robru> dobey: you around? any thoughts on this failure? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-wily/wily/i386/u/ubuntuone-dev-tools/20150819_192346@/log.gz
[22:01] <dobey> robru: there's a new pep8 i guess?
[22:02] <robru> dobey: dunno why, anyway here's fixes: https://code.launchpad.net/~robru/ubuntuone-dev-tools/fix-tests/+merge/268555
[22:03] <dobey> robru: usually failures like that are the result of a new pep8 or pyflakes
[22:03] <robru> dobey: fair enough. is trunk in a releasable state or should I work on distropatches for the existing package too?
[22:04] <dobey> robru: i guess i'd have to get it set up properly to go through ci train, as it hasn't ever had that done. if you want it done fast, upload a distro patch, and i'll look at the MP when i can
[22:04] <robru> dobey: ok thanks
[22:05] <dobey> i'm gone for the day now though :)
[22:05] <robru> dobey: no worries, will distropatch
[22:49] <ahayzen> Hey, guys there appears to be a calendar autolanding job that is stuck (for 4.5 days) on the coreapps jenkins http://91.189.93.70:8080/ which i think is now blocking the weather-app autolanding