[00:30] <imgbot> [00:30] <imgbot> [02:01] <dobey> ToyKeeper: so i see what's wrong (and commented on the trello). sorry, i didn't realize that the process we're supposed to be using for this was going to be the thing that would fail us when we need it most (but i probably should have expected as much)
[04:45] <imgbot> [05:58] <ToyKeeper> dobey: Thanks for investigating that.  I wonder nobody noticed it before I tried it?
[06:00] <imgbot> [06:00] <imgbot> [06:26] <rsalveti> latest rtm:
[06:26] <rsalveti> [06:26] <rsalveti> qtdeclarative5-cordova-2.8-plugin
[06:26] <rsalveti> wonder if that was indeed desirable
[06:29] <Mirv> doesn't sound too good
[06:35] <Mirv> Saviq: bzoltan_: I'd like to put Qt 5.4.1 to the QA signoff queue after your 006 qtmir + 013 uitk landings, is that ok? (both will need a rebuild after those have landed). ie is that ok before 020 unity8?
[07:13] <bzoltan_> Mirv:  OK
[09:05] <jibel> is there a known problem with krillin on Vivid? I updated my device yesterday and it's stuck on the bq logo
[09:06] <ogra_> jibel, yes, 128 was busted
[09:06] <sil2100> I thought rsalveti and ogra_ fixed the vivid systemd-related problems
[09:06] <ogra_> systemd fun
[09:07] <ogra_> 129 is fine
[09:07] <jibel> k, I'll flash this build
[09:11] <sil2100> Ah, ok, 129 ;)
[09:20] <sil2100> Mirv: ping
[09:20] <sil2100> :)
[09:21] <sil2100> Mirv: can we clean-up vivid silo 11?
[09:22] <pete-woods> trainguards: hi guys. could I get vivid silo 24 reconfigured? thanks!
[09:23] <sil2100> pete-woods: on it
[09:23] <Mirv> sil2100: pong! yes, let me do it
[09:23] <sil2100> pete-woods: hm, silo 24? Wasn't that almost ready for publishing?
[09:26] <sil2100> pete-woods: are you sure?
[09:27] <sil2100> (double-confirming)
[09:33] <pete-woods> sil2100: yes, sure. we needed a fix that blocked the landing
[09:33] <pete-woods> it failed packaging review
[09:33] <pete-woods> (no symbols file)
[10:03] <sil2100> Ok
[10:41] <seb128> hum, why is "reboot" doing a power down on my bq rtm
[10:41] <seb128> reboot = the button in the ui you get when pressed power for some seconds
[10:44]  * sil2100 tries that
[10:46] <sil2100> seb128: it reboots my krillin fine here, I'm running the latest 14.09-proposed
[10:47] <seb128> :-/
[10:47] <seb128> sil2100, thanks, works fine for ogra as well, dunno what is different on mine
[10:47] <ogra_> did you ever make it writable ?
[10:48] <ogra_> :q
[10:48] <ogra_> bah
[10:48]  * ogra_ enables focus-follow-eyes
[11:08] <sil2100> ogra_, jibel, davmor2, popey: who's +1 on skipping todays evening landing meeting? We all basically know what to do, and I'm sure testing will go on until the end of today
[11:08] <ogra_> +1
[11:08] <popey> +1
[11:09] <davmor2> sil2100: it might +1 :)
[11:13] <jibel> sil2100, +1
[11:17] <seb128> hum, disconnected
[11:17] <seb128> ogra_, it's in rw, should that change what reboots do?
[11:18] <ogra_> no, indeed it shouldnt ... but i would suspect that to be a difference that could cause something like this
[11:58] <ogra_> imgbot, map 129
[11:58] <imgbot> krillin rtm version: 129 maps to mako version: 191"
[11:58] <imgbot> krillin rtm version: 129 maps to generic_x86 version: 185"
[11:59] <ogra_> imgbot, map 129 vivid
[11:59] <imgbot> mako ubuntu version: 129 maps to krillin version: 140"
[11:59] <imgbot> mako ubuntu version: 129 maps to generic_x86 version: 133"
[12:36]  * sil2100 off to lunch
[13:18] <Saviq> trainguards, seems the branch link in the "Merge conflict" case is broken (includes dot) http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=landing-020
[13:42] <dobey> cihelp: is there no way to have the jenkins MP and autolanding jobs build clicks for the 14.10 target rather than vivid?
[13:43] <dobey> or better yet, in a proper rtm chroot?
[13:50] <fginther> dobey, 14.09 is equivalent to rtm, right? (just trying to make sure I'm not confused)
[13:51] <dobey> fginther: 14.09 is rtm yes; 14.10 is utopic though
[13:52] <fginther> dobey, are you asking about this in regards to pay-ui?
[13:52] <dobey> fginther: since qt 5.4 landed in vivid, the clicks we're getting from jenkins now aren't usable on rtm
[13:52] <dobey> fginther: indeed
[13:52] <fginther> oh
[13:54] <dobey> so anything with c++ that links to libqtbase5 or whatever, will have this problem if it's using the ubuntu-sdk-14.10 frameworks
[13:54] <fginther> dobey, I'll add it to the list and work with someone else on the team to see if we can update the jobs and configs to do an rtm based build. We do have rtm chroots, so it should work
[13:55] <dobey> fginther: that would be great. we're probably going to need some sort of general solution to this, as i see similar problems happening in 6-8 weeks when the W archive opens up and we start building stuff on top of it too for the next cycle (since it's planned to have gcc5 land as default there)
[13:57] <fginther> dobey, indeed, the current implementation is hacky at best.
[14:51] <oSoMoN> jibel, oxide-qt in vivid-proposed failed the boottest (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#oxide-qt), but the error seems to be in unlocking the unity8 greeter, can this be re-run / unblocked?
[14:51] <sil2100> oSoMoN: I think CI are the ones responsible for boottests
[14:52] <oSoMoN> sil2100, right, who should I ping then?
[14:52] <sil2100> oSoMoN: I suppose cihelp in overall might be a good idea
[14:52] <oSoMoN> cheers
[14:52] <sil2100> All members of the CI team get highlighted on that I guess
[14:53] <Ursinha> yes, we do :)
[14:53] <oSoMoN> cihelp: oxide-qt in vivid-proposed failed the boottest (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#oxide-qt), but the error seems to be in unlocking the unity8 greeter, can this be re-run / unblocked?
[14:53] <Ursinha> oSoMoN: I'll have a look, we know what the problem is, just a moment
[14:53] <oSoMoN> excellent, thanks!
[15:00] <sil2100> pete-woods: hmmm, the spreadsheet did something funny
[15:00] <sil2100> And I think request line 61 got corrupted
[15:03] <sil2100> pete-woods: can you fill in all the correct data there? I can access my backups if needed
[15:04] <pete-woods> sil2100: I just added that row again after dobey reverted his stuff
[15:04] <pete-woods> it looks correct to me
[15:06] <sil2100> pete-woods: hm, so your merge was the merge for thumbnailer from tsdgeos ?
[15:06] <kalikiana> ci help, ping, "ERROR _launcher:206 - Timed out waiting for Application with app_id 'tmpz04d7x53' to stop" there's some really strange failures to run autopilot tests
[15:06] <kalikiana> https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/1520/testReport/junit/ubuntuuitoolkit.tests.custom_proxy_objects.test_listitems/SwipeToDeleteTestCase/test_swipe_item_to_right/
[15:07] <pete-woods> sil2100: yes
[15:09] <sil2100> pete-woods: ok, let me assign a silo then... it seems the line below yours has been corrupted then
[15:09] <pete-woods> roll on airline!
[15:09]  * sil2100 goes to correct that
[15:12] <sil2100> pete-woods: hm, wait
[15:14] <sil2100> pete-woods: all my backups mention thostr_ as the person requesting the landing of merge https://code.launchpad.net/~aacid/thumbnailer/fix_dbus_blocking/+merge/251065
[15:14] <dobey> pete-woods: there was a separate row that thostr_ added for the same landing btw
[15:14] <sil2100> pete-woods: while it seems your silo has the same thing
[15:14] <sil2100> Ah, ok, now that explains it
[15:14] <pete-woods> okay, just bin it all :)
[15:14] <sil2100> I thought that thostr_ had a different merge just spreadsheet got broken
[15:15] <fginther> kalikiana, launching of the app during a test is handled entirely by the test suite and the application launch facilities on the phone. The CI infrastructure does not start or stop the application. I do see that there is a crash, maybe that will help.
[15:15] <dobey> have we made the spreadsheet too big now with the archive that google gets all out of sync or whatnot?
[15:15] <fginther> kalikiana, and please use "cihelp" all one word
[15:19] <kalikiana> fginther: hmm I guess I'll revert to qa then. I don't think there's a "launch team" to ask
[15:19] <kalikiana> fginther: how do you see it's crashed?
[15:20] <fginther> kalikiana, go to the main link for the build, https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/1520/, then follow the "Build Artifacts" link
[15:21] <fginther> kalikiana, then follow that down through "ubuntuuitoolkit"
[15:22] <Saviq> trainguards, what's this about https://ci-train.ubuntu.com/job/ubuntu-landing-020-1-build/94/console ?
[15:23] <Mirv> Saviq: train thinks there maybe aren't any changes, so you'd like to specify unity8 in the packages_to_rebuild
[15:23] <Saviq> does the train not rebuild all packages by default now?
[15:23] <Mirv> Saviq: I'm not crystal clear on the logic myself..
[15:24] <sil2100> Saviq: do you want to rebuild unity8?
[15:24] <sil2100> Well, after Robert's rewrites the train is no longer feature-exact (which was a concern from Didier)
[15:25] <sil2100> Saviq: you need to enter the name of the package you want to build
[15:26] <Saviq> sil2100, yeah, I did, was just surprised it doesn't rebuild them all by default
[15:28] <kalikiana> fginther: that crash file can't be related, wrong binary and wrong pid… how do I find the appropriate file that belonds to the failing test?
[15:33] <fginther> kalikiana, it looks like only the first crash gets collected. The pid, 3956, appears to match up for this test - https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/1520/testReport/ubuntuuitoolkit.tests.custom_proxy_objects.test_main_view/MainView10TestCase/test_close_toolbar/
[15:33] <fginther> kalikiana, or am i not reading things right?
[15:35] <sil2100> dobey: I'm looking at the packaging changes for silo 29 - I'm wondering, for ubuntuone-credentials-autopilot you did that trusty compatibility layer and not for unity-scope-click - is the former used in something besides touch?
[15:36] <dobey> sil2100: unity-scope-click already doesn't build on trusty becuase it requires newer versions of many other things, particularly the unity scopes API and such
[15:37] <dobey> sil2100: so i left out the | deps on it, because they wouldn't be useful anyway. but ubuntuone-credentials still builds on trusty, so i want to keep it building on trusty if possible
[15:37] <dobey> well, building and installing
[15:37] <dobey> ubuntuone-credentials has not had much change since trusty
[15:37] <sil2100> dobey: are we using ubuntuone-credentials on the desktop or anywhere besides touch?
[15:38] <dobey> sil2100: i use LTS as host OS, so it's easier to develop/test with it still working on trusty
[15:41] <sil2100> I'm just thinking that the | deps might be a bit unneeded, since we're anyway concentrating on the latest development release with new packages - we can't expect every new package in the archive being buildable on older platforms
[15:41] <sil2100> Besides, we're not building trusty touch images at all
[15:41] <sil2100> But that's just a minor nit-pick
[15:41] <sil2100> Let me publish
[15:43] <dobey> sil2100: we're not expecting everey package in the archive to be buildable on every platform. i'm just keeping the one that already exists and is buildable on the LTS, as such :)
[15:44] <dobey> anyway, thanks
[15:50] <kalikiana> fginther: that test case isn't using qmlscene either
[15:51] <sil2100> charles: assigning!
[15:52] <kalikiana> fginther: also "Search criteria (pid = 3956" != _usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash
[15:52] <charles> cihelp, I suspect I should mark line 62 as "QA signoff needed: no" so am asking... this just adds new regression tests, so there's nothing really to test that doesn't get tested automatically
[15:52] <sil2100> charles: btw. line 62... was that by accident removed from the spreadsheet? Since I think I saw it in the morning but then it was gone
[15:52] <charles> sil2100:  :)
[15:52] <charles> sil2100, I was wondering the same thing. I added it about 10 hours ago but couldn't find it when I began my day
[15:52] <sil2100> charles: (ping trainguards for train related things, since all trainguards are actually non-CI)
[15:53] <charles> trainguards, I suspect I should mark line 62 as "QA signoff needed: no" so am asking... this just adds new regression tests, so there's nothing really to test that doesn't get tested automatically
[15:53] <charles> :)
[15:53] <fginther> kalikiana, Oh, I guess I misunderstood what "Pid:	3956" is referring to in that crash file.
[15:53] <sil2100> charles: I think I checked that in the morning and was like 'yeah, this seems like not requiring QA sign-off'
[15:53] <sil2100> charles: and it seems the spreadsheet just eats up lines since yesterday...
[15:53] <charles> sil2100, the fix_bus_blocking  line seems to have overwritten it in the spreadsheet for some reason
[15:54] <fginther> kalikiana, I'm out of ideas here on what to look at. Are there log files missing that should be collected?
[15:54] <fginther> kalikiana, there's also the option to try to reproduce the results on your own device. documentation is here: http://ubuntu-test-cases-touch.readthedocs.org/en/latest/
[15:55] <fginther> kalikiana, just keep in mind that when using that how-to, the device will be wiped with a fresh image
[15:55] <kalikiana> hmmm maybe "[1426029780.173844] <ERROR> mircommon: Caught exception at Mir/EGL driver boundary (in setSwapInterval): /build/buildd/mir-0.12.0+15.04.20150228/src/client/buffer_stream.cpp(283): Throw in function virtual void mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)
[15:55] <kalikiana> Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_errorEEEE
[15:55] <kalikiana> std::exception::what: Attempt to set swap interval on screencast is invalid" is the real error message here
[15:56] <fginther> kalikiana, That's definitely outside my expertise
[15:56] <kalikiana> I wouldn't suggest anything's missing from the logs - if it's not a crash it may be fine
[15:57] <kalikiana> so I guess I'll head over to unity folks
[15:57] <fginther> kalikiana, good luck
[15:57] <kalikiana> fginther: thanks for your assistance!
[15:58] <charles> sil2100, marking that i-messages MP as not requiring signoff
[15:59] <sil2100> charles: assigning - I checked the merge and it looked good
[16:00] <charles> sil2100, ack
[16:17] <sil2100> jibel, davmor2: how's the image testing going so far?
[16:17] <davmor2> sil2100: sanity passed
[16:18] <jibel> sil2100, it's very early to know
[16:19] <sil2100> jibel, davmor2: at least sanity is ok - did you guys already reach webapp testing? (to see if the cordova removal caused any issues)
[16:19] <fginther> nerochiaro, FYI, the camera-app MP tests should now be using the correct dependencies. Let us know if any builds need a re-run
[16:20] <davmor2> sil2100: I'm still looking at RTM OTA from 224 → 255 so I guess the ebay app opens
[16:20] <nerochiaro> fginther: they were already in the most recent run, i think
[16:21] <jhodapp> sil2100, can you please reconfigure line 33?
[16:25] <sil2100> jhodapp: sure
[16:25] <jhodapp> sil2100, thanks
[16:27] <sil2100> jhodapp: done
[16:27] <jhodapp> awesome thanks
[16:40] <kalikiana> fginther: fyi if anyone else asks it turned out to be https://bugs.launchpad.net/mir/+bug/1425307
[16:58] <sil2100> robru: just in case you didn't get teh message by mail - we skipped today's evening landing meeting
[16:59]  * sil2100 jumps out for a moment to get a perscription from the doctor
[16:59] <sil2100> brb
[17:05] <robru> sil2100: thanks
[17:07] <popey> sil2100: i see tvoss silo 4 is +1 from QA... That would be helpful for us on clock.
[17:08] <dobey> fginther: re: rtm-based click builds, i'm wondering if i should block on that, or build a click myself locally for testing, and then one for uploading to the store when it lands to trunk.
[17:12] <fginther> dobey, I'm hoping to have a better answer today on if this is do-able within the current infrastructure. But if you urgently need something, you should look into an alternative
[17:15] <dobey> fginther: ok, i think it's too late to get it into this weeks ota image at this point anyway, so i'll wait until tomorrow for more drastic measures, and see what you have to say later on today. thanks
[17:29] <dobey> what is this new "boottest" that is all lies and blocking migration of my package? :(
[17:51] <jibel> sil2100, mterry on rtm/krillin 255, the power dialog doesn't display on the wizard
[17:59] <jibel> sil2100, mterry davmor2 bug 1430942
[18:00] <jibel> davmor2, can you confirm
[18:00] <jibel> ?
[18:00] <jibel> pmcgowan, ^ on the promotion candidate
[18:00] <sil2100> jibel: uh
[18:01] <sil2100> Not good
[18:01] <jibel> sil2100, after the wizard it's ok, it is just in the wizard
[18:01] <jibel> on first boot
[18:01] <sil2100> jibel: how can I re-enable the wizard on my phone? What file was needed to be touched?
[18:01]  * sil2100 would like to confirm on his phone
[18:02] <jibel> sil2100, remove /home/wizard/.config/ubuntu-system-settings/wizard-has-run
[18:02] <jibel> sil2100, davmor2 confirmed it
[18:02] <sil2100> jibel: ah, ok then
[18:02] <jibel> */home/phablet/
[18:02] <sil2100> geh, well, I think it's not super blocking, but still would suck to have it on an official OTA
[18:02] <sil2100> kenvandine, mterry: ^
[18:03] <pmcgowan> hmm
[18:03] <pmcgowan> did we even update the wizard this ota?
[18:05] <kenvandine> ugh... i think only one change in the wizard, which just prevented clicking the continue button twice on password set
[18:05] <sil2100> pmcgowan: ubuntu-system-settings was upgraded multiple times
[18:05] <elopio> cihelp: the tests in https://code.launchpad.net/~veebers/autopilot/fix_for_config_init/+merge/251862 are stuck.
[18:05] <pmcgowan> sil2100, yeah but shouldnt effect that, could even be a shell change
[18:06] <kenvandine> sil2100, but i think the past fix that was needed to show the power dialog in the wizard was from the shell
[18:06] <fginther> elopio, just fixed it
[18:06] <kenvandine> in fact, i think the wizard imports some components from the shell
[18:06] <kenvandine> to do it
[18:06] <kenvandine> mterry, ^^ can you confirm?
[18:06] <elopio> fginther: cool. So, should I just wait or retrigger?
[18:06] <kenvandine> sil2100, pmcgowan: so i think most likely a change in unity8 may have broken the wizard
[18:07] <fginther> elopio, just wait, the tests are running now
[18:08] <elopio> thanks fginther.
[18:09] <Ursinha> fginther: what did you do to fix that?
[18:09] <pmcgowan> kenvandine, I dont even see a unity landing yet
[18:12] <fginther> Ursinha, I had to switch the node that those tests were executing on. I had failed to update this last night when I was working on the vanguard issue with the tests timing out
[18:12] <dobey> pmcgowan: i saw a unity8 silo in the list, but there was a merge conflict mentioned in the status column for it
[18:12] <dobey> oh, well, for vivid probably
[18:13] <mterry> kenvandine, sorry was afk
[18:13] <dobey> don't know if there is one for rtm
[18:13] <Ursinha> fginther: got it. collecting data as I'm vanguard tomorrow  :)
[18:13] <mterry> kenvandine, wizard in rtm does import some stuff from unity8
[18:13] <mterry> kenvandine, sil2100, jibel: specifically, the part that shows the power dialog
[18:14] <kenvandine> i thought so
[18:14] <kenvandine> file:///usr/share/ubuntu/settings/wizard/qml/main.qml:233: TypeError: Property 'onPowerKeyPressed' of object Dialogs_QMLTYPE_79(0x10688c8) is not a function
[18:14] <kenvandine> from the log
[18:15] <pmcgowan> of fook
[18:15] <kenvandine> that must be from a unity8 dialog
[18:16] <pmcgowan> but thats the original code I think from when this was fixed https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1381731
[18:17] <kenvandine> yes
[18:17] <kenvandine> the fix for that was to use the dialog from unity8
[18:17] <kenvandine> they must have made a change to that in unity8
[18:18] <kenvandine> UnityComponents.Dialogs
[18:18] <kenvandine> and dialogs.onPowerKeyPressed
[18:18] <pmcgowan> right
[18:19] <kenvandine> so must have been a unity8 landing that broke this
[18:19] <pmcgowan> Saviq, ?
[18:19] <kenvandine> no telling how long ago...
[18:22] <pmcgowan> kenvandine, can we make sure this is in the wizard test plan :(
[18:22] <pmcgowan> this was reported for the mfg line
[18:25] <mterry> kenvandine, pmcgowan: i will look at this today
[18:26] <pmcgowan> mterry, this is blocking the update release fyi
[18:26] <pmcgowan> mterry, we will want to respin and get to qa
[18:30] <mterry> pmcgowan, kenvandine: yup, I see in unity8's rtm branch that the power dialog is summoned a different way
[18:31] <pmcgowan> mterry, so for the record UnityComponents should prolly not break apis
[18:31] <mterry> pmcgowan, well that was one of the reasons we moved the wizard into unity8.  It was depending on things in unity8 that weren't official APIs
[18:32] <kenvandine> pmcgowan, well this is why we moved it
[18:32] <pmcgowan> I bet its broken in vivid too
[18:32] <mterry> pmcgowan, I'd be surprised, because the wizard in vivid no longer has separate power handling code
[18:32] <pmcgowan> ack
[18:33] <kenvandine> mterry, can you whip up a fix?
[18:33] <mterry> kenvandine, looking now
[18:33] <kenvandine> mterry, thx
[18:42] <mterry> kenvandine, please test lp:~mterry/ubuntu-system-settings/power-dialog-fix-rtm
[18:42] <mterry> kenvandine, I have *not* tested yet, am ref-lashing
[18:42] <kenvandine> i don'
[18:42] <kenvandine> t have rtm atm
[18:43] <kenvandine> i need to flash as well
[18:43] <mterry> kenvandine, fair enough  :)
[18:45] <mterry> I burned my nachos for this emergency fix  :-/
[18:45] <pmcgowan> lol
[18:46]  * mterry files expense report
[18:47] <kenvandine> haha
[18:47] <olli> approved
[18:59] <sil2100> ;)
[19:00] <mterry> kenvandine, pmcgowan: looks like it works to me
[19:00] <kenvandine> mterry, can you propose it?
[19:00] <kenvandine> i'm still trying to get my device ready for it
[19:00] <kenvandine> but i can at least get it building in a silo
[19:01] <mterry> kenvandine, I did
[19:01] <kenvandine> cool
[19:01] <mterry> kenvandine, https://code.launchpad.net/~mterry/ubuntu-system-settings/power-dialog-fix-rtm/+merge/252639
[19:02] <kenvandine> mterry, building in silo 1
[19:02] <kenvandine> pmcgowan, ^^
[19:02] <mterry> kenvandine, thanks!
[19:02] <kenvandine> thank you
[19:02] <pmcgowan> mterry, thanks man
[19:03] <mterry> you're welcome ! :)
[19:03] <sil2100> \o/
[19:03] <sil2100> mterry: thanks!
[19:04] <sil2100> jibel, davmor2: are you +1 on re-spinning the promotion candidate with the new wizard fix (after it gets QA'ed and lands?)?
[19:04] <sil2100> jibel, davmor2: I suppose only wizard tests would have to be re-run
[19:05] <davmor2> sil2100: I guess so
[19:09] <mterry> davmor2, that's the only bit I changed -- some qml in the wizard
[19:10] <davmor2> mterry: Shame on you, I hope you are thoroughly ashamed of yourself ;)
[19:15]  * mterry takes a quick shower, will be afk for a bit
[19:29]  * mterry is back
[19:41] <sil2100> o/
[19:42] <sil2100> kenvandine: once the silo is ready for sign off, could you please poke davmor2 and ToyKeeper?
[19:42] <sil2100> robru: ^ keep a lookout for rtm silo 1 landing
[19:42] <robru> sil2100: will do
[19:42] <davmor2> kenvandine: I'd poke ToyKeeper I'm likely to be gone ;)
[19:42] <sil2100> kenvandine: once silo 1 lands we'd need rsalveti to kick a new image - I'll try to join in like 1-2 hours in case everything is ready by then
[19:42] <sil2100> robru: thanks :)
[19:43] <ToyKeeper> Hmm?  Wizard fix?
[19:43] <sil2100> ToyKeeper: yeah, a regression in the promotion candidate
[19:43] <rsalveti> just ping me when you need me
[19:43]  * sil2100 needs to jump out now, back in 1-2 hours
[19:43] <ToyKeeper> Okay, just wanted to make sure it was the one I was expecting.
[19:43] <sil2100> o/
[19:43] <davmor2> ToyKeeper: yeap power dialog doesn't appear if you press the power button in the wizard
[19:48] <pmcgowan> mterry, this is the bug if you want to attach your branch https://bugs.launchpad.net/ubuntu-rtm/+source/ubuntu-system-settings/+bug/1430942
[19:50] <mterry> OK, linked em
[20:28] <kenvandine> mterry, could you test silo 1?
[20:28] <kenvandine> i still can't seem to get a device flashed :/
[20:28] <mterry> kenvandine, ok
[20:29] <kenvandine> my krillin has been pushing the image to the device for nearly an hour now
[20:29] <mterry> kenvandine, what's the deb line for an rtm silo?
[20:29] <mterry> kenvandine, it's different than vivid ones, right?
[20:29] <kenvandine> use citrain device-upgrade 1 ubuntu-rtm
[20:30] <kenvandine> oh, and you need the passcode
[20:30] <kenvandine> use citrain device-upgrade 1 0000 ubuntu-rtm
[20:30] <kenvandine> for example
[20:30] <mterry> kenvandine, oh right...  I forgot citrain exists
[20:30] <kenvandine> hehe
[20:38] <kenvandine> ToyKeeper, silo 1 (wizard regresson) ready
[20:39] <ToyKeeper> kenvandine: Thanks.  :)
[20:39] <robru> mterry: lucky
[20:39] <mterry> robru :)
[20:39] <kenvandine> robru, lol
[20:39] <mterry> kenvandine, should I stop then?
[20:39] <robru> hehe
[20:39] <kenvandine> mterry, yes
[20:39] <mterry> kenvandine, yay
[20:39] <kenvandine> i guess i can stop too :)
[20:39] <kenvandine> mterry, thanks for the speedy fix
[20:40] <mterry> kenvandine, my pleasure  :)
[20:40] <kenvandine> can't wait to get the vivid version synced to rtm :)
[20:41] <mterry> kenvandine, I KNOW
[20:41] <mterry> kenvandine, so much goodness waiting to be unleashed (and some regressions...  but meh)
[20:42] <kenvandine> ha :)
[20:49] <ToyKeeper> After just quick testing, I see no new issues and the known one is fixed.
[20:50] <ToyKeeper> Still not possible to actually read the HERE text, but it has been that way for quite a while...
[20:55] <robru> oooh
[20:56] <robru> kenvandine: should I publish? or will you?
[21:01] <robru> no response, I'll publish
[21:01] <pmcgowan> +1
[21:24] <robru> charles: so we decided that silo 11 doesn't need qa because it only adds tests and doesn't change anything?
[21:24] <charles> robru, right
[21:24] <robru> charles: my kind of silo ;-) ok, will publish
[21:24] <charles> :-)
[21:46] <robru> anybody planning on publishing anything else today?
[23:43] <sil2100> o/
[23:44] <sil2100> ToyKeeper: did the fix silo get signed-off?
[23:46] <sil2100> Oh, I see it did
[23:47] <sil2100> ToyKeeper: did someone kick the new image already?
[23:49] <sil2100> Ok, I don't see imgbot saying anything
[23:50] <sil2100> imgbot: help