[00:00] Saviq: However, apt-get upgrade wants to update ubuntu-system-settings; maybe the archive rev is newer than the silo? [00:01] ToyKeeper, `apt-cache policy ubuntu-system-settings` then? [00:01] Saviq: I'm trying to make sense of it... something doesn't add up. [00:02] Looks like the silo URLs changed since I last updated my scripts. [00:06] May be a local issue, this DNS server is acting really weird. [00:13] Or perhaps something got corrupted here after a few shorts cut the power unexpectedly. This notebook started having physical problems about a week after the warranty expired. :( [00:13] Some programs are resolving hosts just fine, others can't do it at all today. This is new as of like half an hour ago. :( [00:35] ToyKeeper: yeah silo URLs haven't changed during the life of ci train as far as I know. except maybe when RTM was introduced, but not other than that [00:36] ToyKeeper: I had some DNS issues today myself, try uninstalling dnsmasq ;-) [00:37] This is really odd. I can resolve hosts with 'ping' but not 'telnet' or a bunch of other programs. [00:40] It seems like everything checks nsswitch, but some programs might be ignoring resolv.conf. [00:44] Nope, both are using resolv.conf. Nearly identical system calls, too. [00:50] In any case... [00:50] The Updates page works if I manually "apt-get install ubuntu-system-settings" with the archive enabled. [00:50] Unpacking ubuntu-system-settings (0.3+15.04.20150114.1~rtm-0ubuntu1) over (0.3+15.04.20150114~rtm-0ubuntu1) ... [00:51] With my dns issues I'm having some difficulty checking the revs against upstream though. [00:52] It seems to match what's in the PPA. [00:53] robru: I *think* everything is in order for the dep fix in the next rtm build. [00:55] ToyKeeper: I thought RTM was closed? [00:58] robru: Sanity failed due to the OTA issue, so we're trying to get a build with that fixed. [00:58] ToyKeeper: so nobody will yell at me if I publish this? ;-) [00:58] 195, 196, and 197 are all fail due to the same issue, and silo 3 appears to fix it. [00:59] We can't fully verify without a new build though, since it's just a dep change and the citrain tools don't handle that well. [00:59] Er, the silo tools, rather. [01:00] robru: So, 198 should end up being the promotion candidate. [01:00] ToyKeeper: ok, I published it. I guess we'll find out! [01:00] robru: If anyone yells at you, send them to me. QA is blocked until silo 3 is included in a build. [01:00] ToyKeeper: will do! [01:01] Would have been ready an hour ago, but my work notebook is having issues and I haven't had time to replace or fix it yet. [01:31] rsalveti: is rtm image building disabled in cron? if so can you kick an image build? [01:50] robru / trainguards: I set testing to OK for the autopilot sync, but I had the silo created last week, I presume that it's still good to land but I've been told I might need pmcgowan to ack it (as the gates are closed) [01:51] veebers: well it definitely needs qa ;-) [01:51] robru: ah ok, will check that out now [01:51] veebers: but yeah i won't publish it without an ack from management [01:52] robru: ack, for the record, it's a sync for what's in vivid (i.e. no extra fixes or features from vivid). I have included a test report in the comments of that spreadsheet line [01:53] veebers: ack [02:02] robru: sweet FYI I've emailed pmcgowan (I spoke to him last week about getting it started, just need the final ack from him http://pastebin.ubuntu.com/9753260/) [02:04] veebers: right. Once you get that and a qa ack i can publish it. [02:10] === IMAGE 66 building (started: 20150115-02:10) === [02:15] robru, so now that silo 3 landed, when will a new rtm image build? [02:16] kenvandine: i don't know ;-) i guess cron is disabled, asked rsalveti to kick one but he didn't respond. Can you kick it? [02:17] robru: I'm here now [02:17] it seems RTM build just started [02:17] from imgbot [02:17] i don't think 66 is rtm [02:17] sounds like vivid [02:17] oh, right, this is vivid [02:17] Saviq, was that dep removed from vivid too? [02:18] well, RTM is still in cron [02:18] i thought it would be disabled since it's frozen [02:18] In that case, it won't be built for ... ~3 more hours? [02:18] 02 3 * * * DIST=ubuntu-rtm/14.09 for-project ubuntu-touch cron.daily-preinstalled --live [02:18] does anyone know if vivid had the same package dropped? [02:19] kenvandine: sorry, which package? [02:19] qml-module-ubuntu-connectivity [02:19] unity8 dropped the depends [02:19] which dropped it from the rtm image [02:19] kenvandine: don't know for sure, but it should have... If somebody is landing things in rtm without landing in vivid first, that's naughty [02:19] which broke updates in settings and the telegram app [02:20] I'd expect the unity8 guys to land first on vivid, but yeah, would need to check [02:20] the real fix is to seed that package [02:20] that's what i'm worried about [02:20] i fear that image 66 building is going to break updates for people [02:20] kenvandine: qml-module-ubuntu-connectivity:armhf still installed on 65 [02:20] yeah... [02:20] but will it be in 66 :) [02:21] yup, just trying to understand :-) [02:22] kenvandine: system-settings depends on it [02:22] * kenvandine checks rdepends [02:23] in vivid? [02:23] i just added the depends tonight in rtm [02:23] to fix this situation [02:23] yeah, checking vivid [02:23] i have a branch adding the depends for vivid too [02:23] kenvandine: http://launchpadlibrarian.net/194911742/unity8_8.02%2B15.04.20150109.2-0ubuntu1_8.02%2B15.04.20150113.1-0ubuntu1.diff.gz seems fine? [02:24] Unless it was dropped in a previous diff [02:24] kenvandine: but system setting is already depending on it on vivid [02:25] hm, cron is still enabled but it didn't trigger the image [02:25] let me try one by hand [02:25] oh... great [02:25] and weird [02:25] in vivid settings has the depends [02:25] but rtm didn't [02:26] whew [02:26] vivid is safe [02:26] yeah :-) [02:26] we still need that package seeded instead of relying on this [02:26] robru: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch/ [02:26] click packages need it [02:26] new build in progress [02:26] yeah, usually recommended for qml-modules [02:27] it's part of the platform, so we need to seed it [02:27] rsalveti, when was the rtm image build started [02:27] ? [02:27] kenvandine: now [02:27] should I have waited? [02:27] nope... that's good [02:28] alright, should be done in ~1h [02:28] the package was just published less than an hour ago [02:28] so was worried the image started before that [02:28] great [02:28] thanks! [02:28] i'm off then... whew [02:28] good night all [02:28] good night! [02:29] rsalveti: thanks! [02:29] np [02:29] kenvandine: good night [02:30] === IMAGE RTM 198 building (started: 20150115-02:30) === [02:31] there you go [03:35] === IMAGE 66 DONE (finished: 20150115-03:35) === [03:35] === changelog: http://people.canonical.com/~ogra/touch-image-stats/66.changes === [03:50] === IMAGE RTM 198 DONE (finished: 20150115-03:50) === [03:50] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/198.changes === [04:13] ... and there it goes. [06:11] ToyKeeper: any luck? [06:12] robru: Er, I had a couple interruptions, but sanity on 198 is going well so far and the issue we tried to fix seems to be fixed. [06:13] Whatever the reduced-battery-life thing is though, I think it's still present. [06:13] That's the only big thing I expect to come up during testing. [06:13] ToyKeeper: ah ok, glad to hear the dep issue is fixed [06:23] TBH, I still think 184 was probably better, since it had the battery life thing fixed and was thus generally more reliable. [08:45] davmor2: what's the problem with the new RTM images? [08:46] sil2100: I've been online for 2 seconds I've not seen the new one, 195 unity8 drop a communication dependency that some of the rest of the system actually depended on which meant ota was broken as far as I know 198 passed sanity on krillin [08:47] sil2100, there is no problem with 198 AFAIK. Did you hear of any problem? [08:49] davmor2, jibel: no no, I was just wondering if the 'do not upgrade' message is still valid [08:50] sil2100, I didn't try an upgrade from the UI with 198 but at least the page is not blank anymore [08:58] davmor2, jibel: if all is fine, I guess sending an e-mail to the ML would be a good idea [08:59] Since people might still think that upgrading to the latest RTM image is a bad idea [09:03] Saviq: thanks for sending the update e-mail [09:03] sil2100, sure [09:06] Hi there, any CI issue to report ? [09:06] davmor2, your MTA hates me: : Relay access denied [09:08] Saviq: that doesn't surprise me :D [09:11] davmor2, you configured it to hate me?! [09:11] dammit, i have the broken image on my krillin. [09:16] popey, if rw, just apt-get install qml-module-ubuntu-connectivity [09:16] popey, otherwise ubuntu-device-flash [09:16] i dont have rw [09:16] yeah, using u-d-f [09:16] thanks [09:16] popey, system-image-cli from the command line works too [09:20] jibel: nope, it didnt here [09:20] tried twice [09:20] popey, oh really, that's how I upgraded. What doesn't work? [09:20] it didnt upgrade [09:21] popey, and what does system-image-cli -n says? [09:21] too late now, I'm running u-d-f [09:21] k [09:22] Saviq: update of a bunch of low level stuff on my server [09:22] my krillin is taking a loooong time to u-d-f [09:23] unxz taking a while. [09:23] [09:26] Saviq: it should like you again now :) [09:28] popey, when was last update of the clock app? [09:28] before xmas [09:30] We should push a new version to the store as there's updated translations which could go in [09:30] there is a problem wth repeating alarms; not sure it is the clock app or something else [09:31] davmor2 just confirmed it [09:31] davmor2, I'm filing a bug [09:31] ok [09:38] good morning [09:38] trainguards, i need help reconfiguring silo rtm-011 (line 36) which i took over from pstolowski to add the missing OA branch === greyback__ is now known as greyback [09:47] sil2100, davmor2 bug 1411171 [09:47] bug 1411171 in Ubuntu Clock App "Repeating alarm disabled after it went off once" [Undecided,New] https://launchpad.net/bugs/1411171 [09:47] davmor2, can you confirm it. [09:51] jibel: technically we'd need to keep it up till tomorrow to see if an alarm goes off would be nice if we could repeat minutely somehow even if it was mocked I'll have a word with charles when he gets on [09:51] can you not fake the date on the device? [09:51] davmor2, you're technically right but the fact that it's disabled is wrong [09:51] date -s [09:52] popey: hmm [09:53] popey: would that do time too as It would need to be set again before the alarm [09:53] phablet@ubuntu-phablet:~$ date [09:53] Thu Jan 15 09:52:38 GMT 2015 [09:53] phablet@ubuntu-phablet:~$ sudo date -s "Tue Jan 13 09:00:00 2015" [09:53] [sudo] password for phablet: [09:53] Tue Jan 13 09:00:00 GMT 2015 [09:53] phablet@ubuntu-phablet:~$ date [09:53] Tue Jan 13 09:00:05 GMT 2015 [09:53] yes :) [09:53] popey: that might be the way to do it then [09:53] and the clock just jumped to 9am http://people.canonical.com/~alan/screenshots/device-2015-01-15-095247.png [09:55] I'll give it a go in a minute [09:55] k [10:06] davmor2: also need to switch off network time updates in system settings of course! [10:06] :) [10:06] popey: or set it a minute before [10:09] jibel: popey: alarm 1 pass === chihchun is now known as chihchun_afk [10:09] hey trainguards, can you help me with line 36? ^^ [10:09] dbarth: hey! What's up? [10:10] jibel, popey: alarm 2 goes off too so it is just disabled in the clock app [10:10] Ah [10:10] dbarth: on it! [10:13] dbarth: done [10:13] * sil2100 needs to fix his irssi highlights [10:19] brb [10:21] sil2100: ty [10:38] davmor2, yes I did that test too. *Just* the status in the clock app is wrong [10:40] jibel: davmor2 indeed, I can't reproduce here, added comment and screenshots to the bug 1411171 [10:40] bug 1411171 in Ubuntu Clock App "Repeating alarm disabled after it went off once" [Undecided,Confirmed] https://launchpad.net/bugs/1411171 [10:48] popey: let the date and time reset and try it again after the first none modded time it is disabled in the alarms page but the next alarm goes off as expected [10:51] how are you defining "disabled"? [10:52] aha, now it's flipped to disabled. [10:52] popey: instead of the alarm tab being green tick in the alarm page it is grey cross instead [10:52] ok, updated bug [10:52] http://people.canonical.com/~alan/screenshots/device-2015-01-15-105126.png [10:52] like that? [10:53] popey: yeap [10:53] kk [10:53] popey: the concern then is if you turn that back does it then disable it in EDS === chihchun_afk is now known as chihchun [12:03] fginther: hi! any news regarding the lp:pay-ui autopilot tests in jenkins? === MacSlow is now known as MacSlow|lunch === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === alan_g is now known as alan_g|lunch === chihchun is now known as chihchun_afk === MacSlow|lunch is now known as MacSlow === alan_g|lunch is now known as alan_g === chihchun_afk is now known as chihchun [13:33] cihelp: can someone see why jenkins didn't trigger on https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/Default-View/+merge/246564 ? [13:51] alecu, My first attempt at enabling the pay-ui tests ran into a problem where the existing test runner can't find the tests. So we need to figure out what's going on. I don't expect it to be a big problem, just need to dig at it. [13:51] alecu, I'll make a note in the request to keep you updated on progress [13:51] fginther: great [13:52] fginther: btw, where is the test runner expecting the tests to be? [13:52] fginther: I use "make autopilot" when running them from my working branch [13:53] fginther: so perhaps the test runner uses a different mechanism? [13:57] alecu, it looks under tests/autopilot which matches pay-ui. So maybe I'm mis-interpretting the error. We'll just need to investigate what's actually going on here. This is still using the 'old custom' test runner and not the adt-run method so it's a bit clunky to get it working sometimes [13:57] alecu, In the future when things get switched over to using adt-run, these issues should no longer occur [13:59] fginther: ack. So thanks for working on that, and please let me know if I can be of any help (ie, by taking a look at those errors too). === chihchun is now known as chihchun_afk [14:00] popey, looks like jenkins was running that MP while you we're asking the question :-) [14:02] fginther: awesome === seb128_ is now known as seb128 === alan_g is now known as alan_g|afk [14:26] o/ Will publish once I'm back from lunch [14:27] trainguards ^^ Can you spare a silo please? [14:34] trainguards: sorry i need a reconfig again (missed a branch) for silo rtm-011 (line 36) [14:37] trainguards, silo for line 88 please :) === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [14:52] any trainguards around? [14:57] bfiller: for the reject with a message dialogue is the calling phone meant to be hung up on or redirected to answering machine? From the description it sounds like hung up not redirected? [15:05] sil2100: you back maybe? [15:12] dbarth: yeah, but having ISP problems [15:12] dbarth: give me 5 more minutes [15:12] sil2100: uh, sorry [15:12] sil2100: sure, nw [15:13] i'm sorry for the multiple reconfig requests; we didn't get all our ducks in a row in the first place [15:14] Ok, finally I have my DNS back [15:17] Saviq: assigned, but be aware that 000 already has qtmir in it! [15:17] sil2100, ack [15:19] dbarth: Im still having internet problems, might have to reboot my modem once again [15:19] Let me reconfigure for you when Im able [15:21] Phew, ok, nevermind, seems to be good now again [15:21] :) [15:21] * sil2100 hates his ISP [15:22] dbarth: ok, should be reconfigured now - is there anything else I can help with? :) [15:23] davmor2, jibel: how are things looking so far? [15:23] sil2100: like a giant spread sheet [15:24] ...badly? [15:25] sil2100: no just a giant spread sheet ;) looks to be on par with the last image I think at least with the tests I've covered [15:25] sil2100: thanks! it rebuilds now [15:27] sil2100, vivid/018 reconfigure please, added -gles [15:28] Saviq: sure ;) [15:29] sil2100, I try and remember to add it to Sources to start with, but as evidenced, try != do [15:30] davmor2: how about the power-dialog-on-resume bug? [15:30] davmor2: does it seem fixed? [15:30] sil2100: I've not seen it but I haven't tested for it jibel ^ [15:31] Saviq: ah, nifty hack! Well, we could actually make the train more aware of the -gles counterparts and maybe allow the addition of such without a reconfigure [15:34] sil2100, TBH not sure why landers can't just reconfigure as they please (at least for non-conflicting changes) [15:44] sil2100, I didn't reproduce with 198 for the moment. [16:09] trainguards can you retry publishing L52 (silo 12) [16:09] alex-abreu: looking [16:10] Doing! [16:10] sil2100, thx [16:10] alex-abreu: hm, https://code.launchpad.net/~dbarth/ubuntu-html5-theme/remove-cordova-2.8/+merge/242515 seems superseeded [16:10] I think you'll have to reconfigure the silo, rebuild and retest [16:11] sil2100, I rebuilt the silo w/ the new MR (there was a resubmit) [16:11] Since it's built against this older branch which doesn't seem valid [16:11] hmmm [16:11] The train is confused then [16:11] sil2100, yeah seems like it [16:13] sil2100, so I just updated the previously listed MR (the one superseded) w/ the new MR (for which the content hasn't changed), and triggered a rebuild which seems to have completed [16:13] alex-abreu: did you reconfigure after adding the new MRs? [16:14] sil2100, ah no sorry [16:14] alex-abreu: since I see CI Train is not aware of the branches and it didn't build those because of that [16:14] alex-abreu: ok, reconfigure the silo then and rebuild/retest (sadly...) [16:15] sil2100, right, doing it now :) [16:20] Saviq: I agree, we should consider loosening the restrictions on silo reconfigurations. I honestly don't recall a time when somebody asked me to reconfigure something and I had to say no because it was a problem. seems fine to just let people reconfigure as they please [16:21] robru, we try to be reasonable after all :) [16:22] I know there's reasons why you can block publishing, maybe even assignment, but once we have a silo... [16:23] Saviq: yeah I think we should loosen the restrictions on assignment, too ;-) Like I think conflicts should just be a warning, not to actually fail the assignment over that. [16:23] +1 [16:28] In the airline things like that will be completely automated anyway, so anyone will be able to build anything anyway [16:28] sil2100: slangasek: can you guys confirm you now have access to stg-ue-ci-train as per https://rt.admin.canonical.com/Ticket/Display.html?id=77996 ? [16:28] sil2100: yes but how long do we have to wait for that? ;-) [16:30] davmor2: declining the call from the quick reply will make the calling phone go straight to voicemail [16:30] bfiller: thanks for the confirm [16:31] robru: not sure, I expected the airline to fly my packages half a year ago! [16:34] robru: yep, got all the access I need [16:36] robru: confirmed, I have access [16:37] sil2100: slangasek: great, thanks for checking [16:54] sil2100, are you checking silo 12? [16:55] alex-abreu: it's done ^ [16:56] sil2100, oh thank you [16:56] ;) [17:23] holy spit, 28 silos in use [17:32] It's over 9000!! [18:03] charles: ping [18:03] sil2100, pong [18:03] charles: hey, how's the work going on #1411171 ? You think we can get a fix for that pretty soon? [18:04] sil2100, I should know more in about half an hour [18:04] sil2100, it's top of my list right now [18:06] Thanks! [18:29] trainguards silo 018 ↑ please [18:29] o/ [18:30] Saviq: please approve gles branch! [18:30] ;) [18:30] oh crap [18:30] will I never learn [18:31] sil2100, done [18:38] sil2100, jibel, wrt 1411171: can reproduce it, found the bug, working on a fix [18:39] charles: good news! [18:49] sil2100: slangasek: Ursinha: are we on for the meeting today? I wouldn't mind a bit of a sync up [18:50] robru: yep. is sil2100's Internet any better now? [18:50] robru: I can do that, nothing special to report though === alan_g|afk is now known as alan_g [18:51] slangasek: I might try, but still getting waves of internet [18:52] Ursinha: I would like to talk about next steps for the ticket system transition, and figure out if we can drive this from the Foundations side [18:52] sil2100: probably preferable to particles of Internet [18:53] lol [18:54] slangasek: you well know the internet is a wave/particle duality! [18:55] slangasek: can you elaborate? I don't think we're just talking about a deployment here for the ticket system transition to consider that work complete [18:55] ev: join the meeting perhaps? I think that's exactly what we want to discuss. [18:56] ev: ok, so what are we talking about? As I understand it this project has been sidelined now mid-effort; I want to know what's required to get it done [18:56] ah, that can definitely be established by looking at the backlog for the FO01 tasks [18:56] https://trello.com/b/PrlDYfxX/ci-engineering-team-backlog [18:58] ev: that board is hard to read for the uninitiated. all I gather from that is that "spreadsheet replacement" is "ready" [18:59] oh, there's a huge scrolling list of stuff. hm [18:59] robru: I can fix that :) [18:59] slangasek: I need to venture in the direction of home and make dinner, but I'll be back online after. Let me know if there's anything more you need to understand the state of this and what can be done to bring it to completion. [18:59] by explaining what is what [18:59] Ursinha: explain in the meeting so we all benefit ;-) [18:59] :) [19:07] Waave [19:07] Ok, phew, back [19:09] Aw come ooon... [19:33] bregma: ping! Please approve your unity branch: https://code.launchpad.net/~3v1n0/unity/lim-visibility-fixes/+merge/245189 [19:33] (I suspect it's already reviewed) [19:36] sil2100, done [19:37] jibel: hey, just a quick question - did you check if a revert helps with fixing the alarm bug? Or we'll do that after testing finishes? [19:37] sil2100, I did, and it is not reproducible with previous version. it's on the buig report. [19:37] bug* [19:38] jibel: thanks! [19:42] sil2100: will be waiting for the i-dt fix for the alarm bug? or reverting? [19:42] I would hate to hear a revert since it brought in a lot of critical bug fixes [19:43] nik90_: a revert would re-introduce bug LP: #1362341, which the product team also thinks is a serious issue [19:43] Launchpad bug 1362341 in Ubuntu Clock App "OneTime alarms are not automatically dismissed or delete after they are triggered" [High,Confirmed] https://launchpad.net/bugs/1362341 [19:43] Which we would not like as well [19:43] sil2100: it would also bring back https://bugs.launchpad.net/ubuntu-clock-app/+bug/1387231 [19:43] Launchpad bug 1387231 in Canonical System Image "[regression][clock] alarm still rings once it's been disabled or deleted" [High,Confirmed] [19:43] which is very critical [19:44] So it's either whitelisting (bleh) or waiting for the fix [19:44] charles is on it already, but not sure how much more work will be needed here [19:46] yeah [19:46] sil2100: I will help him out in any way I can and coordinate with him [19:46] sil2100, MP'ing now [19:53] sil2100, jibel, nik90_, davmor2: https://code.launchpad.net/~charlesk/indicator-datetime/lp-1411171-strengthen-recurrence-rule-test-rtm-14.09 [19:57] charles, nice, tell me when it's in a silo, I'll help with the verification if it's not too late. [19:57] ack [20:12] charles: column F needs to be a merge proposal [20:12] robru, ack [20:12] charles: unless you're just no-change syncing from vivid, then that's something else [20:13] charles: waiting on a deb package to be built by jenkins. I can then install it to test [20:14] yay low battery not cropped done :) [20:14] robru, no, MP added [20:15] davmor2, nice. when did that get fixed? [20:15] no idea but I see a battery here :) [20:16] charles: alright, rtm 15 [20:17] jibel: ^ [20:45] silo 15 will never start to build or what :( [20:49] jibel, doesnt someone need to tell it to [20:49] charles, ^^ [20:50] no idea [20:55] robru, ^ [20:55] charles: just leave 'packages to build' blank on the build job. your input was invalid [20:56] robru, ok [21:34] rtm 15 wfm, both on repeating and nonrepeating alarms [21:35] charles, sil2100, pmcgowan, jibel, popey: silo 15 fixes the alarm regression spotted early this morning. I just tested and confirmed the fix on N4. Jibel, feel free to test and approve as well. [21:36] nik90_, awesome thanks [21:47] pmcgowan: should I publish that then? [21:48] robru, we should really get a qa signoff was trying to find someone [21:48] pmcgowan, robru I just did [21:48] aha [21:48] there he is [21:48] robru, you can publish. I verified non repeating and repeating alarms and it's OK [21:49] thanks jibel [21:49] jibel: pmcgowan nik90_ charles: great thanks, will publish [21:49] \o/ [21:49] then we would like an image I suspect [21:49] yes [21:49] yay! [21:49] best image ever [21:49] :) [21:50] best clock ever [21:50] :P [21:58] robru, pmcgowan ^ rmadison agrees with the bot. Now we need someone to build an image [21:59] I dont have those powers [21:59] jibel: robru: I may kick off an image if necesary [21:59] sergiusens, ^ [21:59] whoa whoa [21:59] it's just in proposed! [21:59] that's the usual image kick on the tracker? [21:59] cyphermox: wait for it to land first? ;-) [21:59] robru: of course [21:59] I know ;) [21:59] ah, it's slow :) [22:00]