[00:05] <robru> Kaleo, can do. just on phone.
[00:25] <thomi> cihelp: What's the upstream-merger jenkins address since the 1SS move?
[00:25] <thomi> the wiki here(https://wiki.canonical.com/UbuntuEngineering/CI/Playbook) contains a link that doesn't seem correct any more
[00:26] <thomi> i.e.- http://s-jenkins.ubuntu-ci:8080
[00:28] <thomi> nvm - I didn't have the additional DNS server configured. works now - thanks
[00:46] <robru> Kaleo, ok, confirmed AP tests passing and published.
[02:05] <plars> thomi: it's still s-jenkins
[02:06] <thomi> plars: yep - but you need a DNS server now.
[02:06] <thomi> don't get me wrong, that's an *excellent* thing, I just didn't have he config set up correctly :)
[02:09] <cjohnston> plars: did we send out an email about that change?
[07:20] <didrocks> hey Mirv, just gave you one (small) landing action :)
[07:27] <Mirv> didrocks: ok, thanks
[07:27] <didrocks> thanks to you!
[08:14] <Mirv> hmm, what broke loading of unity8 tests for me
[08:32] <Mirv> I got something along the lines of http://bugs.python.org/issue19352, but well I've dist-upgraded so I'll update to r32 system image instead
[08:32] <Mirv> and then only install unity8-autopilot and the packages to test
[08:36] <Mirv> hmmkay, or maybe full flash then...
[08:57] <ev> cjohnston: the dns server? Yes, and updated the VPN documentation for it.
[09:00] <cjohnston> ack. looks like some people missed The email
[09:02] <didrocks> cjohnston: still up? starting to be quite late for you :)
[09:03] <cjohnston> still up, up again, is there really a difference?
[09:04] <didrocks> cjohnston: I don't think there is in practice :)
[09:19]  * Mirv now has busybox only...
[09:20]  * ogra_ might be a tad late for the meeting
[09:22] <didrocks> Mirv: what about busybox?
[09:31] <Mirv> didrocks: I ended up with a device booting into it...
[09:31] <Mirv> something failing with flashing. now just recovered.
[09:32] <sil2100> I hate my google hangouts right now...
[09:34] <ogra_> bug 1253810
[09:38] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20131126.1.changes
[09:50] <didrocks> http://ci.ubuntu.com/smokeng/trusty/touch/maguro/32:20131126.2:20131126/5120/
[09:50] <didrocks> ogra_: ^
[09:50] <ogra_> http://ci.ubuntu.com/smokeng/trusty/touch/maguro/32:20131126.2:20131126/5123/gallery-app-autopilot/
[10:02] <ogra_> [10:07] <vila> Mirv: so, yeah, don't trust http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/627/console
[10:09] <Mirv> distrust enabled
[10:10] <vila> Mirv: :)
[10:13] <vila> Mirv: I'll try to monitor the next job running there but ping me if you notice one before me
[10:14] <vila> Mirv: a new container was created 5 minutes ago and I can start and stop it, so all should be fine. It's just that I've seen weird error messages and can't remember if I've seen them before
[11:54] <didrocks> sil2100: hey, can you release ubuntu-system-settings-online-accounts trunk as well? We have the AP fixes
[11:54] <didrocks> ogra_: popey: is image 32 promoted?
[11:55] <sil2100> didrocks: sure, any specific tests I should run?
[11:55] <didrocks> sil2100: I think just install it and try to create/delete an account
[11:55]  * didrocks adds to the landing spreadsheet
[11:55] <didrocks> tahnks!
[11:56] <sil2100> Ok ;)
[11:56] <sil2100> Damn, someone's drilling hard from my neighbours, started like around 8 in the morning
[11:56] <ogra_> didrocks, not yet ...
[11:56] <ogra_> popey, did you test it yet ?
[11:57] <popey> yes, seems okay to me
[11:57] <ogra_> ok
[11:57] <ogra_> let me publish it then
[11:57] <popey> aside from my alsamixer issue which I don't believe is a) regression or b) show stopper
[11:58] <didrocks> popey: alsamixer issue? (yeah, seeing the list, doesn't seem probably it's a regression)
[11:58] <didrocks> probable*
[12:00] <popey> didrocks: you can reboot the phone by just running alsamixer
[12:00] <popey> bug 1255344
[12:01] <didrocks> popey: oh, indeed! nice easter egg :)
[12:01] <ogra_> popey, done, want to send a mail ? http://people.canonical.com/~ogra/touch-image-stats/20131126.2.changes
[12:01] <didrocks> popey: so yeah, not critical :p
[12:01] <popey> nope, didrocks seems to be sending mails now
[12:01] <ogra_> k
[12:01] <didrocks> popey: you can to the avenger list, or do you want me to?
[12:01] <popey> knock yourself out
[12:02]  * popey updates to 32
[12:02] <didrocks> popey: ogra_: I'll roll that with the more news we are getting on the landing (so in the afternoon)
[12:02] <didrocks> popey: ok, doing then
[12:02] <popey> ok, cool
[12:02] <ogra_> k
[12:31] <sil2100> didrocks: did you refresh the whitelist to include unity-scopes-api? ;)
[12:33] <didrocks> sil2100: yep
[12:39] <sil2100> didrocks: thanks ;)
[13:41] <sil2100> Can anyone try running ubuntu-system-settings-online-accounts AP tests on their device? Since I seem to be unable to do so, they're not working
[13:41] <sil2100> And it doesn't seem to be a regression, the distro version does not work as well
[13:41] <sil2100> I get:
[13:41] <sil2100> ImportError: 'test_online_accounts_ui' module incorrectly imported from '/usr/lib/python2.7/dist-packages/online_accounts_ui/tests'. Expected '/usr/lib/python2.7/dist-packages/online_accounts_ui/tests'. Is this module globally installed?
[13:42] <sil2100> Anyone know how to proceed? Upstream doesn't know as well
[13:42] <seb128> sil2100, see #ubuntu-devel backlog (downgrade python)
[13:48] <Saviq> cihelp, there's only one otto runner available http://s-jenkins.ubuntu-ci:8080/label/ps-radeon-hd8350||ps-nvidia-gt630/? is that known?
[13:50] <cjohnston> vila: any idea ^
[13:50] <retoaded> Saviq, I'm looking into ps-nvidia-gt630 now
[13:51] <vila> Saviq: yes, I didn't know the queue was that ... but I leave you in retoaded safe hands ;)
[13:51] <vila> cjohnston: look at the the CI Vanguard list ;)
[13:52] <cjohnston> vila, I was lookin at the 1ss list. thought it was still part of that
[13:57] <vila> cjohnston: right, I tried to clean things up and get them under light. I may have put too much in Vanguard but I'd rather move them later in post 1ss than the opposite
[13:58] <cjohnston> ack
[14:02] <retoaded> Saviq, ps-nvidia-gt630 is back online
[14:02] <Saviq> retoaded, thanks
[14:02] <retoaded> Saviq, np
[14:07] <cjohnston> sil2100: ping
[14:44] <kenvandine> fginther, https://code.launchpad.net/~ken-vandine/cupstream2distro-config/webcred_artifacts/+merge/196915
[14:54] <Saviq> retoaded, hey, there seems to be a dep issue in otto http://s-jenkins.ubuntu-ci:8080/job/autopilot-testrunner-otto-trusty/1047/console
[14:54] <Saviq> retoaded, can you see what exactly is happening?
[14:56] <Saviq> retoaded, ah I see what happens I think... libunity-mir1 is already built against mir 0.1.2, but it's not published yet https://launchpad.net/ubuntu/+source/mir
[14:57] <Saviq> didrocks, how could that happen, btw ↑? unity-mir isn't in the mir stack is it?
[15:22] <dobey> didrocks: hey. i was bugging fginther last night about daily-release stuff and had some concerns about upstream version number maintenance, and how the docs suggest using non-native version strings for the native packages
[15:24] <Saviq> cihelp, bug #1253198 is really deadly for otto testrunners... especially when there's only one as it happened today
[15:49] <sil2100> cjohnston: hi! Could you wait a moment?
[15:50] <cjohnston> sil2100: sure
[16:03] <Saviq> cihelp, ev, this needs some attention: bug #1255578
[16:04] <didrocks> Saviq: part of the issue is that unity-mir is built against latest mir
[16:04] <Saviq> didrocks, yeah, how? daily-build PPA?
[16:04] <didrocks> Saviq: we remove the mir + rebuild a lot in the past when it wasn't releasable
[16:04] <didrocks> Saviq: yeah
[16:05] <Saviq> didrocks, why would it build against that?
[16:05] <didrocks> Saviq: but, I guess it's time for upstream to act up and fix their regression so that we can move on
[16:05] <Saviq> didrocks, sure, move on is one thing
[16:05] <didrocks> Saviq: well, because they merge their new release in trunk
[16:05] <Saviq> didrocks, making sure it doesn't happen is another
[16:05] <didrocks> Saviq: yeah, the contract with them (if they break their ABI) is that they followup until the transition is over
[16:06] <didrocks> Saviq: which obviously, for multiple releases isn't happening
[16:06] <didrocks> I pinged Kevin yesterday, he asked kdub, but I didn't get any feedback
[16:06] <didrocks> so getting mir unblocked
[16:06] <didrocks> then, we can process the rest and there will be no ABI-linkage issue
[16:06] <ev> retoaded: ^ vanguard?
[16:07] <ev> or are you still super busy with 1SS fixing?
[16:07] <cjohnston> ev: I told him we would handle vanguard
[16:07] <didrocks> dobey: on versionning, actually, for all packages, we are not native. We do use split mode
[16:07] <didrocks> dobey: to create an upstream tarball
[16:07] <Saviq> didrocks, ok, that still doesn't explain how unity-mir trunk could've moved past mir 0.1.1
[16:07] <Saviq> didrocks, or well, daily-build explains *how*, but not *why*
[16:08] <dobey> didrocks: eh? how is it not native if the debian/ dir is in-tree?
[16:08] <didrocks> Saviq: ? daily-build ppas contains: mir
[16:08] <didrocks> Saviq: mir 0.1.2
[16:08] <didrocks> AFAIK
[16:08] <ev> cjohnston: cool, thank you
[16:08] <didrocks> so unity-mir rebuilt against it
[16:08] <Saviq> didrocks, yes, but nothing else builds against daily-build
[16:08] <Saviq> didrocks, otto does not, -ci, -autolanding don't
[16:08] <Saviq> didrocks, so we're deadlocked now
[16:08] <didrocks> Saviq: oh, you are talking about upstream merger?
[16:08] <Saviq> didrocks, yes
[16:09] <didrocks> dobey: bzr split mode is creating the origin tarball + diff.gz
[16:09] <didrocks> dobey: feature of bzr-builddeb
[16:09] <didrocks> Saviq: ah, that's another story, I guess they are adding the ppa
[16:09] <Saviq> didrocks, sorry, probably shouldn't have bugged you about this
[16:09] <didrocks> Saviq: no worry ;)
[16:09] <didrocks> so, yeah, I agree, it should be an optional think
[16:10] <dobey> didrocks: but are actual release tarballs being made and published anywhere that isn't the ubuntu archive? like say, the launchpad downloads for the project?
[16:10] <didrocks> (that's also what the CI Airline fixes)
[16:10] <cjohnston> didrocks: do you know what needs to happen to fix this? /me doesn't know much of anything about upstream merger
[16:10] <didrocks> dobey: some upstream does (and so bump upstream version at the same time)
[16:10] <didrocks> dobey: other just rely on the automatic split mode, there is no real enforcement here
[16:10] <didrocks> cjohnston: let me look, I think I can find example on the config
[16:11] <didrocks> cjohnston: however, I don't know how to deploy this, I hope you do :)
[16:11] <dobey> didrocks: that seems quite confusing; and is quite inconsistent
[16:12] <didrocks> dobey: well, in practice, it's working well for the 250 projects (most of them doesn't care to create real upstream tarballs)
[16:12] <cjohnston> didrocks: haha
[16:12] <cjohnston> I can research it, but we'll see
[16:12] <didrocks> cjohnston: hum, yeah, I thought there was a "no_ppa" tweak in the config
[16:13] <didrocks> cjohnston: I can't find any example :/
[16:13] <didrocks> ah
[16:13] <didrocks> fonud it
[16:13] <didrocks> found*
[16:13] <didrocks> cjohnston: so, lp:cupstream2distro-config
[16:13] <didrocks> stacks/head/apps.cfg
[16:13] <didrocks> look at use_stack_ppa: False # Disabled temporarily due to autopilot regression
[16:14] <didrocks> you need to do the same in stacks/head/unity8.cfg
[16:14] <dobey> didrocks: sure. but "it works" doesn't mean it's optimal, or not confusing, or consistent. :)
[16:14] <didrocks> under unity-mir:
[16:14] <didrocks> dobey: opened to suggestion :) Just to be clear: I dont' want upstream having to do releases
[16:14] <didrocks> use_stack_ppa: False # disable until Mir transitionned their ABI
[16:15] <dobey> didrocks: wouldn't it be better to advise on consistency and using native format for all the projects who don't want to do upstream tarball releases?
[16:15] <didrocks> cjohnston: then, you have to deploy that on your jenkins instance, and for that…
[16:15] <didrocks> dobey: well, some people are really opposed to have native formats
[16:15] <didrocks> because they ship in debian
[16:15] <didrocks> and so, they want to have upstream tarballs
[16:15] <dobey> didrocks: yes, i don't care about some. i care about majority. :)
[16:15] <didrocks> (TBH, I would really +1 for native everyone)
[16:16] <didrocks> dobey: yeah, but again, question of consistency :)
[16:16] <dobey> didrocks: some things will always be special cased
[16:16] <dobey> didrocks: i'd rather have overwhelming consistency, than absolutely no consistency :)
[16:16] <didrocks> dobey: we do have consistency: split mode for everyone
[16:16] <dobey> upstream tarballs shouldn't be on daily-release anyway
[16:17] <didrocks> dobey: well, we do want to daily release everything we are upstream for
[16:17] <dobey> didrocks: but that is the wrong way to package the native packages. yes it works, but it's still wrong :)
[16:17] <didrocks> same rule for all code produced at Canonical
[16:17] <dobey> and there's no reason daily release things can't go into debian, as native packages
[16:17] <didrocks> but why keeping native? it's not native if you are in split mode
[16:18] <didrocks> dobey: you do have other chain of deps
[16:18] <didrocks> in debian
[16:18] <dobey> split mode is a hack :)
[16:18] <didrocks> well, again, this hack is working for all the projects we do maintain
[16:19] <didrocks> cjohnston: do not forget to push the change, there is an upstream merger for the config
[16:21] <psivaa> robru: would you mind taking a look at friends app test failures pls? looks in relation to r118
[16:22] <Saviq> didrocks, FWIW, kdub says this might help https://code.launchpad.net/~kdub/mir/fb-device-enablescreen/+merge/196797
[16:22] <Saviq> didrocks, do you know if anyone checked?
[16:22] <psivaa> robru: http://ci.ubuntu.com/smokeng/trusty/touch/mako/33:20131127:20131126/5136/friends-app-autopilot/531991/
[16:22] <cjohnston> didrocks: https://code.launchpad.net/~cjohnston/cupstream2distro-config/disable-unity-mir-stack-ppa/+merge/196935
[16:23] <cjohnston> so didrocks am I understanding that we are having to do a workaround because Mir broke stuff?
[16:23] <dobey> oh well. i need to go get lunch now anyway. bbiab
[16:25] <didrocks> Saviq: I don't, maybe alan_g? ^
[16:26] <alan_g> didrocks: otp - 5 min
[16:26] <didrocks> cjohnston: it's a little bit more grey than telling Mir broke stuff, but basically yeah :)
[16:27] <didrocks> cjohnston: so, Mir changed its ABI (it's not ABI stable)
[16:27] <didrocks> one of the issue is that we can't release Mir and build unity-mir against it
[16:27] <didrocks> and so, unity-mir tries to install mir from the PPA (as it should, to handle transitions) when merging upstream
[16:28] <didrocks> and so, it takes the Mir we half-broken-we-can't release
[16:28] <didrocks> s/we//
[16:28] <didrocks> cjohnston: that's why the airline will help this, we create isolations and only merge to trunk/land to distro or reject
[16:28] <didrocks> no more "one ppa when we through all bones at it"
[16:28] <cjohnston> right
[16:28] <didrocks> (that all stacks should depend on)
[16:29] <didrocks> where*
[16:31] <alan_g> Saviq: didrocks - no-one has the hardware to test that. :(
[16:31] <Saviq> alan_g, easy, I do
[16:31] <didrocks> alan_g: yeah, I guess, just ask people, we can find someone :)
[16:32] <didrocks> and a Saviq is always highly motivated :)
[16:33] <alan_g> Saviq: you'll have to cherry pick that revision onto lp:mir (It looks like it will work)
[16:33] <doanac> robotfuel: can't remember if i updated you fully yesterday. I got all the systems back up on m-jenkins with the exception of the gt640. we are having some dongle issues or something that require some manual work
[16:34] <Saviq> alan_g, I was hoping to pick up the .debs from the MP
[16:34] <alan_g> Saviq: that's against the dev branch - which has an ABI break
[16:35] <Saviq> alan_g, post 0.1.2?
[16:35] <alan_g> Saviq: we don't hang about. 8^)
[16:35] <Saviq> maan
[16:35]  * Saviq braces
[16:37] <Saviq> so... mir, platform-api, qtubuntu, unity-mir... fun!
[16:37] <robotfuel> doanac:  whats the name of the server that used to be http://10.97.0.1/?
[16:37] <robotfuel> doanac: I need to update some of my preseeds
[16:39] <robotfuel> doanac: I've found it in the wiki
[17:02] <didrocks> plars: joining?
[17:09] <robru> psivaa, no idea what's going on there. clearly the test runner is passing an english sentence as arguments to autopilot-run, which is invalid. that's nothing I can fix on the friends side.
[17:22] <psivaa> robru: ok, yea i see. Not sure what's changed then.
[17:22] <robru> psivaa, where does that string come from? it's not in friends-app source.
[17:23] <psivaa> robru: that is from unittest loader http://pastebin.ubuntu.com/6485389/
[17:25] <robru> psivaa, that's just weird
[17:26] <robru> psivaa, am i crazy or does the 'incorrectly imported from' path exactly match the 'expected' path?
[17:27] <psivaa> robru: no they exactly match :)
[17:32] <ogra_> didrocks, oh, forgot to tell ya ... http://cdimage.ubuntu.com/ubuntu-touch/saucy/daily-preinstalled/ ... new saucy image is done
[17:32] <didrocks> ogra_: wooooooowwww \o/
[17:32] <didrocks> thanks!
[17:50] <psivaa> robru: ok, the test files under tests/ in friends app are symlinked to ../../../../../share/pyshared/friends_app/tests and that seems to cause the failure
[17:51] <psivaa> robru: directly copying it under /usr/lib/python2.7/dist-packages/friends_app/tests/ solves the issue
[17:54] <dobey> does daily-release create a tag for the release after it commits the changes to debian/changelog?
[18:07] <robru> psivaa, pyshared?? that's really strange. friends-app package installs tests to /usr/lib/python2.7
[18:08] <robru> psivaa, i was experimenting with installing them to /usr/lib/python3 in order to test the infrastructure, but that change never landed in trunk/
[18:08] <dobey> export DPKG_GENSYMBOLS_CHECK_LEVEL=4 <- does this need the "export" in debian/rules?
[18:09] <robru> dobey, i dunno, sorry. maybe didrocks knows? ^^
[18:10] <psivaa> robru: http://pastebin.ubuntu.com/6485601/ is what i see there
[18:10] <didrocks> dobey: it's for C/C++ program (so that it forces the strongest type of check in the symbols file)
[18:11] <robru> psivaa, i have no idea how that came to be. http://bazaar.launchpad.net/~super-friends/friends-app/trunk/view/head:/tests/tests.pro clearly declares the installation path... no symlinks.
[18:11] <dobey> didrocks: right. i know what the variable is. i'm just wondering if the "export" is necessary, or if it just needs to be set in debian/rules
[18:12] <didrocks> dobey: IIRC, you need to export it because the check is run in a sub-program
[18:12] <didrocks> dobey: if you can experiment and ensure it's not needed, I would be happy to remove that :)
[18:13] <psivaa> robru: yea, no idea. may be ogra_ knows?
[18:14] <ogra_> about what ?
[18:15] <robru> ogra_, about why friends_app tests are failing. it seems the AP tests are mysteriously being symlinked from where friends-app package actually installs them to, and autopilot doesn't like this.
[18:16] <robru> psivaa, actually I'm thinking that pitti or thomi might know more, since they've been tinkering with the system trying to migrate AP tests to python3.
[18:16] <ogra_> uh, not an autopilot expert ... but i can take a look
[18:16] <ogra_> yeah
[18:17] <robru> ogra_, it's ok thanks.
[18:17] <psivaa> robru: ogra_ ack
[18:17] <ogra_> bah
[18:17] <ogra_> and i totally forgot to notify
[18:18] <ogra_> [18:20] <Ursinha> ogra_, thanks for answering my question before I ask :P
[18:21] <ogra_> heh
[18:21] <Ursinha> ogra_, I was wondering if latest image was 33 or 34
[18:21]  * vila checks which one he just installed...
[18:21] <Ursinha> I have 33 here and it seems to be the last one, so it is :)
[18:21] <ogra_> http://ci.ubuntu.com/smokeng/trusty/touch/
[18:21] <ogra_> that usually tells you
[18:21] <vila> ha, 33 good, oh, last updated 1970-01-01 O_o
[18:21] <Ursinha> vila, lol
[18:21] <ogra_> and http://system-image.ubuntu.com/trusty-proposed/mako/is a good source too
[18:22] <Ursinha> ogra_, the image shows up in http://cdimage.ubuntu.com/ubuntu-touch/trusty/daily-preinstalled/ after all smoketests run?
[18:22] <ogra_> Ursinha, no ... ignore cdimage
[18:22] <ogra_> cdimage only has interim products
[18:22] <Ursinha> s/cdimage/system-image/
[18:22] <Ursinha> right...
[18:23] <ogra_> it shows up there before any tests run
[18:23] <Ursinha> after an image has built how long it takes to show up in trusty-proposed (so my phone thinks there's a new image)?
[18:23] <ogra_> when i promote an image i update the /current link though
[18:23] <ogra_> so that porters using the zips get the same
[18:23] <ogra_> (as we do)
[18:24] <ogra_> Ursinha, once it built on cdimage (which takes about 30min) it takes 0min to be imported in system-image
[18:24] <ogra_> bah
[18:24] <davmor2> ogra_: I'm on 33 I don't see a 34
[18:24] <ogra_> it takes 20min
[18:24] <ogra_> davmor2, i didnt say DONE ... be patient young padawan
[18:24] <Ursinha> haha
[18:25] <davmor2> ogra_: I do patience as well as lead ballons float :)
[18:27] <davmor2> ogra_: out of interest what is the planned times for releases?  I'm assuming this is the 2/3 times a day rollout now?
[18:28] <ogra_> davmor2, iÄm trying to craft a mail since two days to propose new ways of handling images ...
[18:28] <ogra_> but there is always something more important happening :)
[18:28] <davmor2> ogra_: No surely not :D
[18:28] <robru> psivaa, spoke with barry. he says the pyshared thing is standard for a long time. so that should have always been like that. the real question is why does the test system break?
[18:33] <ogra_> [18:33] <dobey> doh, didrocks ran off
[18:34] <ogra_> davmor2, ^^
[18:34] <ogra_> :P
[18:35] <psivaa> robru: ok, autopilot is the same version between image 32 and 33 though so not sure what causes the break
[18:36] <robru> psivaa, pitti is EOD I think, so you should probably email pitti and thomi (and CC me please) and ask them to look into it
[18:40] <psivaa> robru: ack
[18:43] <robru> psivaa, oh, if you compare http://ci.ubuntu.com/smokeng/trusty/touch/mako/32:20131126.2:20131126/5120/friends-app-autopilot/ with http://ci.ubuntu.com/smokeng/trusty/touch/mako/33:20131127:20131126/5136/friends-app-autopilot/ you see that image 32 had the right testcase name, but in image 33 the testcase is replaced with that weird fragment from the traceback.
[18:45]  * popey flashes
[18:51] <dobey> fginther: can you answer questions about the operation of the daily release scripts themselves? (unless you're off to lunch now of course, which given the time, you may be)
[18:51] <robru> fginther, also when you get time: http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/624/console
[18:53] <Ursinha> doanac, robru, I think fginther isn't around today
[18:54] <kenvandine> robru, can you test something for me?
[18:54] <kenvandine> on the device, go to the add accounts screen
[18:54] <kenvandine> does it show service icons?
[18:55] <robru> kenvandine, it did a while ago. what package should i grab from the PPA to test this?
[18:55] <kenvandine> none
[18:55] <kenvandine> just what you have
[18:57] <robru> kenvandine, oh, weird, no icons on the 'add accounts' screen... the U1 icon does show up on the existing accounts though (that's the only account I have at the moment)
[18:57] <kenvandine> yeah
[18:57] <kenvandine> ok, thoughts so
[18:57] <kenvandine> this isn't a regression in online accounts
[18:57] <kenvandine> i think it's a toolkit regression
[18:57] <kenvandine> i'll file a bug
[18:57] <kenvandine> won't block publishing this :)
[18:58] <robru> kenvandine, heh
[18:59] <kenvandine> file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/ListItems/IconVisual.qml:41:5: QML ImageWithFallback: Failed to get image from provider: image://theme/
[18:59] <kenvandine> is the error
[18:59] <kenvandine> or the themed icon is missing now
[18:59] <kenvandine> could be that
[19:14] <robru> kenvandine, ugh, just flashed image 34, can't seem to install click apps.
[19:15] <robru> kenvandine, or it does install, but the installer looks hung while doing it. good
[19:16] <popey> robru: from the store or on the command line?
[19:17] <robru> popey, from the store. installed my own app actually. after hittiing install, it just went to the spinner for a long time. couldn't get past it. then I switched to webbrowser app, then back, then the app appeared in my list of installed apps.
[19:17] <popey> odd
[19:17] <popey> i just tested installing an app on #34, seemed okay
[19:18] <robru> popey, i'll try another one.
[19:21] <robru> popey, hum, seems actually really glitchy. accidentally swiped away from a partially downloading app and now i can't find it again.
[19:21] <dobey> Ursinha: oh. hrmm
[19:22] <Ursinha> dobey, he won't be around until Monday, I believe
[19:23] <robru> popey, now if i start it again, the download won't move past 0%. quite glitchy.
[19:23] <robru> popey, now it says 'install' but the button doesn't respond to taps
[19:24] <dobey> Ursinha: so it seems. and i'm off tomorrow and will be at a sprint next week.
[19:25]  * dobey wonders who to poke about daily-release stuff
[19:26] <robru> dobey, didrocks is the daily-release man. but me, kenvandine, cyphermox, sil2100, and Mirv can help too
[19:27] <robru> popey, seems working after a reboot but now i'm afraid to touch anything during a download.
[19:28] <dobey> robru: do you know if the daily-release script creates a tag in bzr after it commits the new version in debian/changelog?
[19:28] <robru> dobey, that i don't know sorry
[19:29] <robru> popey, so then i left the download alone, screen locked, and when i unlocked my screen the download was gone. basically this is shit.
[19:31] <popey> i never touch anything during an install
[19:31] <dobey> robru: looks like it does not. :(
[19:32] <robru> popey, for a long download, do you let the screen lock? or do you babysit the phone the entire time to stop the screen locking during a download?
[19:32] <popey> i leave it alone
[19:32] <robru> popey, so what then? does the install complete while the screen is locked?
[19:33] <popey> i dont think I've seen it fail, if it fails for you then we need a bug report
[19:33] <robru> popey, what package should I report that against? unity8?
[19:37] <popey> hmm
[19:38] <popey> unity-lens-applications
[19:38] <popey> do it from the phone... adb shell, sudo -u phablet -i, ubuntu-bug unity-lens-applications
[19:44] <dobey> robru: do you know where the code lives that creates the +series.datestamp to append to the upstream version? is it j-l-p?
[19:45] <robru> dobey, i would assume lp:cupstream2distro but I'm not sure.
[19:46] <robru> popey, https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1255653
[19:54]  * dobey wonders why the automatic release thing even bothers with creating a merge proposal if it's just going to automatically self-approve it anyway
[19:57] <robru> dobey, i wonder a lot of things about this system...
[19:57] <dobey> well, yes, me too
[19:58] <dobey> but trying to only deal with the immediate issues at the moment :)
[20:02] <cjohnston> dobey: what do you mean about the 'automatic release thing' ?
[20:05] <robru> cjohnston, when jenkins pushes a release from the PPA to the archive, it then has to commit debian/changelog back to the launchpad trunk, to keep them in sync. instead of committing directly to trunk, it proposes a merge, then approves the merge, and merges by itself.
[20:05] <dobey> cjohnston: whatever is doing the daily-release changes and making the merge proposals
[20:05] <cjohnston> gotcha.. too far outta my area of knowledge
[20:34] <dobey> hrmm, i don't see how to verify that the value from DPKG_GENSYMBOLS_CHECK_LEVEL is actually being used
[20:37] <dobey> do daily-release packages ever get built on virtual arm?
[20:54] <dobey> or is there a good way to determine if one is running virtualized, inside debian/rules?
[21:05] <dobey> cjohnston: do you know what version of tarmac is being used by the autoland script (for the Branch objects)?
[21:15] <xnox> I need some help, with Jenkins UI / UX. I'm logged into jenkins-d, and looking at an autopackagetest, I see no visual way to retrigger it.
[21:15] <xnox> I think in the past it was a matrix reload, or some such, but I don't see it anymore =(