[00:41] <slangasek> fginther: so looking through the boottest failures, http://d-jenkins.ubuntu-ci:8080/view/Wily/view/BootTest/job/wily-boottest-lxc-android-config/lastBuild/console looks like a bug in the boottest infrastructure... why are the boottests assuming that they can dpkg install a package on a running phone?
[01:19] <slangasek> fginther: http://d-jenkins.ubuntu-ci:8080/view/Wily/view/BootTest/job/wily-boottest-thumbnailer/lastBuild/console - this shows it explicitly trying to install libthumbnailer0, despite the fact that libthumbnailer0 is only in wily, not in wily-proposed; also a bug in the boottest infra
[03:02] <fginther> slangasek, I've filed a bug for the libthumbnailer0 problem (https://bugs.launchpad.net/ubuntu-touch-boottest/+bug/1476459).
[03:05] <fginther> slangasek, the problem with lxc-android-config is also a known problem (https://bugs.launchpad.net/ubuntu-touch-boottest/+bug/1464284). The basic problem is that apt installing the set of binary packages was the only way to get boottest going. So it assumes packages can be installed until a human determines that they can't (in which case we have to manually pass a test)
[03:05] <fginther> slangasek, I've passed the current tests for thumbnailer and lxc-android-config so their proposed-migration blockers should be removed soon
[04:58] <slangasek> fginther: ok.  I had assumed that the boottest support was designed "correctly", to take the existing phone image, loop mount it, upgrade the packages, unmount, and flash that
[06:25] <anpok_> robru: i was looking into the boottest regression.. a fix is in progress
[06:31] <anpok_> robru: we need to rebuild mir to resolve that (we bascially failed to detect an internal ABI break) .. with that we will also adress a gcc-5 issue that blocks a different silo and the abi-compliance-checker
[08:00] <anpok_> seb128: 2015-07-21 07:39:24,833 ERROR mir 0.14.0+15.10.20150715-0ubuntu1 is missing from the changelog, which has up to 0.14.0-0ubuntu1. Please sync destination version back to trunk.
[08:02] <mandel> sil2100, did you see my message last night, looks like we cannot do a double silo, we need to do one per version, can we configure that for wily and then I'll do the needed things for utopic
[08:03] <anpok_> seb128: because we have a mir 0.14.0 in wily proposed I need to add another changelog entry?
[08:06] <seb128> anpok_, I'm unsure, something for the cilander to reply to, I guess that's because you try to land a new version when the previous one didn't go through
[08:07] <anpok_> ok
[08:07] <seb128> you probably need the new version to include the previous one or something
[08:07] <anpok_> ok
[08:07] <sil2100> mandel: I can reconfigure that for wily indeed, we can then sync what's possible to sync for vivid and prepare separate branches for the rest
[08:07] <sil2100> mandel: give me a few moment tho
[08:07] <mandel> sil2100, awesome, thx
[08:20] <sil2100> jibel, davmor2: hey, did you guys check and approve the no-QA-sign-off for silo 008? Those look indeed like trivial fixes, but just want to make sure you guys don't think you'd still want to see how it builds without that hard-dep
[08:30] <sil2100> mandel: reconfigured
[08:32] <sil2100> jibel, davmor2: I'll publish the silo in 30 mins if I don't get a NACK from you guys
[08:33] <jibel> sil2100, which silo?
[08:33] <sil2100> 008
[08:33] <sil2100> gcc-4.9 dep removal, not sure if you want to test that or not before publishing
[08:35] <jibel> sil2100, it drops the hard dep on gcc 4.9?
[08:35] <jibel> sil2100, if it builds, it's a pass
[08:36] <sil2100> Thanks, preferred to ask as we had those dbus-cpp issues in the past due to gcc dep changes ;)
[08:36] <sil2100> But here I guess not much can happen
[09:04] <sil2100> ogra_: is your rc-proposed device better now, with 8 fav apps and such?
[09:04] <ogra_> sil2100, yup. since last nights update
[09:05] <jibel> sil2100, last update fixed it as expected
[09:05] <sil2100> Good good
[09:05] <sil2100> I switched my phone to rc so I couldn't check, I corrected the channels and kicked a build yesterday before EOD
[09:29] <mandel> sil2100, love you! thx!
[10:41] <doko> sil2100, slangasek do you know why landing 16 has a ppa dependency on https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay ?
[10:46] <popey> jibel: sil2100 fyi I have just added a clock click to the citrain sheet. The changelog is linked. There's a rotation related bug we'd like to get fixed asap as OTA-5 made the app regress a bit.
[12:16] <jibel> popey, ack. Set it to 'Tested' on the spreadsheet once it is and we'll proceed with the verification.
[12:51] <popey> jibel: which column?
[12:55] <jibel> popey, column K
[12:57] <popey> jibel: thanks
[13:01] <mzanetti> sil2100, hey, not sure if you're the right guy to talk to about this, but maybe you know. could we add a "deb-src" entry to /etc/apt/sources.list.d/extra-ppas.list ?
[13:21] <sil2100> mzanetti: I might be the right person - what entry would you like to add?
[13:21] <mzanetti> sil2100, well, the stable-phone-overlay
[13:22] <mzanetti> sil2100, "sudo apt-get build-dep unity8" always gives me the build-deps from stable vivid, missing things that changed in the overlay
[13:22] <mzanetti> which is not really critical, but if it's just about copy-pasting that entry and adding "-src", it would make our (unity8) lifes a little easier
[13:23] <sil2100> Let me add that to my TODO list to consider ;)
[13:31] <rvr> ogra_: I've tried many times to reflash my arale, but I'm stuck in "error pushing:"
[13:31] <rvr> ogra_: http://paste.ubuntu.com/11914501/
[13:32] <rvr> I can adb shell there, so I don't know what's going on
[13:32] <ogra_> rvr, check syslo, i bet you see a lot USB disconnects
[13:33] <rvr> ogra_: In recovery, where can I see the syslog?
[13:34] <ogra_> oh, in recovery it should actualyl work ... and the syslog of your PC is in the usual place ;)
[13:34] <rvr> Ah, on the PC
[13:38] <rvr> ogra_: http://paste.ubuntu.com/11914540/
[13:38] <ogra_> rvr, yeah, looks fine and in recovery you shouldnt have disconnects
[13:39] <ogra_> rvr, probably /cache/recovery on the device is full or some such
[13:39] <sil2100> I go jump to bed now, I'll switch to a shell so that I can check the train through my phone
[13:39] <rvr> Error happens when pushing device
[13:39] <sil2100> o/
[13:40] <rvr> ogra_: http://paste.ubuntu.com/11914553/
[13:54] <balloons> cihelp, core apps job for clock app seems to be running tests under utopic again. I'm not sure how / why this happened. Can we get generic-mediumtests-utopic removed again? http://91.189.93.70:8080/job/ubuntu-clock-app-ci
[13:54] <fginther> balloons, sure hang-on
[13:55] <balloons> fginther, ubuntu-clock-app-vivid-amd64-ci is also gone from there.. Thanks :-)
[13:56] <rvr> dobey: ping
[13:56] <dobey> rvr: hi
[13:57] <rvr> dobey: Hi. I was testing silo 18.
[13:57] <rvr> dobey: I installed the click package in the bug report, sherlock-whatever, but I can't see it in the Apps scope
[13:57] <dobey> rvr: yes, broken .desktop files don't show up on the dash
[13:58] <rvr> dobey: Ok, so the test is that the scope doesn't crash, right?
[13:58] <dobey> rvr: the .desktop file is invalid so we can't show it. the fix allows the other apps to show up correctly, yes
[13:58] <rvr> dobey: Perfect
[13:58] <dobey> (it wasn't actually crashing, just blocking the results from showing up)
[13:59] <rvr> dobey: Ack
[13:59] <slangasek> doko: because that's the configuration for all of those silos - when they build stuff for the phone in vivid they need to build against that ppa.  That ppa is supposed to be empty for wily so it shouldn't have any impact
[14:03] <balloons> nice, I see a successful run fginther
[14:03] <rvr> dobey: Silo approved
[14:03] <dobey> rvr: great, thanks
[14:04] <slangasek> doko: of course, "supposed to be" != "is"; I see that there are two packages that have been mis-published to the overlay ppa for wily when they were supposed to go to the main archive.
[14:05] <sil2100> Yeah, we should probably remove those
[14:05] <slangasek> sil2100: did they get properly re-published to the archive?
[14:05] <slangasek> they have not been
[14:06] <slangasek> so, they need copied over
[14:06] <sil2100> huh?
[14:06] <slangasek> robru: we had a silo get published to the overlay ppa for wily by mistake; this is really something that should be blocked as a matter of policy
[14:06] <sil2100> I wonder how old those are
[14:06] <slangasek> sil2100: June 16
[14:06] <rvr> ogra_: I have manually pushed all the files to /cache/recovery. How can the flashing be triggered?
[14:06] <slangasek> sil2100: published June 22
[14:07] <slangasek> and still newer than anything in wily
[14:07] <ogra_> rvr, usually by rebooting to recovery
[14:07] <sil2100> Damn, usually we notice those, reconf and re-publish
[14:08] <rvr> ogra_: adb reboot recovery got arale in the same "static" recovery to push the files
[14:08] <ogra_> rvr, well, then i dont know
[14:08] <slangasek> sil2100: I'm assuming that the silo is gone now, right?  If so I'll just copy-package to the archive from stable-overlay-ppa
[14:08] <sil2100> anpok_: ping
[14:09] <anpok_> sil2100: pong
[14:09] <sil2100> slangasek: yeah, if it wasn't re-published then the publisher seems to have missed it...
[14:09] <slangasek> yeah, silo has been reclaimed
[14:09] <anpok_> i see
[14:09] <sil2100> anpok_: I saw you rebuild something, thought you re-built pay-service
[14:10] <anpok_> sil2100: i am working on a fix for the boottest
[14:10] <sil2100> But it seems you rebuilt mir
[14:10] <sil2100> anpok_: is the silo ready for publishing once pay-service is rebuilt?
[14:10] <sil2100> Since the silo appears to be set to 'ready to publish'
[14:11] <anpok_> sil2100: i can tell you in a minutes..
[14:12] <anpok_> *minute
[14:13] <sil2100> Thanks
[14:18] <anpok_> sil2100: not publishable at the moment
[14:24] <sil2100> Ok, let's mark it that way on the spreadsheet
[14:27] <sil2100> Marked
[14:32]  * sil2100 back to bed
[15:02] <davmor2> sil2100: silo004 is wily only are we just landing those?
[15:02] <sil2100> davmor2: yes, it's wily only
[15:03] <sil2100> And yes, I'm not in bed right now :|
[15:03] <sil2100> I think I'm addicted to this chair
[15:07] <davmor2> sil2100: sorry I missed the bed line, how is the cat by the way?
[15:09] <sil2100> The cat is using my bed now instead
[15:48] <anpok_> ping trainguards
[15:48] <anpok_> whats the best way to resolve this build error: https://ci-train.ubuntu.com/job/ubuntu-landing-004-1-build/278/console?
[15:49] <anpok_> the problem is that pay-service from silo04 was published to wily-proposed, and in the mean time a different build was released to wily afaik
[16:11] <sil2100> anpok_: let me take a look in a minute
[16:25] <jhodapp> robru or sil2100, can I please get a silo for line 77?
[16:36] <sil2100> jhodapp: on it
[16:37] <sil2100> jhodapp: no dual landing?
[16:38] <sil2100> jhodapp: assigned :)
[16:41] <jhodapp> sil2100, not on this one yet
[16:41] <jhodapp> sil2100, we'll be doing a large media-hub sync to vivid+overlay soonish
[16:41] <sil2100> Ok, good to know
[16:43] <robru> anpok_: that means there's a version of pay-service in the archive that isn't in trunk. in this case because it's in -proposed: https://launchpad.net/ubuntu/+source/pay-service so usually just wait for the one in proposed to migrate and then the build will succeed later.
[16:44] <robru> anpok_: if you really need to build right now, choose FORCE_REBUILD on the build job to build anyway. But note that this build will become dirty when the -proposed version migrates.
[16:45] <robru> anpok_: oh I just noticed you're rebuilding from the same silo, so in that case, yeah just FORCE_REBUILD.
[16:50] <kyrofa> Hey robru, I just updated my version of lintian and it caught a dep5-copyright-license-name-not-unique on a package that was already migrated from silo 11 to the NEW queue (unity-scope-snappy). Is it okay for me to rebuild that silo and get it migrated again?
[16:51] <robru> kyrofa: yeah that's fine.
[16:51] <kyrofa> robru, will it migrate automatically, or should I ping you?
[16:55] <rvr> boiko: Silo 56 approved
[16:55] <boiko> rvr: great! thanks!
[17:35] <jhodapp> robru, silo 19 is ready to be published
[17:36] <robru> jhodapp: mark it in the spreadsheet?
[17:36] <jhodapp> robru, one sec
[17:38] <jhodapp> robru, ok ready
[17:39] <robru> jhodapp: imma need some merges top-approved https://ci-train.ubuntu.com/job/ubuntu-landing-019-2-publish/80/console
[17:44] <jhodapp> robru, crap ok
[17:44] <jhodapp> thanks
[17:57] <robru> jhodapp: just ping me once they're approved.
[18:03] <kyrofa> trainguards: I'm ready for the updated debs built in silo 11 to be migrated to the NEW queue
[18:04] <robru> kyrofa: OK, one sec
[18:05] <kyrofa> Thanks robru :)
[18:05] <kyrofa> I figured that would be one less thing for the NEW reviewers to complain about when they get to it