[00:33] ribru: the fix is already in rtm:https://launchpad.net/ubuntu-rtm/14.09/+source/unity-system-compositor/+changelog [00:33] ribru: hence why I put that comment there [00:51] AlbertA: kgunn: ah yes, the version in rtm does seem to be higher than the one in distro. should I free silo rtm 1 then? [00:51] ribru: yeah [00:52] hm, the version in rtm is even newer than utopic/vivid, seems like a sync the other way is needed ;-) [03:04] === trainguards: RTM IMAGE 135 building (started: 20141029 03:05) === [04:19] === trainguards: RTM IMAGE 135 DONE (finished: 20141029 04:20) === [04:19] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/135.changes === [08:40] * Mirv frees up 015 (utopic) [09:30] err [09:41] asac: if you ever think you should've gotten a notification and didn't, get me the logs :) [09:41] asac: also if you open system settings and see the update downloading, that's why you didn't get the notification -- you get it once it's downloaded [09:57] Chipaca: i got notification this morning; +1 for the feature [10:00] * ogra_ got it too, OTAed and now his phone restarted the session already 4 times in 2h [10:00] with really really mild usage ... (two webapps and onyl switching between them at times) [10:01] yeah like 50Kb :) [10:07] ogra_, sil2100 - i'm trying out silo 13 to see if it helps [10:07] brendand: ok, I'll check the media-hub revert in some moments [10:07] brendand, ++ [10:26] sil2100, i think our first blocker might be that flight mode is pretty broken [10:26] davmor2, can you confirm? [10:30] good morning [10:30] sil2100: for bugs on the whishlist list, should we go straight for an rtm landing? or vivid + sync [10:31] Morning [10:31] dbarth: are you only targeting rtm landings for now? [10:32] sil2100: actually, we'll want vivid + rtm sync for line 79; so forget that, we'll do the normal process [10:32] dbarth: you have one trunk right now, right? [10:32] besides, silo 8 will stay on the side while oSoMoN lands the new silo [10:32] davmor2, also location not working [10:33] hmm i wonder is this silo at fault [10:33] sil2100: 2 for webbrowser-app, oSoMoN just created an rtm branch for it [10:33] sil2100, webbrowser-app is going to diverge between trunk and 14.09, so we now have two branches, and as a consequence, no sync anymore [10:34] Right, this is the recommended approach [10:55] brendand: right back, what do you want me to check other than flight mode [10:55] davmor2, location [10:55] oh wait, location worked in the end [10:55] but not sure if assisted location is working [10:56] brendand: so flightmode just worked fine here what was the issue you saw? [10:56] davmor2, i turned it off and it still shows the icon and the sim is Offline [10:56] davmor2, but i have a tvoss silo installed [11:01] brendand: http://people.canonical.com/~davmor2/flight-mode.png http://people.canonical.com/~davmor2/flight-mode1.png http://people.canonical.com/~davmor2/flight-mode2.png [11:01] Mirv, can i request that if you or lorne are planning to do manual testing on silo 22, can you ping me beforehand? [11:08] sil2100, ogra_, better late than never, congratz! [11:08] Saviq, thanks ! [11:08] brendand: location is working here too, although it did take longer than normal [11:09] brendand: took about 10 seconds rather than the 5-7 it normally takes [11:10] Mirv: when you have a moment could you please upload http://s-jenkins.ubuntu-ci:8080/job/sudoku-app-click/lastSuccessfulBuild/artifact/generic-click-builder-utopic-armhf/output/com.ubuntu.sudoku_1.1.312_all.click to the store? [11:11] davmor2, does indicator-network show all the networks you'd expect? mine just shows one [11:13] brendand: http://people.canonical.com/~davmor2/network-ind.png [11:13] brendand: pretty much what I expect to see [11:13] brendand: ok, adding a note to the spreadsheet too. I've done a new build in the PPA, but the code reportedly still needs more fixing so no use to test yet. [11:13] popey: done. [11:14] Saviq, is silo 15 landing today/tomorrow (or hoping to at least)? [11:14] brendand, yeah, I'm working on that right now [11:14] brendand, I need to verify one thing and rebuild to be sure and will start testing [11:14] Saviq, will you test it or someone else? [11:15] but bzr's crapping out on me today... [11:16] thanks Mirv [11:35] thostr_, pete-woods - still waiting for instructions on silos 19 and 7. if they aren't going anywhere you should probably free them up [11:42] sil2100, hey, ~rtm in the version is now unavoidable? [11:42] Saviq: thanks! [11:42] Saviq: yeah, basically yes [11:43] sil2100, ok, /me retargets the silo to vivid then... [11:43] Saviq: so, last time we ended up with many binary packages with the same version but different contents last time [11:43] Saviq: which is bad [11:43] sil2100, different *source* content or? [11:44] sil2100, or different binary content as well? [11:44] Saviq: sometimes different source content, sometimes just different binaries (when people were doing source syncs without ~rtm or simply source copies) [11:44] sil2100, ok, thought it was ok to have the same source build for both [11:45] You need to have a different version then, as the binaries that get generated are basically different [11:45] sil2100, yeah understand [11:45] sil2100, can you please help me retarget the silo quickly then [11:45] sil2100, line 30 [11:46] sil2100, I'm cleaning the rtm one [11:46] Ok, let's clean it then and re-assign (that's the only way right now) [11:53] sil2100, if I add/remove branches from a silo, I need to reconfigure it, right? [11:55] oSoMoN: yes :) [11:57] Saviq: ok, having problems with jenkins right now [11:57] sil2100, cleaned [11:57] sil2100, ok, please let me know when ready [11:57] Saviq: I'm trying to re-assign, but I think SSO does some problems again [11:57] sil2100, right, try going to https://ci-train.ubuntu.com/job [11:57] sil2100, and log in there [11:58] sil2100, I had to do that with "reconfigure silo" whenever I was not logged in [11:58] I am logged in but some redirects don't seem to work [11:58] sil2100, oh :/ [11:59] Mirv: can you help me out? [11:59] Mirv: can you try going to line 30 in the spreadsheet and trying to assign that? [12:27] davmor2: hey, so I was supposed to push rtm silo 3 to rtm, so that cwayne could build the custom tarball so that you could test, but the silo is awaiting qa team signoff [12:28] davmor2: I'm happy to walk through the changes with someone from qa if that would help [12:33] jdstrand: I'm testing it now, so far only issue I've hit is that the news scope isn't displaying anything which I would assume would get fixed in the tarball but I could be wrong looking into that now though [12:33] davmor2: ok cool. are there any denials? (this should be unrelated, btw) [12:35] jdstrand: there are some I've been tailing syslog, but I'll paste you the log after [12:35] ok [12:36] we aren't really fixing any policy here-- just one for apps that use udm's qml interface [12:37] jdstrand: so all the apps that are in the list to test so far have been fine, I need to do the incoming out going calls, but got caught up on why the news scope was blank [12:39] * sil2100 is retrying the silo assignment [12:40] sil2100: ok.. [12:40] Still cannot do that ;/ [12:40] It doesn't do the POST it seems, doesn't want to redirect me [12:40] Mirv: can you try? [12:42] sil2100: same here.. [12:42] Maybe we need help from webops? [12:42] sil2100: I've seen similar once before two weeks or ago or so. then I just filled pepare-silo manually. [12:46] Will do that then [12:51] trainguards: hi guys! could I get RTM silo 19 totally reconfigured? I've stripped out the non MRs that fix non-RTM bugs now [12:52] pete-woods: sure, looking [12:54] sil2100: can I get row 51 of the spreadsheet changed from rtm to vivid? [12:54] pete-woods: reconfigured and switched to tested: no [12:54] Please re-build and retest ;) [12:54] yep. all good fun [13:01] sil2100: sorry could you help out with that? [13:14] pete-woods: uh, strange, it said it removed that [13:14] Looking [13:14] thanks :) [13:15] pete-woods: ok, should be good now, but I think something is b0rken in CI Train then ;) [13:15] * sil2100 goes prepare lunch o/ [13:21] sil2100, Mirv I need a silo for line 73 [13:21] gst-plugins-bad [13:30] abeato: ok [13:31] Mirv, thanks [13:36] trainguards: can I get row 51 switched from rtm to vivid? I have an rtm silo assigned already [13:48] ogra_: for health-check tests to run we think psutil is needed in the image: http://dashboard.ubuntu-ci:8080/smokeng/utopic/touch_stable/krillin/135:20141029:20141028-3ca60be/640/health-check/224356/ [13:48] ogra_: any chance that it was removed along with autopilot [13:48] ? [13:48] psivaa_, where did that come from before ? [13:48] ah, that might be [13:49] cant you just install it in the setup phase of health-check ? [13:49] boiko: it'd mean the PPA rtm-026 would be emptied? (it can't be converted on the fly) [13:50] ogra_: we could if that's not needed by anything else [13:50] and yes it does not look like being needed [13:50] trainguards: ping, can we get a silo for line 79 [13:51] bah, unity8 segfault while replying to sms using the indicator [13:51] i doubt it is ... we dont really support python programming for app devs ... and system bits should properly define a dependency [13:51] seb128, yeah, all the time currently :( [13:51] ogra_, is anyone working on that? [13:51] Saviq? [13:51] seb128, yeah, indeed :) [13:51] seb128, got .crash? [13:52] Saviq, maybe, apport still busy doing its thing [13:53] Mirv: yep [13:53] shrug, unity8 respawned but I started the messaging app and it's spinning endlessly now [13:54] Mirv: I will land this stuff only on vivid, and check with bfiller what is worth adding to rtm's wishlist [13:54] seb128, yes [13:54] seb128, that might be because the app was left around [13:54] seb128, apps are not killed along with the session [13:54] seb128, close and launch again [13:54] seb128, kill it once and it will work again [13:55] dbarth: done [13:55] boiko: ok! [13:55] thanks [13:55] Mirv: thanks! [13:57] ogra_, Saviq: thanks [13:57] oh, another fallout/fail [13:57] unity respawned, I opened the indicator and the message was still there, and I replied inline [13:57] which acted like that worked [13:58] but apparently it didn't, the message is not in the log nor counted on the lock screen stats [13:58] and didnt because the messaging app was stuck in bg [13:58] sil2100, getting the redirect issue when trying to reconfigure, do you have a solution? [13:58] well, isn't that done by a service? [13:58] that service is called unity8 [13:58] (managing apps) [13:59] no, sending sms [13:59] I though telephony-service was doing that [13:59] oh, yeah [13:59] e.g that the feature was not relying on the app to run [13:59] but if the messaging app held that hostage ... [14:00] k [14:00] oh, another fail [14:00] lol [14:00] replying from the messaging menu, it asks me what sim to use [14:00] stop that ! [14:00] SIM2 SIM1 [14:00] or I only have one sim in that phone [14:00] iirc i heard about a bbug for that one [14:00] whose issue is that? [14:01] Mirv: of note, oxide is still building in the phablet ppa, but i'll need a binary copy later in the day to silo 15 btw [14:02] bfiller, ^^^wasnt there a bug for the SIM1/2 selection popup if you only have one SIM ? [14:04] Saviq, no dump no :-/ [14:04] :/ [14:04] why the heck is apport failing to collect those? [14:04] SegvAnalysis: Skipped: missing required field "Disassembly" [14:04] bah [14:05] funny, i definitely have a bunch of .crash files for unity8 [14:05] I do [14:05] and it gets properly updated all the time [14:05] they just are 100k and without gdb dump [14:05] so they are useless [14:06] errors.u.c should do the processing on a retracer, no ? [14:06] no, they don't have the dump [14:06] weird [14:06] nothing that can be used for retracing [14:06] https://errors.ubuntu.com/bucket/?id=/usr/bin/unity8%3A6%3A__assert_fail_base%3A__GI___assert_fail%3A__GI___pthread_mutex_lock%3A__gthread_mutex_lock%3Astd%3A%3Amutex%3A%3Alock [14:06] thats definitely one of mine [14:06] not that weird, apport doesn't collect those if the dump is larger than some % of the free memory [14:07] so it depends of your free memory [14:07] ah [14:08] trainguards, i have line 80 also ready for a silo [14:08] eh, as the queuebot said [14:09] i'll prep rtm landing requests targetting backport branches real soon [14:11] shrug, medi-hub eating 100% cpu now [14:11] I think I should properly reboot [14:11] things are weird after unity8 goes down [14:12] yep [14:12] i always do a reboot then [14:13] oh my [14:13] oh, telephony-service segfaulted 10 minutes ago [14:13] could be one of the issues with the replying from menu weirdness [14:13] I think I exceeded available size of the silo POST header for reconfigure [14:14] sil2100, ↑ [14:14] sil2100, getting 413 when trying to reconf silo 5 [14:14] which suggests to me the amount of data I'm trying to pass through is too much? [14:17] cwayne: davmor2 tells me the silo passed. shall I push now? [14:17] jdstrand: please [14:17] ogra_: once apparmor-easyprof-ubuntu gets into the archive can we kick a build? we need it to land a new custom tar [14:17] Saviq, exceeded the 512 branches limit for a single landing ? :) [14:18] ogra_, that's what I'm worried indeed [14:18] ogra_ (and cwayne): it is apparmor, click-apparmor and apparmor-easyprof-ubuntu [14:18] cwayne, if sil2100 doesnt object [14:18] sil2100: ^ [14:18] all three :) [14:18] * ogra_ doesnt mind doing as many builds as the builders can bear [14:19] iw would prefer to do them back to back in a constant flow ... [14:19] sadly smoketesting wouldnt cope with that [14:19] * jdstrand doesn't care how it goes-- I just want to make sure cwayne has all three when he does his custom tarball [14:20] * Saviq managed to reconfigure... had to copy the data manuall [14:20] y [14:21] dbarth: ok, to both oxide binary copy and line 80 [14:22] landing-029 (vivid) for line 80 [14:22] can we not reconfigure our silos any more? [14:23] I need rtm 003 reconfigured since the apparmor in there is not the version the silo was configured with (we should not rebuild anything though-- it is all tested. this is just to get past the build step) [14:23] err [14:23] the publish step [14:24] "Can't publish: Some packages in the ppa are not at the latest version [14:24] Please rerun the prepare job, eventually only with that project." [14:24] istr I used to be able to do that ^ [14:25] ah, it is in the spreadsheet === charles_ is now known as charles [14:38] trainguards: i think you can also unload silo rtm 020, which won't be accepted for landing this week [14:39] trainguards: also, vivid silo 008, the status is really: in testing, not stuck in publishing state [14:42] jdstrand: publishing worked now . I think build with watch_only alone would have been enough. [14:42] cwayne: ok, pushed to proposed. they are finding their way now [14:42] Mirv: oh rather than the reconfigure? good to know [14:56] brendand: I rebuilt the click for camera-app and updated the link in the spreadsheet (also emailed to you) [15:08] Wellark: poke, you responsible for rtm landing 013? [15:08] trainguards: i have verified silo 009, but it seems the spreadsheet is out of sync: i can't mark it tested there, can you help [15:09] sil2100: did we get to the bottom of the unity instability yet? [15:09] it should correspond to line 28, for landing in vivid [15:10] it is also silo rtm 20 which is verified, but should *not* land on rtm [15:11] jdstrand: what version of click-apparmor should be in 14.09? [15:11] cyphermox: dunno [15:11] cyphermox: lemme check [15:11] Wellark: if you're not touching it then all is fine [15:12] cyphermox: tvoss is [15:12] but apparently he got ebola or something [15:12] I just want to make sure it doesn't clash with the vivid landing for other dbus-cpp fixes.. [15:12] cyphermox: other dbus-cpp fixes? [15:12] cyphermox: I don't even know how that should relate to them [15:12] http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=dbus [15:12] cyphermox: that branch fixes two top blockers [15:12] *silo [15:13] so we need them in [15:13] you can't build dbus-cpp separately and land one without telling someone about the other [15:13] ie. the second to land needs to get rebuilt [15:13] cyphermox: I'm not landing anything [15:13] ChickenCutlass: do you know that folks think that unity crashing might be media-hub related? [15:13] Wellark: that's all I wanted to know, thanks [15:13] cyphermox, thostr_: please figure out what to do with rtm-013 silo [15:13] asac: I asked kgunn yesterday and that was not the case [15:14] asac: and if it is. That is a real problem — how could that happen [15:14] thostr_: how ready are you changes to land? also, have they landed in vivid yet? [15:14] ChickenCutlass: i think its a different thread if media-hb can bring down unity, but still doesnt make it less important [15:15] ChickenCutlass: yeah, so theory is notifications are effectively audio clients, so create/kill...causes "left overs" to hang around on dbus [15:15] Wellark: cyphermox: this is tvoss... anyhow, I just started to rebuild as it had a strange build error... [15:15] at least the signature matches [15:16] cwayne: click-apparmor 0.2.11.2, apparmor-easyprof-ubuntu 1.2.38 and apparmor 2.8.96~2652-0ubuntu5.3 [15:16] for a fix that is comming from tvoss [15:16] kgunn: asac so that is not media-hub. That is prob the sbud client [15:16] right [15:16] ok [15:16] thostr_: so you're not driving the landing right now, just rebuilding out of interest? [15:16] ChickenCutlass: yeah...the bug currently reflects this theory/thinking [15:16] cwayne: your custom tarball will include the 'touch -t' change on /var/lib/apparmor/profiles/click_*? [15:16] kgunn: ok thanks [15:17] ChickenCutlass: people just aren't reading :) [15:17] lol [15:17] cyphermox: well, this might be the root cause also for the unity crashes we're seeing... so just trying to help while tvoss is away [15:17] alright [15:17] I think we should possibly look into landing this in vivid first... [15:19] jdstrand: yep, it will [15:19] nice [15:19] sil2100: ogra_: so all the bits for apparmor are ready, could we kick a build? [15:20] thostr_: can I ask you what crashes? there's other changes which might help too.. [15:20] sure ... sil2100 ? [15:20] Yeah, sorry guys, had lunch and then UE Live [15:20] ogra_, cwayne: looking at the backlog, but I think it's +1 [15:20] i just want a "yes" :) [15:20] cyphermox: it's still the issue of not having a dash [15:20] hum, what bug is that? [15:21] sil2100, apparmor needed in image before custom tarball can land [15:21] is there a stack trace on it? [15:21] thats what this build is for [15:21] cyphermox: https://bugs.launchpad.net/ubuntu/+source/unity-scope-scopes/+bug/1386653 [15:21] ogra_: yeah, as I thought [15:21] Ubuntu bug 1386653 in unity8 (Ubuntu) "Scopes fail to launch when the network stack is not up" [Undecided,Confirmed] [15:21] ah, thanks [15:21] dbarth: still having problems setting the silo to tested yes? [15:22] sil2100: yeah, i guess so [15:22] sil2100: i was trying to clean up the various silos i have around [15:23] sil2100: so if we take 020(rtm) and 009(utopic/vivid) [15:23] cwayne, sil2100 build triggered [15:23] sil2100: i'd like to delete 020(rtm) and land 009 [15:23] ogra_: thanks [15:23] davmor2: so once the build is done, would you still have time for custom test? [15:24] there were a few more changes that leaked in, but most are quite trivial [15:24] dbarth, sil2100: do you remember if a binary copy from the phablet-team PPA (for oxide-qt) is enough, or if a source copy is needed? [15:24] dbarth: ok, so delete 20 you say - let me free that up then [15:24] And check sil0 009 [15:24] trainguards: can I haz a silo for line 81, please? [15:24] oSoMoN: where do you want to land it? [15:24] sil2100: yup [15:25] sil2100, rtm [15:25] incidentally, oxide is now finished building in https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+packages [15:25] cwayne: in theory yes, as we are looking to use it to check for issues in the image but it depends how long [15:25] oSoMoN: if the phablet-team PPA oxide-qt has been built for utopic then a binary copy to the ubuntu-rtm silo should be enough [15:25] dbarth, which is why I was asking :) [15:25] it was for utopic indeed [15:26] nice, more silos ready [15:26] excellent, a binary copy will save us time (5+ hours to be precise) [15:27] dbarth: can you try changing the tested field now? [15:27] ok [15:28] marked tested, let's see what the bot says [15:29] === trainguards: RTM IMAGE 136 building (started: 20141029 15:30) === [15:29] sil2100: what needs to happen next for fixing bug 1339916 in ubuntu-rtm? [15:29] bug 1339916 in whoopsie (Ubuntu RTM) "SystemIdentifier can change between reboots" [High,Triaged] https://launchpad.net/bugs/1339916 === alan_g is now known as alan_g|tea [15:31] bdmurray, do you have a silo already with lxc-android-config in it ? [15:33] bdmurray: oh! Ok, let me help out with that landing, I think we forgot you didn't do any landings before :) So, that's a whoopsie upload + something else, right? [15:39] sil2100: yes, a whoopsie sync from utopic and an upload of lxc-android-config [15:39] Excellent [15:39] Preparing === alan_g|tea is now known as alan_g [15:44] bdmurray: now we need to upload lxc-android-config [15:44] bdmurray: can you check if you can upload to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-009 ? [15:46] sil2100: I don't see the "You can upload packages to this PPA using" message from Launchpad [15:47] hmmm... ok, then the easiest way would be for you to provide me a source package for lxc-android-config [15:47] And I'll upload [15:47] (since I have no power to grant upload powers) [15:49] make sure you use the lxc-android-config from rtm as base actually [15:49] rtm and utopic diverged [15:50] ogra_: right, you'd pointed me at rtm4 previously [15:51] :) [15:51] sil2100, ribru: can I have a rtm silo for line 81, pretty please? [15:52] oSoMoN: ok [15:57] trainguards: can you please publish silo 4 (vivid) ? [15:58] bfiller: can you arrange that the same camera-app being published from rtm-018 is uploaded as .click to the store? (I can also upload, if just given .click url) [15:58] oSoMoN: MP not approved [15:59] oh, it's "Merged". that should be pretty approved... [15:59] ogra_, are there no vivid images yet? ;| [15:59] how am I supposed to test anything... [15:59] ogra_: hey ogra, were there any vivid images yet? how about questions about whether there are vivid images? ;) [16:00] Saviq: he has had around 40 requests in 24h about the topic :) [16:00] ogra_, are there no vivid images yet? [16:00] 41 [16:00] Mirv, d’oh, I was pretty sure I had removed the MR from the list this morning, sorry about that [16:00] ogra_, are there no vivid images yet? [16:00] 42 [16:00] now that's a good number [16:00] Mirv, can we force the publication, or do I need to manually revert the state of the MR to "approved" ? [16:00] oSoMoN: we can force, no problem [16:01] Mirv, excellent, thanks [16:02] sil2100, Mirv, ribru: can one of you please do the binary copy of oxide-qt from https://launchpad.net/~phablet-team/+archive/ubuntu/ppa/+packages to ubuntu-rtm/landing-015 ? [16:04] * ogra_ throws little paperballs at Saviq and Mirv [16:04] i'm working on it ... [16:05] (should be ready later tonight ... no promise that they boot though ... there is a good bunch of systemd services now) [16:05] oSoMoN: done. required command line usage. [16:06] Mirv, thanks! [16:07] Saviq, there were build machine issues til late last night ... and today i already spent all day fixing up the build scripts ... but it will still take a while, each iteration of changes takes hours [16:09] asac, bug 1387231 [16:09] :) [16:09] bug 1387231 in Ubuntu Clock App "[clock] alarm still rings once it's been deleted" [Undecided,Incomplete] https://launchpad.net/bugs/1387231 [16:09] Mirv: hey, I top-approved the merge that wasn't approved yet in ubuntu silo 12 [16:10] Not build machine issues as such, I just didn't write the livefs copying script quite right (this was the first cycle we had to do this, since livefs-in-LP was new last cycle) and so the livefs objects had the wrong require_virtualized setting [16:10] plars, why are terminal and dropping letters still on the krillin dashboard? [16:11] cjwatson, yeah, i tried to simplify :) [16:11] I've since fixed the script so that this won't be a problem next time [16:11] issues with building on the wrong machine :) [16:11] Yeah [16:11] cyphermox: there's the other branch still https://code.launchpad.net/~thomas-voss/dbus-cpp/fix-1361642/+merge/236820 [16:12] AGH, people changed it [16:12] this is ridiculous [16:12] slap the people [16:12] :) [16:12] I'll just scrap that branch and make a new one [16:13] ogra_: thx. commented on it; i dont think it is mine though [16:13] mine is about disabling, not deleting [16:13] deleting helped/worked in the end [16:14] cyphermox, see line 55 on eth spreadsheet (and silo 13) [16:14] that was added [16:14] I'm getting tired of this [16:15] Mirv: you can scrap lines 74 and 75 [16:15] kgunn, there is a problem with silo 13 - it seems i can't get out of flight mode once i enable it [16:15] kgunn, on the bright side it makes the crashes go away! [16:16] brendand: sort of good news :) [16:16] there is a million of things in that silo [16:17] cyphermox: maybe just reuse the silos for the new branches? [16:17] a million ? [16:17] its like it is its own distro :) [16:17] Mirv: no [16:17] ogra_: you talkin' bout silo 13v? [16:17] cyphermox: ok. so, freeing up silos landing-012 and rtm-009 [16:17]