=== chihchun_afk is now known as chihchun [07:52] trainguards: Can I get a silo for row 77 (Mir 0.11 release) [08:07] racarr: assigned, even though it conflicts with silo 8 [08:07] so just take care of the landing order within your team [08:08] Mirv: Thanks :) I've got Saviq in the same room so we will work it out. [08:18] ci-help: Mir autolanding seems to be down...anyone have any info? [08:18] cihelp: ^ [08:22] trainguards, reconfigure of vivid silo 21 please? [08:24] racarr, do you have an MP that's not merging that I can use to debug? [08:27] fginther: Sorry I don't understand [08:27] just any MP? But one thats not yet ready to land? [08:27] We are trying ot land https://code.launchpad.net/~alan-griffiths/mir/MVC-refactor-msh-Shell-hierarchy/+merge/248030 but it was TAed all night [08:27] and nothing happened [08:27] racarr, that's exactly what I need to look at, thanks [08:30] fginther: :) Thank you [08:30] Ahhh aha sorry I understand your original sentence now [08:30] <--jet lag brain [08:30] :) [08:36] racarr, I'm confused by the target branch for this MP. Jenkins is watching MPs against lp:mir, but this MP is against lp:~mir-team/mir/development-branch [08:41] racarr, was lp:mir re-targeted recently? It's now an alias for lp:~mir-team/mir/0.11 [08:44] Mirv, can I have a reconfigure of vivid silo 21 please? [08:45] fginther: Ah...it was supposed to be targeted at the 0.12 series e.g. devel branch [08:45] fginther: Fixed it now...(e.g. lp:mir should be pointing at devel again) [08:51] Saviq: done [08:52] racarr, thanks [08:53] sil2100, thanks [09:00] fginther: Do you think that was the problem? [09:10] sil2100, when I reconfigure a silo from the spreadsheet, I'm left at a white page since the upgrade, fortunately the job still runs, but I can't see it, have to go to the job page manually [09:12] racarr: http://s-jenkins.ubuntu-ci:8080/job/mir-vivid-amd64-autolanding/272/consoleFull running for https://code.launchpad.net/~mir-team/mir/add-input-method-surface-spec/+merge/248063 so yes, that was the issue [09:13] Saviq: yeah, we know about it... it seems to be some issue with the new jenkins, robru was looking into it but not sure he'll be able to fix that soon [09:15] racarr: https://code.launchpad.net/~alan-griffiths/mir/MVC-refactor-msh-Shell-hierarchy/+merge/248030 is already scheduled to run next [09:15] sil2100, kk [09:24] sil2100: I don't find (probably just failing to search) info on where are all the vivid autopilot test results gone for the last two weeks? [09:25] Mirv: the issue is in the terminal app... they still didn't fix/change the trunks respectively [09:25] Mirv: CI cannot find the right version in bzr right now [09:26] popey: hey! Do you have any information regarding the terminal-app? Which one in the end is the default one? And why is there 'latest' in the revision field in the desktop file? [09:26] sil2100: oh, right, I fixed that on my setup by patching the line 207 in /usr/bin/phablet-click-test-setup to just use bzr without "-r latest" (shouldn't default be latest anyway..) [09:26] Just love those unhandled exceptions [09:27] sil2100: where are you seeing "latest"? [09:28] popey: it's as we talked last week, it's in the current terminal-app in store, in its manifest file vcs-bzr-revno [09:29] sil2100: popey: if the line 207 http://bazaar.launchpad.net/~phablet-team/phablet-tools/trunk/view/head:/phablet-click-test-setup is executed ("-r latest") in practice it yields ""Requested revision: 'latest' does not exist in branch: bzr+ssh://bazaar.launchpad.net/+branch/ubuntu-terminal-app/"" [09:29] Where the BZR_REVNO is set to 'latest' if not set to anything, if it's not defined [09:29] works for others, and works for terminal too if simply using the default (which should be latest, shouldn't it) [09:30] so this is a bug in what? the cmake? [09:31] popey: not sure exactly, but I know the CMake file sets BZR_REVNO to "latest" if not set otherwise, and it is not - and "latest" is not really a valid bzr revision [09:31] right, i see [09:31] the one in the store comes from lp:ubuntu-terminal-app/reboot [09:31] hmmm, hangout issues again [09:31] we need jenkins to point at reboot, and for us to switch default to reboot in lp [09:31] then that should fix it, right? [09:31] popey: but I think the vivid images still have the non-reboot installed by default [09:32] why!? [09:32] the reboot is the default in store [09:32] 0.7.41 [09:32] (I need someone with a bit of time to fix the jenkins side) [09:34] trainguards: can silo 28 be published, please? [09:36] oSoMoN: sure [09:36] thanks Mirv! you’re back among us? [09:37] oSoMoN: merges unapproved [09:37] oSoMoN: yes! :) [09:37] darn, I’ll approve [09:37] welcome back! [09:37] Mirv, how’s the little one? [09:38] ok, approved now [09:39] oSoMoN: thanks! and fine! [09:39] publish success [09:41] sil2100: let me know if there's anything I can do, but I think it's out of my control, sorry :( [09:42] cihelp should I give up hope on http://q-jenkins.ubuntu-ci:8080/job/qt-release-gatekeeper/ ? I pinged in December or so but didn't get an answer. I'm running tests locally of course, that job just was nice in the earlier big landings when it worked. [09:43] popey: poking around about that, I'll coordinate with you the switch to reboot then :) [09:43] Mirv: looking [09:45] ok [09:50] vila: thanks! warning it's probably somewhat complex, and I don't know how it used to work :) regarding the job itself it tries to do the correct thing (update everything from a manually specified PPA), but I don't know how the "execute all tests" worked successfully [09:51] Mirv: apparently the job requires a phone in http://q-jenkins.ubuntu-ci:8080/label/gatekeeper-mako/? and none of them are online [09:51] vila: yeah, that's the first problem [09:51] Mirv: so, unless I'm mistaken, it onl... ha, first ;-) [09:52] vila: well, at least I could tinker more and try to get some results out if those were online, but I remember having some error even when they were online earlier at some point. and I think the error was of the sort that the device got lost at that point :) but it might have been a generic problem at that point. [09:52] I just don't know how much of that test execution in that job is shared with eg the generic jobs that are kept up-to-date, and how much is something that gets outdated fast [09:53] if it shares the logic of executing autopilot tests with everything else, it could "just work" given devices [09:53] Mirv: right, so; I've added mako-14 and the job failed, let see why [09:53] err, no it's still running >-/ [09:54] http://q-jenkins.ubuntu-ci:8080/job/qt-release-gatekeeper/label=gatekeeper-mako/39/console [09:58] popey: which version of terminal is the reboot one? [10:01] sil2100: 0.7 is reboot, 0.6 is previous === chihchun is now known as chihchun_afk [10:26] popey: ok, what we need to do 2 things now [10:27] popey: first, we need this reviewed (or a similar fix included): https://code.launchpad.net/~sil2100/ubuntu-terminal-app/fix_cmake_revno/+merge/248352 [10:27] popey: second, we need to retarget lp:ubuntu-terminal-app to the /reboot branch [10:30] sil2100: approved [10:30] trainguards: can I have a silo for line 87, please? [10:30] oSoMoN: sure [10:30] popey: you think such a change makes sense? I saw it in clock-app and there it worked like a charm as well [10:30] yes [10:31] sil2100: do you know how we can force jenkins to run on that now? https://code.launchpad.net/~sil2100/ubuntu-terminal-app/fix_cmake_revno/+merge/248352 [10:31] (given you're not in the team. [10:31] Once this is merged in we would need to build a new click of it and then retarget [10:31] hmm [10:32] yes [10:32] jenkins will build the click for us [10:32] once its triggered [10:32] popey: I think it's time to poke cihelp in this case ;p [10:32] ok [10:32] Since sadly I have no clue [10:32] cihelp: please can someone trigger jenkins on https://code.launchpad.net/~sil2100/ubuntu-terminal-app/fix_cmake_revno/+merge/248352 [10:35] sil2100, popey, it was triggered automatically [10:35] it was? [10:35] magic! [10:43] fginther: thanks for the magic :) [10:55] ugh fun, internal compiler error :/ [10:55] sil2100: http://91.189.93.70:8080/job/generic-mediumtests-vivid/948/? - its still pulling the wrong tests [10:57] popey: it's probably because it tries to fetch those from the lp:ubuntu-terminal-app branch instead of /reboot, I think we need to retarget for it to be fixed [10:57] ok, so re-target then re-run yes? [10:59] sil2100: doing that now [10:59] We could try, I just hope it won't break the merge or something ;) [11:02] lets see! [11:06] trainguards i can give up vivid silo 8, it was just a test silo...thanks [11:06] http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=landing-008 [11:06] kgunn: freeing it up then, thanks! [11:08] sil2100: hang on, your merge is against the old one, not the reboot, right? [11:08] sil2100: this failed again. I think we need some help https://code.launchpad.net/~sil2100/ubuntu-terminal-app/fix_cmake_revno/+merge/248352 [11:08] It should be against the reboot [11:09] popey: it was against the reboot, but now that the target switched then it's saying it's against trunk [11:09] right, but the tests are still failing. [11:09] Ok, looking [11:11] huh, those look like some normal failures due like broken tests or something [11:12] Actually [11:12] popey: not sure why but it looks to me it still tries to run the old tests - does the new reboot terminal-app have new autopilot tests? [11:12] popey: ok, I see the problem... [11:13] popey: the reboot terminal app doesn't have new tests ;/ [11:13] ah [11:13] popey: all its tests are for the old terminal app, so no wonder they all fail as they expect the old app... we need someone writing tests for this application [11:13] right [11:13] will get on that. [11:14] Anyway, let's get this branch hand-merged then and release a new click [11:14] This would at least unblock all other testing [11:14] We will have 100% failrues in the terminal app, but at least we'll have other test results for vivid [11:14] I'll be honest when we uploaded and switched to reboot I had no idea it was still included in any images [11:15] ;) Yeah, it seems the decision was made that it should stay in the devel and devel-proposed images [11:15] As it's handy for developers === chihchun_afk is now known as chihchun [11:37] sil2100, ogra_: fyi the si importer is currently disabled in cron because I'm making the channel changes requested by john-mcaleely / victorp [11:38] sil2100, ogra_: so any image builds will have a short delay in being visible, and please don't manually run import-images without checking with me :) [11:39] slangasek, thanks for the info ! [11:39] slangasek: ok, thanks ;) [11:42] sil2100: is there anything you need from me to get that through? [11:58] slangasek: BTW I reverted your archive-reports changes from yesterday after I confirmed that snakefruit could rsync from bilimbi::ubuntu-rtm-dists/ again [11:58] That was probably obvious, but [11:59] popey: would you mind if I merge it in manually? === MacSlow is now known as MacSlow|lunch [12:00] cjwatson: ah, did you? Thanks, I thought I'd done it myself [12:00] sil2100: sure [12:01] ogra_, sil2100: importer back online, it was a rather quick change [12:16] slangasek: \o/ [12:16] hmm [12:16] popey: can you build the terminal-app click? [12:16] i wonder why my phone thinks there is an update ... [12:17] we didnt build any images last night, did we ? [12:17] ogra_: rtm? There was a new one as the cronjob is enabled [12:17] (i had the notification when i got up this morning) [12:17] 225 [12:17] sil2100, oh, i wonder who enabled that and forgot about it then :P [12:17] hah ;) [12:17] sil2100: which one, old or reboot? :) [12:18] imgbot, status rtm 225 [12:18] Error: There does not seem to be any build with the number rtm [12:18] popey: the reboot one ;p The one that's now in lp:ubuntu-terminal-app [12:18] pfft [12:18] imgbot, status 225 [12:18] Status: succeeded, Started: 2015-02-03 03:02:15 UTC, Finished: 2015-02-03 03:52:23 UTC [12:18] Build URL: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch/+build/19052 [12:18] Changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/225.changes [12:18] sil2100: it should build in jenkins automatically. [12:18] vila: so, over at the gatekeeper job you can now see the real problem - it flashes alright, reboots and then loses the device. so currently the job is really good at "killing devices"... that would be the real problem to fix. [12:19] sil2100: http://s-jenkins.ubuntu-ci:8080/job/terminal-app-click/ [12:19] popey: oh, ok, would be happy if it gets published to the store somehow ;) [12:19] 27393 [12:19] er, ignore that [12:19] yeah, I'll do it now. [12:21] popey: thanks! We'll try to get an image built afterwards to see if things are looking any better [12:22] ok [12:22] will ping you when uploaded [12:22] sil2100: http://s-jenkins.ubuntu-ci:8080/job/terminal-app-click/174/console failed :( [12:22] sil2100: popey: so is the trunk vs reboot still a problem? I mean, phablet-click-test-setup --distribution=ubuntu --series=vivid --click com.ubuntu.terminal still errors out similarly [12:23] I see it talks about lp:ubuntu-terminal-app while the fix is in /reboot [12:23] Mirv: the fix is in lp:ubuntu-terminal-app now [12:23] Mirv: as we did the switch, lp:ubuntu-terminal-app is the /reboot now [12:23] sil2100: aah [12:24] hmm, why does it give it then still [12:24] Mirv: and it will fail until the new version of terminal is in the images [12:24] Mirv: since the current one has still the invalid revno in the manifest [12:24] but it fails to even build a click now [12:24] aha [12:24] popey: oh? [12:24] Where does it fail? [12:24] http://s-jenkins.ubuntu-ci:8080/job/terminal-app-click/174/console [12:25] popey: eeek, looks like the switch broke something, it's trying to do a bzr update from the old tree or something? [12:25] Mirv: ^ do you know anything about the click generation process? [12:26] i suspect there's a script in jenkins which pulls from /trunk? [12:26] * ogra_ wonders why location doesnt work at all anymore here [12:36] sil2100: not much besides "if I click here a .click is generated" [12:36] click for .click! [12:39] sil2100: Mirv the good news... http://s-jenkins.ubuntu-ci:8080/job/terminal-app-click-reboot/ [12:39] there's a separate job for the reboot branch [12:40] * popey clicks "rebuild" to see if 46 is okay [12:40] uh [12:40] Ok [12:41] nice [12:41] \o/ [12:53] ok, 46 built [12:54] nice² [12:54] "vcs-bzr-revno": "46" [12:54] looks good === alan_g is now known as alan_g|lunch [12:55] Mirv: could you please upload http://s-jenkins.ubuntu-ci:8080/job/terminal-app-click-reboot/lastSuccessfulBuild/artifact/out/com.ubuntu.terminal_0.7.46_armhf.click to the store? [12:56] popey: done [12:57] thanks === chihchun_ is now known as chihchun [12:57] approved [13:00] trainguards: can silo 28 be published, please? [13:02] note: silo 28 will require a core-dev ack, but the packaging change is trivial [13:04] oSoMoN: will publish in a moment (preparing lunch now) [13:05] thanks! [13:08] I can do that too [13:08] oSoMoN: you like breaking my Qt 5.4 PPA, do you? :) (just joking, I just need a kick a rebuild after each webbrowser landing) [13:10] ogra_: if around right now please ack bumping of oxide dependency pkging change https://ci-train.ubuntu.com/job/ubuntu-landing-028-2-publish/lastSuccessfulBuild/artifact/packaging_changes_webbrowser-app_0.23+15.04.20150203-0ubuntu1.diff [13:12] Mirv, sorry about that… [13:12] Mirv, I can’t wait for Qt 5.4 to land btw, there’s a new QML API that will greatly benefit webbrowser-app [13:12] oSoMoN: that's really trivial, but that would be the one benefit of getting rid of the 5 packages that use the private header from transition, so they wouldn't need constant rebuilds [13:13] oSoMoN: ooh, sounds good! there was great progress also while I was away, so I hope we can hit the feature freeze in two weeks [13:13] Mirv, yeah, that would be much easier for everyone indeed [13:13] Mirv, that’d be awesome [13:15] mvo_, ogra_: would one of you guys have a minute to ack the packaging changes in https://ci-train.ubuntu.com/job/ubuntu-landing-028-2-publish/lastSuccessfulBuild/artifact/packaging_changes_webbrowser-app_0.23+15.04.20150203-0ubuntu1.diff ? [13:16] oSoMoN: sure, do you have a link to button I need to press? diff looks fine [13:16] oSoMoN: if not I will find it myself :) [13:16] sil2100, we seem to have a problem... https://launchpadlibrarian.net/196457195/buildlog_ubuntu-vivid-armhf.unity8_8.02%2B15.04.20150203.1-0ubuntu1_FAILEDTOBUILD.txt.gz [13:17] "internal compiler error: in symtab_remove_unreachable_nodes, at ipa.c:547" [13:17] only armhf [13:17] but reproducible [13:17] Mirv: so, yeah, it breaks the phone :-/ Well, it hangs even, we did talk with plars about protecting that adb wait-for-device call with a timeout so your job should fail and the instrumented phones can be recovered [13:18] difficult to repro locally, doesn't happen for x-building, phone just rebooted when encountered this error it seemd [13:20] still trying [13:21] not really sure how to proceed :/ [13:22] mvo_, just an IRC "ACK" is enough :) [13:22] mvo_, thanks, the MR that needs approving is https://code.launchpad.net/~osomon/webbrowser-app/save-restore-state/+merge/242678 [13:23] oSoMoN, looks all fine to me [13:23] thanks! [13:24] Mirv, the packaging changes in silo 28 have been acked by not one but two core-devs :) [13:25] ogra_: unping the pkging change ack [13:25] oSoMoN: ok, thanks! [13:25] * Mirv thinks a real "unping" removing previous highlight would be a neat feature [13:26] lol [13:28] trainguards: should I just retry the build on vivid silo 25? or do you want to take a look on what caused that error? [13:29] boiko: it would look like a temporary problem in archive info, so just try again [13:30] (hash sum mismatch) [13:30] Mirv: thanks === MacSlow|lunch is now known as MacSlow === alan_g|lunch is now known as alan_g === bregma_ is now known as bregma [14:04] Saviq: the error is still reproducible? Were you able to repro it on the phone? [14:06] sil2100, I got it once and the phone rebooting, still trying - and yeah PPA behavior is consistent, I've tried to remove the branch I suspect triggers this (even though it's not touching those files at all) from the silo, building now [14:06] sil2100, can't repro more on the phone :/ [14:07] Saviq: ok, give me a sign if it was caused by any of your changes, since otherwise it might be some change in the toolchain or something [14:07] sil2100, whether any of my changes trigger it doesn't really matter, does it, is still a bug in gcc... [14:12] popey: were you able to release the new terminal? [14:13] dobey, Hi! [14:14] sil2100: I uploaded it at least, not sure if accepted. I tested some 15 mins ago that phablet-click-test-setup still fails at the moment. [14:14] Mirv: with the new click? [14:14] sil2100: Mirv i accepted it moments later [14:14] 12:56 < Mirv> popey: done [14:14] 12:57 < popey> approved [14:15] Mirv: could you do a `click list --user=phablet --manifest` on your phone where you say its failing and find the terminal-app there? [14:15] vcs-bzr-revno: should be correct [14:16] its certainly updated in the store [14:16] http://people.canonical.com/~alan/screenshots/device-2015-02-03-141506.png [14:18] sil2100: http://paste.ubuntu.com/10035505/ line 1037 [14:18] om26er: hi [14:19] dobey, how do I verify fixes for silo 19 ? [14:19] popey: thanks! All looks ok from this side [14:19] for convenience bug 1282392 and bug 1376445 [14:19] bug 1282392 in Canonical System Image "nothing listens to keyringError signal" [High,In progress] https://launchpad.net/bugs/1282392 [14:19] bug 1376445 in Canonical System Image "Addition of signon-apparmor-extension causes token lookup problems" [High,In progress] https://launchpad.net/bugs/1376445 [14:19] Mirv: are you sure it's failing for the same reason as before with the latest terminal-app? [14:20] om26er: it's on hold until mardy's fix lands, i think. dbarth, mardy ^^ did we get the required fixes for that in on the online-accounts/apparmor side? [14:21] dobey: we are building them in a silo [14:21] cihelp, is s-jenkins not working? can't seem to access it? [14:21] mardy: which one? [14:21] sil2100: it looked like it said latest. but note I can't arbitrarily run it eg. now again since I'm heavily running AP tests. if you have a device, just run th ecommand [14:22] phablet-click-test-setup --distribution=ubuntu --series=vivid --click com.ubuntu.terminal [14:22] Saviq: check your vpn ? s-jenkins is up [14:22] vila, yeah, am on vpn, timing out here :/ [14:23] mardy, so that means the silo is blocked right now ? [14:23] vila, ah, we need to lower the MTU here in Brussels... [14:23] mardy, dbarth: were we going to add those to the existing silo 19, or should we just land silo 19 as it doesn't break things without the apparmor extension, and then ensure the new silo doesn't break with that already in? [14:24] Saviq: MTU... I think that's the most wtf bug I can think of... [14:24] Mirv: upgrading [14:24] dobey, om26er: it's silo 3 [14:24] vila, might be some network setup here at the sprint [14:25] mardy, I'm confused, aren't we talking about silo19 for ubuntuone-credentials ? [14:25] Saviq: yeah, can be any network gear on your path. The worst part is that I've seen cases where *some* requests succeed [14:25] mardy: it failed to build [14:25] mardy, my initial query was about 19 [14:25] dobey: yep :-( [14:26] om26er: yes. we wanted to land it before the rtm image, but there were some additional issues with the signon-apparmor-extension which prevented that. mardy has a fix in silo 3 that should allow both to finally work together, but it failed to build (and that silo is for vivid, not rtm, so it would still need backported). [14:27] dobey, ok, I'll block 19 then. [14:27] om26er: but the stuff in silo 19 will work just fine without signon-apparmor-extension, so i'm happy to land it now and have it in the image already as a means to block the backport of those fixes landing later === marcusto_ is now known as marcustomlinson [14:27] om26er, dobey: I don't think that silo 19 should be blocked, it could go in regardless of our stuff [14:28] om26er: the only issue is that to test it you need to manually install signon-apparmor-extension [14:28] dobey, mardy hmmm, ok so that brings back to my original question. How do I verify the fix for silo 19 ? [14:28] I can do that, sure. [14:28] om26er: i'm going to update the comment column for that, one second [14:29] mardy: well, installing signon-apparmor-extension will break it, so testing with that will fail. [14:29] mardy: which means it would be blocked until we get your fixes into rtm [14:30] haha! [14:30] dobey: right, it will break it, but we could still verify that things go a little further [14:30] mardy: so either we land it as is, and use it as a means to block the seed change if the new fixes don't fix it, or we block and wait and land them all at the same time [14:31] dobey, I'd prefer the second option [14:31] dobey: I'm all for landing it, maybe we can just verify that it brings no regressions [14:31] mardy: right. install of free packages in the store should work fine, but purchasing won't [14:32] we can verify the lack of regressions. the exact changes already landed in vivid and verified with no regressions there [14:35] dobey, mardy hmm, so I guess we want to land the silo then. So i'd like to know, if the test plan passes, there are no regressions ? or is there anything else I should be looking for as well ? [14:38] om26er: you can run through the test plan and verify there are no regressions. you can then install signon-apparmor-extension, reboot, and verify that installation from the store works correctly (best to test with a u1 account created prior to installing the silo), but purchasing paid apps will fail with signon-apparmor-extension installed with the changes due to the issue that the change in silo 3 should fix once it lands [14:38] mardy: ah, looks like some tests failed and need to be updated for the change perhaps [14:41] Mirv: with the upgraded terminal all works fine [15:04] ricmm: https://code.launchpad.net/~ricmm/platform-api/fix-wrong-test-load/+merge/248228 needs to be approved [15:06] sil2100: ofc [15:06] seb128: could you approve it? [15:08] sil2100, ricmm, done [15:12] seb128: awesome, thanks [15:12] sil2100: publishing then? [15:12] ricmm: yep :) [15:16] sil2100: thx [15:31] om26er: so are you testing for lack of regressions in rtm 19, or are we blocking it on the other landings from mardy? :) [15:34] dobey, I am testing it [15:36] om26er: ok, great. thanks [15:38] dobey, do you know of a for-purchase app in the store that I should search for ? [15:39] om26er: riddling is $2.99, there's also "wallet lightener pro" or you can search for "price:2.99" (price must be lowercase) [15:42] dobey, so I seem to have downloaded a 'for buying' app for free (without a credit card) [15:43] doesn't feel normal [15:43] surely not a regression on the *client* side :) [15:45] om26er: did you already purchase it previously? [15:45] dobey, never did. [15:46] om26er: what app? [15:46] dobey, Riddling [15:46] om26er: did you install it a long time ago when it was free, on the account you're using? [15:47] (riddling used to be free, it's been in the store a very long time) [15:47] dobey, that might have happened, I guess. [15:47] om26er: then you've already "purchased" it. [15:48] om26er: i have the same behavior for riddling on my account [15:48] so that's not new === chihchun is now known as chihchun_afk [16:26] robru, ogra_, jibel, davmor2, popey: as it's Tuesday again, I need to skip the evening meeting [16:27] sil2100: why don't you just change the time of the meeting on a Tuesday ;) [16:27] sil2100: or cancel it [16:28] davmor2: not much I can do with it, maybe cancel it - but sometimes I'm able to skip and then stay for the meeting [16:28] Since no other hour makes sense as I have meetings before and later in the evening most of the participants are no longer working [16:30] sil2100, i wouldnt mind canceling [16:30] i doubt we have much to discuss, do we ? [16:44] trainguards yo can i get a silo for line 91 ? [16:51] sil2100: hey you still on ? === chihchun_afk is now known as chihchun [16:56] did we have a final decision abouot the meeting ? [16:58] kgunn: https://ci-train.ubuntu.com/job/prepare-silo/3967/console uh there's a problem with your merges. never seen that one before. the only thing I can think of is that your mp list should be single-spaced... [16:59] sil2100, something got fooked up, that's unity8 trunk in a silo: https://launchpadlibrarian.net/196485248/buildlog_ubuntu-vivid-armhf.unity8_8.02%2B15.04.20150203.7-0ubuntu1_FAILEDTOBUILD.txt.gz [16:59] sil2100, same failure [17:00] that includes the just-released gcc [17:01] robru: ack, ok, give it a go now [17:01] (and thank you) [17:02] kgunn: https://ci-train.ubuntu.com/job/prepare-silo/3968/console oh god it's the same error [17:03] ogra_: sil2100: the new/correct terminal-app should be available now for the vivid images on krillin, but it looks like those are not being pulled in still since the job doesn't get past phablet-click-test-setup. I think that's something that has to be done on the image creation side right? [17:04] kgunn: gimme a minute to dig [17:04] thanks man [17:04] sil2100, bug #1417664 [17:04] bug 1417664 in gcc-4.9 (Ubuntu) "Unity8 build causes internal compiler error on armhf" [Undecided,New] https://launchpad.net/bugs/1417664 [17:04] seb128, in case you're wondering what's happening with your qtmir landing ↑ :( [17:04] Saviq, shrug [17:05] Saviq, that changeset was in its own silo and ready to land a week ago :/ [17:05] seb128, I know, I'll land qtmir separately first thing tomorrow if nothing else comes around [17:05] No landing meeting today? [17:05] Saviq, thanks [17:08] kgunn: https://code.launchpad.net/~mzanetti/ubuntu/vivid/qtsystems-opensource-src/inputinfo/+merge/248397 yeah this is the one causing the problem. looks like the merge target is invalid -- you're trying to merge into a udd branch, those are a bit special. can you replace that mp with a new mp that targets the proper project source branch? [17:08] mzanetti: ^ [17:09] kgunn: note I don't actually know what the correct branch would be. if there isn't one, we'd have to do a source upload instead of an MP. [17:10] Mirv: ^ is there an lp project for qtsystems-opensource-src? [17:10] robru: kgunn: this should be better, I hope: https://code.launchpad.net/~mzanetti/ubuntu/vivid/qtsystems-opensource-src/inputinfo/+merge/248418 [17:11] mzanetti: nope, train can't handle merge targets that start with 'lp:ubuntu/' I've just learned. [17:11] ok...updated in the sheet [17:11] mmm or not ok then... [17:12] robru: ok, removing those...and mzanetti will give you the packages to upload [17:12] kgunn: yeah I guess you're going to need to just put 'qtsystems-opensource-src' as an additional source package and then I can upload it manually in a bit [17:12] robru: can you upload a source package from that branch? lp:~mzanetti/ubuntu/vivid/qtsystems-opensource-src/inputinfo [17:13] ack [17:13] mzanetti: yeah I can do that [17:13] thanks [17:15] mzanetti: what should the version be? 5.0~git20130712-0ubuntu8? [17:19] kgunn: mzanetti ok you got silo 0 and I uploaded the source package. [17:20] kgunn: mzanetti: I'm expecting a phone call in 10 minutes so if you need anything else let me know now. [17:37] trainguards: can I please get vivid silo 25 reconfigured? I have just added a new component there [17:47] trainguards: also, could you please get a silo assigned for row 88? [17:47] boiko: sorry otp, back soon [17:48] robru: no problems, thanks [18:16] boiko: ok sorry about that. [18:17] boiko: having a bit of trouble with the spreadsheet... [18:23] boiko: https://code.launchpad.net/~renatofilho/ubuntu/vivid/syncevolution/default-syncInterval/+merge/247768 oh this MP has an invalid merge target. train can't handle lp:ubuntu/ merges, it has to be a "real" lp project. [18:24] boiko: either retarget the merge at some real lp project (lp:syncevolution if that exists), if not it has to be a source upload. [18:25] boiko: reconfigured silo 25 for you, mind the conflict with silo 13 [18:41] robru: thanks, that's fine (the conflict), the fix is not urgent so if you are low on silos that one can wait [18:41] robru: row 88 would be good to get a silo for, bfiller and renato want to test it soon [18:45] boiko: oh, did you miss my message above? I can't assign 88 because the MP has an invalid target. [18:59] robru: oups, sorry, I missed that one, ok, let me see with bfiller and renato how they want to deal with it [19:01] boiko: turns out lp:syncevolution doesn't exist (unless it's hiding under a different name somewhere, I dunno), so as far as I can see there's really only one option, we have to do it as a source upload. [19:02] robru: and how can I do that? I just get a silo assigned and push the source directly to the ppa? [19:02] boiko: pretty much, except you wouldn't have permission, I'd have to do it. [19:02] robru: ah ok, so I have to upload the source somewhere for you to get it? [19:02] boiko: so on row 88, please delete the MP, and in column G just put 'syncevolution' [19:03] boiko: well I can build the source from the MP myself ;-) [19:04]