[02:02] <robru> oops, IRC issues, I'm back now, if anybody needs anything please ping me
[09:30] <sil2100> jibel: hey! Are you guys looking at krillin now? Is all testing finished for arale already?
[09:49] <sil2100> jibel: would be nice if we also had someone picking up silo 17, since Omer wasn't able to test it properly
[10:00] <Laney> is any cihelp person here? I'd like it if you could investigate why http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#adwaita-icon-theme says boottest is red when it is green on https://jenkins.qa.ubuntu.com/job/wily-boottest-adwaita-icon-theme/lastBuild/
[10:17] <jibel> rvr, Hey, can you take silo 17, omer was unable to test it, his device has a broken slot
[10:19] <rvr> jibel: Ok
[11:07] <Mirv> (repeating from late yesterday evening) dbarth: could you check spreadsheet lines 13, 15, 30 and clarify status/needs of those
[11:07] <Mirv> lines changed a bit since yesterday
[11:07] <Mirv> dbarth_: ^ (in case highlight needs that "_" in there)
[11:15]  * sil2100 off to prepare lunch
[11:18] <dbarth_> Mirv: ah ok
[11:42] <fginther> Laney, hello. In trying to fix the source package issues, we've accidentally broken the creation of the results file that is sent to britney. It shouldn't be too hard to fix, but it might take an hour or two
[11:42] <Laney> fginther: oh right, is that what I pinged about?
[11:43] <fginther> Laney, you pinged on https://jenkins.qa.ubuntu.com/job/wily-boottest-adwaita-icon-theme/lastBuild/ :-)
[11:43] <Laney> yus
[11:43] <Laney> probably is
[11:44] <Laney> fginther: anyway, cool, thanks for working on this issue!
[11:47] <cjwatson> kgunn: https://code.launchpad.net/~cjwatson/launchpad/bmp-show-diffstat/+merge/260921 - FYI since that was one of your stakeholder requests
[11:56] <rvr> jibel: ping
[12:02] <jibel> rvr, pong
[12:03] <rvr> jibel: Test case requires first boot, I reset the phone instead. Not sure if that's enough warranty of the clean setup.
[12:05] <rvr> Hmmmm... but I can try to reproduce the problem without the silo and with reset.
[12:09] <jibel> rvr, it's the closest environment you can get without too much effort, otherwise, flash the device, go to fastboot, flash the recovery with adb enabled, go to recovery, install the package from recovery and reboot. But it is not worth it
[12:12] <jibel> rvr, you need help with this silo or it is all good?
[12:12] <jibel> this = 17
[12:12] <rvr> jibel: Then the silo looks good
[12:14] <rvr> boiko is not available
[12:41] <pmcgowan> jibel, sil2100 how we doin
[12:41] <sil2100> pmcgowan: rvr is testing silo 17 now, since Omer didn't have a device that would be good for testing it
[12:41] <sil2100> I suppose krillin regression tests are in progress in overall
[12:42] <pmcgowan> great so no arale blockers yet either sil2100
[12:43] <sil2100> Yeah, the only blockers were the cut-the-rope thing that we already agreed on and location, which has been signed off - so it seems arale testing is done
[12:43] <sil2100> I poked jibel and he said it's done
[12:50] <pmcgowan> sil2100, jibel I want to get this cosmetic/usability fix in today as well https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1450894
[12:50] <sil2100> Ah, the one that seb128 mentioned?
[12:51] <sil2100> pmcgowan: ok, you want this for the krillin release though, right? Not arale?
[12:51] <pmcgowan> yeah, got consensus with design
[12:51] <pmcgowan> krillin only
[12:51] <pmcgowan> well ota4+
[12:56] <jibel> pmcgowan, works for me.
[12:57] <bregma> trainguards, could I get a reconfigure run for line 48 (silo ubuntu/landing-021) please?
[12:57] <sil2100> bregma: on it
[12:57] <bregma> ta
[12:59] <sil2100> bregma: reconfigured, yw
[13:15] <dobey> cihelp: it seems https://jenkins.qa.ubuntu.com/job/wily-boottest-unity-scope-click/lastBuild/ finished about 14h ago, but http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html says it is still in progress, so the package is still being held in proposed :-/
[13:16] <Ursinha> dobey: hi :) we're working on the boottest issues this week, let me see if that has to do with the changes we've been making
[13:17] <dobey> hmm, the private jenkins seems to be timing out or something though
[13:18] <Ursinha> dobey: weird, I just accessed it
[13:18] <Ursinha> dobey: are you connected to the vpn?
[13:19] <dobey> i was, yes
[13:19] <Ursinha> odd
[13:20] <Ursinha> dobey: it might be related to "<fginther> In trying to fix the source package issues, we've accidentally broken the creation of the results file that is sent to britney. It shouldn't be too hard to fix, but it might take an hour or two"
[13:20] <plars> Ursinha: dobey: I can get to it fine
[13:20] <dobey> ah ok
[13:21] <Ursinha> dobey: "test in progress" some times means britney (proposed-migration "brain") didn't understand the test was completed, so what fginther said there sounds related
[13:21] <dobey> Ursinha: right
[13:21] <dobey> hopefully it's that then, and will be fixed in a couple hours :)
[13:22] <Ursinha> dobey: yeah :) fginther and plars are working on boottesting this week to make it smarter and results more readable, it should improve greatly
[13:23] <plars> yeah, looking into this now
[13:25] <fginther> dobey, plars, I can unwedge individual package while this problem gets sorted out. dobey working on unity-scope-click now
[13:27] <dobey> fginther: ok, thanks
[13:40] <rvr> sil2100: Can I approve silo 17 directly?
[13:40] <sil2100> rvr: hey! What do you mean?
[13:40] <rvr> sil2100: Whether I will break something if I sign off in the spreadsheet :)
[13:41] <sil2100> Nooo, the spreadsheet seems to be working right now, so feel free to do it normally
[13:41] <rvr> Ok, approving silo 17
[13:41] <rvr> boiko: ^
[13:41] <sil2100> Excellent
[13:41] <sil2100> \o/
[13:41] <sil2100> rvr: thanks
[13:41] <boiko> rvr: thanks a lot \o/
[13:43] <sil2100> Ok, we need an archive admin to +1 it
[13:48] <dbarth_> Mirv: replied for 13, 15 and 31; basically there is just 1 request remaining
[13:59] <Mirv> dbarth_: excellent! it's line 14 now and it has a dual landing silo 001
[14:02] <dbarth_> Mirv: thanks!
[14:03] <boiko> sil2100: the packagaging changes are only in wily, right? we landed some critical fixes that were not landed on wily, and now they will land there
[14:15] <dobey> fginther: i see it made it through now. thanks :)
[14:24] <sil2100> boiko: yeah, and since it's a dual landing we can't land just one of them
[14:24] <sil2100> I mean, we can, but we wouldn't want that
[14:24] <sil2100> We don't seem to have an archive admin around though
[14:28] <rvr> Today I hit this bug. Nothing critical, but looks ugly https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1454882
[15:08] <cyphermox> cihelp: could someone please take another look at wily-desktop-amd64-smoke-default ? It's been failing for a long while, seems to have gotten better recently but I can't seem to find a reason for it to fail -- the install using wily pending images works.
[15:14] <dobey> cihelp: hrmm, "chroot problem" on fisher03 (ppc64el) or do lp people need to be pinged for that? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-022/+build/7502354
[15:17] <ChrisTownsend> trainguards: May I have a silo, pretty please?
[15:18] <sil2100> ChrisTownsend: on it :)
[15:18] <ChrisTownsend> sil2100: Thanks:)
[15:20] <sil2100> yw!
[15:22] <plars> dobey: I think that's for trainguards, not ci
[15:23] <sil2100> dobey: looking
[15:23] <sil2100> Uh, let's rebuild
[15:23] <plars> cyphermox: sorry for the delay, my irc didn't highlight for some reason, I'll take a look
[15:23] <cyphermox> plars: no worries
[15:24] <cjwatson> dobey,plars,sil2100: chroot problems are LP issues (or lower-level), please don't just retry without giving us a chance to investigate
[15:25] <cjwatson> unfortunately we've lost the evidence now, and other recent builds on that builder seem to be OK
[15:25] <sil2100> cjwatson: apologies for that, that was usually what we were told to do in the past (not by the LP team though)
[15:26] <cjwatson> sil2100: there was a point where chroot problems were relatively common and due to apt-related races, but we dealt with that in launchpad-buildd and now they're anomalous situations.  do you happen to remember what the build log indicated?
[15:26] <dobey> cjwatson: that's why i asked if i should just ping lp instead :)
[15:26] <sil2100> cjwatson: I'll try to fetch that
[15:26] <cjwatson> dobey: indeed, and you got the wrong answer :)
[15:26] <dobey> indeed
[15:26] <cjwatson> sil2100: the build log is gone now, retrying loses it
[15:26] <cjwatson> sil2100: which is why I asked if you remembered it :)
[15:27] <sil2100> I still have it in my memory ;)
[15:27] <sil2100> I mean, I have the log in my browser memory, let me pastebinit
[15:27] <cjwatson> ah, cool
[15:27] <sil2100> That's what I meant fetching it
[15:27] <sil2100> cjwatson: http://paste.ubuntu.com/11545012/
[15:27] <dobey> cjwatson: https://launchpadlibrarian.net/208179642/buildlog_ubuntu-wily-ppc64el.ubuntuone-credentials_15.10%2B15.10.20150603_BUILDING.txt.gz
[15:28] <cjwatson> gosh, that's exciting
[15:32] <cjwatson> sil2100: ok, the retry was fine in this case, I'll see if I can track down what happened though
[15:33] <sil2100> Thanks :)
[15:36] <rvr> jibel: sil2100: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1461593
[15:37] <sil2100> huh
[15:40] <sil2100> rvr: is that part of the standard test plan? i.e. did this work last time the regression suite was run?
[15:43] <rvr> sil2100: Hmm... Let me check if I can see a similar test. I was running a test case for "2G data only" which only has the first steps in the bug report.
[15:44] <sil2100> Ok, anyway, looks a bit bad, but I leave it up to you guys to decide if it's a blocker
[15:49] <rvr> sil2100: This works fine in stable
[15:50] <pmcgowan> rvr, did you check if it comes back after time, I recall a realted bug on a delay
[15:52] <rvr> pmcgowan: Hmm... let me recheck, it may be the case
[15:58] <rvr> pmcgowan: Over five minutes and still waiting
[15:58] <pmcgowan> rvr, ok aybe not then
[15:59] <rvr> pmcgowan: 7 minutes, and connection was back
[16:01] <pmcgowan> oh
[16:05] <pmcgowan> rvr, it sounds like https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418077 which should be fixed
[16:05] <pmcgowan> awe, ^^
[16:09] <rvr> pmcgowan: awe: Interesting, because when switching from 3G to 2G, data connection is up very quickly. The bug report implies that both changes would trigger the problem.
[16:13] <awe> rvr, can you please include which operators you used in the bug?
[16:13] <rvr> awe: Sure
[16:13] <plars> cyphermox: something has /var/cache/debconf/config.dat locked when a latecommand is running in the preseed to install some additional packages. I don't know why this change came into wily or where it came from though. Any ideas?
[16:13] <awe> also, if the image you're testing the OTA4 image?
[16:14] <awe> rvr, ^^
[16:14] <rvr> awe: Yup, that's already reported. #23 in ubuntu-touch/rc-proposed/bq-aquaris.en
[16:15] <awe> just confirming
[16:15] <awe> hmmm
[16:16] <awe> can you reproduce the problem again and attach the output of 'list-modems', 'list-contexts' ( both in /usr/share/ofono/scripts ) and /var/log/syslog
[16:16] <awe> rvr, certainly sounds similar to the bug pmcgowan posted above, but that was fixed awhile back...
[16:17] <rvr> awe: Of course, on it
[16:17] <awe> rvr, unfortunately I can't reproduce with krillin due to the fact that it only does 2g here in the US
[16:17] <awe> but I'll try on arale
[16:24] <rvr> awe: Output of 'list-modems' and 'list-contexts': http://paste.ubuntu.com/11545969/
[16:34] <awe> thanks rvr
[16:35] <awe> I'll review this afternoon; I'm headed to grab some lunch now. be back in a bit...
[16:42] <cyphermox> plars: no. nothing should keep it locked; is there any way you could add a check for that lock as the very first step of the late command, so we know whether it's something in the latecommand that triggers it or if it's from the install?
[16:43] <plars> cyphermox: that's what I'm trying to do, but not with much luck to see what's happening so far
[17:26] <pmcgowan> renatu, charles did you get a silo yet? need that tested today
[17:28] <pmcgowan> sil2100, for a dual landing how can you tell if it published to the overlay? are vivid and wily in parallel?
[17:29] <sil2100> pmcgowan: it's automatically published to the overlay PPA
[17:29] <sil2100> It publishes them in parallel, but the overlay part is just a PPA copy so it's almost instant
[17:29] <pmcgowan> sil2100, looking at https://bugs.launchpad.net/dialer-app/+bug/1460111
[17:30] <pmcgowan> its not closed out, maybe just takes a while
[17:30] <pmcgowan> oh
[17:30] <sil2100> Yeah, because the fix wasn't in dialer-app ;/
[17:30] <pmcgowan> righto
[17:30] <sil2100> The fix was in telepathy-ofono and it wasn't marked for Ubuntu-RTM
[17:30] <sil2100> So it wasn't auto-closed
[17:31] <pmcgowan> right
[17:31] <pmcgowan> I will fix the bug up then
[17:31] <charles> pmcgowan, wrt the led silo, I'm sorry, I thought you and renatu were on it
[17:31] <charles> pmcgowan, I don't see it in the spreadsheet, adding it now
[17:31] <pmcgowan> charles, thanks, I don't ever do silos myself
[17:31] <charles> pmcgowan: ack :-)
[17:31] <rvr> sil2100: Are you creating a new image with silo 17?
[17:31] <pmcgowan> that would be asking for trouble
[17:31] <charles> renatu, are you around?
[17:31] <sil2100> rvr: on it now, I was out shopping
[17:32] <rvr> sil2100: Ok
[17:33] <charles> renatu, looks like https://code.launchpad.net/~renatofilho/unity8/blue-led/+merge/224899 is failing jenkins
[17:33] <charles> but it passed earlier a few revisions up, so this may be a hiccup
[17:33] <charles> I'll resubmit it
[17:44] <charles> ah! renatu, disregard previous comment for the obvious reason
[17:48] <sil2100> hmm
[17:48] <sil2100> imgbot didn't notice the build apparently
[17:50] <charles> trainguards, +1
[17:50] <robru> charles: on it
[17:51] <robru> charles: ok, silo 46, note the conflict in silo 4.
[17:51] <charles> hurmmm, yeah
[17:53] <charles> I think it should be okay, renatu's patch in silo 46 only touches qml/Panel/Indicators/IndicatorsLight.qml ... but checking the unity8 shellrotation diff to confirm
[18:00] <robru> charles: it's fine if they conflict, you just have to manage rebuilding whichever one publishes second.
[18:05] <charles> robru, I need to reconfigure line 57 to add tiheum's branch as well; when I run Landing Tools > Reconfigure > Click here I get "Problem accessing /job/-0-reconfigure/parambuild. Reason: Not Found"
[18:06] <fginther> Laney, I found something I don't understand. On wily, "grep-aptavail -X -n -S -sPackage gcc-5" does not list libgcc1, but "apt-cache show libgcc1" shows that libgcc1's Source package is gcc-5.
[18:07] <fginther> Laney, this is related to that MP you proposed a few days ago for boottest. Thought you might know what's going on here.
[18:09] <robru> charles: try now
[18:10] <charles> robru, works now, thanks :)
[18:10] <robru> charles: you're welcome
[18:21] <boiko> robru: do you by chance know why telepathy-ofono is listed as Not considered in the update excuses? (this is related to silo 17)
[18:22] <robru> boiko: the three previous lines say "unsatisfiable depends"
[18:22] <boiko> robru: ouch! duh, should have seen it :)
[18:23] <boiko> salem_: ^
[18:23] <robru> boiko: yeah not sure the details but you'll have to poke at those depends.
[18:24] <robru> boiko: salem_ https://ci-train.ubuntu.com/job/ubuntu-landing-017-1-build/190/artifact/telepathy-ofono_packaging_changes.diff/*view*/ looks like "libmission-control-plugins-dev (>= 1:5.14.0)" is new, check that's available in wily.
[18:24] <robru> boiko: salem_: nm, it's libhybris-utils, duh
[18:24] <robru> looking at wrong spot
[18:25] <boiko> robru: we had that package in vivid overlay already, but it seems hybris is not available on those arches, so we might need to make the package building conditional
[18:26] <salem_> boiko, what archs?
[18:26] <boiko> salem_: arm64, powerpc and ppc64el
[18:26] <robru> salem_: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#telepathy-ofono
[18:27] <boiko> robru: if we fix the build/packaging in the MP that's currently on the silo and rebuild it, can you re-publish it afterwards?
[18:27] <robru> boiko: so I guess technically this counts as an arch regression; make it conditional on those arches if possible, otherwise you might be able to get an archive admin to wave this through
[18:27] <robru> boiko: yep
[18:27] <salem_> robru, boiko thanks
[18:28] <robru> salem_: you're welcome
[18:35] <charles> robru, I was wrong, the reconfigure of line 57 to add tiheum's branch didn't take. Re-attempting a reconfigure gives me the same "Problem accessing /job/-0-reconfigure/parambuild. Reason: Not Found" error as before
[18:36] <robru> charles: oh you're adding a new package. I thought you were adding a new MP within the same package.
[18:37] <robru> charles: yeah I have to reconf that.
[18:37] <charles> robru, ack
[18:38] <robru> charles: ok should be good now
[18:39] <charles> robru, thanks again :)
[18:39] <robru> charles: you're welcome!
[18:43] <ChrisTownsend> trainguards: Could you please publish landing-035?
[18:44] <robru> ChrisTownsend: done! good luck with SRUing!
[18:45] <ChrisTownsend> robru: Thanks!  I think this one will get through pretty fast.
[18:45] <robru> sweet
[18:54] <pmcgowan> hey sil2100 I am still hoping on silo 46 and we seem to have an app icon issue to attend to
[18:56]  * robru --> lunch
[18:58] <boiko> robru: package rebuilding on silo 17
[19:03] <boiko> robru: when you are back, it seems that the package already landed on vivid overlay(?) and now a rebuild fails
[19:26] <robru> boiko: checking
[19:26] <sil2100> pmcgowan: sure thing, yeah, I just meant that the blocker bugs are out of the way, but we can land some additional things on the way as well
[19:27] <sil2100> As you proposed on the meeting yesterday
[19:27] <robru> boiko: oh, no, that's just because 602.2 is sitting in propose. just FORCE_REBUILD it and it'll work.
[19:27] <boiko> robru: nice! let me do that then
[19:27] <robru> boiko: I think that's technically a train bug, I should fix that to check only dest archive, and ignore proposed. I've seen this pop up before.
[19:28] <boiko> robru: ack. want me to report that? if so, where?
[19:28] <robru> boiko: it's ok, I'm filing it
[19:29] <boiko> robru: ok
[19:30] <robru> boiko: https://bugs.launchpad.net/cupstream2distro/+bug/1461661
[19:31] <boiko> robru: nice
[19:45] <jgdx> trainguards, hey, seems I have two identical spreadsheet lines creating two silos. Only need one. :) Line: 14, 41 and Silos: 30, 33
[19:46] <jgdx> actually, if I want to build, what do I choose? In the dash only the status differ.
[19:47] <jgdx> kenvandine, what did I do? ^ :P
[19:48] <jdstrand> pmcgowan: fyi, https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1456628/comments/6
[19:49] <robru> jgdx: looks like mirv assigned you one extra by mistake. I'll free 30 since it's empty anyway
[19:50] <pmcgowan> jdstrand, very good
[19:50] <robru> jgdx: so build 33 if you need a rebuild.
[19:55] <jgdx> robru, cheers
[19:56] <robru> jgdx: you're welcome
[20:09] <boiko> robru: silo 17 rebuild finished
[20:10] <robru> boiko: ok, published. it's in vivid overlay already, will show up in wily-proposed soon
[20:37] <boiko> robru: thanks!
[20:37] <robru> boiko: you're welcome
[20:46] <boiko> robru: even though the update excuses says it is testing the package, there are some "old binaries left on <arch>" and the Not considered message
[20:46] <robru> boiko: ah, you'll need to get somebody from #ubuntu-release to clear those out
[20:48] <boiko> robru: /me joins and asks
[21:04] <jibel> renatu, what is the change with the theme in silo 46? Should the app icons be different?
[21:05] <renatu> jibel, I am not sure what is the changes on the icons
[21:06] <jibel> pmcgowan, ^ do you know?
[21:07] <pmcgowan> oh crap
[21:07] <pmcgowan> did you bring the entire theme in?
[21:07] <pmcgowan> charles, ^^
[21:07] <pmcgowan> thats what we wanted to land later
[21:08] <charles> pmcgowan, oog. The individual icon wasn't in a separate MP...
[21:08] <charles> yes, we'll want to split that up then.
[21:08] <pmcgowan> we want it soon but not today
[21:09] <pmcgowan> gotta run
[21:10] <charles> ack
[21:12] <charles> jibel, so as per ^ we'll want to shelve https://trello.com/c/JXxJRGIt/1753-ubuntu-landing-046-unity8-ubuntu-themes-renatu-charles
[21:13] <charles> I'll unmark it in the spreadsheet until we get a revised MP for unity-themes
[21:14] <plars> cyphermox: so it seems something along the way is running debconf-communicate, and that's locking that config.dat. It's got to be something in the install process though, which is causing some package installs in late_command setup to fail
[21:14] <cyphermox> well, I just tried debconf-communicate
[21:15] <cyphermox> gonna try again to be sure
[21:16] <tedg> trainguards, could I please get a vivid silo for line 57 please?
[21:18] <robru> tedg: silo 30
[21:20] <tedg> Thanks robru
[21:20] <robru> tedg: you're welcome
[21:25] <jibel> charles, tedg when silos 46 and 30 are ready for testing, can you ping ToyKeeper to do the verification. I've to leave now.
[21:25] <tedg> Sure
[21:25] <charles> jibel, ack
[21:28] <boiko> robru: should I be worried about the Regression status on the update_excuses page?
[21:29] <robru> boiko: generally yeah
[21:30] <robru> boiko: that's a boottest, it's known to be flaky. Ask cihelp to investigate/retry
[21:30] <robru> (Also i saw that passed last time)
[21:31] <plars> boiko: which job?
[21:31] <robru> plars: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#telepathy-ofono
[21:33] <fginther> plars, *sigh* looks like it still failed with a ssh command failure
[21:33] <plars> fginther: yeah, just saw the 255
[21:34] <plars> fginther: but we got an exit code 12, which is different :/
[21:34] <cyphermox> plars: as far as I can tell, debconf-communicate does work after the install
[21:35] <plars> fginther: that should be erronious package according to adt-run, but the 255 tells me it was more likely ssh
[21:35] <plars> cyphermox: debconf-communicate is the thing locking that file and preventing progress though
[21:35] <plars> so I guess, yes it's working :)
[21:35] <cyphermox> plars: I just ran  echo "GET keyboard-configuration/layoutcode | sudo debconf-communicate" from a sudo chroot /target, in another VT on the CD (because I forgot to start the installer in a live session)
[21:36] <cyphermox> that should have failed as much as whatever it is taht you guys are running in latecommands
[21:36] <plars> cyphermox: nothing in the preseed that gets added for the test setup uses debconf-communicate
[21:36] <fginther> plars, yeah, it kinda looks like adt-run interpretted that as an erroneous failure based on it trying to do a specific thing.
[21:36] <cyphermox> anything using debconf...
[21:36] <cyphermox> apt-get some such, or dpkg, or whatever
[21:37] <fginther> plars, wft, I'll fix the permissions on boottest.sh, it somehow got flipped in a recent MP
[21:38] <cyphermox> I'm happy to try installing packages now, if you tell me what it is that runs in the latecommand
[21:38] <fginther> plars, I'll take care of this as you look busy
[21:44] <robru> kenvandine: around for a packaging ack? https://ci-train.ubuntu.com/job/ubuntu-landing-016-2-publish/
[21:50] <fginther> boiko, plars, trying wily-boottest-telepathy-ofono again
[21:52] <boiko> fginther: thanks