[06:56] <abeato> trainguards ^^ :)
[07:26] <pstolowski> cihelp hi, i need help with the failure in silo 40. seems like it's not happy about symbols changes, but only on powerpc; it passes elsewhere. e.g. http://pastebin.ubuntu.com/11491341/
[07:27] <sil2100> mandel: ping, any news on the location silo?
[07:30] <seb128> hey sil2100
[07:31] <sil2100> seb128: hey
[07:31] <seb128> sil2100, location is known to be not slow/not accurate on vivid images?
[07:31] <seb128> I updated my bq on friday and I've been having issues with that this w.e
[07:32] <sil2100> seb128: yeah, there are issues with location on vivid images right now, not sure how bad it is on krillin but on arale it doesn't work at all even
[07:32] <sil2100> But mandel is on it
[07:32] <seb128> it's not good on vivid
[07:32] <seb128> it took me more than a day to get a position, and I was outside with working 3g
[07:33] <seb128> and today I've a position (being inside on wifi) but the it's within a 10km circle
[07:40] <abeato> sil2100, could I have a silo for line 61?
[07:49] <sil2100> abeato: on it, looking
[07:49] <sil2100> abeato: do you have separate trunks for vivid and wily? Or do you land the same thing for both distros always?
[07:50] <abeato> sil2100, that's the plan, however there is currently a bug in the golang toolchain in wily (for powerPC), so I won't ask for a wily silo for the moment
[07:50] <sil2100> hmm, so it won't build on wily?
[07:51] <abeato> sil2100, in fact there is a pending silo in wily for a previous nuntium landing (line 39)
[07:51] <abeato> sil2100, right, see bug #1454183
[07:51] <sil2100> Ok then
[07:51] <sil2100> Makes sense, ok, assigning silo
[07:52] <abeato> great, thanks
[07:52] <sil2100> Just wanted to make sure a dual-landing isn't a better choice here
[07:53] <abeato> sure, in fact it would be if we did not have that issue :)
[07:53] <sil2100> abeato: silo 19 for you :)
[07:54] <abeato> :)
[08:09] <sil2100> jibel: re your e-mail - agreed, no need to waste time waiting for a decision/fix for the location bits
[08:09] <sil2100> jibel: I poked mandel already but I guess he's not up yet
[08:09] <mandel> sil2100, I am!!!
[08:10] <mandel> jibel, sil2100 building a deb to test and update the ppa
[08:10] <mandel> jibel, sil2100 did the fix over the weekend but did not test it
[08:19] <sil2100> mandel: is it in a silo?
[08:19] <mandel> sil2100, pushing the changes to silo 05
[08:21] <sil2100> jibel: is the trello bot working? Since I don't see it creating cards for the new click/tarballs I approved today
[08:22] <sil2100> jibel: ah, wait
[08:22] <sil2100> jibel: nvm that
[08:28] <mandel> jibel, silo 5 is rebuilding for you to take it for another sping
[08:28] <mandel> spin*
[08:31] <sil2100> jibel, davmor2_hols, ogra_: meeting!
[08:31] <ogra_> if google would let me :P
[08:31] <sil2100> Uh oh
[08:32] <Mirv> sil2100: I'm in london, maybe I'll check your faces but can't attend :)
[08:32] <sil2100> Mirv: ah! Sprinting :)
[08:32] <popey> tumbleweed meeting
[08:32] <sil2100> No cats...
[08:33]  * ogra_ sighs ...
[08:33] <Mirv> sorry :(
[08:33] <popey> ok
[08:35] <sil2100> No worries ;)
[08:35] <popey> sil2100: so what did you want to discuss about Clock / Calendar / Calculator / Cweather *   (* Delete as applicable)
[08:36] <sil2100> jibel: so, I was wondering, popey had a request for a new clock-app, do you guys know if this could land for this milestone?
[08:36] <sil2100> popey: I hope it doesn't have any new icons though?
[08:37] <jibel> sil2100, it is a question for Pat
[08:38] <popey> yes, there is a new icon sil2100
[08:38] <popey> (which seems reasonable, given I note other apps are landing theirs)
[08:38] <popey> (system settings new icon is already in the image)
[08:39] <popey> (on krillin)
[08:39] <sil2100> huh
[08:39] <sil2100> Ok, we really need Pat for this one ;)
[08:40] <popey> sure, i can wait
[08:40] <popey> I mean, once it's tested, we can land in the store when we please
[08:40] <popey> the key thing is the testing bit ㋛
[08:44]  * mandel reboots
[08:46] <jibel> popey, understood, we have 1 sick and 2 on holidays today, so priority is on critical fixes and if we have room, we'll review the apps
[08:46] <popey> sure sure :)
[08:46] <popey> no pressure from me:)
[08:47] <jibel> thanks :)
[08:50] <seb128> sil2100, on my bq/vivid, the messaging indicator envelop doesn't turn blue anymore on received msg, do you know if that's a known issue/what component to blame? telephony-service?
[08:51] <sil2100> seb128: not sure if it's not intentional, I mean, I remember someone saying that the icons (besides the power icon) will be monochrome only from now on
[08:51] <sil2100> But I might be misunderstanding
[08:52] <seb128> sil2100, so you don't have any indication you received a message now?
[08:53] <sil2100> I think it should look different then - jibel do you know what was the deal with monochrome indicator icons?
[08:54] <jibel> seb128, on vivid it turns white (or lighter grey) when you receive a notification
[08:54] <jibel> it's dark grey otherwise
[08:55] <jibel> and it is intentional
[08:56] <seb128> jibel, it's so subtle that I didn't notice the change of color
[08:57] <seb128> jibel, do you know if there is a bug report about the design change/if there was discussions/feedback on how well the monochrome is working
[09:02] <jibel> seb128, I don't remember any bug report or discussion on a ML
[09:03] <seb128> jibel, thanks, maybe I'm going to start one ;-)
[09:06] <sil2100> +1 ;)
[09:14] <oSoMoN> trainguards: what can I do to solve the build error in silo 1 ? would it make sense to re-target the landing to wily only? given that the gates are closed for vivid-overlay, I guess this makes sense
[09:17] <seb128> sil2100, jibel, that's reported as https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1450894
[09:23] <sil2100> oSoMoN: let me take a look
[09:26] <ogra_> mandel, your change wont prevent the job from running on every boot
[09:39] <jibel> mandel, ogra_ is right, the file event is trigger on every boot even if the file already exists
[09:41] <jibel> mandel, also you start ubuntu-location-provider-here-slpgwd twice, second call will exit 1 and location-service will never start
[09:44] <sil2100> oSoMoN: hm
[09:45] <sil2100> oSoMoN: no retargeting is needed, we can simply only publish the wily parts of the landing in this case
[09:45] <sil2100> oSoMoN: but still, you'd either need to re-include the missing version or force-build the silo
[09:47] <mandel> jibel, did I, shit, sorry
[09:47] <mandel> ogra_, hmm.. that was from loic, let me change that
[09:47] <ogra_> mandel, just drop all the nonsense from the "start on" line ... only keep the file creation check
[09:48] <mandel> ogra_, true, since the create event is just fired in a create no if it is present, right?
[09:49] <mandel> jibel, sorry for the double start, I missed that
[09:51] <mandel> ogra_, jibel looks better => https://code.launchpad.net/~mandel/ubuntu-location-provider-here/move-to-vivid/+merge/257910
[09:56] <oSoMoN> sil2100, right, but if later on I want to land further changes, I’ll still have a vivid silo hanging around, so re-targetting and landing only in wily for now is probably better
[09:56] <oSoMoN> given that we don’t really know when the vivid-overlay freeze will be over…
[09:57] <oSoMoN> sil2100, can you do the re-targetting for me, please?
[09:58] <jibel> mandel, I tried that and the file event was emitted on every boot
[10:00] <mandel> jibel, really, that should not happen => http://upstart.ubuntu.com/cookbook/#upstart-file-bridge
[10:03] <jibel> mandel, I know but double-check on a device.
[10:04] <mandel> jibel, fun fun... I'll do a double check in the device, if that is the case.. fu** to upstart
[10:04] <jibel> mandel, I tried on rc-proposed/meizu.en/arale 9
[10:05] <jibel> mandel, and there is no reason that adding extra 'and' clauses would make it start on every boot if it doesn't with only the file event.
[10:06] <mandel> jibel, true, the anyway those starts where not needed
[10:06] <mandel> s/the/but
[10:08] <sil2100> oSoMoN: let me check how the reconfigure will work, since normally changing series is not possible without wiping and re-assigning the silo
[10:18] <oSoMoN> sil2100, ok, if it’s not possible then I guess we can ahead with the dual silo and then once it lands in wily we just free it
[10:19] <mandel> jibel, you are right, that file call is execute everyboot time, either the docs lie or the file is create in each boot (something I hope that does not happen)
[10:20] <ogra_> mandel, did you get my last lines before the reconnect ?
[10:20] <mandel> ogra_, no, I did not
 mandel, just drop all the nonsense from the "start on" line ... only keep the file creation check
 also, make it a task (by adding the "task" keyword) dand drop the "stop on"
 s/dand/and
 and then just keep the old script but shield the "start ubuntu-location-provider-here-slpgwd" with "|| true"
[10:21] <mandel> ogra_, what do you mean with "shield" the script?
[10:21] <ogra_> apped || true to that line
[10:21] <ogra_> so it doesnt stop execution of the job if it returns non-zero
[10:22] <ogra_> (probably add a sleep if you want to give it some time to start)
[10:24] <mandel> ogra_, ok
[10:31] <sil2100> oSoMoN: I didn't want to reconfigure as dual-landing silos are basically wily silos already
[10:31] <sil2100> oSoMoN: for instance, if you don't want to land for vivid, all you need to do is ask a trainguard to remove the vivid binary packages
[10:31] <sil2100> From the silo
[10:32] <sil2100> oSoMoN: so I would say - just force-build the silo (or include the missing changelog entries) and give me a sign to remove the vivid package
[10:36] <oSoMoN> sil2100, ok, will do
[10:37] <Laney> how come oxide-qt has a "passed" boottest?
[10:38] <Laney> https://jenkins.qa.ubuntu.com/job/wily-boottest-oxide-qt/ http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#oxide-qt
[11:07] <joc_> could anyone give me a hint as to how to get the citrain tool working to install silos on a vivid+overlay device?
[11:07] <sil2100> joc_: what series are you running on your local PC?
[11:07] <joc_> currently running something like "citrain device-upgrade 019 XXXX ubuntu" results in the PPA being added but nothing uprgraded
[11:08] <joc_> sil2100: vivid
[11:08] <joc_> the phablet-tools-citrain package is whatever is in universe I think
[11:09] <sil2100> joc_: yeah, it needs a newer version of the tools, as we're using Pin Priorities now
[11:09] <sil2100> I see Mirv's phablet-tools didn't yet land in the overlay...
[11:09] <sil2100> Anyway
[11:09] <sil2100> joc_: use the phablet-tools from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-028
[11:10] <joc_> sil2100: ah thanks, i didnt know about that ppa
[11:10] <sil2100> joc_: well, it's an unofficial place but the final idea is to have the right phablet-tools in the overlay-PPA
[11:11] <Mirv> sil2100: oh... thanks for reminding :) there was that "let's wait if ji_bel has something to say"
[11:11] <sil2100> But it didn't land yet
[11:11] <Mirv> but actually it was alright
[11:11] <sil2100> Mirv: aaah
[11:11] <sil2100> Right, I'm pretty sure jibel won't have anything against it
[11:11] <sil2100> :)
[11:11]  * Mirv landing
[11:11] <sil2100> jibel: right?
[11:11] <sil2100> Mirv: thanks!
[11:12] <joc_> sil2100: so i should have the overlay ppa enabled on my host pc?
[11:13] <Mirv> sil2100: mm, what now? https://ci-train.ubuntu.com/job/ubuntu-landing-028-2-publish/36/console
[11:14] <sil2100> o_O
[11:14] <Mirv> sil2100: wow, it even landed (binary copy just happened)..
[11:14] <Mirv> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+packages?batch=75&memo=75&start=75 - the first one
[11:14] <Mirv> O_o
[11:16] <sil2100> joc_: yeah, I think it should be safe to have that enabled, it mostly has phone-stuff anyway - or at least installing phablet-tools from that and then disabling it
[11:20] <jibel> sil2100, why to the overlay ppa rather than a standard SRU? it's an host package and the fix sounds reasonable for SRU, while it's unlikely that people will have the overlay unable on their desktop
[11:20] <jibel> s/unable/enabled/
[11:21] <sil2100> Yeah, it might be SRUed indeed
[11:21] <pstolowski> anyone from cihelp there?
[11:22] <jibel> sil2100, IMO stable-phone-overlay should contain only phone specific packages that cannot and don't want to be SRUed
[11:23] <sil2100> jibel: the idea of the stable-phone-overlay is also to include those things that we want to SRU but are urgent enough that we don't want to wait through the whole SRU process
[11:23] <ogra_> we should remove the phablet-tools package from universe
[11:24] <sil2100> But I agree, it's best if we don't include non-touch packages there
[11:24] <ogra_> there is no way to keep it up to date across all release3s without a ton of paperwork
[11:24] <ogra_> people *need* to use the pahblet-tools PPA anyway
[11:24] <ogra_> there is no way around that ... so having the package in universe is moot
[11:25] <sil2100> ...or that, well, I don't follow phablet-tools development closely
[11:25]  * ogra_ neither anymore :)
[11:25] <Mirv> there's no such thing as phablet-tools development, just random commits when someone needs something
[11:25] <Mirv> I mean, no-one owns it
[11:26] <popey> so with that few commits, putting it in the archive should not be that much overhead
[11:26] <popey> just needs someone to manage the release
[11:26] <popey> "just"
[11:28] <brendand_> Mirv, which is crazy
[11:29] <sil2100> ;p
[11:29] <sil2100> brb, lunch
[12:03]  * ogra_ curses
[12:55] <fginther> pstolowski, hello, what's the problem?
[13:14] <pstolowski> fginther, hi! silo 40 is failing on powerpc only indicating problems with symbols. e.g. http://pastebin.ubuntu.com/11491341/
[13:15] <fginther> pstolowski, oh, as this is a silo related issue, I'll direct this to trainguards
[13:15] <pstolowski> fginther, which is weird, since it passes on other architectures. it seems to be expecting -0ubuntu1 now (which we have in the changelog), but why only powerpc. and it was fine before?
[13:15] <pstolowski> fginther, ah, fair enough, thanks
[13:24] <pstolowski> trainguards ^ ideas?
[13:47] <sil2100> pmcgowan: hey
[13:47] <sil2100> pstolowski: let me take a look in a minute
[13:48] <sil2100> pstolowski: hmmm
[13:50] <pstolowski> sil2100, sure, thanks
[13:52] <sil2100> pstolowski: damn, this might be a bit troublesome
[13:55] <pstolowski> sil2100, anything changed recently? why only powerpc?
[13:55] <sil2100> It's indeed interesting why it only happens on powerpc, let me dig deeper
[13:57] <sil2100> pstolowski: actually this might be a red herring
[13:57] <sil2100> pstolowski: I think the actual problem might be the newly added symbols that are visible above, for instance as seen in this willy build
[13:57] <sil2100> https://launchpadlibrarian.net/207774287/buildlog_ubuntu-wily-powerpc.unity-scopes-shell_0.5.4%2B15.10.20150529.2-0ubuntu1_BUILDING.txt.gz
[13:58] <sil2100> Somehow those are now visible on powerpc
[14:02] <pstolowski> sil2100, weird. i've just checked the 1st symbol, it should be covered by this: http://pastebin.ubuntu.com/11497617/
[14:04] <pstolowski> sil2100, yeah, these symbols are not new
[14:04] <sil2100> Interesting stuff, hm, looking a bit more
[14:04] <pstolowski> sil2100, they are covered by  (c++|arch=!amd64 !arm64 !ppc64el) rule
[14:05] <pmcgowan> sil2100, hey
[14:06] <sil2100> pmcgowan: I heard from popey that people already started landing the new icons while we still didn't finish arale
[14:06] <sil2100> Something about system settings having the new one already
[14:06] <sil2100> Is that coordinated?
[14:07] <pmcgowan> nothing landed to vivid afaik, but could be going to the store for core apps
[14:07] <sil2100> Maybe it slipped in with one of the fixes or something?
[14:07] <popey> pmcgowan: http://people.canonical.com/~alan/screenshots/device-2015-06-01-150711.png
[14:07] <popey> thats my krillin
[14:07] <sil2100> Looks like the new icon to me
[14:07] <sil2100> popey: you're running vivid, right?
[14:07] <popey> ah, my krillin is ubuntu-touch/devel-proposed/ubuntu 227 - is that wily?
[14:07] <sil2100> popey: yeah, that's wily
[14:07] <popey> Codename:       wily
[14:07] <popey> yeah
[14:07] <popey> ignore me then
[14:08] <sil2100> pmcgowan: ...ok, ignore that question ;)
[14:08] <pmcgowan> wily
[14:08] <pmcgowan> yeah
[14:09] <ogra_> popey, dont run wily ... it will likely break in interesting ways :)
[14:09] <pmcgowan> popey, btw i like the old one better
[14:10] <popey> pmcgowan: me too
[14:10] <popey> ogra_: what channel should I be on, on krillin?
[14:10] <pmcgowan> jibel, so whats the deal with silo 5, just busted?
[14:11] <ogra_> popey, one of the rc ones ...
[14:11] <jibel> pmcgowan, in it's current state, yes.
[14:12] <jibel> mandel|lunch, ^ what's the status on 5?
[14:12] <sil2100> jibel: for the krillin OTA-4 we'll also need the new device tarball from john-mcaleely, rvr is on it?
[14:13] <jibel> sil2100, it's done
[14:13] <sil2100> \o/
[14:13] <jibel> sil2100, almost, 2 MMS tests left
[14:14] <jibel> sil2100, actually MMS tests fail
[14:14] <jibel> rvr, does it work without the device tarball?
[14:14] <rvr> Well, but MMS didn't work for me in the past, so...
[14:15] <john-mcaleely> ha. mms is not news :-)
[14:15] <ogra_> send postcards ... cheaper anyway
[14:15] <rvr> lol
[14:15] <john-mcaleely> email. always been a better choice
[14:17] <popey> ogra_: ubuntu-touch/rc/ubuntu-developer ?
[14:17] <popey> ogra_: is there one that has the here stuff?
[14:18] <ogra_> popey, http://system-image.ubuntu.com/ubuntu-touch/rc-proposed/bq-aquaris.en/
[14:18] <ogra_> err
[14:18] <popey> hah
[14:18] <ogra_> thats the latest vivid+overly
[14:19] <ogra_> and http://system-image.ubuntu.com/ubuntu-touch/rc-proposed/meizu.en/ is the same thing for arale
[14:19] <popey> ta
[14:20] <sil2100> https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/ has stuff explained
[14:20] <sil2100> Might need to include additional info inside
[14:22] <jibel> sil2100, john-mcaleely device_krillin-20150529-8e13c5f is ok. MMS can be sent but not received. It is not related to the tarball.
[14:24] <sil2100> john-mcaleely: you're free to publish :)
[14:24] <jibel> om26er, you tested the custom tarball for krillin last Friday right?
[14:27] <john-mcaleely> sil2100, will do so shortly (otp)
[14:42] <rvr> bfiller: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1460664
[14:43] <rvr> Hmm
[14:44] <rvr> The strings are in es.po indeed
[14:46] <om26er> jibel, yes, I did.
[14:46] <om26er> (IRC was disconnected and I didn't know)
[14:47] <cjwatson> (librarian is working)
[14:50] <sil2100> cjwatson: thanks, yeah, we missed changing that on Friday
[14:51] <boiko> trainguards: I got an exception on silo 16, will a rebuild fix it or does it need anything else to work?
[14:53] <sil2100> boiko: hey!
[14:53] <alex-abreu> trainguards can you reconfigure silo 2?
[14:54] <sil2100> boiko: no, it won't be that easy... it seems you released address-book-app for wily already from the selected trunk
[14:54] <sil2100> boiko: so this trunk should be either only used for dual-landings or only for wily landings
[14:54] <sil2100> boiko: you should either release to wily and sync back to vivid, or use dual-landings or create a separate trunk for vivid
[14:54] <sil2100> alex-abreu: on it
[14:55] <boiko> sil2100: ok, let me check with bfiller what to do now
[14:55] <sil2100> pstolowski: ok, I'll be back to trying to figure out what happened in a moment, got distracted
[14:55] <boiko> sil2100: thanks!
[14:56] <sil2100> boiko: yw! It's just that the selected trunk needs to always be used only to release for a selected focus, so either you target stable or you target devel :)
[14:56] <sil2100> Since otherwise there wouldn't be any useful history in bzr
[14:56] <sil2100> alex-abreu: done
[14:57] <alex-abreu> sil2100, thx
[14:57] <bfiller> sil2100: can we dual land now? that is what we want but vivid overlay frozen, correct>?
[14:57] <sil2100> bfiller: yeah, it's still frozen... so we propose just releasing to wily for now and then syncing it back
[14:58] <bfiller> sil2100: ack, boiko lets do that ^^
[14:58] <boiko> bfiller: that might be the best thing to do
[14:58] <sil2100> bfiller: dual-landings can also be used for only landing to wily, but it's best to just get a wily silo as it's less manual work for everyone
[14:58] <boiko> sil2100: should I change the spreadsheet, or can you configure it internally?
[14:58] <sil2100> boiko: I'll have to re-assign the silo in this case
[14:58] <boiko> sil2100: that's fine
[14:58] <sil2100> boiko: ok, on it :)
[14:58] <boiko> sil2100: thanks!
[15:02] <sil2100> boiko: done, silo 016 again, just remember there's a wily silo with dialer-app already in 004 (shell rotation)
[15:03] <boiko> sil2100: ok
[15:38] <sil2100> pstolowski: hah!
[15:39] <sil2100> I think I found it
[15:39] <sil2100> pstolowski: you still around?
[15:39] <sil2100> Let's go pm on  this
[15:39] <pstolowski> sil2100, yes
[15:39] <john-mcaleely> sil2100, still a good time to publish the approved vivid tarballs?
[15:39] <sil2100> john-mcaleely: yes :)
[15:40] <john-mcaleely> ok, let me do that then
[15:41] <john-mcaleely> sil2100, done. krillin & vegetahd pushed
[15:42] <john-mcaleely> thank you
[15:42] <sil2100> \o/
[15:42] <sil2100> Thanks :)
[16:30] <jibel> rvr, om26er did you sign off silo 5?
[16:35] <sil2100> Doesn't it need some more tweaking?
[16:36] <jibel> sil2100, no one from QA signed it off AFAIK
[16:37] <sil2100> I wonder why it's marked as such then
[16:39] <om26er> rvr, I didn't. rvr though it was not needed anymore ?
[16:39] <sil2100> om26er, jibel, rvr: I switched it back to untested
[16:40] <om26er> s/not needed/no a blocker.
[16:40] <sil2100> om26er: it's still a blocker, but the silo was b0rken
[16:47] <jibel> sil2100, pmcgowan silo 5 is still bad
[17:45] <rvr> jibel: I didn't test any silo today
[18:43] <pmcgowan> jibel, silo 5 worked for me - installed the debs, reboot, turn on wizard, reboot, run through wizard, open Here app and got a fix
[18:43] <pmcgowan> om26er, ^^
[18:43] <pmcgowan> if thats the correct method
[19:39] <ogra_> pmcgowan, you need to remove /home/phablet/.config/ubuntu-system-settings/wizard-has-run before rebooting (note the wizard will come up as soon as the file is gone, but reboot anyway)
[19:39] <ogra_> if you leave the file in place you dont actually test the issue
[19:57] <pmcgowan> ogra_, I used phablet-config which I thought did that
[20:15] <popey> balloons: any more news on the migration to vivid in jenkins?
[20:42] <balloons> popey, nope..
[22:21] <bfiller> robru: can you publish silo 21 please?
[22:22] <robru> bfiller: sure, but need merges approved first: https://ci-train.ubuntu.com/job/ubuntu-landing-021-2-publish/61/console
[22:22] <bfiller> robru: let me do that