=== salem_ is now known as _salem
[03:04] <lpotter> grr.. why isnt that waiting to build anymore...
[03:22] <robru> lpotter: check the build deps in the packaging
[03:24] <robru> renatu: tedg : failed to build with no build log is an lp bug, all you can do is try again
[04:45] <lpotter> robru: build deps worked before last change to media-hub was merged. the diffs look like it should work
[04:53] <lpotter_> hmm.. seems media-hub doesn't actually apply the version number change now ;/
[05:08] <robru> lpotter_: what version number change? You need to bump the build dep version every time if you want the build to wait for a different package in the same silo
[05:13] <robru> lpotter_: like if you set the build dep to wait for the new build, and then release that and start a new silo, the dep is then satisfied by the distro version so it doesn't wait anymore
[05:13] <robru> You have to bump the dep for every new silo
[05:41] <lpotter_> the version change to media-hub (to 4.2.1) should be part of the diff. qtubuntu-media should still have the build dep of >= 4.2.1
[05:42] <lpotter_> the other change kept it at 4.2.0
[05:42] <lpotter_> the one just merged
[09:15] <pstolowski> trainguards hmm, chroot problem? https://requests.ci-train.ubuntu.com/#/ticket/1587
[09:17] <sil2100> pstolowski: it's on the s390x build
[09:18] <sil2100> Let me re-try
[09:18] <sil2100> (in the PPA)
[09:23] <pstolowski> k
[10:29] <pete-woods> trainguards: hey folks. could I get a packaging ack on silo 80?
[10:29] <pete-woods> the massive --- in the symbols is just an artifact of how we do different symbols for each series
[10:30] <pete-woods> (it always shows the foo.sybols file as being removed)
[10:30] <pete-woods> we have foo.symbols.vivid, foo.symbols.xenial, etc for the actual symbols files
=== _salem is now known as salem_
[12:26] <robru> pete-woods: you need a core dev
[12:44] <Saviq> trainguards, https://requests.ci-train.ubuntu.com/#/silo/036#audit_log seems to be stuck since yesterday, any known issues?
[12:45]  * Saviq might try building diffs
[12:48] <robru> Saviq: status job stuck, killed it
[12:48] <Saviq> robru, ack
[12:49] <Saviq> robru, you not on holidays any more?
[12:49] <robru> Saviq: should fix itself within 15 min
[12:49] <Saviq> ack
[12:49] <robru> Saviq: been walking around all day, I come to work to relax 😉
[12:50] <Saviq> :D
[12:53] <Saviq> mzanetti, ltinkl ↑↑ should be fine in 15 mins or so
[12:54] <mzanetti> yeah... I was watching the build last night... wasn't really worried
[13:42] <kenvandine> rvr, i just checked, the cellular data switch silo 80 had already been approved by QA but settings needed a rebuild because of silo 41 landing
[13:42] <kenvandine> rvr, they don't touch any of the same panels, so shouldn't be an issue
[13:43] <rvr> kenvandine: Ok
[13:43] <rvr> kenvandine: Do you want me to verify?
[13:43] <kenvandine> it's building now
[13:43] <kenvandine> but i guess someone will need to look at it once it's built
[13:43] <kenvandine> but there's no overlap at all
[13:47] <rvr> kenvandine: Better to have a quick look
[13:48] <kenvandine> rvr, yeah... i'll give you a shout when it's rebuilt
[13:48] <rvr> Cool
[13:55] <Saviq> robru, status job stuck again? https://ci-train.ubuntu.com/job/ubuntu-landing-036-0-status/18352/console
[13:57] <Saviq> ah no there it goes
[13:57] <robru> Saviq: not necessarily: https://ci-train.ubuntu.com/job/ubuntu-landing-036-0-status/buildTimeTrend the run time has not exceeded the average
[13:57] <robru> Saviq: if it goes past 15-16 minutes you can kill it
[13:57] <Saviq> robru, yeah sry
[13:57] <Saviq> robru, it's done now
[13:58] <robru> Saviq: yeah, speeding that up is my top priority when I get back on monday. also the new bileto magic has an auto-kill thing that terminates it after an hour so it'll never get stuck for 20 hours ever again ;-)
[13:59] <Saviq> not like jenkins couldn't do it ;P
[14:08] <robru> Saviq: oh you wanna be stuck with jenkins forever huh?
[14:08] <Saviq> robru, I don't hate it is all
[14:09] <robru> Saviq: oooooooh I hates it
[14:09] <Saviq> yeah I've noticed ;)
[14:09] <Saviq> it is, ultimately, a glorified cron, but it does some nice things once you configure it right
[14:10] <robru> Saviq: bileto uses the real cron, accept no substitues
[14:16] <pstolowski> jibel, hello, any chance to include this bugfix https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595421 in ota-12 if it's QA-ready this evening?
[14:16] <ubot5> Launchpad bug 1595421 in unity-scopes-shell (Ubuntu) "Location trusted prompt for Scopes shown immediately after the wizard" [High,In progress]
[14:20] <jibel> pstolowski, sure
[14:21] <pstolowski> jibel, cool, thanks!
[14:39] <jibel> slangasek, hi, can you revert what landed in this silo https://requests.ci-train.ubuntu.com/#/ticket/1199 ? it causes bug 1595933
[14:39] <ubot5> bug 1595933 in Canonical System Image "devices don't boot on first boot after upgrade or fresh flash" [Critical,Confirmed] https://launchpad.net/bugs/1595933
=== chihchun is now known as chihchun_afk
[14:48] <kenvandine> rvr, silo 80 is built, please give it a quick look
[14:49] <rvr> kenvandine: Ack
[14:56] <Saviq> jibel, can't reproduce the boot lock on turbo whatever I do, but I've had fingerprints registered already and working, so that might have an impact
[14:56]  * Saviq bootstraps frieza
[15:07] <kenvandine> rvr, silo 80 autopkgtest failed, it was unity8 tests had a timeout
[15:07] <kenvandine> rvr, none of that changed in this silo, so shouldn't effect this
[15:07] <kenvandine> affect
[15:08] <rvr> Second unity8 timeout failure I see this week
[15:08] <rvr> Someone should take a look and fix that
[15:10] <rvr> Shit, I don't have a tiny SIM for turbo, I have to flash another device
[15:18] <Saviq> jibel, tvoss, I got frieza stuck after wipe + ubuntu-touch/rc-proposed/ubuntu@9 + OTA to 10
[15:18] <Saviq> what do we wanna get out of it?
[15:20] <tvoss> Saviq, ideally lastboot
[15:22] <jibel> tvoss, I've also a crash of system-settings but unlikely what causes the hang
[15:50] <rvr> kenvandine: Silo 80 looks good
[15:50] <rvr> kenvandine: Checked in current build number: 366 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en
[15:51] <kenvandine> rvr, great!
[15:51] <kenvandine> rvr, give it another signoff and i'll publish it
[15:52] <kenvandine> and check off another ota12 landing :)
[16:08] <slangasek> jibel: can I revert> if it's landed in the archive, the only way to revert is with a new upload of the affected packages; is that what you're asking for?
[16:33] <jibel> slangasek, actually we'll move forward and fix the issue instead of reverting, there is a infinite loop in an upstart job.
[16:33] <slangasek> ok
[16:33] <slangasek> jibel: I'm glad, I don't have an easy revert button for a triple landing silo
[16:33] <slangasek> so a revert would unfortunately have involved a fair amount of work
[16:52] <kenvandine> rvr, can you signoff on silo 80?
[16:52] <rvr> kenvandine: Yes, sir
[16:52] <rvr> Dobe
[16:52] <rvr> Done
[16:54] <kenvandine> rvr, thx
[17:11] <Saviq> jibel, tvoss, I tried to modify biometryd.conf in a few ways (making it manual, for example) and nothing seemed to help, removed it now completely and it's getting stuck still
[17:11]  * Saviq flashes 9 back and will upgrade packages one by one
[17:12] <tvoss> Saviq, ack and thx
[18:02] <Saviq> jibel, tvoss, installing just biometryd-bin I can't get it to get stuck on factory reset
[18:05] <robru> slangasek: can you file a bug against lp:bileto to resurrect the revert code? jenkins *has* an easy revert button but it has completely bit-rotted into oblivion. should be easy to hook it back up in the new bileto world.
[18:18] <Saviq> jibel, I can't get it to get stuck after wiping :/
[18:18] <Saviq> after a full dist-upgrade
[18:54] <camako> Doing triple landing in silo 41, I'm getting a "Destination version 0.23.1+16.10.20160610.1-0ubuntu1 is missing from changelog" error for yakkety. What do I need to have in the changelog for it to work for all three targets?
[18:55] <camako> ^ robru, any idea?
[18:56] <robru> camako: as the error says, you need to have the entry for 0.23.1+16.10.20160610.1-0ubuntu1, which is probably from another silo considering that it's -0ubuntu1
[18:57] <camako> robru, then wouldn't xenial and vivid complain? or is bileto smart enough to overwrite the versions for those?
[18:57] <robru> camako: "smart enough", bileto just clobbers the changelogs for everything but the first one in the list of series.
[18:58] <robru> camako: your silo is missing this: https://launchpad.net/ubuntu/+source/mir/0.23.1+16.10.20160610.1-0ubuntu1
[19:00] <camako> ok
[19:00] <robru> camako: which was aparently copied from silo 43, but silo 43 no longer contains mir, so that would be from some previous landing
[19:01] <camako> robru, it's just the version in the changelog that 's wrong... It was labeled with vivid's label not yakkety
[19:03] <robru> camako: your problem could be that you're targetting lp:mir/0.23, trio silos should generally be targetting trunk unless you know what you're doing.
[19:03] <robru> camako: like, looking at the commits at lp:mir/0.23, train has never released to there before, so not super surprising that it's contents are goofy
[19:05] <camako> robru, oh you're right. That's wrong
[19:05] <robru> camako: I recommend dropping that MP and making a new MP targetting lp:mir/ubuntu, which seems to be the "trunk" you're using (it has the correct yakkety changelog)
[19:05] <camako> yes
[19:05] <camako> thanks
[19:06] <robru> camako: strangely lp:mir hasn't seen a commit since 2013, I recommend deleting that and renaming lp:mir/ubuntu to just lp:mir
[19:06] <robru> that would bring you into line with literally every other project
[19:06] <camako> robru, lp:mir is our dev trunk... lp:mir/ubuntu is our distro dest
[19:08] <robru> camako: apologies, I glanced at http://bazaar.launchpad.net/~mir-team/mir/trunk/changes and assumed it was lp:mir
[19:08] <robru> which it isn't
[19:09] <robru> camako: anyway target lp:mir/ubuntu in the MP and rebuild and you'll be fne
[19:09] <camako> robru, ack... thanks again
[19:09] <robru> camako: you're welcome!
[19:27] <boiko> alesage: hi, just FYI, silos 42 and 29 (which are targetted to land in this OTA) are marked as ready, do you need us to do anything else, or is it just a matter of waiting now?
[19:28] <alesage> bioko seeing these now, will have a look at thx for the info
[19:28] <alesage> boiko, ^^
[19:29] <boiko> alesage: thanks!
[22:50] <ToyKeeper> boiko, tiagosh: Silo 42 (messaging-app) failed because it broke the ability to open address-book while sending a message.
[22:52] <ToyKeeper> Not sure why though, since all the changes looked unrelated to that.
[22:59] <boiko> ToyKeeper: ugh, maybe it is something already on trunk? I haven't seen the latest landings in there, let me give a quick test
[23:00] <ToyKeeper> boiko: I tried krillin rc-proposed 365 with and without the silo.
[23:00] <ToyKeeper> The silo install only changed one package, messaging-app.
[23:01] <ToyKeeper> ... and the MPs looked pretty innocent.
[23:01] <ToyKeeper> boiko: So, you're probably right.  Changes inherited unintentionally?
[23:01] <boiko> ToyKeeper: so, without the silo it works?
[23:02] <ToyKeeper> Yes, it works without the silo.
[23:03] <boiko> ToyKeeper: trying here, let me see
[23:04] <ToyKeeper> I had to go back one image since the latest ones fail to boot.  Otherwise, everything is current.
[23:05] <boiko> ToyKeeper: I have image 366 on my krillin, booting fine
[23:06] <boiko> ToyKeeper: running device-upgrade to make sure I have latest from silo
[23:07] <ToyKeeper> Yeah, I ran into this on today's images, only somehow worse: https://launchpad.net/bugs/1595933
[23:07] <ubot5> Launchpad bug 1595933 in biometryd (Ubuntu) "devices don't boot on first boot after upgrade or fresh flash" [Critical,In progress]
[23:09] <boiko> ToyKeeper: oups, seems I am in the group of lucky ones who were not affected
[23:10] <boiko> ToyKeeper: so you open the bottom edge, press the contact button and nothing happens?
[23:11] <boiko> ToyKeeper: here on krilling @ rc-proposed 366 it works for me
[23:12] <ToyKeeper> I start a new message via bottom edge, press the contact button, and nothing happens.
[23:12] <boiko> ToyKeeper: could you please send me the log? but I think the problem you are seeing doesn't exist on image 366 (as there was a landing of both messaging-app and address-book-app in there)
[23:12] <boiko> ToyKeeper: would you mind pasting the logs of messaging-app somewhere for me to confirm?
[23:13] <ToyKeeper> Maybe I can get 366 to boot, and test again.
[23:13] <boiko> ToyKeeper: also, you might want to install qtdeclarative5-ubuntu-contacts0.1 and qtdeclarative5-ubuntu-addressbook0.1 at version 0.2+15.04.20160621.3-0ubuntu1
[23:13] <ToyKeeper> If it depends on things which landed today, then it shouldn't work on an older version.  :)
[23:14] <boiko> ToyKeeper: yep, renatu can probably confirm, but I bet his changes to address-book-app and messaging-app are related so you need both at latest version
[23:14] <boiko> ToyKeeper: if not booting, try just to upgrade the address-book-app related packages to the latest available, should fix the problem
[23:14] <boiko> ToyKeeper: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/366.commitlog
[23:15] <ToyKeeper> Yes, it'll just take a bit to reflash and get it working and then re-test.
[23:17] <boiko> trainguards: can someone please review the packaging changes on silo 29?
[23:17] <boiko> ToyKeeper: great! thanks!
=== boiko_ is now known as boiko