[02:10] === trainguard: IMAGE 43 building (started: 20140522 02:10) === [02:44] ^ will be missing the NM fix, I was still fighting autopkgtests. [03:30] === trainguard: IMAGE 43 DONE (finished: 20140522 03:30) === [03:30] === changelog: http://people.canonical.com/~ogra/touch-image-stats/43.changes === [03:37] cyphermox: yeah, NM is still stuck in proposed [03:37] yes [03:37] I'm trying to figure out what' still broken in autopkgtests that prevents it from passing [03:37] but even then there still would be friends [03:37] if you want, feel free to force it through [03:37] (or to ask someone to force it through) [03:38] oh [03:38] there it is [03:42] this really isn't my day [03:43] five uploads for such simple matters, it's really sad [03:44] rsalveti: I can kick off an image when it actually makes it [03:44] or delegate to somebody else, don't feel like you need to stay up [03:44] yeah, not sure if we can do much at this point [03:44] maybe infinity might be able to help, but not sure [03:45] otherwise we'll wait the EU team to be up [06:07] Mirv: hey! you should probably remove ~ubuntu-unity from https://launchpad.net/~ubuntu-sdk-team/+members I guess, mind doing that? :) [06:08] didrocks: morning, sure. [06:09] done [06:10] great, thanks! [06:23] ogra_: any chance of triggering an image for cyphermoxs network-manager fix with any joy that will mean we can avoid traincon0 I was told it should be in 43 last night but it must of missed the image as I don't see it in the change log and networking was still off by default === jdstrand_ is now known as jdstrand [07:00] robru: sil2100: hey, you probably have misdone something (like a full build after the reconfigure, which wipes out everything). Contrary to what you told on the backlog, a reconfigure does NOT force you to rebuild anything. It keeps what's still in the ppa and keep the local build info as well. Then, you just press build with "only packages". [07:20] davmor2, NM is stuck in -proposed so a new build wouldnt help ... [07:22] :'( but, but, but, but :) [07:22] davmor2, seems the autopkgtest of friends fails [07:22] yes [07:22] gutted [07:22] ogra_: feel free to ask an archive admin to skip it [07:22] (friends) [07:23] is this a pitti fix? [07:23] cjwatson, are you around already ? we could need some autopkgtest override for network-manager [07:23] I'm really off to bed now, my eyes are closing [07:23] (well, for friends in fact) [07:23] cyphermox: dude go sleep [07:24] cyphermox, why can we skip friends (if i get asked) [07:24] it's a regression in libsoup, not a problem in NM [07:24] ok, thanks [07:24] go to sleep :) [07:24] I added a branch to bug 1322013 to add autopkgtests to libsoup to catch this [07:24] bug 1322013 in libsoup2.4 (Ubuntu) "libsoup2.4 2.46.0-2ubuntu1 may have regressed soup_message_set_request" [Undecided,New] https://launchpad.net/bugs/1322013 [07:24] awesome [07:24] but I haven't fixed the problem [07:24] k [07:25] if you just revert libsoup it works [07:25] back later ;) [07:25] yeah, go sleep [07:27] davmor2: the video scope thumbnail issue is still there [07:27] popey: yeah but I don't care about that :) [07:27] its a regression, you should :þ [07:33] didrocks: yeah, so I guess what happened is that the lander, after the reconfigure, did a whole rebuild without the force rebuild flag - while he should have just rebuilt that one component that had a merge added [07:34] sil2100: exactly, and so it's not the reconfigure which is at fault as I saw on the backlog [07:34] and build does what it's expected to "ditch everything and restart" [07:34] (hence the security to force only "partial rebuilds" [07:34] ) [07:34] didrocks: indeed, makes sense [07:35] didrocks: in any way CI Train did what it was supposed to ;p [07:35] yeah, the only issue is that skipping one component isn't really clear [07:35] when there is nothing to rebuild [07:35] maybe that check can be removed… it was more for daily release anyway [07:36] and we rebuild anyway [07:41] ogra_: so, it says it's still running the autopkgtests for network-manager, has that been re-ran or something? [07:41] sil2100, read the backlog [07:41] :) [07:42] ogra_: my backlog only says that 'friends autopkgtest is faining and should be skipped', no mention of the tests still running ;) [07:43] From what cyphermox told me I thought those already finished running and we know the results [07:43] Ok, it seems that update_excuses is just not updated on my side it seems [07:43] right [07:44] if you look at the jenkins output you see that only frieends on x86 fails [07:44] i guess worst case we can upload the libsoup "fix" from the bug [07:45] Well, it wouldn't fix the issue, it would only make one additional autopkgtest to fail ;P [07:46] no, it would make the libsoup test being skipped [07:46] cjwatson: there are a lot of good people waiting for your archive powers [07:46] dont be pushy ... he will reply once he is here [07:46] :) [07:47] seems infinity is off sick today [07:49] sil2100, the tests are still running because pitti seems to have done a subsequent upload 2h ago [07:49] Oh [07:49] (in fact there where four NM uploads for this issue [07:50] one fix, and then three fixes of different tests that are hit by the same problem ... yay for copy-pasting app code onto tests :P [07:51] hehe, right, I see that in the package history ;) [07:57] psivaa: morning! Once you're up, could you take a look why we have so many phablet-test-run problems on #43? [07:57] hmm, and image tests seem to have failed half way through image 42 ... 43 wasnt even attempted [07:57] Right, I meant 42 [07:57] Strangeness [07:58] psivaa: as ogra_ said, do you know what's going on? ^ [07:58] sil2100: let me take a look. === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - [08:00] wow, quite a lot of settle before/after tests failed [08:09] So... trying to test an old camera bug, but all I'm getting is crashes instead. [08:14] sil2100: ogra_ : so all the jobs somehow hanged in the middle of runs. The host where the devices are attached was upgraded last night. so i suspect this could have something to do with it [08:15] i've kicked off them again. let me see how it goes [08:16] Anyone interested in a unity8 crash dump from image 41? It seems to be easily reproducible. [08:16] http://toykeeper.net/tmp/_usr_bin_unity8.32011.crash.bz2 [08:17] ToyKeeper: when is it happening? [08:18] sil2100: Launch camera app, kill it, launch it again. [08:18] It's apparently not quite as easy as I first thought... got it twice in a row, but now it's not cooperating. [08:32] 'k, camera bug re-confirmed. [08:32] ogra_,sil2100: network-manager forced [08:32] cjwatson: \o/ Thanks! [08:32] \o/ [08:33] thanks [08:44] sergiusens: is there a new gallery click? does it need to go to the store? [08:44] popey: most likely, I was waiting on the framework change though [08:45] lool: ^ [08:45] the phone has the new frameworks [08:45] the store probably doesnt though [08:56] sil2100: davmor2 is talking to bueno and I just asked jdstrand about apparmor click which he's working on now. we need both of those before we can upload gallery and then build #44 [08:56] sil2100, hmm, two new security failures [08:56] ah, popey is to fast :P [08:56] popey, apparmor-easyprof-ubuntu seems to fail too ftr [08:57] popey: thanks ;) let's get it moving then, use the whip on them! [08:57] (also framework issues) [08:57] lool, we need to coordinate that better the next time ... use a silo or so [08:59] sil2100: we got all clock app tests passing in jenkins atm (yay :) )...the issue with the calendar app messing up clock app results is something we are looking into. [09:00] ogra_: these shouldn't be coupled [09:00] lool, the tests are [09:00] ogra_: which tests? [09:01] security tests test for the latest framework [09:01] ogra_: as I said, these dont need to be coupled [09:01] if they have not been adjusted they seem to fail [09:01] but they are :) [09:01] ogra_: a) add framework, b) update stuff that depends on framework, c) use new framework [09:01] ogra_: oh really, interesting, which ones? [09:01] nik90_: excellent! Just wanted to make sure - is the fix part of the recent UITK landing? [09:01] lool, right and use a silo for a)and b) [09:02] sil2100: yes it was part of the recent uitk landing [09:02] thats why we have them [09:02] to shield us from possible regressions in the actual images [09:02] ogra_: I had updated the frameworks without silo last week and this was just another case of it, but if you could point me at the failure I'd be interested [09:03] lool, http://ci.ubuntu.com/smokeng/utopic/touch/mako/43:20140522:20140513.2/8152/security/1151651/ [09:03] Determining policy version for 'ubuntu-sdk-14.10-dev1' ... ERROR: Could not determine policy version for 'ubuntu-sdk-14.10-dev1' [09:04] same for click-apparmor [09:05] ogra_: ok; good to know for the future, I didn't know we had it there [09:05] the latter one ships a test click package that needs to be updated for example [09:05] :) [09:13] popey: sil2100: so beuno is aware, lool is going to talk to bueno too, and lool and popey have already talked to jdstrand too so everyone is in the loop. Ken is in a meeting currently so I'll let him know after everyone is a winner \o/ [09:14] thanks davmor2 !! [09:14] davmor2: thanks! [09:14] It's good to have someone on the 'inside' [09:14] i.e. on the sprint [09:14] ;) [09:15] The sprint is what's keeping me from testing half the core features... I have no service here. [09:15] (that, and an ever-growing stack of things which need to be done right away) [09:15] great, that makes me look forward to next week :P [09:17] are we still at TRAINCON-0 ? [09:18] ah, apparently not [09:18] we will see ... [09:18] after 44 has build [09:19] but it looks good from what is landing ... we might not need TRAINCON-0 === zsombi__ is now known as zsombi [09:21] sil2100: just talked to ken, they don't need to upload a new gallery app because they fixed the abi to work both ways, he did however say that the new framework is still useful for everyone though [09:21] davmor2: just as I suspected [09:22] davmor2: thanks for all the info ;) [09:22] sil2100: which is why I can confirm it works \o/ [09:23] ogra_: so, I leave it up to you to decide when to build the new image [09:24] sil2100, well, once everything landed ... :) [09:24] sil2100, we want gallery i guess [09:24] and the security fixes [09:24] ogra_: as per what davmor2 and kenvandine said, well, a new gallery-app is not *required* as they fixed content-hub to work both ways, but it would be nice to have that properly fixed indeed [09:25] With the bump [09:26] sil2100, gallery still has 4 failures [09:26] and there is a landing that supposedly fixes these [09:26] Yeah, but it's not tested yet [09:26] line 31 [09:26] can I have a silo for click-apparmor and apparmor-easyprof-ubuntu to fix the security image tests? [09:26] so lets get someone test it :) [09:27] this will add support for the newly added click frameworks to click apparmor [09:27] (as well as add 1.2 of the policy to apparmor-easyprof-ubuntu) [09:27] oh, I guess I need to update the spreadsheet [09:28] * jdstrand forgets that step [09:28] popey, davmor2, can anyone get gallery tested at the sprint, so it could land for 44 ? [09:29] ogra_: I wouldn't block on that, as it's not a broken gallery just incompatibilities with autopilot [09:29] i would ... but yur call [09:29] sil2100: should I be using https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc#gid=0 like I would before? (istr problems with the spreadsheet but I haven't paid close attention to the thread) [09:30] jdstrand: https://wiki.ubuntu.com/citrain <- this one points to the most up-to-date one [09:30] jdstrand, yeah, that url looks right [09:30] ok, thanks [09:31] davmor2, ogra_: so let's do it like this - let's see if Bill can test that landing in the nearest 30 minutes, if not we kick an image without that landed [09:31] ok [09:31] davmor2: as our person on the inside, do you see Bill anywhere? He was the lander for that one [09:32] * ogra_ would very much like a green image before the weekend... [09:32] sil2100, would be nice to update the spreadsheet header [09:32] traincon-0 etc [09:32] I'll go have a hunt again [09:32] biab [09:32] mhr3: thanks for the reminder! We won't be in TRAINCON0 too long I guess though [09:32] sil2100: ok, spreadsheet updated [09:32] mhr3, if 44 looks fine we wont have TRAINCON-0 [09:32] sil2100, but we are now [09:33] mhr3, who said so ? [09:33] :) [09:33] are we not? [09:33] well, we want to wait for 44 [09:33] if that doesnt fix the issues we will [09:33] either way, i'd like some silos :) [09:34] so many free ones... [09:34] (if you land something be super careful, we *will* hunt you down if you break 44 :P ) [09:34] mhr3: ;p in the past such a number of silos was already considered 'low on silos'! [09:35] mhr3: anyway, assigning those slowly [09:36] davmor2: you're the man ;) [09:36] well, i'm not asking to publish anything, just to assign them :P [09:37] * ogra_ is out for a bit (need to finish mowing the lawn before it rains) .... lest see if everything landed when i return ;) [09:37] sil2100: so found bill he it is mostly there he is finishing things off this morning and will ping you once it's done [09:38] s/he/he says [09:38] balloons, a review please :-) - https://code.launchpad.net/~fginther/cupstream2distro-config/coreapps-pep8-3/+merge/220593 [09:39] davmor2: excellent o/ [09:44] sil2100: where can I get the packages that changed from one image to another? [09:45] boiko: launchpad [09:45] davmor2: anywhere specific? [09:45] boiko: http://people.canonical.com/~ogra/touch-image-stats/ [09:45] cjwatson: thanks a lot! [09:46] boiko: oh sorry change logs not the actual packages [09:47] davmor2: yep, I want to see what packages changed, sorry, I didn't make it clear [09:49] fginther, please add reminders hooks as well [09:50] everything else looks good [09:51] balloons, done, updated branch pushed [09:52] approved [10:08] sil2100, ogra_: ToyKeeper just discovered if you take a photo with the camera with flash on the image is black she is currently writing a bug report for that :( [10:08] * sil2100 sighs [10:08] davmor2, ToyKeeper: could you guys check if it happens on the last promoted image? [10:09] davmor2: https://bugs.launchpad.net/camera-app/+bug/1322121 [10:09] Ubuntu bug 1322121 in camera-app "pictures taken with flash are almost completely black" [Undecided,Confirmed] [10:09] davmor2, ToyKeeper: I'm leaning more into the way of not instantly blocking on issues we didn't earlier have in our test-plan, as per one of asac's propositions [10:10] I don't know how long the bug has been there. [10:11] It's a big issue, Critical, but if it would be already in the last promoted image I wouldn't block on this this time [10:11] I would mark it as a blocker for the next image [10:12] Since otherwise we can be pushing the promotion for like forever [10:14] Let's see... what was the last promoted image? [10:15] ToyKeeper: #28 [10:15] (long time ago) [10:15] I can never remember what day of the week it is, what time it is, or the number of the last promoted image. It changes all the time, so it falls out of my brain. [10:15] That's why I want #44 to be considered as a promotion candidate [10:15] I'm really hoping 44 can be promoted too. :) [10:16] (traincon 0 has a tendency to suck up *all* of my time) [10:16] ToyKeeper: the spreadsheet is your helper then ;) If you go to https://wiki.ubuntu.com/citrain then you can see the latest promoted image written in the header [10:18] sil2100: just collard popey and it is present on his image 28 it looks like the timing is out on the flash and shutter [10:19] phew, ok, let's add that to the 'future blocker' list but not consider it for #44 [10:19] * sil2100 is still waiting for Bill's team to test the gallery-app AP landing [10:21] :) [10:22] Let's give them a few more minutes :) [10:22] hmm, new crash on dialer-app [10:23] additionally to the indicator and dialer-app itself the list-modems script crashes again [10:24] bah, and indicator-network crashes on messaging-app now too [10:24] Damn, all tests finished already, I'm not used to smoketesting working so fast [10:24] ah, it did on 41 as well [10:24] ogra_: so, bfiller said he's running AP tests right now, so we should have it ready soon [10:25] yeah [10:25] well, i dont see anything landed on -changes yet ... so its a competition between security and galler now ;) [10:25] lets see who wins :) [10:26] with these two fixed that will leave us with shorts, dialer and filemanager issues ... [10:26] oh, and terminal too :( [10:27] Terminal had failures from time to time as well, but rarely [10:27] yep [10:29] I guess shorts should be fixed soon, as the cause has been identified [10:29] sil2100: still one failure (: looking at it and will work on a fix, but probably won't be ready until later this afternoon [10:30] land what you have then ... one is better than four [10:30] bfiller: is that some existing failure, or something new fails? [10:33] sil2100: one of the existing failures, just need to rework the test as the underlying code chnaged [10:34] bfiller: you think it would be possible to land this as it is? And then rework the rest in a separate landing? Or would you prefer to do it in this branch? [10:35] sil2100: the dashboard will have failures with this still, but 1 failure is better than 3 or 4 :) [10:35] sil2100: would prefer to fix it so it's all green but if this is blocking you we can push current one [10:36] bfiller: ok, let's push this one then - it will need a click release as well after landing, right? [10:36] bfiller: just flip it to 'tested' and let's get the machinery going [10:36] sil2100: ok [10:36] bfiller: thanks! We'll be waiting for the other landing then soon ;) [10:37] sil2100: done, hopeful we'll have a fix soon for the remaining failure [10:39] ogra_, bfiller: gallery-app published! [10:39] Let's wait for it to hit the archive - not sure how to proceed with the gallery-app click version [10:39] I never really comprehended the process for that one [10:40] sil2100: someone has to build the click and upload it to the store, usually sergiusens or popey handle that [10:40] bfiller: do you know if the change needs to be merged into trunk? Or can a branch be used? [10:40] popey, sergiusens: ^ [10:41] sil2100: think it's best to wait for it to get into trunk then the version of the click will match bzr rev [10:41] sergiusens: right? [10:41] bfiller: sil2100 can't use the same click framework, needs updating; waiting on ack from beuno and jdstrand on new packages [10:41] right [10:41] store is in the process of being updated for the new framework [10:41] Ok then [10:42] ogra_: anyway, I leave you in charge of kicking the image - I need to jump out now for lunch and trip preparations! [10:42] * sil2100 wants a shiny #44 badly [10:44] * sil2100 notes down to read up about clicks and their release process before Malta [10:44] sil2100, yeah, np ... [10:44] i'll wait for a ping about gallery and watch out for the security uploads [10:46] ogra_: would be nice to have the security upload as well, but I wouldn't wait for that - as if I understand correctly they're just test needing update, right? [10:47] the framework needs to be added [10:47] not sure if thats only the test ... i thinnk it is more [10:47] and if gallery uses the new framework you actually want apparmor to know it [10:48] Ok, if there is risk that there's something more, then I suppose let's not risk it [10:48] lets jjust wait for both ... no need to rush if we can have it proper [10:49] ogra_, sil2100 : the gallery app does not need the new framework [10:49] ah, i thought something needed it ... [10:49] the abi breakage was fixed in the content-hub yesterday and released [10:49] was that content-hub ? [10:49] ah, k [10:50] sil2100: ok, so it seems the new gallery doesn't have new APIs as I thought, so we can still use it with the 14.04 framework [10:50] so in today's image gallery is working fine with the content-hub, current changes to gallery are to fix an unrelated problem with failed ap tests [10:51] Yeah, that was my earlier understanding [11:17] if the gallery is using the new framework, the click install is not going to work until silo 6 is ready. I have packages. testing locally, will upload to silo very soon [11:20] jdstrand, it doesnt use the new framework, but i'll wait for silo 6 with the image [12:01] Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - [12:01] fail === Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - === MacSlow is now known as MacSlow|lunch === psivaa is now known as psivaa-afk === om26er_ is now known as om26er [12:20] robru: Sadly the Launchpad webapp doesn't have any sensible way to know when the publisher's finished, at the moment [12:21] sil2100: how we doing is 44 ready? [12:27] Perhaps another option would be to have a gadget on iso.qa that says "build me an image once are available" [12:36] ogra_: did you guys start the 44 build [13:00] davmor2, still waiting for jdstrand to finish silo 6 [13:00] seems he got distracted by an ssh issue :) [13:01] I got sidetracked for a minute. it didn't help that my dput upload silently discarded my upload [13:01] Just hope we'll make it till davmor2 EOD [13:02] Mirv: may I ask for a Silo? [13:03] bzoltan1: sure. I'll just assign one for oSoMoN first. [13:05] done, for both [13:12] jdstrand: did you upload the packages to the PPA successfully now? [13:13] * ogra_ would hit the trigger ... but then we cant promote since apps using the new framework wouldnt work [13:20] sil2100: can I have a silo for line 40 please [13:20] sil2100: to fix last broken test [13:20] bfiller: already on it :) [13:21] sil2100: thanks [13:21] ogra_: we might have all gallery app AP tests fixed even! [13:21] In 44 [13:21] yay [13:22] jdstrand, bfiller, whoever hits the archive first of you two wins a prize ... :) [13:22] * sil2100 would prefer both to hit the archive at once [13:22] :) === MacSlow|lunch is now known as MacSlow [13:31] I am not really helping myself win this race. I dput (which silently failed) and got distracted. I then built in another ppa and forgot to uncheck 'Rebuild binaries' [13:33] jdstrand: did you dput to the silo PPAs before? Since maybe you don't have the required permissions? [13:33] jdstrand: in that case, you can simply give me the source packages and I or ogra_ can push those for you [13:33] But I thought you had the power for that [13:33] he does [13:33] it's all fine. they are building in the silo. they don't take long [13:34] jdstrand, just upload if you are confident [13:34] was just saying, it slowed me down a bit [13:34] We trust you jdstrand! [13:34] * jdstrand wanted arm binaries for click apparmor to test [13:34] thanks! but I want to test on the device. I'm sure it's fine, but a few more minutes [13:35] Once that's in, let's not wait for the gallery-app remaining fix - I would prefer davmor2 to have some time for dogfooding [13:35] And for smoketesting [13:35] That one additional failure can be fixed in #45 [13:37] sil2100: +1 it's 15:36 here now === psivaa-afk is now known as psivaa [13:51] Hi, should I be able to use the framework ubuntu-sdk-14.10-qml-dev1 in image #43 on utopic? [13:51] sil2100: so are we enforcing TRAINCON-0 yet? [13:52] asac, we wanted to see 44 [13:52] right, but we should just start operating lke in TRAINCON-0 [13:52] but be careful about landings today ... no massively big or dangerous landings etc [13:52] if it goes well we lift the embargo quickly [13:53] here the traincon practices slide deck: https://docs.google.com/a/canonical.com/presentation/d/1FOqa6jqGEFPgJ2Ghxgkb7Cqi774IujImPHfYFEYnJgc/edit [13:53] ogra_: right, but we have clear rules for what careful landing means [13:53] asac: yes, we're basically operating as TRAINCON-0 now, but as we currently wait on specific landings, we do not do any other landings [13:53] * ogra_ would still prefer red/yellow/green instead of numbers :P [13:53] we should jsut apply the mechanisms from traincon to be careful [13:54] sil2100: ok cool. double check the slide deck [13:54] of course not set in stone what is in there, if you feel something needs adjustment to be effective let me know [13:54] ahayzen, nope, but in 44 [13:54] asac: sure :) [13:54] ogra_, thanks, cool was wondering why i was getting strange errors :) [13:55] ahayzen, 43 has the frameworks, but not the corresponding security changes, so app confinement will get in your way [13:55] ogra_, yeah tht sounds about right from the errors [13:55] :) [13:55] ogra_, will click-buddy need to be updated as well? [13:56] oh, might be ... not sure [13:56] sergiusens, cjwatson ^^^ does click-buddy need a bump for the new frameworks ? [13:56] ogra_, i think it is coming from click-buddy...but when building the click the last thing you get is 'WARNING:root:Ignoring missing framework "ubuntu-sdk-14.10-qml-dev1"' [13:56] I'll leave that to sergiusens [13:56] click-buddy? [13:56] I really have to read that up [13:57] ahayzen: That shouldn't matter [13:57] Why didn't all the bumps happen when the new framework was introduced? [13:57] That just means the framework isn't on your build system [13:57] sil2100, i talked to lool this morning ... next time we'll get that in a silo instead [13:57] cjwatson, yeah it builds the click fine, just from a user point of view i wanted to give u guys a heads up [13:59] ogra_: right, saw that, but back then I wasn't aware that so many parts were left unhandled with visible consequences [13:59] Since, as I already said, I'm still not completely click-enabled knowledge wise [13:59] i didnt think of click-buddy either [14:00] we can sit down and make a list next week ... what needs to go into that silo when landing a new framework [14:00] and put that on the wiki or whatnot [14:01] It's not desperately important that it all lands at the same time [14:01] You just can't use the new frameworks until it's all done [14:01] But you couldn't use them before either, so no regression [14:01] cjwatson, well, it messes up the image now with half implemented stuff [14:01] not really something i like to promote [14:02] Nothing's messed up, it just isn't complete [14:02] Don't overstate [14:02] (and we are eagerly waiting for a promotable image) [14:03] well, we tell people they should use the new framework ... and they can on the IDE but what they develop wont run ... a promoted image should have these bits complete imho [14:03] Well you shouldn't tell people they should use the framework until it's done [14:03] or that :) [14:03] That's the thing to fix, not worrying about landing everything at once [14:03] ogra_: I also wonder how much we should redesign to centralize the list of frameworks, like for Ubuntu release data [14:04] For a promoted image all that matters is that the framework(s) we recommend work [14:04] yeah, centralizing sounds good [14:05] cjwatson: ogra_ ahayzen click-buddy doesn't care for the framework; it just needs to be created. WARNING:root seems to come from python logging and not anyhing 'echoed' by click-buddy (which after a talk with zbenjamin and come community guys we are redoing) [14:06] That's from click, it can be ignored (and we should possibly silence that) [14:07] sergiusens: I don't think click-buddy necessarily needs to be updated to ubuntu-sdk-14.10 especially urgently, but it still defaults to ubuntu-sdk-13.10, which is kind of bad given that people have been talking about dropping that framework [14:07] cjwatson: well, we are doing it wrong; we actually need to build with the framework defined in the manifest [14:08] sergiusens: Yes, true [14:08] At which point click-buddy will be definitely irrelevant for framework changes [14:09] yeah; as such, the sdk will also apply the same rules wrt [14:10] cjwatson, as i understood it was decided to not drop 13.10 [14:11] OK. It's still not a great choice of default nowadays, I think [14:11] definitely [14:11] <- out for a bit ... lets hope the final bits landed when i return in ~20min [14:19] jdstrand: we seem to be getting some security test failures with the latest image, have you seen those already? === tedg is now known as ted === slangase` is now known as slangasek [14:32] boiko: just saw the latest landing you prepared, looks awesome :) But currently we're low on silos, so if you could wait a little bit then it would be awesome [14:32] jdstrand: how's the landing proceeding? [14:33] sil2100: sure, no problems [14:37] sil2100: looking at an autopkgtest issue (think it is a bad test) [14:37] plars: I have, that is what's in silo 6 [14:39] plars: right, it's a known issue ;) [14:55] wheer do we stand wrt gallery-app [14:57]