=== chihchun is now known as chihchun_afk [06:18] robru: there's a packaging branch https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src but I can take care of updating it [06:20] Mirv: ahhhhhhhhhhhhhh, didn't know that, thanks & sorry [06:22] np [06:55] * Mirv finds the related upstream thing https://codereview.qt-project.org/#/c/101049/ [07:52] Mirv: could you reconfigure silo 8 for us? [08:02] Mirv: I have two MRs for the RTM branch, one is prerequisite of the other. Can I land both in the same silo? [08:08] thostr_: sure [08:08] bzoltan: yes [08:09] Mirv: Coooool [08:13] argh [08:13] something wrong with prepare-silo [08:15] indeed [08:16] found a workaround [08:17] so thostr handled, trying bzoltan next [08:17] Mirv: you have my support dude :) [08:18] robru: sil2100: "assign a silo" style of reconfigure fails since it uses "parambuild?" instead of "buildWithParameters?", or at least the former yields 404 and replacing that part reconfigured a silo successfully [08:25] trainguards, you fighting with the spreadsheet / ci-train? /me can't reconfigure, was getting 404 first, now the MPs are not whitespace-separated in the param list? [08:28] cant' reconfigure my silo either [08:30] pstolowski, got a workaround: just copy the list of MPs yourself into the merge_proposals param [08:31] Saviq, getting 404 on reconfigure page [08:31] pstolowski, I was having that before too but now it's working [08:34] Saviq: I was able as described above [08:35] Saviq: pstolowski: but, I do it with the trainguard only prepare-silo one... [08:35] the normal reconfigure failed [08:35] robru: sil2100: so yeah right the normal landers' reconfigure seems also broken, not sure if possible to do some url trickery or not [08:36] Saviq, ah, you pasted them with url.. I think i'll just wait a little bit till it's fixed [08:36] Saviq: ah, now the normal link worked for you? [08:36] Mirv, I didn't get the 404, had to paste the URLs myself though, they were lacking whitespace between the different urls [08:42] Saviq: right [08:42] prepare-silo reconfig seemed to work alright after fixing just that one part of the url [08:43] Mirv, can you actually reconfigure silo 12 for us please, I added qtmir-gles [08:44] Saviq: sure [08:44] Saviq: wow, now my prepare-silo also doesn't 404 anymore [08:45] robru: sil2100: are you sure neither of you is hacking stuff right at the moment? :) the 404 is gone, but whitespaces missing from MERGE_PROPOSALS [08:45] :D [08:45] are you *sure*? ;) [08:46] 30mins ago the url was 404, but fixing to point to buildWithParameters worked and even the whitespaces were there [08:48] Saviq: https://ci-train.ubuntu.com/job/prepare-silo/3983/console not all targetting the same branch? [08:49] Mirv, oh [08:56] Mirv, it should be good now [09:01] Mirv: not doing anything here! ;) [09:03] Saviq: done [09:03] Mirv, thanks [09:03] sil2100: weird fluctuation of behavior [09:27] trainguards hey, not really sure i understand why my reconfig attempt isn't working === chihchun_afk is now known as chihchun [09:28] hmm, looks like the vivid image buolds failed [09:33] uid checker thing [09:33] do you get the emails? [09:34] kgunn: it's because something (tm) is broken that's not you. I'll try it. [09:35] heh, now the prepare-silo 404 is back too [09:35] no, it just randomly changes. when it's broken the url change works. when it works the whitespaces are missing.. [09:35] Laney, yeah, i do ... seems to be all pittis fault :=) [09:36] muhaha [09:38] kgunn: reconfigured [09:38] ta [09:52] sil2100, you might want to move the tag on this one: https://bugs.launchpad.net/dialer-app/+bug/1417886 [09:52] Launchpad bug 1413316 in telepathy-ofono (Ubuntu) "duplicate for #1417886 Dialler shows 'No network' even though SIM is present (vivid)" [Critical,Confirmed] [09:52] Mirv, hey, could you also reconfigure my silo in line #64? [09:52] sil2100, it's a duplicate of an old bug that has way more investigation on it [09:53] Mirv: hey, thanks for trying...but don't think that silo reconfig'd and i just tried and it didn't work again [09:54] @don't think it worked earlier, b/c we added a branch for u-s-c to address something, and it still failed the build in the same way [09:58] kgunn: hmm, it does say it reconfigured https://ci-train.ubuntu.com/job/prepare-silo/3987/console [09:58] bzoltan: don't go touching my vivid 005 silo :) [10:00] k [10:00] thanks! [10:00] Mirv: ohh... sorry [10:26] ogra_: if you could kick a new vivid image once you have the builds fixed then it would be awesome [10:26] sil2100, indeed [10:30] ogra_: btw. are you using 14.09-proposed on your krillin? [10:30] havent upgraded today yet ... but yes [10:31] popey: do you have the latest 14.09-proposed on any of your devices? :) [10:32] think so, yes [10:32] channel: ubuntu-touch/ubuntu-rtm/14.09-proposed [10:32] current build number: 226 [10:32] yes, looks like it [10:33] popey: coould you pastebin me the output of `click list --user=phablet --manifest`? Interested in the terminal sections :) [10:34] sil2100: http://paste.ubuntu.com/10051403/ [10:36] popey: thank you! [10:38] np [10:46] cihelp: could anyone try re-running ubuntu-rtm mako smoketesting on the latest image for me? Need to double confirm it's still dying [10:49] sil2100: do you have the url handy ? [10:49] https://jenkins.qa.ubuntu.com/job/utopic-touch_stable-mako-smoke-daily/610/consoleFull [10:58] vila: I want a re-run since I'm wondering a bit what terminal-app it uses and if it was only some transient state last time... in theory the terminal-app installed by default in these images should be the new one, which should not cause the current error [11:04] sil2100: I've started http://q-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-mako-smoke-daily/611/console [11:05] vila: thanks! [11:05] sil2100: by the way, do you have access to do it too or not ? [11:05] vila: yes, through the VPN [11:06] sil2100: ack [11:10] sil2100: failed in the same way [11:10] Interesting [11:11] sil2100: lp:ubuntu-terminal-app tip is revno 48, the job requests revno 161 [11:12] vila: I know, which is wrong as the current terminal app from the store (and the one that seems to be installed in the tarball) is the one using rev 48 [11:12] vila: somehow it doesn't update the terminal app [11:12] sil2100: so were is this 161 coming from ? [11:12] sil2100: I seem to recall that they change their focus branch recently [11:12] vila: 161 was the old terminal app, a previous version - we changed trunks so now this revision does not exist [11:12] *dev focus [11:13] right, so something needs to be updated somewhere... [11:13] vila: that's why we published a new terminal app yesterday that now has the correct revision number [11:13] Is it normal we don't use --wipe? [11:13] there is also a previous error: [11:13] bzr: ERROR: Server sent an unexpected error: ('error', 'ValueError', 'requested revno (161) is later than given known revno (48)') [11:14] + phablet-click-test-setup --distribution ubuntu-rtm --series 14.09 [11:14] bzr: ERROR: Server sent an unexpected error: ('error', 'ValueError', 'requested revno (161) is later than given known revno (48)') [11:14] Yeah, that's the same thing [11:14] :) [11:14] Anyway, maybe because we don't do --wipe the devices have some old clicks installed? [11:14] vila: can you access the device that it just tried running on? [11:15] sil2100: no :-} [11:15] vila: I would need `click list --user=phablet --manifest` pastebinned from that device (from adb best) [11:15] Awww [11:16] sil2100: it may be possible but I have no idea how :-/ [11:48] sil2100: you mentioned a new terminal app, does it match the one in http://people.canonical.com/~ubuntu-archive/click_packages/click_list (imbw but this file seems to be involved, so checking with you) [11:54] elopio: could you please take a look at this merge of yours? https://code.launchpad.net/~canonical-platform-qa/sudoku-app/autopilot-workaround_dialog/+merge/246255 [11:57] trainguards: any idea why the build is showing as failed on vivid silo 13? I checked the PPA and the packages all built fine [12:09] boiko: looking [12:10] boiko: yeah... it's a bug in CI Train (LP: #1417961) [12:10] Launchpad bug 1417961 in CI Train [cu2d] "CI Train does not remove packages from its config after a reconfigure" [High,New] https://launchpad.net/bugs/1417961 [12:10] boiko: let me fix it manually for you [12:11] sil2100: should I rebuild or something like that, or is it just fine like that? [12:15] boiko: I'm doing a watch-only build [12:15] sil2100: ok, thanks === marcusto_ is now known as marcustomlinson_ === MacSlow is now known as MacSlow|lunch === marcustomlinson_ is now known as marcustomlinson [12:52] Mirv: sil2100: I would need a massive reconf on the RTM silo5 :) We intend to land biiiiig things :) from all over the places [12:53] kenvandine, Hi! [12:54] bzoltan, uuuh, in RTM ? scary ! [12:56] ogra_: we are sdk people, we do scary stuff :) https://www.youtube.com/watch?v=T8r3cWM4JII [12:57] whatever that was, it crashed FF hard :) [13:01] ogra_: that is a 10hour video of This is Sparta [13:01] bzoltan: does it have permission from on high if not then it goes no where fast :P [13:02] well, it has killed my FF in some definitive way now ... it starts again but i only get empty pages or no CSS or even "server not found" === alan_g is now known as alan_g|lunch [13:04] boiko: oh! [13:04] I mean [13:05] boiko: sorry, I meant bzoltan [13:05] bzoltan: oh! Reconfiguring then [13:06] ogra_: ohh dude :) i did not mean that. Sorry [13:07] bzoltan, well, you didnt write firefox i guess ... not your fault :) [13:08] bzoltan: reconfigured [13:12] sil2100: thanks [13:13] ogra_: :) sending you a killer video is :) [13:14] davmor2: yes the bug #1358610 is targeted to w7 [13:14] Error: Launchpad bug 1358610 could not be found [13:14] heh ... at least i could see the ad before it crashed ... so youtube got its share of money from the click :P [13:23] charles, Hello [13:28] sil2100: o/ [13:28] sil2100: how do I sync a package from vivid to rtm? [13:32] trainguards, 404 again? :( [13:33] Chipaca, see line 22 as an example [13:33] you put "sync:ubuntu,vivid $package $name" in "additional sources" [13:34] oh! [13:35] 404 if I'm not logged in!? [13:37] trainguards, oh, and "Removing $foo from silo" on reconfigure, but they don't actually get removed? [13:37] Saviq: it's as illogical to me as it's to you? :) [13:37] Mirv, can you please remove qtmir and qtmir-gles from vivid silo 21 for me [13:37] Saviq: yes, the bug #1417961 mentioned [13:37] Saviq: ok [13:37] bug 1417961 in CI Train [cu2d] "CI Train does not remove packages from its config after a reconfigure" [High,New] https://launchpad.net/bugs/1417961 [13:37] Mirv, ah [13:38] Saviq: ta [13:43] trainguards, can i have a silo for row 68? (not sure if it's missing anything tho) [13:43] Saviq: done [13:43] Mirv, thanks [13:48] Saviq: after recent Robert's changes this bug appeared, as he changed the rules of package watching and didn't handle most of the edge-cases as Didier did [13:48] Didier was really good with all corner-cases [13:59] hey om26er [13:59] so you need a test plan for indicator-power [13:59] https://wiki.ubuntu.com/Process/Merges/TestPlan/indicator-power [13:59] * kenvandine adds to spreadsheet [13:59] * ogra_ twiddles thumbs waiting for livecd-rootfs === alan_g|lunch is now known as alan_g [14:05] om26er, i updated the spreadsheet, hope that helps [14:06] kenvandine, thanks for that, I'll get back to it in a while [14:07] om26er, nothing in the indicator really changed, just exposed a new property on dbus [14:09] sil2100: do i need to do anything more to row 68? [14:13] Chipaca: no, all is ok, I'll handle it in a moment :) [14:13] Was on lunch now [14:14] (and now on UE Live!) [14:14] sil2100: thanks [14:14] sil2100: I try to update the gles package for RTM, would you please reconf the silo5 for me? [14:15] bzoltan: one moment :) [14:21] cihelp: any idea why "phablet-config writable-image" is failing here? http://paste.ubuntu.com/10054269/ [14:23] oh, nevermind, got it: my device was not connected to the network [14:23] mardy: that's not really a cihelp question, but iirc you may need to also specify the password you set up with developer-mode [14:24] mardy: thanks, it was really a network issue, my device wifi was off :-) [14:24] mardy: with "-r", so if you still have problems, you might also try that [14:25] mardy: ack [14:27] sil2100: ok, so on the vivid/terminal-app issue... I just installed locally with image 97 from ubuntu-touch/devel-proposed [14:27] and according to click list, I have com.ubuntu.terminal 0.7.41 [14:28] sil2100: I don't think that's right still, or if it is, then the manifest is also wrong for this version of terminal app: [14:28] "x-source": { [14:28] "vcs-bzr": "lp:ubuntu-terminal-app", [14:28] "vcs-bzr-revno": "latest" [14:29] sil2100: my guess is that the wrong terminal-app is still getting pulled in [14:30] plars: strange, since the click_list from snakefruit has com.ubuntu.terminal_0.7.46_armhf.click listed [14:30] hmm === MacSlow|lunch is now known as MacSlow [14:31] plars: I wonder why the latest images don't have the latest terminal-app then [14:31] plars: the image builds should just fetch the latest click from the store [14:31] sil2100: you are requesting the terminal-app-reboot one? [14:32] sil2100: I haven't seen how that side of it works, so I don't know what you do to change the click package you pull in, but both the old and new are still built [14:32] plars: no no, the terminal-app is now the reboot one [14:32] plars: it got updated that the main terminal-app now should be the reboot one [14:32] sil2100: if that's true, then it's pointing at the wrong branch and revision in the manifest [14:32] popey: ? [14:32] plars: no, it should be all ok [14:33] plars: on my phone it's pointing to the right thing on my vivid device [14:33] sil2100: with krillin image 97? [14:33] 97? [14:33] oh, vivid [14:34] plars: yes, vivid 97 [14:34] weird, I *just* installed this fresh [14:34] hmmm [14:35] sil2100: but that 0.7.41 version is wrong? it's different on yours? [14:35] yes, should be .46 [14:36] "name": "com.ubuntu.terminal", [14:36] "title": "Terminal", [14:36] "version": "0.7.46", [14:36] "x-source": { [14:36] "vcs-bzr": "lp:ubuntu-terminal-app", [14:36] "vcs-bzr-revno": "46" [14:36] }, [14:36] This is what I have, but it's not a fresh install [14:37] hm [14:37] plars: but wait [14:37] sil2100: any chance you've gone and updated it? [14:37] plars: actually it's good #97 doesn't have the version [14:37] plars: since #97 is old, we didn't have a nightly build for vivid [14:38] So the new one should be only available on the next build [14:38] still waiting for the promotion ... [14:38] heh, ok [14:38] (so I had to upgrade it myself) [14:38] plars: but I was wondering about ubuntu-rtm though [14:38] sil2100: trying to reconfigure silo ubuntu 9 and getting an error [14:38] sil2100: Problem accessing /job/ubuntu-landing-009-0-reconfigure/parambuild. Reason: [14:38] Not Found [14:38] sil2100: rtm shouldn't have terminal-app at all right? [14:38] plars: since from the smoketesting page I saw that for mako failed [14:39] plars: krillin rtm doesn't, but mako rtm does (I was shocked as well) [14:39] (still on UE Live! though, will continue this after we're done) [14:39] right, I was not looking at mako yet since this problem was only krillin/vivid afaik... looking [14:39] ack [14:40] davmor2: stop trolling! :D [14:41] hahaha [14:41] sil2100: Not to put pressure on :) But would you reconf teh silo5? [14:43] bzoltan: phew, ok, have a moment now [14:45] robru: the new parambuild in jenkins is a bit broken ;p [14:46] bzoltan: done [14:46] sil2100: thank you [14:46] plars: do you know how to access a smoketesting device? :) [14:46] bzoltan: sorry it took so long, the ubuntu-on-air came in the way ;p [14:47] sil2100: no worries, we had a glitch anyway with one of the MRs [14:47] sil2100: yes and com.ubuntu.terminal 0.7.41 on mako vivid 88 also [14:47] plars: I'm asking because of this - this is from rtm on mako: http://q-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-mako-smoke-daily/611/console [14:47] "version": "0.7.41", [14:47] "x-source": { [14:47] "vcs-bzr": "lp:ubuntu-terminal-app", [14:47] "vcs-bzr-revno": "latest" [14:47] plars: mako ubuntu-rtm? [14:48] oh right, hang on [14:48] :) [14:48] plars: since here it's completely chaos, as it seems its something with revno of 161, which might point to a pre-reboot version of terminal [14:48] Which shouldn't exist in the store anymore [14:49] sil2100: well, but when was that click package built? the manifest data is supposed to be filled in then [14:50] ok, mako-rtm #187 has com.ubuntu.terminal 0.5.161 [14:50] so, yes... that looks wrong I think [14:50] plars: the click was built yesterday EU afternoon and it has all the correct metadata when installed from the store [14:50] plars: this is interesting, since right now the store has only 0.7.46 :| [14:50] So how did the ubuntu-rtm image get the old terminal app? [14:51] plars: btw. why aren't we doing a --wipe when flashing the devices? Was there a reason for that? [14:51] sil2100: yes, we were told not to, and that it was redundant if we use --bootstrap [14:51] since pretty much the beginning [14:52] if that's changed and --wipe now does something above and beyond --bootstrap, then I never heard about it [14:52] but aiui, --bootstrap still replaces everything [14:55] bfiller, just FYI that the ubuntu-keyboard MPs should now be running the autopilot tests [14:55] fginther: awesome, thank you [14:56] WOW :) [14:56] bfiller, you're welcome (and thanks to plars for working on it) [14:57] plars: from what I know only --wipe removes all data, but hm [14:57] ogra_: ^ how is it? Does --bootstrap wipe all your data too? [14:57] I could have mixed something up [14:57] sil2100, it formats the partitions iirc [14:58] right [15:00] Mirv: look what I got ^ [15:00] Ok, trying to get more info on how exactly the clicks are installed [15:05] sil2100: it would appear that it's in the custom image [15:06] http://system-image.ubuntu.com/pool/custom-761e8a93754d4170fc8f1d4dad38567fb260cca55a8f42141d2da6c682ac43bf.tar.xz [15:06] sil2100: ^ [15:07] sil2100: and it doesn't look like that custom tarball has changed for mako-rtm in a long time - even image 138 has the same tarball === plars changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: [15:08] sil2100: The silo5 seems to be messed up bug time... no idea what is wrong there. First it failed in a spectacular way with the -gles package... and now it fails even on the reconf after I tried to remove that branch. [15:08] bzoltan: er... ok :) [15:09] Mirv: ^ [15:09] Mirv: I assume that the versioning of my RTM gles package is somehow strange for the machine [15:09] bzoltan: if that persists, the previous one, ping robert about that. and yeah the 404:s happen today too, bug filed. [15:09] bzoltan: that's what it claims, a version string problem [15:10] bug #1417958 <- sil2100 too [15:10] plars: interesting [15:10] bug 1417958 in Ubuntu Landing Team "Reconfiguration options ~broken" [Undecided,New] https://launchpad.net/bugs/1417958 [15:10] Mirv: yes, but what should be the right version? and what was wrong with that one? I used a version what is in the PPA [15:10] Mirv: thanks! [15:13] bzoltan: you miss the -0ubuntu stuff completely [15:13] bzoltan: so no, it does not match the non-gles package's version === sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Various issues with the CI Train [15:15] Mirv: hmm... darn it. You are right like always [15:17] plars: ok, it seems that for some reason the terminal-app is in the custom tarball that's not auto-updated [15:17] plars: which I suppose is not a good idea [15:18] lool: hey! You around? [15:18] sil2100: yup [15:18] lool: I see that the custom tarball for mako has terminal-app in it [15:18] lool: it's outdated badly right now - why do we have it in the custom-vendor-here_14.09-proposed_mako.tar.xz tarball in the first place? [15:19] sil2100: I think it was a space issue [15:19] sil2100: we dont have automation for these custom tarballs, so I guess it's always going to be out of date until we do [15:20] lool: in this case I think we should really remove terminal-app from it [15:20] sil2100: I suspect the original reasons for moving it there are still valid (space?) [15:20] lool: not sure... [15:21] lool: but I suppose ubuntu-rtm wasn't supposed to have terminal-app anyway, since the krillin ones don't [15:21] Devel has it on default anyway [15:21] slangasek: ^ do you recall the constraint that forced the move of terminal-app and other apps to custom tarball, and would you know if these still exist? [15:22] lool: so all the apps that got moved to the custom tarball need manual updating? [15:22] If yes, I suppose that's a big big flaw [15:23] sil2100: I certainly agree [15:25] lool: the constraint is "product management said we're not shipping it on the image for bq" [15:26] sil2100: ^ [15:26] slangasek: ah right, hence only in mako/rtm and not in krillin/rtm === tyhicks` is now known as tyhicks [15:27] sil2100: the alternative would be to have it in the rootfs and to remove it in krillin/rtm, but that a waste of space hence wasn't chosen [15:28] lool: I would simply remove it from the custom for RTM anyway, since otherwise we'd have to have someone to maintain it and make sure always the most up-to-date version is included [15:28] lool: by remove from custom I mean remove it in overall, we have it in devel anyway [15:29] sil2100: I wonder if it's also an issue in vivid? [15:30] lool: no, on vivid it's on the rootfs it seems [15:30] lool: at least it's always up-to-date [15:30] so I guess this issue would be the other way around if we were to promote a vivid image [15:30] What do you mean? [15:33] sil2100: that if we promote images to stable, we will want to remove terminal from krillin [15:35] it shouldn't be in the rootfs for vivid; that's a bug, we shouldn't have differences in the rootfs/custom tarball split based on which branch we're on [15:36] sil2100: ^^ indeed, I think that implies that this is a missing landing on vivid ;) [15:36] slangasek: missing landing? ;) [15:36] slangasek: I just know that vivid has a more recent terminal-app which seems to be in sync with what's in the store [15:36] sil2100: well, "landing" - changes in the ubuntu-rtm/14.09 dist that are not in vivid [15:37] sil2100: because this is a difference in the livecd-rootfs behavior between the two branches, which is wrong [15:37] Indeed ;) [15:37] sil2100: yes; the problem is that "oh, vivid's ok" is actually a bug in the vivid build [15:37] But if we were to switch those to the custom as we do it for ubuntu-rtm, this would imply we would need to have someone managing the custom tarballs on daily basis [15:37] no [15:37] To make sure none of the apps in there are always up-to-date [15:38] s/none/all [15:38] for vivid, we should fix it so that terminal-app is provided by the custom tarball, not the rootfs [15:38] and for the standard vivid channel, we sholud be using the *reference* custom tarball, which is built as part of the image build and is up-to-date wrt terminal-app [15:39] i thought the long term target was to move all clicks into the custom tarball [15:39] Damn, this is confusing [15:39] just that nobody ever got to it [15:39] ogra_: that's not been agreed [15:39] Since there's the reference custom tarball and the custom tarball [15:39] ah, k [15:39] well, it seems the cleanest option [15:39] ogra_: and that still doesn't help sil2100's problem, which is the out-of-date custom tarballs [15:40] yeah [15:40] slangasek: if it's in the reference custom tarball it will be created from up-to-date clicks during build time, right? [15:40] lool: I guess there hasn't been any progress on removing the need for nokia here to be specially-treated in the custom tarball? [15:40] sil2100: yes [15:41] slangasek: then I suppose we would need to move the terminal-app to this reference custom tarball as well for ubuntu-rtm in mako [15:41] Instead of the hand-built custom tarball [15:41] Since then the hooks can remove it for krillin, right? [15:42] slangasek: it will always need to be in the custom tarball, but ideally it ought to be a click; that doesn't help with the fact we will want to ship some proprietary code in the rtm image and not in the ubuntu images, so I guess this will persist [15:42] sil2100: no. The reference custom tarball for ubuntu-rtm *already* has terminal-app in it; the problem is that you're looking at a channel that's not *using* the reference custom tarball [15:42] Ah, ok, so it's either using the reference custom tarball or a hand-build custom tarball, right? [15:43] Ok, all clear now [15:53] trainguards yo! could i get a quick reconfigure on vivid silo 0 ? [15:54] trainguards hey, may i ask you to reconfigure silo 8 (vivid), thanks! [16:13] kgunn, pstolowski: on it! [16:20] grrr [16:22] sil2100, thanks! [16:24] boiko: could you top-approve merges from silo 004? [16:26] sil2100: oups, yes, sorry [16:27] sil2100: done [16:27] boiko: re-publishing then [16:36] om26er, do you need anything else from me for silo 0? [16:36] kenvandine, no, its fine. I'll be getting back to it in a few minutes. Just need to finish this branch. [16:37] om26er, ok, sorry for bugging you [16:37] it showed blocked still, so was worried :) [16:40] === IMAGE 89 DONE (finished: 20150204-16:40) === [16:40] === changelog: http://people.canonical.com/~ogra/touch-image-stats/89.changes === [16:41] \o/ [16:43] phew, finally [16:53] kgunn, tweaked your line, it's "libevdev", as we need the source package, not the bin one [16:54] ah thanks [16:54] kgunn, and mzanetti, with just libevdev2 added it booted fine for me [16:54] kgunn, obviously you need trainguards to reconfigure, _and_ I'm worried the train might choke on mixed sync: and source uploads, in which case we'd just need to add "libevdev" to the list and ask a trainguard to copy from archive [16:55] ah...i wondered about that being "supported" [16:55] Saviq: yeah, the train doesn't support those... but if you list all sources as source syncs and make sure that in the 'packages to rebuild' you only list those packages that you want to sync, it will sync those and leave the others as they are [16:56] kgunn: ^ [16:56] So, let's say, we have a line like: "sync:ubuntu/vivid p1 p2 p3", and actually we want to only have p2 as a sync and p1 and p3 to be normal source uploads [16:56] kgunn: Saviq: there's no such thing as "mixed source & sync". you either have a sync silo or you have some source uploads. [16:57] sil2100, ok, could you reconfigure silo 0 for us then? [16:57] Then during builds, only build (in the 'packages to rebuild') write 'p2' and never the rest [16:57] sil2100, yup, understood [16:57] sil2100: ugh [16:57] Upload p1 and p3 to the PPA and do a watch-only build [16:57] robru: hack ;) [16:57] robru: anyway, could you take a look at the jenkins issues today? [16:57] sil2100: yeah looking now. [16:58] Since it was a bit troublesome to prepare silos and reconfigure ;) Nothing impossible, but still [16:58] Not sure what was wrong with those constant 404s as well [17:00] sil2100: yeah what 404s were you getting? like the prepare was running but 404ing on the mp urls? or the job itself would 404 before you could run it? [17:00] sil2100, that seems to have been jenkins going 404 if you didn't have the perms to that page [17:00] robru, https://ci-train.ubuntu.com/job/ubuntu-landing-000-0-reconfigure/parambuild [17:00] robru, is 404 unless I log in [17:01] robru, ogra_, jibel, davmor2, popey: of course, no LT meeting due to the allhands call [17:01] Saviq: oh right, the login... hmmmm [17:01]