[00:15] rsalveti: mediaplayer still crashing: http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4525/mediaplayer-app-autopilot/ [00:16] plars: that's because we didn't yet merge https://code.launchpad.net/~robru/mediaplayer-app/fix-1231418/+merge/188502, to disable it [00:16] plars: scene selector is not supported at the current version, but the test is still there [00:16] fginther, hey, the message at the end of https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-maguro/1850/testReport/junit/mediaplayer_app.tests.test_player_with_video/TestPlayerWithVideo/test_scene_selector_visibility_with_touch_/ feels very strange [00:17] fginther, according to thomi 1.2 was last used on precise [00:17] fginther: it's *aaaaaages* old :) [00:18] a rerun proved it to be a casual thing, but still brings in some worries [00:18] ah, ok [00:19] sergiusens: https://code.launchpad.net/~sergiusens/phablet-extras/qtmultimedia-touch-quick/+merge/188962 please only add quick for the mir case [00:19] sergiusens: there's another block bellow, mir: { [00:20] with a QT += opengl [00:20] add it there [00:21] rsalveti, rar, ack [00:21] rsalveti, switching channels are we? [00:21] sergiusens: just used the wrong one [00:22] as you were talking here [00:22] too tired as well haha [00:22] rsalveti, I'm everywhere :-P [00:27] rsalveti, being pushed [00:27] rsalveti, pushed [00:31] sergiusens: thanks [00:31] rsalveti, what's the equiv of bzr push --overwrite btw? [00:31] sergiusens: with git? [00:31] rsalveti, yeah [00:31] sergiusens: git push -f [00:32] rsalveti, ty sir [00:58] sergiusens: added your lxc-android-config change to https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdGNWb0tTVmJLVzFZd0doV3dVOGpWemc#gid=0 [00:59] sergiusens: now to hope people can agree that this can land tomorrow [01:01] rsalveti, well it avoids races ;-) just add that ;-) [01:04] veebers: yeah. its a ro image where we enable developer-mode. [01:04] and then install the unity8-autopilot package [01:04] doanac: understood, cheers [01:23] thomi, ping [01:23] fginther: hey [01:24] thomi, regarding the 1.2 protocol issue sergiusens brought up. which side is using 1.2? [01:24] fginther: the backend driver - I guess libautopilot-qt [01:25] in fact, '1.2' means 'unversioned', since we only started versioning it in 1.3. AP assume that anything unversioned is '1.2' [01:25] thomi, thanks, I'll see if I can find any evidence along those lines [02:04] starting new build, which should include the regression fix for ringtone/sms notification sound [04:02] fginther: still awake? [04:03] is anyone here able to spin us a custom phablet image with new mir, unity-mir and platform-api? [05:04] ogra_: lool: 78 is looking good, it's expected to have at least one failed test with mediaplayer-app, as scene selector is not supported anymore [05:05] we have a pending MR to fix that: https://code.launchpad.net/~robru/mediaplayer-app/fix-1231418/+merge/188502 [05:41] Mirv: hey, how are you? [05:41] didrocks: morning, fine, bit more normal day today [05:41] heh ;) [05:41] didrocks: ui toolkit is no good at the moment, I'm now testing the qtdeclarative separately [05:42] Mirv: ah ok ;) good that you detected this! [05:42] Mirv: can you please try to release all the rest that we can? [05:42] (if sil2100 gave some instructions) [05:42] I think we're going to publish the current image [05:43] I haven't received anything from sil2100 [05:43] and he didn't write anything on the spreadsheet? [05:43] * didrocks checks [05:44] to the libusermetrics that there's some AP tests problems he's having, on the unity-scope-home there isn't anything I think [05:44] Mirv: can you look at libusermetrics? The tests will take 5 minutes I guess [05:45] didrocks: yeah, I can stop this declarative testing for a bit and test it instead [05:45] Mirv: thanks, just do in whatever order you want [05:58] on the dashboard, http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/ what does the build number mean? [05:58] for example 78:20131003:20131002.1 [05:58] there are 2 build ids in the string [05:58] ..03 and ...02.1 [06:18] Mirv: once you are done with the current ones, let's discuss about the Mir thingy (give me a head's up) [06:18] jibel: oh interesting, it was always the same ones repeated before [06:19] jibel: TBH, I don't know :/ [06:21] didrocks, sorry :) also sometimes people speak with image number (77,...) and sometimes in build number 20131003,... is there a way to know which correspond to what [06:21] jibel: oh, for that one, sure [06:21] jibel: so basically 20131003 is the ubuntu part [06:21] for example in media-info I can find the build id but don't know to which image number it corresponds [06:22] (containing only the android bits) [06:22] when you merge it to the android part (which can change even if you didn't rebuild any ubuntu part), you get the real "id" for the image [06:23] which are those numbers, 76, 77… [06:23] to find them, they are in front in the dashboard [06:23] this is how you can spot them :) [06:23] 78:20131003:20131002.1 -> image 79 [06:23] oupss [06:23] 78:20131003:20131002.1 -> image 78 [06:24] didrocks, so in summary, when plars sent a message with tests results for image 77, I must go to the dashboard to know that 77 is 02.1, correct? [06:25] jibel: right, we should promote this number as well, it's the real uid for the image [06:25] thanks [06:26] jibel: just be warned, you can have 2 images with 02.1 [06:26] like 77 and 78 can be 02.1 [06:26] if we just rebuild the android part [06:26] understood. [06:29] jibel: so, we are going to have Mir fixes today [06:29] we'll probably need the same round of testing than yesterday [06:30] didrocks, good, I'm continuing manual testing of MIR anyway [06:30] and found other issues, like pip not working for pinned app, and details like this [06:31] jibel: well, if only we had some "details" to fix like that, I would be happy [06:31] * didrocks just locked his phone again [06:32] high CPU usage under MIR is a killer. unity8 never goes below 100% [06:35] jibel: I put it as a showstopper yesterday but management disagreed [06:44] Mirv: FYI, I just prepare (merging, updating config and kick a rebuild) to be ready for the new Mir stack [06:46] didrocks: ok, thanks. still takes a bit of time before I'm ready for that. [06:46] Mirv: yw! at least, it should be built by then, so less wait :) [06:46] Mirv: as upstream don't merge the build-dep bump, everytime I'm doing that myself FYI [06:47] (the upstream merger can't merge because the new Mir version isn't there) [07:03] Morning! [07:04] didrocks: why hud got marked as FAILED? I still see the sync request on the unapproved queue... [07:04] didrocks: ok, could you sponsor lp:~kubuntu-packagers/kubuntu-packaging/qtdeclarative-opensource-src_5.0.2 ? all tests pass, and I also received separate testing from Chris Wayne / Matthew Fischer that they are very happy with its fix [07:05] hey sil2100! [07:06] sil2100: hum, but you told that some AP tests were failing, right? [07:06] Mirv: \o/ [07:06] didrocks: yes, but it wasn't because of HUD - as I had the same problems and couldn't really get any solid results when using vanilla 75 ;) [07:07] didrocks: all was ok on image 70 with the new hud [07:07] sil2100: ah ok, please change the status then [07:07] didrocks: I'll try to bisect as ogra_ advised what's wrong that 75 suddenly 'burps' [07:08] Mirv: did you start on the home scope? [07:08] didrocks: not yet [07:08] didrocks: libusermetrics now in archive [07:08] sil2100: look at the latest results, all is green, so you should just reflash with that one [07:08] Mirv: \o/ [07:08] ok, so now that sil2100 is here, let's sum up [07:08] Mirv, didrocks: wasn't robru supposed to do that? [07:08] sil2100: it's marked to you only in the chart at least [07:09] didrocks: reflashing then \o/ [07:09] sil2100: he was… apparently, he couldn't get his laptop working and so, he didn't process anything [07:09] sil2100, i cannot access launchpad all day, so I can't install anything from PPAs, so I can't test anything before publishing. I emailed you about this. [07:09] Mirv: hum, yesterday it was marked for robru, as I gave it to him since he didn't have any tasks [07:09] Mirv: yeah, but I ask robru to coordinate with sil2100 on his end of day [07:09] robru: is it better now btw? [07:09] I could run the scope-home unity7 tests, although I need to switch to a different machine then for working (which is still ok, I've a spare one) [07:09] robru: ah! Ok, didn't open my mail yet ;) ACK [07:10] I've at least a known-good unity7 test machine here [07:10] or you can't still access to LP? [07:10] Mirv: great ;) [07:10] so what I propose [07:10] Mirv -> home scope [07:10] Reflashing the device [07:10] sil2100: apparently AP has some fixes, so worth another try [07:10] didrocks, hum, no, still bad. I opened an RT for it, and I'll ping #is in the morning. [07:10] didrocks: you mean the new AP? [07:10] robru: ok, good luck [07:11] sil2100: yeah, new AP /!\ look at your emails, I forwarded to you. There are 2 projects that needs some additional merging [07:11] sil2100: ignore the toolkit one anyway (maybe it should just be merged), as Mirv tested, it's not a good shape [07:11] Mirv: I think you pinged pustream btw about the sdk? [07:11] and then, Mirv -> Mir once built [07:12] didrocks: ok, home scope. sdk upstream knows about the issues, yes. [07:12] Mirv: have you opened a bug? (some upstream wants paperwork to tack) [07:13] track* [07:13] didrocks: well hmm, it's more like 'it's all broken' (some mainview issue as indicated by zsombor), but yeah I'll file a bug as well [07:13] Mirv: all? waow ;) [07:14] ah, I guess sil2100 edited the wrong line [07:14] the sdk "FAIL" one instead of the hud [07:14] * didrocks fixes [07:14] didrocks: well the toolkit's own tests pass, but apps AP:s break quite badly [07:15] interesting [07:15] Mirv: anyway, thanks for spotting/testing carefully ;) [07:19] sil2100: FYI for your AP problems, please make sure you wait after boot until the nautilus windows pops up for Nexus. at that point the connection breaks so if you started phablet-test-run before, it won't work. also note the home screen unlocking needed mentioned by ogra. [07:19] :| [07:19] Missed the rows it seems... [07:20] didrocks, sil2100, Mirv: is powersaving still broken in desktop xorg? I remember that being broken ages ago but I just now noticed that my screen has been on all evening after many hours of inactivity... [07:20] Mirv: I'm running it clean through SSH, so I'm always unlocked - and the tests were running, but suddenly after a while either unity8 or autopilot itself hangs up on dont-know-what and waits indefinitely [07:20] Unable to being properly killed [07:21] robru: hum, working here, would worth trying to kill g-s-d and get it restarted [07:22] sil2100: you shouldn't run it through SSH but use phabllet-test-run [07:22] yeah [07:22] phablet-test-run is the way to go [07:22] like phablet-test-run -p -n [07:22] (/!\ -p should be before -n) [07:23] I tend to run non-unity8 AP:s without -n, and unity8 with -n, seems to work [07:23] Mirv: last time people told me not to use phablet-test-run for normal tests [07:23] Mirv: yeah, I don't really know about the magic, I just know the infra always use -n from what I heard [07:23] Damn, I think my Nexus got bricked? [07:23] sil2100: reflash with --no-backup (will erase the whole config) [07:24] sil2100: hmm, I've never heard that [07:24] didrocks: I tried to use -n always, but most tests were failing then [07:24] weird, not the case for me :/ [07:24] sil2100: phablet-flash ubuntu-system --channel devel-proposed -b [07:24] Mirv: with --no-backup [07:24] Mirv: will it work when it's stuck on the Google screen? [07:24] ah, maybe that's -b [07:24] sil2100: if you can adb shell, yeah [07:25] Yeah, busybox [07:25] ok, -b implies --no-backup [07:25] didrocks: bootstrapping (-b) wipes out everything anyway, it's even more powerful than --no-backup [07:25] sil2100: when stuck on the Google screen, the trick I use is to reboot in recovery mode. From there, phablet-flash find its way [07:25] yep [07:25] ERROR:phablet-flash:Unsupported device, autodetect fails device :o [07:25] vila: will try that [07:25] why would you run app tests with -n, it stops unity8 and running apps without it is not the way users do [07:26] sil2100: yeah, you need to specify -d mako then [07:26] sil2100, add -d [07:26] (IIRC, you have a mako) [07:27] sil2100: and I don't even use -b nor --no-backup (it's hard enough to retype the contacts I forgot to transfer to the sim before cutting it into a nano sim that I haven't tried hacking to put it back in my other phone, sorry this parenthesized stuff is getting far longer than expected ;o) [07:27] jibel: well, seems that upstream design AP tests without the shell running, and that's why you get more failures than the infra does [07:27] vila: it's better to do run with --no-backup at least [07:27] like you detect more issues [07:27] vila: right now I only use it for testing purposes, so I only have the WiFi password on it - so I'll bootstrap it from 0 I guess [07:27] like 4 images ago, all the crashes was due to having a fresh user [07:28] so it's not the same testing without --no-backup [07:28] didrocks, you're not doing integration tests then [07:28] didrocks: /me nods [07:28] jibel: well, tell that to upstream :) [07:28] jibel: I don't deny it at all, just telling what's the current situation [07:28] didrocks: but it's a trade-off, I try to use it as my main phone [07:28] I hope you can convince them ;) [07:29] vila: yeah, but be aware that's not what we should do in that team as we need to ensure people flashing their device can at least having application starting :p [07:29] which wasn't the case if you start fresh in that example [07:29] jibel: do you know if anyone apart from lool can promote an image? [07:30] (lool will be around later today) [07:30] didrocks: understood, but I know some other people are testing this way, variety is important for testing too [07:30] didrocks, no idea [07:30] vila: yeah, but we at least need some people testing it the "fresh way" as well [07:30] didrocks: that's sad, since last time I heard they said they only used -n for the unity8 tests - didn't remember they did it for all of the tests ;) But I might have misunderstood? [07:30] vila: I don't think we support migrations yet [07:30] sil2100: well, that's what I heard, I didn't look at the utah code [07:30] jibel: ok, we'll wait for him I guess [07:31] sil2100: flashing working? [07:31] didrocks: unity-scope-home seems to require newer libunity as well (libunity-protocol-private0) [07:32] diff being http://bazaar.launchpad.net/~unity-team/libunity/trunk/revision/299 [07:32] didrocks: it seems to proceed this time, phew [07:33] I don't see how the protocol-scope-discovery.vala change relates the the commit comment though [07:33] Mirv: ok, feel free to test with it (but please do some unity7 testing a little bit more rigourusly then) [07:34] hum, 7.1.1 [07:34] Mirv: don't we have 7.1.2 already? [07:34] Mirv: let me look at the home scope code [07:34] didrocks: yes, the actual package dependency is protocol-scope-discovery.vala [07:34] I mean, >= 7.1.2+13.10.20131002.2 [07:35] Mirv: oh, you're right [07:35] Mirv: ok, please try with both (and only those) [07:35] just ensure we don't regress unity7 in particular :) [07:36] sil2100: to prepare and test AP, should be stage one version in the ppa or you want to build trunk yourself? [07:38] didrocks: I see some autopilot package in the daily-build PPA right now - it's not the trunk version that needs testing? [07:40] sil2100: it's the trunk version we want to test (see the email I forwarded to you as well) [07:40] + some additional fixes in some packages [07:43] * sil2100 wonders why the merges didn't get top-approved yet [07:43] sil2100: I think that they are failing without the new AP [07:43] so chicken and egg issue [07:43] (or no backward compatibility) [07:44] didrocks: I know, but even the autopilot branch didn't get top-approved, and CI only had success on it [07:44] argh [07:44] veebers: around, do you know why? ^ [07:45] veebers, thomi: ^? It's approved 2 times but not top-approved, I don't see a reason for that? [07:45] https://code.launchpad.net/~veebers/autopilot/fixing_backend_being_none/+merge/188762 [07:46] didrocks: to test I would have to build this branch locally anyway [07:47] sil2100: yeah, please do then, sorry for the additional work :/ [08:00] rsalveti: lool: sorry for the noise, but yeah those changes are correct. (the target was not reliable & relies on internet access which fails on the buildds so I did back that out.) [08:00] git log, will clearly state that I did intentionally reverted. [08:02] didrocks: will take a moment as my armhf building is not top-speed [08:03] sil2100: hum, not sure you need to build on armhf [08:03] sil2100: for autopilot at least [08:03] they are all arch: all, no? [08:03] No, autopilot-touch is any [08:04] yeah, it's a mistake btw [08:04] seems it's just a metapackage [08:04] But it's finishing now ;) [08:04] ah,but there is a dep [08:04] anyway, ok ;) [08:04] sil2100: so, I would say: try everything that doesn't need a patch [08:04] if they pass, then, try the last 2 ones :) [08:04] (I guess sdk and unity) [08:17] didrocks, i'm partially around atm, in case you want to have 78 released (after manual call tests) [08:18] (for the next hour or longer) [08:18] ogra_: oh please please! :) [08:18] ogra_: promote it! [08:18] (I dogfooded it this morning) [08:18] didrocks, did someone do call/sms tests ? [08:19] I don't think about that one, popey around? ^ [08:19] ogra_: I don't have a sim card :/ [08:19] (incoming calls and sms, do they produce sound ?) [08:19] right, so lets wait for popey to do one :) [08:19] ya [08:19] (yeah, they are supposed, the fix is in, so I guess it was tested) [08:19] popey: hey! [08:19] yo [08:19] my maguro battery is dead :( [08:19] * seb128 click update (78), 100M to download, some people have been busy ;-) [08:19] popey: so image 78, we just need the call/sms tests [08:19] 09:18:38 < popey> Huzzah! Ringing and sms tones works in image 78 [08:19] \o/ [08:19] :D [08:19] ogra_, popey just said they do [08:20] timing++ [08:20] ah, i didnt read the backlog [08:20] ;) [08:20] ogra_: well, it was at the same minute that we discussed it here [08:20] should we just assume they do as well on maguro ? [08:20] ogra_: I would assume TBH [08:20] * ogra_ thinks there was no HW specific issue [08:20] right [08:20] lwets release that thing :) [08:20] yeah, it wasn't HW specific [08:21] ogra_: \o/ [08:21] * popey prepares a mail [08:21] ogra_: then, now, enjoy your national holiday :) [08:21] 78 is 20131003 right? [08:21] \o/ [08:22] wow, was 70 really the last one we pushed? [08:22] time flies [08:22] sil2100, didrocks: That's odd, I'm sure thomi said he had top approved this: https://code.launchpad.net/~veebers/autopilot/fixing_backend_being_none/+merge/188762 [08:23] done, give it a few minutes to promote and sync ... [08:23] veebers: it seems he just double approved it instead! Let's top-approve it then ;) [08:23] sil2100, didrocks: Hmm, I think we got our lines crossed, he approved but not top approved :-\ [08:23] popey, right, 20131003/78 [08:23] sil2100: sounds good to me :-) [08:24] it also looks like the merge here failed due to network/apt issues: https://code.launchpad.net/~veebers/unity/fixing_ap_tests_for_updated_autopilot/+merge/188969 [08:24] veebers: thanks for the branch btw.! I'm testing it right now, so far so good [08:24] sil2100: nw, awesome news [08:24] popey: yeah, 2 days ago :) [08:26] 81MB! [08:26] Monster [08:27] popey: quite easy (my fiber connection was just updated to 1Gb :p) [08:29] didrocks: I'm here [08:29] didrocks: you wanted to promote an image? [08:29] I guess ogra_ did already [08:30] lool: we just did it [08:30] (like 9 minutes ago) [08:30] cool [08:30] sil2100: joining? [08:31] Badum tsss [08:31] didn't get the /etc/writable fix? [08:32] hum, the ubuntu-download-manager is doing quite some syslog spamming [08:35] I guess maybe I need to flash with --no-backup [08:41] http://popey.com/~alan/device-2013-10-03-094053.png [08:41] "Apply update failed: No update has been downloaded" [08:41] * popey tries again [08:42] ogra_: joining HO? [08:42] vila: ? [08:42] better that time [08:43] lool: omw [08:43] ogra_: oh sorry, forgot [08:45] no, it's still a file with --no-backup [08:45] Mail sent. [08:53] Damn, so far so good this new AP [08:53] I re-ran notes-app and the test failures were gone, so I guess they were flacky [08:58] shrug, updates' "retry" seems not work [08:58] 3 times upgrade fails on network errors and that I need to reboot the device to try again [08:59] seb128: while you're there, try changing your phone orientation and see the retry button covering... (can't remember the labels) [09:00] vila, bug #1229374 [09:00] bug 1229374 in ubuntu-system-settings "Update button doesn't work when orientation changes" [Low,Confirmed] https://launchpad.net/bugs/1229374 [09:00] seb128: thanks, subscribed [09:00] yw [09:01] I wonder why screen rotation stopped working on the n7 [09:01] it used to work there [09:01] seb128: can't remember seeing it working there [09:02] it was, when I enabled screen rotation in system settings, I first tested on my n7 [09:03] ha right, system settings is where I realized rotation was working, but that was on mako [09:16] didrocks: all tests passed on my device - I even updated to the uitoolkit branch that veebers prepared, ran UI toolkit tests and it was green [09:16] didrocks: but the AP branch didn't get yet merged in, now there was some connection/apt problem on amd64 during autolanding... [09:16] didrocks: not sure what to do with the UI Toolkit one, since we don't want to release UI toolkit for now, right [09:16] ? === alan_g is now known as alan_g|afk === alan_g|afk is now known as alan_g [09:25] sil2100: awesome news on new AP :-) [09:26] sil2100: sorry, was discussing with lool [09:26] sil2100: new UI toolkit >> right, I think we want the old UI toolkit to pass with the new autopilot [09:26] * didrocks backlog [09:26] * lool school and lunch 7 [09:26] sil2100: \o/ [09:26] * lool school and lunch & [09:26] sil2100: can we backport veeber's fix in the current ui toolkit package? [09:27] maybe that would be a way :) [09:27] didrocks: I'll check how bad is it with the old UI toolkit - if it's bad, I'll try backporting [09:27] But I guess backporting might be needed ;) [09:27] sil2100: yeah, so current package + this merge only [09:27] let's cross fingers ;) [09:32] Mirv: psivaa: jibel: Mir ready in the ppa [09:32] so mir + unity-mir + platform-api (+ unity-system-compositor on desktop) [09:33] I guess install iamge #79 and running those ^ [09:33] didrocks: ok, i was just getting http://pastebin.ubuntu.com/6187395/ but may be i am too early? [09:33] * didrocks tests on destkop meanwhile [09:33] psivaa: they are at libmirserver5 now! [09:33] didrocks: ack, will install that. thanks [09:33] yw ;) [09:33] ABI addicts [09:34] Wait, mirserver5 really? [09:34] for real! [09:35] sil2100: do you think we'll be able to publish autopilot before 12 UTC? [09:35] sil2100: oh, we need to rebuild it in the ppa btw… [09:36] didrocks: depends on if the merges will get in ;/ I can manually merge them in if needed, but since rebuilds will have to happen I somehow doubt targetting before-12 [09:36] sil2100: well, ok, let's try to rebuild autopilot meanwhile [09:36] sil2100: is the unity patch in? we can rebuild it? [09:37] didrocks: it's approved since 1 hour, but still not merged in - I guess CI is building it still [09:38] sil2100: ok, let's rebuild autopilot for now [09:38] sil2100: keep me posted on the sdk, I can't wait ;) [09:38] nice that latest unity7 is fine as well under AP! [09:38] sil2100: well, I think if we don't push unity7, it's not that a biggie anyway [09:39] (as long as the patch is merged) [09:40] sil2100: autopilot rebuilding [09:43] \o/ [09:43] I cherry-picked the fix to ubuntu-ui-toolkit, I'll do a test-build too but anyway propose the change to the packaging branch [09:49] excellent! [09:52] didrocks: https://code.launchpad.net/~sil2100/ubuntu/saucy/ubuntu-ui-toolkit/manual_merge <- should I do a MR? [09:52] And should I change it from UNRELEASED to saucy already? [09:52] It's still building here [09:52] Actually... [09:52] Let me not waste time for building the armhf package [09:52] sil2100: I think you don't need to merge that branch, do you? [09:52] sil2100: you just need to merge the changelog back to the upstream branch [09:53] I'll downgrade to old UI toolkit and just push that modified file directly and check if it works [09:53] (once we upload manually) [09:53] yeah ;) [09:53] sil2100: hum, modified file? [09:53] you mean, you push the diff? [09:53] didrocks: ok! [09:53] (as the file maybe contains more) [09:54] Mirv: have you finished libunity + scope-home? (just looking at the unapproved queue) [09:54] Yes, I actually meant the file, since I can use the manual_merge branch, and it's the UI toolkit in-archive-source with that diff applied ;) No worries, testing! [09:56] didrocks: I needed to start a rerun of the Unity7 tests, some autopilot error happened. I'm testing it manually on another machine as well. [09:57] ok [10:00] didrocks: oh! I just now noticed the 'UTC' in 12 UTC [10:01] didrocks: till 12 UTC I guess we'll make it ;) [10:01] sil2100: ok ;) [10:07] apw, infinity: the patch in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882147 (inotify support in overlayfs) was determined to not cover some particularly important scenarios, right? Do either of you know if work is being done elsewhere to add this support? [10:07] Ubuntu bug 882147 in coreutils (Ubuntu) "overlayfs does not implement inotify interfaces correctly" [Undecided,In progress] [10:08] ok, now had a good run! [10:09] publishing libunity + unity-scope-home. [10:09] ev, i have some half baked patches which might cover 'most' of it, but they arn't ready to use, and i know of noone else doing anyting indeed. plus it is definatly not clear you can close the gap entirely due to a semantic gap [10:11] apw: could we say, "on overlayfs it works, but here are the drawbacks" with your patches? Without looking at them, some support is better than none [10:11] didrocks: http://10.97.0.1:8080/view/cu2d/view/Saucy/view/Unity/job/cu2d-unity-saucy-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_libunity_7.1.2+13.10.20131003-0ubuntu1.diff [10:11]