[09:19] <bzoltan> hello folks... would anybody be here to reconfigure the silo13? Set an other strange conflict ...
[09:20] <bzoltan> robotfuel: cyphermox, rsalveti ^
[09:27] <ogra_> bzoltan, heh, good luck with getting any landings on the weekend
[11:10] <bzoltan> ogra_: I am not after landing ... but to get a bloody non conflicting build in the Silo
[11:10] <bzoltan> ogra_:  :) that is the fun part ... all MRs were tested, gave green and merged without conflict locally
[11:18] <ogra_> well, there are simply no propoer plans for driving the silos on weekends yet
[11:18] <ogra_> (i brought that up last week, but there is no solution atm)
[12:02] <bzoltan> ogra_: I do not hav high expectations :)
[12:03] <bzoltan> ogra_: btw, would you reconfigure it? If that is what it needs...
[15:55] <asac> cyphermox: want to help a citrain?
[15:55] <asac> emergency landing?
[16:33] <asac> cyphermox: dont worry
[16:33] <asac> we wait till monday (in case you read this)
[16:37] <bzoltan> whoever reconfigured my silo :) thank you a lot ...
[16:53] <bzoltan> does anybody know what that means http://162.213.34.102/job/landing-013-3-merge-clean/13/console
[17:18] <rsalveti> [17:53] <bzoltan> rsalveti:  do you know what that error is about?  ^^
[17:57] <sil2100> mandel: hi!
[17:58] <sil2100> mandel: regarding that broken u-d-m - does the branch attached to the bug fix the problem?
[17:58] <sil2100> asac: I'll try to do an emergency landing ASAP
[18:05] <sil2100> popey: ^
[18:06] <popey> sil2100: no idea.
[18:06] <popey> sil2100: i can test if someone can build me a deb or whatever?
[18:06] <sil2100> popey: I'll test it as well, I'm building it in a silo now
[18:07] <sil2100> popey: would appreciate your help
[18:07] <sil2100> Major fuckup from my side
[18:07] <popey> sil2100: No problem at all. Lets focus on getting it fixed and tested and not dwell on who broke it.
[18:08] <popey> sil2100: my device is on 212 right now, should I update to 214 and then await a ppa?
[18:09] <sil2100> I guess 214 might be a good idea, as it's broken
[18:10] <popey> kk
[18:10] <popey> doing now
[18:17] <cjwatson> woo, finally all tests passing on my libclick branch
[18:17] <cjwatson> might not be too far away now ...
[18:19] <popey> sil2100: just ping me when you need something, I'm afk but I get pinged from highlights
[18:41] <sil2100> popey: ppa:ci-train-ppa-service/landing-004 <- PPA link!
[18:41] <sil2100> It's built
[18:42] <popey> sil2100: ok
[18:42] <popey> sil2100:  you planning on doing ap tests?
[18:43] <sil2100> popey: dogfooding for sure, not sure if we have AP tests for this?
[18:44] <popey> no idea
[18:45] <popey> root@ubuntu-phablet:/# apt-cache policy ubuntu-download-manager
[18:45] <popey> ubuntu-download-manager: Installed: 0.3+14.04.20140224-0ubuntu1 Candidate: 0.3+14.04.20140301-0ubuntu1
[18:49] <popey> sil2100: testing installing a new click package and using update manager, both work with that ppa installed
[18:50]  * popey tests a bit more
[18:52]  * sil2100 reboots after an upgrade
[18:55] <sil2100> popey: can you try the update tests from https://wiki.ubuntu.com/Process/Merges/TestPlan/ubuntu-download-manager as well?
[18:57] <popey> sil2100: ok
[19:00] <sil2100> popey: thanks!
[19:00] <sil2100> So far so good on my device as well
[19:02] <popey> sil2100: hm, i cant do 3g test, no 3g data on this sim
[19:02] <sil2100> popey: then WiFi should be enough, I'll do 3G data test otherwise
[19:03] <popey> thanks
[19:07] <sil2100> hmmmm
[19:09] <sil2100> Crap, 3G downloading doesn't seem to work ;/
[19:09] <sil2100> Let me revert and see if it worked in the past
[19:12] <popey> you sure you have data available on your sim? not run out of allowance?
[19:13] <sil2100> Webbrowser works fine
[19:13] <popey> ok
[19:13] <sil2100> And I'm pinging stuff fine
[19:13] <popey> worth checking ☻
[19:13] <sil2100> But the script for downloading just doesn't work ;/ While it works on WiFi
[19:19] <sil2100> I'll retry the test
[19:30] <sil2100> geh
[19:31] <popey> wassup?
[19:32] <sil2100> So, it seems that strangely now switching from 3G to WiFi (and the other way around) breaks the downloading - at least it seems so
[19:32] <popey> sounds like that problem I reported in browser
[19:32] <sil2100> I would say this: I'll fill in a bug but land this anyway
[19:33] <sil2100> ralsina_: ping
[19:34] <popey> sil2100: i have re-triggered bug 1277589
[19:34] <popey> (while testing your u-d-m update"
[19:35] <sil2100> Crap
[19:35] <sil2100> So, it's reintroducing a regression, yes?
[19:35] <popey> however
[19:35] <popey> no
[19:35] <popey> i downgraded u-d-m and it still happens
[19:35] <sil2100> Ah, but you downgraded to which version?
[19:35] <popey> i just think that bug isn't fixed - separately from your u-d-m issue
[19:35] <sil2100> The archive has a broken one
[19:36] <popey> "This bug was fixed in the package ubuntu-system-settings - 0.1+14.04.20140218.1-0ubuntu1
[19:36] <popey> "
[19:36] <sil2100> popey: to which you downgraded?
[19:36] <popey> no, hang on...
[19:36] <popey> I update to your new u-d-m
[19:36] <popey> triggered the above bug, thought "uh-oh" so I downgraded u-d-m back to the one in #212
[19:36] <sil2100> Oh
[19:37] <popey> to make sure that didnt re-introduce it
[19:37] <popey> and I can trigger the above bug again on #212 stock
[19:37] <sil2100> And it's there, right? 212 seems to have the 'right' version
[19:37] <sil2100> Ok
[19:37] <sil2100> phew.
[19:37] <popey> yes, 212 has the right version, but its still broken
[19:37] <popey> sorry, shouldn't have mentioned it ☻
[19:37] <popey> it's clouding the conversation ☻
[19:38] <popey> just going to do one more test of your u-d-m upgrading from 212 to 215
[19:38] <sil2100> :)
[19:38] <sil2100> \o/
[19:38] <sil2100> If it goes good then let's release
[19:38] <sil2100> \o\
[19:38] <popey> k
[19:42]  * sil2100 keeps his fingers crossed
[19:46] <popey> sil2100: ok, i upgraded over wifi and it worked fine with your u-d-m, and I did the other tests for installing click packages too
[19:47] <sil2100> popey: awesome, thanks for the help man ;)
[19:47] <sil2100> Let's get this published
[19:47] <popey> np
[19:47] <popey> thanks for jumping in to fix
[19:51] <popey> sil2100: its a shame 215 was so recently triggered, will this be in the 3am image?
[19:53] <sil2100> popey: I guess so
[19:54] <sil2100> popey: I don't have the power of triggering image builds, so we'll have to wait for the next tick
[19:54] <popey> sil2100: rsalveti can
[19:55] <sil2100> popey: you can try poking him if he's around ;) But first wait until it hits the archive properly!
[19:55] <sil2100> Sicne it's probably still in -proposed
[19:55] <popey> well right now 215 is still being qa'ed
[19:55] <popey> http://ci.ubuntu.com/smokeng/trusty/touch/
[19:56] <popey> so would be preferable to leave it some time. and as it's saturday, might be prudent to just wait for the 3am kick, or piggyback on another image that someone else may kick for whatever reason
[19:56] <ogra_> want an image build once it is in ?
[19:56] <popey> unconvinced it's worth it, what do you think ogra_?
[19:57] <ogra_> who built 215 ?
[19:57] <popey> ricardo
[19:57] <popey> 2.5 hours ago
[19:57] <ogra_> ah, yeah, i see it in the backlog
[19:57] <ogra_> yeah, then testing will still take 3-4h for it
[19:59] <ogra_> which means if i built then 216 will clash with 217 testing
[19:59] <ogra_> so lets juts leave it to cron (3am UTC)
[19:59] <ogra_> else we will only get messy test results in the end
[20:01] <popey> +1
[20:08] <popey> sil2100: want to reply to that mail on the list letting everyone know?
[20:11] <sil2100> popey: to which mail?
[20:11] <sil2100> popey: I already sent out an info that we did that landing and the next image should be ok
[20:11] <sil2100> To the ML
[20:18] <popey> cool
[20:18]  * ogra_ sent a followup about the images
[20:18] <popey> i hadn't seen it, sorry
[20:20]  * ogra_ goes back to watch snooker :)
[20:24]  * popey goes back to portal 2
[20:25] <popey> *on* *linux* :D
[20:28] <sil2100> :D
[20:29] <sil2100> Ok, I see u-d-m is ready for migration, so I go now
[20:29] <sil2100> See you on Monday! (hopefully)
[23:02] <ogra_> rsalveti, wow, ofono is seriously broken (at least on e.crash from the scripts per test ... some have two)