[00:02] <robru> blam
[01:54] <popey> robru, whoever runs that bot might want to remove the colon after the url, some irc clients treat it as part of the url, so when you click it, it 404s
[02:02] <robru> popey: buggy irc client!
[05:52] <robru> popey: ^^ ARE YOU HAPPY NOW?!?! :-P
[05:56] <robru> Incredible, translation updates push to trunk, invalidates all the silos. It's beautiful <3
[08:37] <mardy> trainguards, can we just force https://requests.ci-train.ubuntu.com/#/ticket/591 to land somehow? The failures are intermittent, and apparently related to CI infra
[08:40] <robru> mardy: that's actually landed and would merge right now but there seems to be a train problem, I'm looking into it
[08:40] <mardy> robru: cool, thanks! :-)
[08:41] <Mirv> mardy: yes, it's now really landed.
[08:41] <Mirv> robru: not really a problem maybe, migrated 36 minutes ago, maybe just not updated yet?
[08:41] <Mirv> mardy: you can see it's now in release pocket https://launchpad.net/ubuntu/+source/online-accounts-api
[08:41] <robru> Mirv: no there's a crazy traceback in the migration script: https://ci-train.ubuntu.com/job/check-publication-migration/27122/console
[08:41] <mardy> Mirv, robru: but trunk is not updated, is it?
[08:43] <mardy> (the MP doesn't appear to be merged)
[08:45] <robru> mardy: no the train is broken, I'm working on it.
[08:46] <mardy> robru: good luck :-)
[08:47] <Mirv> mardy: yes, it'd be normally right after it migrates, and the ticket would show "Landed"
[08:48] <Mirv> mardy: we could force it now that there are no proposed migration problems, but I assume robru is wanting to fix it for real so let's wait a bit
[08:48] <robru> mardy: thanks, this one is weird.
[08:48] <robru> mardy: yeah are you blocked on this? we can force merge if you're in a hurry but I'd like to fix it proper and see it be fixed before I go to bed
[08:49] <mardy> robru, Mirv: no hurry, better fix it once and for all, if possible :-)
[08:49] <jibel> robru, can you remove the 'request autopkgtest' button from bileto until it is functional?
[08:49] <jibel> it is just confusing and link to the build artifacts are lost
[08:49] <robru> jibel: can people not be trusted not to click it? :-/
[08:50] <jibel> robru, no they don't
[08:51] <jibel> sil2100, is the changes bot running?
[08:51] <sil2100> Not if the instance went down again... let me check
[08:52] <sil2100> eh, can't log in as chinstrap is still down, need VPN, one moment
[08:55] <robru> mardy: Mirv: ok fix in trunk, will hit production in ~20 and then we can try this again
[08:56] <robru> jibel: seems nobody clicked it since the last time I cleared it out...
[08:58] <robru> sil2100: Mirv: btw if somebody clicks that 'request autopkgtest' button and then they want to give up on it (stop watching for results) you can do that by: rm -vrf ~/silos/*/*/*_autopkgtest
[09:07] <sil2100> robru: ACK
[09:07] <sil2100> jibel: ok, looks like it works
[09:07] <sil2100> jibel: the job runs every 30 minutes so maybe it had a delay or something
[09:11] <Mirv> robru: thanks!
[09:12] <robru> well technically what I said would clear it for *all* silos but there aren't any silos that are using this currently so it's a minor difference.
[09:13] <Mirv> robru: wasn't the force merge supposed to still be there for trainguards? https://ci-train.ubuntu.com/job/ubuntu-landing-042-3-merge-clean/build?delay=0sec
[09:14] <robru> Mirv: it's always forced now, because only trainguards can run it, and the non-force was completely redundant
[09:15] <Mirv> robru: makes sense, then there's another problem with that since it failed, maybe because I just removed one MP from there
[09:15] <robru> Mirv: (the failure you got is the same one that bit mardy, fix will hit production in 2 minutes)
[09:17] <Mirv> robru: ah... great
[09:17] <robru> Mirv: why are you merging 42? one of the packages isn't at dest...
[09:18] <robru> mardy: https://code.launchpad.net/~online-accounts/online-accounts-api/trunk done
[09:18] <robru> sorry for the hassle
[09:19] <robru> Mirv: it'll work now anyway, confirmed ^^
[09:19] <mardy> robru: my hero! Thanks!! :-)
[09:19] <Mirv> robru: because unity-lens-music will go to another landing
[09:19] <Mirv> robru: it was added after it was published
[09:19] <robru> mardy: you're welcome
[09:19] <robru> Mirv: weird, ok
[09:20] <Mirv> robru: mzanetti and me can't find anything that has new commits in https://requests.ci-train.ubuntu.com/#/ticket/621
[09:20] <Mirv> https://code.launchpad.net/~mzanetti/unity8/ubuntuanimations/+merge/276511 has one commit on the day of the build, but that's also in the sources
[09:20] <Mirv> mzanetti: maybe someone uncommitted again something and push --overwrite:d?
[09:21] <robru> Mirv: mzanetti: the new commit is on trunk. you can discover this by clicking 'status' and scrolling down to the part where it checks your silo, it will list the URL that has new commits.
[09:21] <mzanetti> on trunk... dafuq...
[09:21]  * mzanetti looks
[09:21] <Mirv> robru: Status is a link!!! :D sorry...
[09:22] <robru> Mirv: everything orange is clickable.
[09:22] <Mirv> yeah, I know, I just had skipped that somehow
[09:22] <Mirv> robru: ah, many trunks get translation updates all the time
[09:22] <robru> Mirv: it's a bit  unfortunate in this case as the migration script has one log for all silos, so you have to scroll literally to the bottom to find silo 60
[09:23] <Mirv> robru: that's alright
[09:23] <robru> Mirv: yeah this is a bit iffy. I added this check for the case when a conflicting silo finally merges, so you know to rebuild to incorporate the conflict. translations throws a wrench in that though
[09:25] <robru> Mirv: I suppose I'll have to work out a way so that it only sets the status if the new commits are not translation commits, but that seems a bit hard & slow (so in addition to iterating over every MP in every silo I'd also have to iterate on every commit in every branch in every silo to make sure the new ones are only translations).
[09:25] <Mirv> that's slow yes
[09:25] <robru> sigh, I need to file some bugs
[09:31] <mzanetti> robru, can it be that it complains about the launchpad translation commits?
[09:31] <robru> mzanetti: yes
[09:31] <Mirv> mzanetti: that's what we just discussed
[09:31] <Mirv> mzanetti: I'll publish the silo manually copying, since they're all universe packages
[09:31] <mzanetti> oh, sorry
[09:32] <mzanetti> Mirv, I guess we can revert the translation commit, lp should redo it tonight then...
[09:32] <robru> Mirv: try publish job? I think it should work
[09:32] <mzanetti> Mirv, whatever you think it's easier
[09:32] <Mirv> robru: bad state https://ci-train.ubuntu.com/job/ubuntu-landing-060-2-publish/8/console
[09:32] <robru> ah
[09:34] <Mirv> mzanetti: ah damn, unity-api is actually in main :(
[09:34] <Mirv> mzanetti: just means I need that one copied by someone else
[09:35] <mzanetti> please stop scaring the sh*t out of me :D
[09:35] <sil2100> Mirv: sorry! I MIRed it recently ;p
[09:36] <Mirv> sil2100: damn you! :)
[09:37] <Mirv> mzanetti: 060 is already published to vivid overlay now :) just waiting for a core-dev to copy unity-api to xenial, I copied the other two
[09:39] <mzanetti> thanks a bunch Mirv
[09:42] <Mirv> mzanetti: ok seb128 helped us, let's keep the silo until we see that proposed migration happens in xenial. but it's now there too.
[09:44] <mzanetti> Mirv, and again, tanks a lot :)
[09:45] <robru> Mirv: migration script starts in a minute, will take 20 minutes to update the status for silo 60 tho
[09:45] <seb128> jibel, I think that comment saying that indicator-datetime is not translated is probably the uitk template/timestamps strings not being translated
[09:50] <Trevinho> Mirv: added new silo, but generated changelog is so wrong.... https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-042/+packages :-(
[09:53] <robru> Trevinho: what's wrong with it? looks actually reasonable to me
[09:53] <Trevinho> robru: oh, i maybe see the reason... It uses https://code.launchpad.net/~unity-team/unity-lens-music/saucy as base
[09:53] <Trevinho> robru: it's wrong since he only change should be the icon change
[09:54] <Trevinho> this is suspicious -Vcs-Bzr: https://code.launchpad.net/~unity-team/unity-lens-music/trunk
[09:54] <Trevinho> +Vcs-Bzr: https://code.launchpad.net/~unity-team/unity-lens-music/saucy
[09:54] <robru> Trevinho: yup, pointing your MP at saucy would cause a goofy changelog
[09:54] <Trevinho> yeah.... it was proposed to the wrong branch ./
[09:55] <robru> Trevinho: no big deal then, repropose and rebuild
[09:57] <mzanetti> Mirv, should it have merged the code by now?
[09:58] <robru> mzanetti: no, it *just* published. it's so new the train hasn't even noticed it's published yet
[09:58] <mzanetti> heh, ok
[09:58] <robru> mzanetti: it'll sit in proposed for a bit, the ticket status will show 'Proposed pocket' for a while, then it'll merge some hours later
[09:58] <mzanetti> right
[10:00] <xavigarcia> rvr: Hi there
[10:00] <xavigarcia> rvr: silo 51 is again ready to QA... I've fixed the issues you found on the warning dialog and I've also updated the test plan
[10:01] <rvr> xavigarcia: Yeah, I saw it, thanks
[10:01] <xavigarcia> rvr: np
[10:04] <Mirv> mzanetti: proposed migration
[10:05] <Mirv> mzanetti: hours at minimum, then check http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity8 if it's stuck for real
[10:05] <Mirv> mzanetti: it's not wanted that stuff gets thrown to xenial and forgotten, therefore we wait for the migration tests
[10:12] <Trevinho> robru: it's still wrong... :(
[10:15] <robru> Trevinho: look at thebranches, they're different.
[10:15] <Trevinho> mh
[10:15]  * Trevinho should rebase...
[10:15] <robru> Trevinho: I duno what branch you started with but it doesn't look like the trusty branch
[10:15] <Trevinho> yeah, it wasn't a my branch... So you're right
[10:16] <robru> Trevinho: hm they match at commit 148, so 149 is this anomalous commit, not sure where that came from 2 years ago
[10:17] <robru> Trevinho: also double-check the bzr tags. that's how the train generates the changelog. it looks for the most recent bzr tag on the branch and includes everything after that in the changelog, so find the most recent release commit and tag it with the version number of that release, should stop the train from including anything older than that in the log
[10:18] <Trevinho> ok
[10:21] <robru> Mirv: https://requests.ci-train.ubuntu.com/#/silo/060 crap, it won't auto-merge as long as that 'needs rebuild' is in there.
[10:22] <robru> Mirv: might have to merge it manually... or delete the translation commit ;-)
[10:33] <Mirv> robru: ah right. well I'll merge it manually once migration is done
[10:34] <robru> Mirv: sorry about that, as usual corner cases ruin a brilliant plan
[10:38] <Mirv> robru: :) heh, but eventually that brilliant plan works! like these auto-updating statuses and everything that is now there.
[10:39] <robru> Mirv: yeah that's slick. it's about to get slicker, too. I'm parallelizing it so a) it's way faster and b) when you click Status you only see the log for the request you clicked on, don't have to search through all silo.
[11:19] <rvr> pstolowski: ping
[11:21] <pstolowski> rvr, pong
[11:22] <rvr> pstolowski: I think silo 60 already landed
[11:22] <pstolowski> rvr, great, that means i can rebuild the other one
[11:23] <pstolowski> rvr, nope, not merged yet
[11:24] <rvr> Oh
[11:40] <jibel> xavigarcia, about silo 51 when the phone rings it's a bit weird to see the volume notification with label 'headphone' then the notification again with the label 'speaker' when the call ends. Is it really the expected behaviour?
[11:40] <jibel> rvr, ^ did you see that too last time you tested this silo?
[11:43] <xavigarcia> jibel: not sure about that... I should ask design.. But it looks a bit weird... yeah
[11:46] <Mirv> pstolowski: rvr: unity8 is still in xenial-proposed, so no merging
[11:58] <rvr> jibel: Nope, I do not remember that problem
[12:01] <jibel> rvr, xavigarcia ok, silo blocked until you have a confirmation
[12:04] <xavigarcia> jibel: ack
[12:08] <popey> The twitter scope, is it in the store or only on the image?
[12:08] <popey> asking for a friend :)
[12:08] <jibel> xavigarcia, about silo 6 indicator-location when is the indicator supposed to be removed from the panel? currently it is removed when the user turns GPS off, it should be when location is switched off, or like the spec says after 5 min without an access to the location service.
[12:09] <jibel> ?
[12:10] <xavigarcia> jibel: Following the specs stated in the bug it should not appear
[12:10] <xavigarcia> jibel: And GPS is controlled from the settings
[12:10] <xavigarcia> jibel: that's what I understood
[12:11] <jibel> xavigarcia, okay, I double check and confirm in a minute
[12:12] <xavigarcia> jibel: https://docs.google.com/document/edit?hgd=1&id=1810KDpFl2Mxsn1z3wehPU9pkbS6R6o-j1-pmYpkYb7A#
[12:12] <bzoltan_> jibel: Mirv: the silo10 has the corrected UITK translation  files. No code changes
[12:16] <Mirv> bzoltan_: looks correct
[12:16] <Mirv> both .pot + .po:s
[12:19] <jibel> xavigarcia_lunch, actually both location detection and gps must be switched off to remove the icon from the panel. Given that there is only one switch left in the indicator, switching it off should be enough to remove the icon, isn't it?
[12:20] <jibel> bzoltan_, thanks, I trust you checked every single string for invalid characters? :)
[12:20] <xavigarcia_lunch> jibel: mmm, I guess so... and it's not doing it, right?
[12:20] <jibel> xavigarcia_lunch, nope
[12:21] <jibel> xavigarcia_lunch, you must disable location detection and gps from system settings
[12:21] <xavigarcia_lunch> jibel: ok.... will fix it then. Thanks for finding out
[12:21] <pete-woods> trainguards: hi guys. got a silo for indicator-network that switches out our vendored menu harness for the newly packaged gmenuharness
[12:21] <pete-woods> needs a packaging ack: https://ci-train.ubuntu.com/job/ubuntu-landing-038-2-publish/18/artifact/indicator-network_content.diff
[12:21] <pete-woods> thanks to anyone with spare cycles to have a look
[12:21] <jibel> xavigarcia_lunch, yw, design should also clarified the spec on this specific point.
[12:21] <xavigarcia_lunch> jibel: yeah
[12:22] <pete-woods> whoops, better diff (https://ci-train.ubuntu.com/job/ubuntu-landing-038-2-publish/18/artifact/indicator-network_packaging_changes.diff)
[12:22] <xavigarcia_lunch> jibel: I wil ping them before pushing anything, to confirn
[12:22] <jibel> xavigarcia_lunch, thanks
[12:22] <xavigarcia_lunch> jibel: np
[12:26] <bzoltan_> jibel:  No I did not. I would lie if I would say that I have checked 5594 strings. but I have checked those what were messed up yesterday
[12:27] <Mirv> pete-woods: how switching libraries would not require QA, or is that the same identical code now separated to own package?
[12:29] <jibel> bzoltan_, np :) approved
[12:30] <bzoltan_> jibel:  thanks.. it was a lame bug. I will never trust chromium browser again... vi rules
[12:31] <jibel> bzoltan_, heh, sorry we missed it too
[12:31] <jibel> or found too late
[12:32] <abeato> Mirv, I need to upload http://people.canonical.com/~abeato/qtmultimedia-opensource-src/ to silo 9 :)
[12:38] <pete-woods> Mirv: the lib is only used in the test suite, the indicator doesn't get affected at all
[12:38] <pete-woods> it's a library a bit like autopilot
[12:38] <pete-woods> but for gmenus
[12:39] <pete-woods> we just want to use the same lib across all the indicators, rather than copying
[12:39] <Mirv> abeato: ok
[12:39] <Mirv> pete-woods: ok
[12:39] <Mirv> ok ok
[12:40] <abeato> Mirv, ok thanks
[12:40] <Mirv> abeato: how's the upstreaming faring with Jim + Yoann? you should probably divide the upstreaming work between you two and offload as much as possible to Yoann
[12:41] <abeato> Mirv, I think Jim already synced with upstream, this upload is for something wrong we noticed, I'll sync back with jhodapp once he is around
[12:42] <Mirv> abeato: no, there is zero upstreaming work done: https://codereview.qt-project.org/#/q/project:qt/qtmultimedia,n,z so far
[12:43] <Mirv> abeato: the current qtmultimedia that is shipping in our overlay is diverged from the July upstream commit and has new features that are not in upstream, so the plan is 1. you get it working, 2. you upstream all new features, 3. you drop the current qtmultimedia API you have and replace with what is in upstream.
[12:43] <abeato> Mirv, ok, didn't really know the status, as is Jim the one handling this
[12:43] <Mirv> abeato: bug #1514344 is to follow it. ok. I just occasionally ask since we're basically walking on a thin line by shipping something that is actually rejected by upstream, and just hoping no-one starts to use the API in our stable release since it will be dropped.
[12:44] <Mirv> abeato: anyway, uploaded to the PPA since we've agreed this is the situation currently
[12:44] <abeato> Mirv, understood, I agree with the plan too
[12:46] <anpok_> cihelp: there seems to be a problem with unity-system-compositor-cir -> unity-system-compositor-xenial-amd-ci has problems with pbuilder
[12:46] <anpok_> http://jenkins.qa.ubuntu.com/job/unity-system-compositor-xenial-amd64-ci/5/console
[12:48] <pete-woods> Mirv: thanks! :)
[12:52] <Mirv> pete-woods: yw!
[12:54] <bzoltan_> jibel: it would be fun to make a simple script to test if the strings are sensible.
[12:55] <jibel> bzoltan_, sure, if you find a definition of 'sensible string'
[12:55] <jibel> it can be anything
[12:56] <bzoltan_> jibel: I will think about it.. I have an idea
[13:02] <jibel> kenvandine, there are at least 2 problems with the custom ringtones silos: 1. custom sound is removed from the list when user selects another sound, 2. The custom sound is also available in message notifications
[13:02] <jibel> kenvandine, also I noticed that 'Alarm Clock' is the first ringtone, is it expected?
[13:03] <jibel> note that this last point has nothing to do with the silo
[13:03] <kenvandine> it's alphabetical
[13:03] <jibel> kenvandine, yeah, but is it expect to have alarm clock as a ringtone ?
[13:03] <kenvandine> also, the design calls for the custom ringtone to be removed
[13:04] <kenvandine> jibel: i don't know if anyone thought about that, but it's in the directory with all the ringtones
[13:05] <kenvandine> jibel: good point on the ringtone showing up under messages
[13:05] <kenvandine> i'll fix that
[13:07] <jibel> kenvandine, it's a really annoying to remove it. custom background are not removed when the user picks another one
[13:07] <kenvandine> yeah, we don't have a design for managing them
[13:07] <kenvandine> the design is quite simplistic
[13:07] <kenvandine> it'll evolve though
[13:08] <kenvandine> we'll eventually add a loop selector, so you can select a clip from a song to repeat
[13:08] <jibel> kenvandine, we could keep one at least and replace it when the user selects a different custom sound
[13:08] <kenvandine> when we work on that i'll push design to do something about managing custom ringtones
[13:08] <kenvandine> jibel: we could, but that would require a lot of refactoring of the panel
[13:09] <kenvandine> not UI
[13:09] <kenvandine> just implementation
[13:09] <kenvandine> and the way we maintain the list
[13:09] <kenvandine> jibel: which we'll need to do when we add the loop stuff
[13:13] <kenvandine> jibel: i just pushed a fix for the ringtone showing up in the messages lists, rebuilding silo now
[13:15] <seb128> jibel, kenvandine, I think the alarm clock one is there because we don't have a directory specific for the clock/reminder
[13:16] <seb128> we only have ringtones and messages
[13:18] <rvr> Mirv: ping
[13:19] <jibel> seb128, okay, it's just a bit odd.
[13:20] <seb128> jibel, agree, we would need to a separate set of sounds for alarm&reminders
[13:20] <seb128> seems like a valid request for design
[13:20] <jibel> seb128, I'll file a bug
[13:20] <seb128> thanks
[13:42] <pstolowski> rvr, silo 14 rebuilt and looks good, ready for qa
[13:45] <jibel> pstolowski, thanks, unblocked
[13:53] <jhodapp> Mirv, zero is definitely not true, most of it is upstreamed
[13:54] <jhodapp> Mirv, we've backported our qdeclarativeplaylist API to the 5.7 dev API upstream...so now there's just a tiny bit that needs upstreaming that's not part of an API
[13:55] <tvoss> sil2100, around?
[14:25] <davmor2> sil2100, jibel, morphis: Finally the bluez5 silos are ready to land sil2100 can you spin up an image once they do please
[14:26] <abeato> davmor2, morphis \o/
[14:27] <abeato> morphis, well done :)
[14:27] <davmor2> sil2100: can you give me a ping once the image builds then please then I need to test across all four devices
[14:27] <morphis> YEAH!!!!
[14:32] <jibel> davmor2, great, lets celebrate \o/
[14:35] <pmcgowan> oh my
[14:39] <davmor2> pmcgowan: it's only taken a week of debugging and morphis patiently fixing to get it landed \o/
[14:39] <pmcgowan> well done morphis and davmor2
[14:39] <morphis> pmcgowan: thanks
[14:39] <morphis> pmcgowan: but be prepared... the suspend issue you discovered will be still there on arale :)
[14:41] <pmcgowan> morphis, oh thats not good
[14:41] <pmcgowan> enjoying my current battery life
[14:42] <morphis> pmcgowan: we need to land this big thing first
[14:42] <morphis> but investigation on the suspend issue is ongoing
[14:44] <Mirv> jhodapp: abeato: I meant that there are no commits in upstream since August. thanks for adapting to the Source -> Items though, that's a big win! but also addItems and moveItem are in API and not in upstream. plus then any bugfixes of course.
[14:44] <jhodapp> Mirv, yep, I'll be working on the last bits of that today
[14:44] <jhodapp> Mirv, upstreaming
[14:47] <morphis> sil2100: when there are any problems merging all three silos please ping me
[14:49] <jhodapp> sil2100, hey I heard you maintain ubuntu-touch-meta? It has a media-hub dependency on version 3 and silo 9 is going to land version 4, so its dependency needs updating
[14:51]  * popey joins the queue for sil2100 
[14:51] <popey> sil2100, is there a plan to have a mid-way fix between OTA-8 and OTA-9?
[14:51] <popey> or am I dreaming?
[14:52] <popey> pmcgowan, ^ maybe you know actually
[14:52] <Mirv> jhodapp: excellent, the silo 009 is a result of long hard work but OTA-9 will basically resolve then ~everything
[14:53] <Mirv> morphis: davmor2: 2/3 silos published, 043 needs core dev
[14:53] <pmcgowan> popey, we are considering it yes
[14:53] <jhodapp> Mirv, yes indeed, and thanks!
[14:53] <popey> k
[14:53] <popey> 25/12/2015? :)
[14:53] <pmcgowan> popey, for special fixes
[14:53] <pmcgowan> yeah
[14:53] <popey> oh, not for general landings?
[14:54] <pmcgowan> no
[14:54] <pmcgowan> just cherry icks
[14:54] <pmcgowan> picks
[14:54] <popey> okay. ahayzen jhodapp ^
[14:54] <popey> we were wondering about the media stuff
[14:54] <ahayzen> popey, no we were saying will there be a framework bump for OTA9
[14:54] <jhodapp> popey, I'm fine with it going out with OTA9
[14:54] <popey> oh
[14:55] <ahayzen> popey, or are you asking multiple questions? ;-)
[14:55] <popey> i misunderstood, fair enough
[14:55] <popey> maybe, yes, that
[14:55] <popey> ahem
[14:56] <ahayzen> otherwise we'll end up with the usual situation of people on OTA8 trying to run a music-app that won't run due to media-hub/mediascanner2 changes in OTA9 etc
[14:58] <morphis> Mirv: wow
[14:58] <morphis> Mirv: anyone we can ping to get this done now?
[14:58] <Mirv> morphis: on #ubuntu-devel, I'll ask
[14:59] <morphis> Mirv: thanks
[15:02] <sil2100> jhodapp: on it! Sorry, I had some visitors ;)
[15:02] <jhodapp> sil2100, awesome thank you!
[15:02] <jhodapp> sil2100, you can put that into silo 9 with our changes if desired
[15:09] <dobey> kenvandine: hey, can i bug you for a packaging ack? :)
[15:09] <davmor2> sil2100: what kinda excuse is that???
[15:11] <sil2100> davmor2: a good one!
[15:12] <davmor2> sil2100: who would you normally pick on core dev wise for landing like 43?
[15:15] <kenvandine> dobey, in a few :)
[15:17] <sil2100> hmmm
[15:17] <sil2100> cyphermox, kenvandine: hey guys! I would need someone to publish the bluez silo (silo 43)
[15:23] <cyphermox> sil2100: ok
[15:23] <sil2100> jhodapp: hey, I'll prepare the seed change locally and upload once you release the package - reason is that we're about to land the bluez silo which already has ubuntu-touch-meta
[15:23] <jhodapp> sil2100, let me know when you've pushed the change to ubuntu-touch-meta and I'll make sure that media-hub*3 can be removed without breaking things
[15:23] <sil2100> So we'll have to re-build
[15:24] <jhodapp> sil2100, lol good timing :)
[15:24] <sil2100> jhodapp: yeah ;) Well, I could upload, but that would be pointless as we'll have to rebuild anyway
[15:24] <jhodapp> sil2100, so is that an issue, because like I said we'll have media-hub 3 and 4 installed then
[15:24] <sil2100> jhodapp: well, once you land it, I can publish the seed change before the new media-hub gets into an image
[15:25] <jhodapp> ah perfect, ok
[15:25] <jhodapp> that's a good plan then
[15:25] <kenvandine> dobey, link for the packaging ack?
[15:26] <dobey> kenvandine: https://requests.ci-train.ubuntu.com/#/ticket/668 is the silo
[15:26] <dobey> the request
[15:29] <davmor2> cyphermox: \o/ thanks dude
[15:33] <tvoss> sil2100, hey there :) could you cancel the outstanding builds for powerpc for https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-021/+packages
[15:33] <tvoss> sil2100, they will fail and I'm tired of waiting
[15:33] <sil2100> tvoss: sure, ok
[15:34] <sil2100> tvoss: cancelled ;)
[15:34] <tvoss> sil2100, thank you
[15:35] <jhodapp> jibel, background playlists are ready for testing, it should show up in the QA Trello board shortly (silo 9)
[15:35] <jhodapp> jibel, let me or abeato know if there's any questions
[15:36] <kenvandine> dobey, good to go, should i publish?
[15:38] <dobey> kenvandine: yes please. thanks!
[15:40] <cjwatson> tvoss: I'm sorry about the wait.  Somebody (*glares at suspect*) put all the builders on manual without telling us about it or explaining why.
[15:40] <tvoss> cjwatson, no worries :)
[15:54] <tvoss> sil2100, I would appreciate a review here: https://code.launchpad.net/~thomas-voss/location-service/enable-dual-landing/+merge/278143
[15:56] <sil2100> tvoss: looking after the meeting :)
[16:23] <morphis> robru, sil2100, Mirv: you saw the discussion around version numbers in #ubuntu-devel?
[16:26] <xavigarcia> jibel: Hi there, I've already talked to design and we agreed that when switching off the Location switch it will make hide the location icon
[16:26] <xavigarcia> jibel: silo 6 shoud be again ready with that change
[16:27] <xavigarcia> jibel: there is a 5 minute delay showing the icon that is not clear yet, they already added a note to the specs stating that
[17:03] <jdstrand> sil2100, pmcgowan: when did we start shipping 15.10 frameworks on the device? I see the folloing on mako:
[17:03] <jdstrand> $ ls -1 /usr/share/click/frameworks/*15.10*
[17:03] <jdstrand> /usr/share/click/frameworks/ubuntu-sdk-15.10-dev1.framework
[17:03] <jdstrand> /usr/share/click/frameworks/ubuntu-sdk-15.10-html-dev1.framework
[17:03] <jdstrand> /usr/share/click/frameworks/ubuntu-sdk-15.10-papi-dev1.framework
[17:03] <jdstrand> /usr/share/click/frameworks/ubuntu-sdk-15.10-qml-dev1.framework
[17:04] <jdstrand> I find this very confusing. how can a 15.04 stable system have 15.10 frameworks?
[17:04] <pmcgowan> jdstrand, it shouldnt we should have removed that
[17:04] <jdstrand> (not to mention, click-apparmor in the overlay doesn't know what to do with them, so if an app targeted it, it would blow up)
[17:04] <jdstrand> ok, good
[17:04] <jdstrand> well, for some definition of good
[17:05] <pmcgowan> sil2100, we were supposed to take thse out when we went to 15.04.1
[17:05] <jdstrand> pmcgowan: shall I file a bug?
[17:05] <pmcgowan> jdstrand, yes please
[17:07] <jdstrand> pmcgowan: https://bugs.launchpad.net/ubuntu-rtm/+source/ubuntu-touch-meta/+bug/1518393
[17:40] <sil2100> pmcgowan: will remove those as well, yeah...
[17:41] <robru> morphis: I saw mention of version numbers but I didn't follow what the problem was our what the desired behavior was. Please file a bug against lp:cupstream2distro explaining it in detail
[17:42] <davmor2> sil2100:  if all the bluez5 stuff landed are you able to spin up a new image please, not sure if you got my earlier request
[17:46] <pmcgowan> sil2100, they are ok on xenial but not on vivid overlay
[17:54] <sil2100> davmor2: looks landed indeed, checking if everything is published and I'll kick an image now
[17:54] <sil2100> pmcgowan: yeah, not sure how those ended up in our vivid seeds, maybe I copied them over by accident
[17:55] <davmor2> sil2100: blame the Spanish inquisition nobody will expect that ;)d
[17:56] <sil2100> It's building now :)
[17:59] <davmor2> sil2100: \o/
[18:31] <robru> hmmmmm
[18:33] <robru> kenvandine: do you know what's going on with https://requests.ci-train.ubuntu.com/#/ticket/54 ? seems an old landing, not sure what happened there...
[18:34] <kenvandine> robru, oh... that wasn't supposed to be merged
[18:34] <kenvandine> it was an experimental silo
[18:34] <robru> kenvandine: yeah I don't know why the train is trying to merge it, since it's not landed.
[18:34] <robru> unless the version numbers match or something...
[18:34] <kenvandine> robru, can i edit the silo then kick a rebuild?
[18:35] <kenvandine> it's still useful for us
[18:35] <robru> kenvandine: yeah
[18:37] <robru> kenvandine: oh, haha, false alarm. it wasn't trying to merge it, there's just a bug causing the error to *say* merge&clean.
[18:38] <kenvandine> robru, good
[18:39] <robru> kenvandine: side effect of sloppy imports. the 'X failed:' prefix for exception messages is set at import time rather than runtime and the merging code gets *imported* in that script so it uses that prefix on exceptions
[18:43] <robru> kenvandine: you can force build to overcome that ^
[18:51] <kenvandine> robru, thx
[18:52] <robru> kenvandine: you're welcome
[18:57] <fginther> anpok, I'm looking at the unity-system-compositor problem you reported. If I find the fix, I'll rebuild that MP
[18:59] <anpok> thx!
[19:11] <fginther> anpok, it looks like this build was triggered from a manual rebuild. Is that correct?
[19:16] <anpok> yes
[19:28] <fginther> anpok, thanks for confirming. The build parameters appeared to have been set from when the job was configured to build for wily and it caused problems when building under xenial.  I've retriggered a new build with 'local_archive_pocket' set to xenial.  That should work, but will monitor it to make sure.
[19:28] <anpok> oh
[19:28] <anpok> ah.. right the build failure back then was still with a wily setup..
[19:29] <anpok> thx
[19:30] <fginther> anpok, you're welcome, sorry that this detail handled more intuitively
[19:30] <fginther> *isn't* handled more intuitively
[19:57] <boiko> rvr: hi, I just need to rebuild telepathy-ofono on silo 25 to include the fixes that just got merged from silo 52
[19:58] <boiko> rvr: as it is only bluetooth device names, shouldn't interfere with the tests already done
[20:22] <dobey> trainguards: can someone retry a few builds for me?
[20:22] <dobey> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-015/+build/8324821
[20:23] <dobey> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-015/+build/8271658
[20:23] <dobey> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-015/+build/8271661
[20:23] <dobey> thanks
[20:23] <robru> dobey: on it
[20:31] <rvr> boiko: ok
[20:54] <popey> ToyKeeper, thanks for testing music - seems I made a mistake and gave you the wrong click, have updated the citrain and trello card accordingly!
[20:54] <popey> (this fixes the issue you identiied)
[20:54] <popey> *identified