[00:15] <robru> Wellark_, on it
[00:59] <bregma> robru, what the status of my landing-008 publish?
[00:59] <robru> bregma, just looking at that now.
[01:00] <bregma> synchronicity
[01:01] <robru> bregma, ok looks good to me, just need an ack from a core dev to review the packaging changes (I'm not authorized for that). I pinged cyphermox already
[01:02] <bregma> just keep swimming swimming swimming
[01:20] <robru> bregma, ok, got RAOF reviewing your diff. he's mentioning that the dependency on libgrail is dropped, is that on purpose?
[01:23] <bregma> robru, unity has not been dependent on grail for a very long time
[01:23] <robru> bregma, ok cool
[01:25] <robru> bregma, ok published, packaging acked by RAOF
[01:28] <robru> brb, phone
[02:53] <robru> bah, longest phonecall ever.
[02:53] <robru> anybody need anything before I EOD?
[02:56]  * robru -> EOD
[03:45] <rsalveti> hm, just created another x86 based image and click hook run-user failed to run
[03:46] <rsalveti>   File "/usr/lib/python3/dist-packages/click/commands/hook.py", line 74, in run
[03:46] <rsalveti>     Click.run_user_hooks(db, user_name=options.user)
[03:46] <rsalveti> gi._glib.GError: symlink /opt/click.ubuntu.com/.click/users/phablet/.com.ubuntu.calculator.new -> /usr/share/click/preinstalled/com.ubuntu.calculator/0.1.3.224 failed: No such file or directory
[03:46] <rsalveti> drwxr-xr-x 2 clickpkg clickpkg 4.0K Mar 12 03:35 click.ubuntu.com
[03:46] <rsalveti> user phablet can't create any file at /opt/click.ubuntu.com/
[03:47] <rsalveti> wonder if we'll hit the same issues with the armhf images
[04:38] <Mirv> morning, and thanks for doing the process-cpp fix before thomas
[04:39] <Mirv> thanks also whoever clicked the unity-mir rebuilds in the Qt PPA :)
[04:39] <rsalveti> Mirv: yw :-)
[05:52] <rsalveti> yeah, big regression, bug 1291192
[06:02] <Mirv> doh
[06:14] <robru> Mirv, good news. webapps team came to me with a big landing, but I convinced them to wait for after qt5.2, because I would have had to pull 3 or 4 things out of your silo for that ;-)
[06:18] <tvoss> good morning :)
[06:18] <tvoss> seems like I broke some things.
[06:29] <Mirv> robru: whoo :)
[06:29] <robru> Mirv, any idea when qt5.2 will land?
[06:30] <Mirv> tvoss: yup, unfortunately :( you'll need to have some sort of script to pull all depenendencies and build them against the dev packages installed from the landing PPA or something similar
[06:30] <Mirv> robru: tomorrow, hopefully, if today is decided we can land it tomorrow European time.
[06:30] <Mirv> robru: everything is ready except for some hopeful fixes to autopilot tests in a couple of apps
[06:30] <tvoss> Mirv, what exactly broke? I know of unity-mir, which rsalveti fixed
[06:30] <robru> Mirv, good luck! i'm so eager to see that get in. crazy!
[06:31] <Mirv> robru: didrocks hopes to have completely smooth Qt 5.2 transition to get back to promoted images as soon as possible
[06:31] <Mirv> robru: me too :)
[06:32] <Mirv> tvoss: the process-cpp itself broke building I guess most that depends on it (well, I know unity-mir and some other was mentioned). https://launchpadlibrarian.net/169119692/buildlog_ubuntu-trusty-amd64.unity-mir_0.3%2B14.04.20140311.3-0ubuntu1_FAILEDTOBUILD.txt.gz
[06:32] <Mirv> "fatal error: core/signal.h: No such file or directory"
[06:33] <Mirv> tvoss: so the fix was as simple as https://lists.ubuntu.com/archives/trusty-changes/2014-March/011596.html
[06:33] <Mirv> that's of course something that's not necessarily spotted without using pbuilder or such environment for the testing
[06:33] <tvoss> Mirv, why haven't we seen anything of those problems in CI?
[06:33] <Mirv> since you might and usually have packages installed that are not strictly dependencies
[06:34] <tvoss> Mirv, but in CI as well?
[06:34] <Mirv> tvoss: because eg. unity-mir landed before process-cpp, and only when process-cpp landed further rebuilds of the deps like unity-mir became impossible
[06:34] <Mirv> tvoss: compiling process-cpp itself had not problems, just packages that use it
[06:35] <tvoss> Mirv, okay. but the only build dependency we have right now is unity-mir. and that slipped because we took unity-mir out of the process-cpp landing
[06:35] <Mirv> the best would be of course some amount of automatic reverse-dependencies building
[06:53] <didrocks> tvoss: hey
[06:55] <didrocks> tvoss: can you ensure process-cpp has some test cases please? And part of the test cases should be "rebuild all reverse dependencies" as the API isn't stable
[06:55] <didrocks> tvoss: we got blocked yesterday on rebuilding the emergency fix for unity-mir due to it
[06:55] <didrocks> and rsalveti quickly fixed it (thanks)
[06:59] <tvoss> didrocks, not sure what you mean by api not stable?
[06:59] <didrocks> tvoss: we couldn't rebuild unity-mir with latest process-cpp
[06:59] <tvoss> didrocks, I can surely add a test case to rebuild all reverse depends
[06:59] <didrocks> tvoss: so yeah, I guess that will be needed
[06:59] <didrocks> mind doing that for next landing?
[06:59] <tvoss> didrocks, yup, but that wasn't due to the api but due to a missing dep on the -dev package of process-cpp
[06:59] <tvoss> didrocks, I can surely do that
[06:59] <didrocks> thanks ;)
[07:00] <tvoss> didrocks, do we have a script that automatically pulls and builds all reverse build dependencies?
[07:00] <didrocks> tvoss: I don't think we have that
[07:04] <didrocks> tvoss: you might want to use "reverse-depends -b" to detect all the package which build-depends on you
[07:30] <didrocks> cjwatson: once you are around, can you please have a look at bug #1291192?
[08:03] <Wellark_> any ubuntu-core-devs available?
[08:03] <Wellark_> would need a NEW packaging review to get this MP landed: https://code.launchpad.net/~unity-api-team/connectivity-api/ci-testrun/+merge/210511
[08:06] <sil2100> Wellark: hi, usually seb did most of the preNEW reviews for cu2d, so it's probably best to wait for him
[08:06] <didrocks> Wellark: the change itself is good, I'm doing a NEW review at the same
[08:06] <didrocks> sil2100: seb does? :)
[08:06] <sil2100> didrocks: I remembered him doing it, since when you do them then you won't do the MIR for it, right? ;)
[08:07] <didrocks> sil2100: yeah, but I still NEWED 90% of them…
[08:07] <sil2100> didrocks: true...! Bad wording on my side!
[08:07] <didrocks> Wellark: as we try to standardize the packaging, can you move the "Section" stenza just after Priority please? (nitpick)
[08:08] <didrocks> in debian/control
[08:08]  * sil2100 just remembers poking seb a lot with those because didrocks told him so ;p
[08:09] <didrocks> Wellark: you're forcing gcc 4.7 because of properties-cpp? :)
[08:09] <didrocks> Wellark: not sure why are you depending on libdbus-1-dev, shouldn't libdbus-cpp-dev brings it in? (and you only use the cpp bindings, right?)
[08:10] <didrocks> Wellark: same, to standardize, can you put recommends after depends?
[08:11] <didrocks> Wellark: also, on Package: libconnectivity-cpp0
[08:11] <didrocks> no need to repeat the section as it matches the source one
[08:11] <didrocks> Wellark: also, please suggest the -doc, not recommends
[08:13] <didrocks> Wellark: just a note once you will want to enter main: you will need a symbols file
[08:13] <didrocks> so bonus point if you add it now :)
[08:14] <didrocks> Wellark: your version should be 0.0.1-0ubuntu1 btw in debian/changelog
[08:18] <didrocks> Wellark: your .pc file Requires: dbus-cpp
[08:19] <didrocks> so Package: libconnectivity-cpp-dev
[08:19] <didrocks> shouldn't dep on libproperties-cpp-dev, but on libdbus-cpp-dev
[08:19] <didrocks> (bonus for trailing stenza)
[08:19] <didrocks> Wellark: that's it for what I can spot :)
[08:19]  * didrocks paste the logs on the review
[08:22] <Wellark> didrocks: thanks!
[08:23] <didrocks> Wellark: yw, keep me posted once the changes are done, I'll just then redo a quick review :)
[08:23] <Wellark> didrocks: will do :)
[08:23] <didrocks> (and NEW it in the archive, once landed)
[08:25] <Wellark> didrocks: could you claim the review from ubuntu-core-dev side and indicate Needs Fixing?
[08:25] <Wellark> thanks!
[08:26] <didrocks> Wellark: sure, done!
[08:57] <sil2100> didrocks: in-between stuff I started doing packaging reviews of the core-apps that popey poked us about to make them more archive-upload-feasible if you don't mind
[08:57] <didrocks> sil2100: sure, nothing on the list… however, I told him it's a complicated one
[08:58] <didrocks> and I'm not really supportive to aggravate the problem having them in the archive
[08:58] <didrocks> sil2100: he did ask you directly? It's not jason?
[08:58] <sil2100> didrocks: I must say I'm always a bit confused when there's clicks and debs for one thing
[08:59] <didrocks> sil2100: yeah, and this is getting worse if we continue injecting more apps
[08:59] <didrocks> this is what I told him. Also, it's lost time I guess in term of packaging reviews and NEWing
[08:59] <sil2100> didrocks: he poked me previously asking 'how to proceed' to get those into the archive, and I got the bugs from him then
[08:59] <didrocks> not sure he will find an archive admin + FFe
[08:59] <sil2100> Right
[08:59] <didrocks> sil2100: interesting, if you don't have anything else to do, sure
[09:00] <didrocks> sil2100: but to be clear, this is NOT our priority
[09:00] <didrocks> if we have anything else, this one will be
[09:00] <seb128> sil2100, didrocks: what softwares are we talking about?
[09:00] <didrocks> seb128: core apps
[09:00] <didrocks> in click store
[09:00] <didrocks> seems like popey is pushing that we have debs version as well
[09:00] <didrocks> (which brings the situation when it's only fixed in one side and not the other and people get confused)
[09:01] <seb128> we said we would have some of them usable on the desktop so they can be worked on/dogfooded for convergence
[09:01] <seb128> but that only a limited set, like gallery (which is already in)
[09:01] <seb128> camera, notes as well I think
[09:01] <didrocks> seb128: we do have already have some, right?
[09:01] <seb128> yeah
[09:01] <sil2100> Yes, those we had from the beginning
[09:01] <didrocks> the ones which were debs before click
[09:01] <didrocks> so I guess it's good to keep those
[09:01] <seb128> I think we shouldn't invest out of the limited set we are aiming at putting on the desktop next cycle
[09:02] <didrocks> seb128: +1
[09:02] <didrocks> that's what I told popey 2 days ago
[09:02] <sil2100> didrocks: if it's not priority then I don't push on those any further
[09:02] <didrocks> sil2100: thanks :) btw, there is one thing you can look at if you have time
[09:02] <didrocks> sil2100: the unity8 AP tests which continuously fails
[09:02] <didrocks> (not due to the crash)
[09:02] <didrocks> it's the last one I guess
[09:02] <didrocks> http://ci.ubuntu.com/smokeng/trusty/touch/mako/232:20140311.2:20140304/7098/unity8/879786/
[09:02] <sil2100> didrocks: sure, what's up? You mean, the unicode problem, or something new
[09:02] <didrocks> 'tmp5ics4X' != u''
[09:03] <sil2100> Ah, this one ;)
[09:03] <didrocks> sil2100: it's not new, it's there for some images already
[09:03] <sil2100> Ok!
[09:03] <didrocks> and always failing
[09:03] <sil2100> Yeah, I saw it locally as well basically
[09:03] <didrocks> as well with Qt 5.2
[09:03] <didrocks> sil2100: yeah, would be good to understand/get that fixed
[09:03] <didrocks> if this one is fixed, we expect 5.2 with 100% passing on mako again :)
[09:03] <sil2100> didrocks: aye! On it then ;)
[09:03] <didrocks> thanks ;)
[09:07] <seb128> sil2100, didrocks, popey: just for the record, that's what we agreed on at previous vUDS for this cycle
[09:07] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/client-1404-unity8-on-desktop
[09:07] <seb128> "(3) Enable key core Touch applications for both Unity7 and Unity8 (gallery, notes, camera, browser, calculator)"
[09:08] <seb128> so it seems we are missing calculator
[09:08] <seb128> but it's the only one on the list
[09:08] <didrocks> yeah, making sense to add that one if needed, one is fine, but we won't add more
[09:08] <didrocks> (it's really costly for work that will be removed)
[09:09] <ogra_> hmm, why did we have two image builds with only 10min between them yesterday ?
[09:10]  * ogra_ will try to get the bot ready by the weekend ... 
[09:10] <didrocks> ogra_: yeah, not sure… Seems only one was labelled though, right?
[09:11] <ogra_> didrocks, yes, only the first one
[09:11] <ogra_> and obviously there were no changes between these two
[09:12] <didrocks> ogra_: do you know how the labelling works, why the other didn't get one?
[09:12] <didrocks> (like the second one)
[09:12] <didrocks> system-image was too smart and thought "I don't need that one" :p
[09:12] <didrocks> (I doubt about it)
[09:13] <ogra_> didrocks, not sure what happened there, but s-i definitely didnt pick it up ... else we would be at 234
[09:13] <didrocks> yep
[09:13] <didrocks> it's not like that that we'll arrive soon to #332!
[09:13] <didrocks> :)
[09:13] <didrocks> ogra_: maybe it's worth digging though
[09:13] <ogra_> haha
[09:14] <didrocks> in case we'll need one at some point of the future and there is a race
[09:14] <ogra_> i'll ask stephane later ...
[09:14] <didrocks> thanks
[09:14] <didrocks> in that case, it was rather beneficial :)
[09:14] <ogra_> will look at the logs, but i doubt i'll find anything
[09:14] <didrocks> ok, keep me posted please :)
[09:15] <sil2100> didrocks, seb128: hah! ANd I just made a packaging review for calculator ;p
[09:15] <ogra_> might be that he did some maintenance work and disabled the cron job or so
[09:15] <sil2100> (that was the one click-core-app I finished doing)
[09:15] <didrocks> maybe
[09:15] <seb128> sil2100, good ;-) let me know if you need NEW review
[09:15] <didrocks> ogra_: would be good to be warned (even afterwards) in that case
[09:15] <didrocks> ah great sil2100 :)
[09:15] <sil2100> seb128: sure ;) Will take care of that later and poke you then
[09:15] <seb128> cool
[09:15] <sil2100> The merge still isn't reviewed
[09:18] <ogra_> hmm, intresting, so you cant start click apps on 233 (according to rsalveti) but all tests seem to work
[09:19] <didrocks> ogra_: you can't install click apps
[09:19] <didrocks> isn't it?
[09:19] <didrocks> a new installed one
[09:19] <didrocks> (I was updating)
[09:19] <didrocks> btw, just worked here
[09:19] <didrocks> let me try from the store
[09:20] <ogra_> ..."It seems we got a critical click regression with 233 (click user hook
[09:20] <ogra_> fails to start), making the user unable to launch any click package
[09:20] <ogra_> (camera, facebook, twitter, etc)."...
[09:20] <ogra_> he said launch
[09:20] <Mirv> didrocks: your discussion reminded me, lp:qtcreator-plugin-cmake would enjoy a preNEW review too (I just added missing copyright headers).
[09:20] <didrocks> ogra_: hum, he didn't parse it that way, but you're right
[09:21] <didrocks> Mirv: ok, I'll try to have a look (second NEW review of my day :p)
[09:21] <didrocks> ogra_: yeah, worked here
[09:21] <seb128> oh, click top the daily e.u.c trusty report
[09:21] <seb128> https://errors.ubuntu.com/problem/58560a4ce3c2e52baaaa19390dc28579e7f5e8c3
[09:21] <Mirv> didrocks: ok!
[09:21] <seb128> cjwatson, ^ saw that I guess?
[09:22] <didrocks> seb128: yeah, that's related to what ricardo told I guess the hook not being refreshed)
[09:22] <didrocks> ogra_: I think we'll need a fresh installation to see it
[09:22] <didrocks> let me try
[09:23] <ogra_> i would, but then i dont have bandwith for the meeting :P
[09:23]  * ogra_ gets some fresh coffee
[09:23] <didrocks> ogra_: I'm getting it
[09:24] <didrocks> ahah, I was starting to blame ogra on "can't push to the image"
[09:24] <didrocks> then adb shell was failing
[09:24] <didrocks> and finally I noticed the cable was unplugged :p
[09:29] <ogra_> heh
[09:31] <ogra_> so after OTA I have no issues on my flo
[09:32] <didrocks> ogra_: coming?
[09:57] <mhr3> didrocks, so, could we get a silo for all the new-scopes related stuff?
[09:57] <didrocks> mhr3: sure, what line?
[09:58] <mhr3> didrocks, 21
[09:58] <didrocks> mhr3: shouldn't you have some unity8 as well?
[09:58] <mhr3> it's there
[09:58] <didrocks> I can't read then :p
[09:58] <mhr3> last mp
[09:58] <didrocks> ah indeed
[09:58] <didrocks> I can read then
[09:59] <didrocks> mhr3: ok, remember blablabla, not before 5.2, blablabla, you will have to rebuild and retest, blablabla
[09:59] <didrocks> the warnings you had yesterday :p
[09:59] <mhr3> didrocks, right, right
[09:59] <didrocks> sign here with "I accept…" -> [     ]
[10:00] <mhr3> I'm aware of limitations. [ mhr3 ]
[10:00] <didrocks> \o/
[10:00]  * didrocks uses his new shiny option then!
[10:00] <mhr3> so... hell about to break loose?
[10:00] <mhr3> :)
[10:00] <didrocks> heh ;)
[10:01] <didrocks> mhr3: btw, as well ERROR:root:unity-scope-mediascanner is already prepared for the same serie and destination in landing-002
[10:01] <didrocks> in addition to the Qt one
[10:02] <mhr3> hm, ok, no biggie
[10:02] <didrocks> WARNING:root:One or more projects are already in use for the same destination and series in another silo (see above). However, the ignore flag was set. Please inform both silos owners directly.
[10:02] <didrocks> mhr3: and so, silo 003!
[10:03] <didrocks> ogra_: davmor2: ok, bootstrapping done
[10:03] <didrocks> I can launch click packages without network
[10:03]  * didrocks adds wifi now :p
[10:06] <didrocks> ogra_: davmor2: installed calculator and launched -> works here
[10:06] <didrocks> however, I have the click crash as well
[10:06] <didrocks>  gi._glib.GError: symlink /opt/click.ubuntu.com/.click/users/phablet/.com.ubuntu.calculator.new -> /usr/share/click/preinstalled/com.ubuntu.calculator/0.1.3.224 failed: No such file or directory
[10:07] <didrocks> so, something to look at anyway
[10:10]  * didrocks will go away for a run
[10:10] <didrocks> ogra_: davmor2: sil2100: do you mind following up with Colin if he's coming in between? ^
[10:10] <ogra_> sure
[10:10] <didrocks> thx!
[10:11] <didrocks> davmor2: no need to bootstrap for you then I guess
[10:17] <Wellark|pingpong> didrocks: please see my comments in https://code.launchpad.net/~unity-api-team/connectivity-api/ci-testrun/+merge/210511
[10:18] <sil2100> didrocks: ok ;)
[10:19] <didrocks> Wellark|pingpong: bonus point with trailing comma on latest depends, and suggests please (to avoid noisy diff in the future). However if you don't require properties-cpp in your .cp file, you shouldn't add it as a -dev depends, fix either the .pc file or the dependency :)
[10:20] <didrocks> Wellark|pingpong: all the rest is fine :)
[10:20] <didrocks> Wellark|pingpong: just reping me once those changes are done
[10:20] <Wellark|pingpong> who ever is building against my library also needs properties-cpp
[10:20] <Wellark|pingpong> it's a header only lib
[10:20] <Wellark|pingpong> so it must be in -dev Depends
[10:20] <didrocks> Wellark|pingpong: so you need your .pc to Requires it
[10:21] <Wellark|pingpong> it does not have .pc
[10:21] <didrocks> oh?
[10:21]  * didrocks wonders why
[10:21] <Wellark|pingpong> why should it have?
[10:21] <Wellark|pingpong> as it does not install eny libs nor link against anything
[10:21] <didrocks> Wellark|pingpong: properties-cpp.pc
[10:21] <didrocks> I see one
[10:22] <cjwatson> didrocks: yikes, sorry
[10:22] <didrocks> /usr/lib/x86_64-linux-gnu/pkgconfig/properties-cpp.pc
[10:22] <didrocks> Wellark|pingpong: why don't you see it? ^
[10:23] <didrocks> cjwatson: no worry, still weird that we can't reproduce ricardo's issue though
[10:23] <Wellark|pingpong> didrocks: oh.
[10:23] <Wellark|pingpong> interesting
[10:23] <didrocks> cjwatson: but yeah, that and the crash fix, I think sil2100 can help assigning a silo if you have that before I come back
[10:23] <Wellark|pingpong> that must be a new one :)
[10:23] <Wellark|pingpong> didrocks: ok. adding it.
[10:24] <didrocks> Wellark|pingpong: thanks :)
[10:24] <cjwatson> didrocks: that could just be ensuredir failing for the same reason but the error being eaten for some reason; I suspect it's uninteresting
[10:24] <didrocks> Wellark|pingpong: will be back in ~1h15
[10:24] <cjwatson> (ricardo's issue)
[10:24] <Wellark|pingpong> didrocks: although all it does is -I/usr/lib/include :)
[10:24] <didrocks> cjwatson: ah, ok :)
[10:24] <Wellark|pingpong> */usr/include
[10:24] <didrocks> Wellark|pingpong: yeah, but being future-proof while we spot it!
[10:24] <Wellark|pingpong> true.
[10:25]  * didrocks really away now
[10:25] <cjwatson> didrocks: I'm still in morning mode with children chattering to me, playing games, etc. though, so give me a bit of slack on this one please
[10:25] <ogra_> cjwatson, well, seems only rsalveti can reproduce it ... we all tried, so it doesnt seem to hit everyone equally
[10:25] <didrocks> cjwatson: sure, no worry, if we can start/have an image built before vUDS starts, it's fine (I don't expect to see a lot of landings happening right now)
[10:26] <sil2100> ;)
[10:26] <imgbot> wohoo
[10:27] <sil2100> Now that was weird
[10:28] <ogra_> why ?
[10:28] <cjwatson> ogra_: I'm sure it depends whether you previously had any apps unpacked at all
[10:28] <ogra_> cjwatson, well, i tried with OTA on an image that has a lot of clicks installed
[10:29] <ogra_> and didier did y fresh bootstrap install
[10:29] <ogra_> s/y/a/
[10:30] <cjwatson> it looks like it would happen if /opt/click.ubuntu.com/.click/ didn't previously exist
[10:31] <mhr3> didrocks, can you reconf row21? had to remove some mps
[10:32] <mhr3> apparently bzr is being stupid
[10:36] <sil2100> mhr3: I can reconfigure
[10:39] <Wellark|pingpong> didrocks: all done.
[10:40] <mhr3> sil2100, k, thx
[10:41] <sil2100> mhr3: done
[10:41] <cjwatson> ogra_: I've reproduced an identical error with a new test, anyway
[10:41] <ogra_> ah, great
[10:41] <cjwatson> even if I don't have a recipe for triggering it on the phone
[10:52] <cjwatson> sil2100: please can you assign a silo for https://code.launchpad.net/~click-hackers/click/trunk/+merge/210579 ?
[10:52] <cjwatson> sil2100: oops, wait a sec
[10:53] <sil2100> cjwatson: sure, waiting ;)
[10:53] <cjwatson> you always spot the buglet when proofreading the MP diff, right ...
[10:54] <cjwatson> sil2100: OK, better now (was just a performance bug)
[10:54] <sil2100> cjwatson: the same merge, yes?
[10:54] <cjwatson> yep
[10:58] <sil2100> cjwatson: silo 004 assigned for your merge -> the merge itself looks strange, as it's proposing lp:click to some other branch, but I don't know the structure of the click project and believe that you know what you're doing ;)
[10:59] <sil2100> cjwatson: do you have the required permissions to press the 'build' button in silos?
[10:59] <sil2100> cjwatson: or you want me to do it for you?
[10:59] <cjwatson> yes
[10:59] <cjwatson> I mean yes I have perms I think
[11:00] <sil2100> Awesome ;) Then just proceed to landing-004 and you can build - if there's a change in the merge itself, you only have to press 'build' and mention click as the project name to rebuild
[11:01] <cjwatson> yep.  I have to go for a bit too, I emergency-dumped childcare on Kirsten
[11:07] <sil2100> Sure, thanks for the fix!
[11:09] <cjwatson> rsalveti: FWIW, I think it would have been totally fine to try to wake me by phone for this kind of thing
[11:11] <ogra_> cjwatson, well, luckily we have the choice to not promote an image if we find such things ;) so we can easily wait til you are around again
[11:12] <cjwatson> Yeah, but that puts me in the situation of delaying Qt 5.2 even more
[11:12] <cjwatson> In context I'd rather be woken :)
[11:12] <ogra_> heh, ok
[11:13] <ogra_> (i dont see you blocking 5.2 ... we just recently promoted an image, fine if we can get a better one, but not mandatory imho)
[11:14] <cjwatson> Is 5.2 going to start landing today?
[11:14] <ogra_> up to Mirv and didrocks
[11:16] <cjwatson> BTW the trivial repro recipe for rsalveti's bug is:
[11:16] <cjwatson> root@ubuntu-phablet:/opt/click.ubuntu.com# mv .click .click-safe
[11:16] <cjwatson> root@ubuntu-phablet:/opt/click.ubuntu.com# su - phablet
[11:16] <cjwatson> phablet@ubuntu-phablet:~$ click hook run-user
[11:17] <cjwatson> you can rm -rf /opt/click.ubuntu.com/.click; mv /opt/click.ubuntu.com/.click{-safe,} afterwards
[11:18] <cjwatson> no idea why it didn't happen to didrocks on a fresh bootstrap; maybe it wasn't quite fresh enough or something
[11:18] <cjwatson> oh it sort of did, it's just that he could still launch apps
[11:18] <cjwatson> meh
[11:45] <Mirv> cjwatson: we've a meeting in 1h 15min if you want to join, but in general the remaining blocker (or thing that needs a plan) are the regression in AP tests http://q-jenkins:8080/job/autopilot-release-gatekeeper/69/#showFailuresLink (gallery-app not counting, it needs a rebuild)
[11:45] <Mirv> well notes app should be fixed too
[11:46] <Mirv> 2 in calendar + music-app, 1 in messaging-app, 4 in unity8 (unless already fixed)
[11:57] <didrocks> cjwatson: hum, I'm pretty sure I used the boostrap option (and had to reconfigure all user's config + no click apps installed)
[11:57] <cjwatson> I suspect that you were able to launch apps because you tried installing one first
[11:57] <cjwatson> but it's just a guess, *shrug*
[11:57] <didrocks> oh possibly
[11:57] <didrocks> cjwatson: on 5.2 -> not likely today, but will keep you posted
[11:57] <cjwatson> current version in landing-004 fails differently, I've rethought things a bit and am going to push another version
[11:58] <didrocks> ok :)
[12:00] <didrocks> cjwatson: yeah (finished backlogged), I don't think you are blocking 5.2 TBH. I'll ensure it's not used as an excuse if neede :)
[12:00] <didrocks> needed*
[12:10] <davmor2> didrocks: so 233 is working fine for me but I'm assuming there is going to be another spin for the click fix right?
[12:11] <davmor2> didrocks, Mirv: when are we looking to land Qt 5.2 now anyway I forgot to ask in the hangout (hadn't woken up yet is my excuse :) )
[12:11] <didrocks> davmor2: yeah for 233
[12:11] <didrocks> davmor2: well, when all remaining issues will be fixed
[12:12] <davmor2> didrocks: but where's the fun in a green image there is no work for everyone :D
[12:13] <didrocks> davmor2: well, we are not green and the fun can happen now on the Qt 5.2 landing slot :p
[12:13] <davmor2> didrocks: haha
[12:14] <Mirv> davmor2: it depends ^. if the today's AP run can be trusted to the extent that it worked with the click breakage, remaining AP failures could be 2 calendar-app, 2 music-app, 1 unity8
[12:15] <cjwatson> I don't believe that the click breakage will have affected AP in the slightest
[12:16] <cjwatson> It seems very unlikely to me anyway
[12:16] <Mirv> cjwatson: well the apps are not starting like http://q-jenkins:8080/job/autopilot-release-gatekeeper/70/label=mako-06/testReport/junit/calendar_app.tests.test_yearview/TestYearView/test_selecting_a_month_switch_to_month_view_with_touch_/ so I assumed it was because of the click
[12:16] <Mirv> there might be something else going on with Leo's latest run of course too
[12:17] <cjwatson> Hm
[12:17] <cjwatson> Maybe I'm wrong
[12:17] <Mirv> on my mako 233 upgraded to qt 5.2 I only have 7 apps listed as installed as a whole, ie no click apps
[12:17] <sil2100> uh
[12:17] <cjwatson> Mirv: I guess you've never installed any apps
[12:18] <cjwatson> But certainly if you're affected by the "click hook run-user" breakage then ~/.local/share/applications/ symlinks will be missing
[12:18] <cjwatson> So I guess that could indeed affect AP
[12:19] <Mirv> cjwatson: I believe apps like Facebook, Gallery-app etc are preinstalled, and were yesterday still. this is after phablet-flash -b
[12:19] <cjwatson> Right
[12:19] <cjwatson> You'll probably find that if you install any random app, and then reboot, the preinstalled apps will appear
[12:25] <didrocks> Mirv: it shouldn't impact, or, we'll have exactly the same breakage on the main CI results
[12:27] <Mirv> confirmed
[12:28] <Mirv> didrocks: was it so that the dashboard results test environment is identical to what Leo is running at the gatekeeper job? anyhow, I was looking at http://q-jenkins:8080/job/autopilot-release-gatekeeper/70/#showFailuresLink
[12:29] <Mirv> where now all click apps seem to not start, while they work for me after colin's trick to install one additional app
[12:30] <didrocks> Mirv: it should be from what I understood, but unsure
[12:34] <Mirv> davmor2: I'm running some random apps quickly from the manual chart now
[12:39] <davmor2> Mirv: great, I'm about to do the same :)
[12:42] <cjwatson> OK, that's much better, publishing click
[12:46]  * sil2100 goes for lunch
[12:57] <Mirv> davmor2: feel free to retest more "Font small" apps too, I marked them slightly different saturated green after testing 4
[12:58] <davmor2> Mirv: will do :)
[13:01] <Mirv> elopio: davmor2: joining?
[13:16] <Mirv> elopio: I interpreted 69 + 70 results as remaining unfixed AP:s being 2 calendar-app, 2 music-app, 1 messaging-app, 1 unity8 (saviq said has a fix). 70 is problematic since click apps didn't start, so after the new click is in archives we'll need another AP test run
[13:17] <Saviq> Mirv, https://code.launchpad.net/~macslow/unity8/fix-object-name-of-notification-ap-test/+merge/210588 FWIW
[13:18] <Mirv> elopio: if you agree with those cal + mus + mess ^ I wonder if you could file a bug of each of them tagged qt5.2 so that the http://is.gd/pNalUg list would show the true 5.2 status regarding bugs
[13:18] <Mirv> Saviq: ok!
[13:19] <davmor2> popey: your bug for the squares can I have the number please I am able to confirm it with joy now :)
[13:21] <popey> davmor2: bug 1285184
[13:24] <Mirv> marked the weather app qt 5.2 bug as fixed after testing it works now
[13:24] <davmor2> popey: ta
[13:25] <davmor2> Mirv: browser not supported error on g+ so the text issue might be fixed but the browser size is causing issues (it's basically trying to open the desktop browser)
[13:25] <davmor2> s/desktop browser/desktop version
[13:31] <Mirv> didrocks: should I ignore-conflicts now because of the scopes being landed?
[13:32] <didrocks> Mirv: oh yeah, you wil need to :)
[13:32] <Mirv> well I assume the answer is yes, but just checking before first time use
[13:44] <Wellark> didrocks: thanks for the review!
[13:44] <didrocks> Wellark: yw ;)
[13:45] <Wellark> didrocks: will I ping you once the "testing" is done and the silo is ready to land so you can do the necessary NEW universe magic?
[13:47] <rsalveti> ogra_: cjwatson: I could easily reproduce the click issue when flashing with bootstrap
[13:47] <didrocks> Wellark: sure
[13:47] <rsalveti> ota would indeed be different
[13:48] <ogra_> rsalveti, didrocks couldn't
[13:48] <rsalveti> weird, with bootstrap?
[13:48] <ogra_> but well, fixed now :)
[13:48] <rsalveti> I flashed both manta and flo, got the issue on both
[13:48] <rsalveti> sure, just reading backlog :-)
[13:48] <ogra_> i only did OTA on my flo
[13:48] <ogra_> where i indeed couldnt reproduce
[13:49] <cjwatson> rsalveti: it's ok, I understand it now :)
[13:49] <cjwatson> it's just waiting for the next proposed-migration + publisher run now
[13:51] <rsalveti> lovely
[13:57] <rsalveti> and we're planning to land qt5.2 tomorrow
[14:02] <Mirv> davmor2: I tested the g+ too, not supported. although I guess that might be a Google change, unless you've tested recently it works with Qt 5.0? the Google not supporting me seems pretty familiar to me as non-mainstream browser user
[14:02] <Mirv> (or non-mainstream browser User-Agent owner)
[14:03] <davmor2> Mirv: no it's not using the web container and is using a bastardised UA iirc so works fine on the n10 and n4 unless you click back but the n7 has a huge display size that I think is breaking it
[14:05] <Mirv> davmor2: oh, right, closing and reopening it works now. maybe I rotated the phone and it affected somehow it first.
[14:06] <davmor2> Mirv: hmm could be
[14:07] <davmor2> Mirv: roll on oxide is all I can say :D
[14:07] <Mirv> or then it was just the first time when I logged in and got forwarded to wrong page
[14:08] <elopio> Mirv: I overslept today, I'm still getting used to the hour change of all the meetings.
[14:09] <elopio> Mirv: yesterday I was trying to confirm the autopilot failures on the phone, but I couldn't start the apps
[14:11] <Mirv> elopio: it's good to sleep. I'm filing some bugs now you can check later if they are ok.
[14:12] <Mirv> elopio: yes the new click landed and apparently affected things. fix is now/soon in.
[14:12] <elopio> Mirv: that would be nice, thanks.
[14:16] <Mirv> elopio: done now for music/calendar/messaging: http://is.gd/pNalUg - so 1 unity8 AP (as shown in your run 70 where click apps failed though) should be fixed by https://code.launchpad.net/~macslow/unity8/fix-object-name-of-notification-ap-test/+merge/210588
[14:16] <Mirv> elopio: then I don't know about the gallery-app, I guess it should be recompiled and AP tests ran manually. or if the archive version is recent enough, apt-get install gallery-app gallery-app-autopilot installs a second gallery app icon from the PPA (in addition to the Click app) which works and maybe then tests could be run too
[14:17] <Mirv> elopio: I linked your branch to the notes-app bug, should it be marked In Progress at least or similar? I didn't touch it
[14:18] <elopio> Mirv: it's not a fix for the bug. My branch makes us get only one error corresponding to the bug, and works it around for the rest of the tests.
[14:19] <elopio> installing the gallery here to give it a try...
[14:19] <Mirv> elopio: ok, right.
[14:20] <Mirv> elopio: btw I checked that click 0.4.18.3 is now in the archives, so if the gatekeeper job does have archive sources available too (in addition to PPA) when it runs the dist-upgrade, a test run could be started now
[14:20] <cjwatson>  click | 0.4.18.3 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
[14:20] <pmcgowan> Mirv, I scheduled a follow which is a bit late for you so hope you can attend, otherwise maybe someone can attend for you
[14:20] <cjwatson> Yeah, I was just about to say
[14:20] <cjwatson> didrocks: you could kick an image build now I think
[14:21] <pmcgowan> he is in his session on landings right now
[14:21] <elopio> Mirv: I don't know where the job takes the packages from.
[14:21] <cjwatson> I know
[14:21] <cjwatson> pmcgowan: IRC is asynchronous, I'm fine with a delay :)
[14:21] <pmcgowan> cjwatson, ;)
[14:21] <elopio> for things like the weather app, it just uses whatever is installed in the phone.
[14:21] <Mirv> pmcgowan: that should be ok this time, and it's right after the Qt UDS session. can you join it btw? I don't have answers myself to the question of what to do about new Qt versions in the future.
[14:22] <pmcgowan> Mirv, I will attend but also may not have answers
[14:23] <Mirv> let's see
[14:28] <Mirv> elopio: when it uses the PPA, if it does apt-get update && apt-get dist-upgrade, then it'd install all the newest stuff not yet in the image too, if normal Ubuntu archive sources are in /etc/apt/sources.list. but if in doubt, better wait the new image built ^
[14:31] <Mirv> elopio: one more thing (sorry for spamming:) before I forget: autopilot-qt had a wrong version in the PPA that had failing AP tests - this could affect our results now as well on the next run. https://lists.ubuntu.com/archives/trusty-changes/2014-March/011048.html
[14:31] <Mirv> elopio: I've fixed it in the landing PPA so that the autopilot-qt rebuild there is now the same as what we actually have in archives (not what is in autopilot-qt trunk)
[14:31] <elopio> Mirv: you are not spamming, everything you are saying is useful.
[14:31] <elopio> I should have attended the meeting, then you wouldn't have to repeat it all :)
[14:32] <elopio> Mirv: I would prefer to wait for the new image built
[14:32] <elopio> so we can compare our results.
[14:32] <elopio> but if you want, I can launch a run now, and then another one later.
[14:33] <didrocks> cjwatson: thanks, doing
[14:34] <Mirv> elopio: later is fine, but maybe scheduled so that you manage to kick another run for repeatibility before your EOD
[14:40] <elopio> Mirv: sure, I'll just coordinate with the autopilot team so I can run two today.
[14:47] <alesage> is this a bad time? ;) kenvandine with a question about this ubuntu-wallpapers ci failure, looks jammed http://s-jenkins.ubuntu-ci:8080/job/ubuntu-wallpapers-trusty-amd64-ci/5/console
[14:48] <alesage> cihelp when you have a minute ^^
[14:50] <fginther> alesage, looking
[14:59] <Mirv> mhr3: do you plan to have the scopes tested and landed today? there needs to be someone around who kicks rebuild of unity-scope-click unity-scopes-api unity-scopes-shell unity8 in Qt 5.2 landing-006 after merge-and-clean has finished
[14:59] <fginther> alesage, I've made some change to the ci job and I think it'll work now. I believe the problem is that something in the build chain blows up on the unicode file names
[15:00] <alesage> fginther, interesting, that sounds like a "real thing", always feel bad if it's just a red herring so thanks :)
[15:04] <fginther> alesage, I've restarted the job (again). this time it should work
[15:05] <sergiusens> tedg, hey, you have your cursor over l31 in the spreadsheet; are intending to edit?
[15:05] <tedg> sergiusens, Nope, just hovering. Go ahead
[15:06] <sergiusens> thanks
[15:06] <alesage> thanks fginther!  kenvandine ^^
[15:06]  * sergiusens tries to avoid weird collisions
[15:06] <didrocks> oh btw
[15:06] <didrocks> [15:06] <didrocks> (couldn't do it before, ETOOMUCHDISCUSSIONS in the session)
[15:07] <kenvandine> fginther, alesage: thanks!
[15:09] <sergiusens> sil2100, hey, can I get a cart for l31?
[15:09] <sergiusens> unless anything is silocked
[15:10] <sil2100> sergiusens: hi! Let me check how we look with that
[15:15] <sil2100> sergiusens: ok, it's not colliding with anything, and with the click fix landed we can add a new silo
[15:15] <sil2100> sergiusens: let me assign
[15:15] <didrocks> sil2100: noooooooooooooooooooooooo
[15:16] <mhr3> Mirv, that depends on you :)
[15:16] <sil2100> didrocks: ok ;p
[15:16] <didrocks> sil2100: I was kidding, I hoped that sergiusens would go crazy ;)
[15:16] <didrocks> I lost, so sad :p
[15:17] <sergiusens> didrocks, are you darth did?
[15:17] <sil2100> didrocks: ...
[15:17] <didrocks> ahah ;)
[15:17] <sil2100> ;P
[15:17] <didrocks> sil2100: go ahead :)
[15:17] <mhr3> Mirv, if you're about to land 5.2 soon enough, we don't need to land the scopes-related stuff, if it's still going to take a while, we'd prefer to land the non-unity8 parts and rebuilt the pkgs in the 5.2 landing ppa
[15:17] <sil2100> CURSE YOU DIDIER! ;p Ok, I'm assigning then ;)
[15:17] <sergiusens> :-)
[15:17] <didrocks> :p
[15:17] <didrocks> \o/
[15:18] <rsalveti> goal for qt 5.2 is tomorrow
[15:19] <Mirv> mhr3: goal is indeed tomorrow for 5.2
[15:19] <Mirv> mhr3: so I'd suggest either land scopes today or wait until after 5.2. but the today with the caveat that you get a landing team member to rebuild the mentioned packages for 5.2 after publish + merge&clean done
[15:21] <mhr3> Mirv, didrocks, we *can* land the non-unity8 related bits, i'm leaving up to you whether we should land those bits today or later
[15:21] <mhr3> imo smaller landings == better
[15:22] <didrocks> Mirv: it won't impact the image?
[15:22] <didrocks> argh
[15:22] <didrocks> mhr3: ^
[15:22] <didrocks> like it's not activated by default?
[15:22] <mhr3> didrocks, if we leave out unity8, it won't
[15:22] <didrocks> Mirv: are those just rebuild? you are happy to do that?
[15:23] <didrocks> or mhr3 ^
[15:23] <mhr3> didrocks, yes, just rebuild for what's in qt landing ppa
[15:23] <didrocks> mhr3: yeah, not a whole rebuild thought please
[15:23] <didrocks> mhr3: just settings in rebuild_only the components that will need be rebuilt once you merge and clean the other silo
[15:23] <mhr3> just those 5 pkgs :)
[15:23] <didrocks> yep :)
[15:25] <Mirv> didrocks: mhr3: I checked that yes unity-scope-click unity-scopes-api unity-scopes-shell unity8 are just rebuilds, like said a landing team member needs to force rebuild for those packages after merge&clean phase like I did yesterday evening for unity-mir just before going to sleep
[15:26] <Mirv> (it's only that it happens that process-cpp broke it back then)
[15:26] <didrocks> yeah, unfortunate :)
[15:26] <didrocks> if mhr3 is going to take the load, I think it's fine
[15:26] <didrocks> and fair :)
[15:27] <Mirv> mhr3: so at http://162.213.34.102/job/landing-006-1-build/build?delay=0sec packages_to_rebuild insert unity-scope-click unity-scopes-api unity-scopes-shell unity8   and check "force_rebuild"
[15:27] <Mirv> after the trunks have been updated with the latest releases
[15:27] <didrocks> no unity8 please :)
[15:27] <didrocks> I don't think it's time to transition
[15:28] <Mirv> oh, right, no unity8 if not landing that :)
[15:28] <mhr3> Mirv, didrocks, yea, i can do it, need to check up with the second conflicting silo we had
[15:28] <didrocks> but the rest ;)
[15:28] <mhr3> didrocks, and talk to you how to remove unity8 from the silo :)
[15:28] <didrocks> mhr3: second? What? I give you one possibility and you spreadh :p
[15:28] <didrocks> mhr3: just click on "configure"
[15:28] <didrocks> in the silo
[15:28] <didrocks> just tell me if you don't know what to setup :p
[15:28] <didrocks> mhr3: you will be the first self-reconfigure CI Train man on earth!
[15:29] <mhr3> didrocks, i was just about to say that that's landing-team only feature :P
[15:29] <didrocks> mhr3: look at the silos
[15:29] <didrocks> do you see "landing-team" on the button?
[15:29] <sil2100> sergiusens: if anything, assigned to 004
[15:29] <mhr3> didrocks, it indeed disappeared :)
[15:30] <didrocks> mhr3: silent updates FTW \o/
[15:30] <mhr3> didrocks, heh
[15:30] <didrocks> mhr3: I couldn't announce them in the session though, writing an email
[15:30] <mhr3> very well
[15:30] <mhr3> will do once my sessions end
[15:30] <mhr3> so i can focus on it properly :)
[15:31] <didrocks> yep :)
[15:31] <Wellark> didrocks: silo 1 ready to land
[15:33] <didrocks> sil2100: mind checking if you have time?
[15:34] <sergiusens> thanks
[15:39] <davmor2> Mirv: I've gone through all the apps that were listed as small font and retested them all.  I've then gone through quickly and confirmed popey 's red items and found 3 broken apps that start fine but die after and popey has confirmed them so that list should now be correct
[15:40] <sil2100> didrocks: ACK
[15:41] <sil2100> Wellark: looking
[15:41] <sil2100> didrocks: you preNEWed it already, right? I see your comment on the merge so I guess it's a +1!
[15:42] <didrocks> sil2100: yeah
[15:49] <ogra_> didrocks, what happened to your plans to build an image after click landed
[15:49] <didrocks> 16:06:35         didrocks | [15:49] <didrocks> ogra_: it didn't? ^
[15:49] <ogra_> oh
[15:50] <didrocks> Ubuntu Touch armhf (re-building)
[15:50] <didrocks> phew :)
[15:50] <didrocks> you got me puzzled if I really pressed the button or not
[15:50] <ogra_> hmm, seems cdimage is already done
[15:51] <ogra_> didrocks, yeah i'm fiddling with an IRC bot that watches builds ... seemingly it didnt work ... back to the drawing board
[15:51] <didrocks> heh
[15:54] <didrocks> "In silo landing-001. Migration: One package at least is not available at the destination. connectivity-api (0.0.1+14.04.20140312-0ubuntu1) is in the NEW queue. "
[15:54] <didrocks> great :)
[15:54] <didrocks> (never saw it automatically)
[16:00] <davmor2> meh xchat doesn't allow highlighting on [16:00] <davmor2> -t
[16:01] <robru> didrocks, oh yeah, silo 1 is a brand new package, needs a preNEW. I had pinged cyphermox to review it last night but I guess he never did
[16:01] <didrocks> robru: yeah, I did a review
[16:01] <didrocks> and got some fixes
[16:01] <robru> didrocks, ah, thank you
[16:01] <didrocks> no worry!
[16:01] <didrocks> just need to click the right button now :p
[16:02] <didrocks> robru: NEWed
[16:02] <robru> yay!
[16:03] <didrocks> Wellark: FYI ^
[16:04] <sil2100> \o/
[16:06] <didrocks> davmor2: can you dogfood #234?
[16:07]  * didrocks feels it's a good one :)
[16:07] <didrocks> plars: keeping on eye on the tests for that one? ^
[16:07] <davmor2> didrocks: you and your optimism
[16:07] <didrocks> always, you know me!
[16:07] <didrocks> :)
[16:10] <davmor2> didrocks: I'd like to update to 234 but it doesn't show up :P
[16:10] <didrocks> davmor2: maybe the diffs are not generated yet
[16:13] <ogra_> davmor2, join #ogra-test ... and see if the imagebot behaves :)
[16:13] <ogra_> it should give a notice once it is ther
[16:13] <ogra_> e
[16:14]  * didrocks counters attack with #didrocks-test then!
[16:14] <ogra_> lol
[16:15] <davmor2> ogra_: nice
[16:15] <davmor2> didrocks: you don't test though that's my job :P  sets up #davmor2-tests-breaks-complains-writes-a-bug
[16:17] <didrocks> :)
[16:18] <plars> didrocks: I'm actually off today through friday. Unfortunately I'm going to be traveling so there won't be much opportunity to take a look
 [16:20] <didrocks> plars: oh, did you need to relaunch anything?
[16:21] <robru> didrocks, sil2100, Mirv, cyphermox: just want to let everybody know that I have a doctor's appointment at 12:30 (~3 hours from now) so I'll be taking a slightly longer lunch for that.
[16:22] <didrocks> plars: or you think it will work on its owN?
[16:22] <plars> didrocks: I don't know I haven't looked (see my previous message) I've been fairly busy trying to get ready to leave from home. What's the issue?
[16:22] <sil2100> robru: ok, ACK
[16:22] <robru> thanks
[16:22] <didrocks> plars: not today in previous days
[16:22] <didrocks> plars: like, you didn't need to do any intervention?
[16:22] <sil2100> robru: not too many landings today, so take care ;)
[16:22] <didrocks> robru: no worry, get better! :)
[16:23] <plars> didrocks: I didn't rerun anything yesterday, no
[16:23] <didrocks> plars: ok, let's cross fingers we won't have any provisioning issue today :)
[16:23] <didrocks> thanks plars for the notice
[16:23] <plars> didrocks: if you are expecting an issue with provisioning the image, you may want to give rfowler_ a heads up
[16:24] <didrocks> plars: ok, we'll gave a look then
[16:29] <mhr3> didrocks, can you remove landing ask #28?
[16:29] <davmor2> ogra_: Done might be lying I still see no update
[16:29] <didrocks> mhr3: I'm in session all the day, sil2100/robru should be available ^
[16:29] <ogra_> davmor2, i definitely see it on the server
[16:29] <mhr3> sil2100, pls ^
[16:29] <ogra_> which is where the bot looks too
[16:30] <robru> mhr3, sil2100 : on it
[16:30] <ogra_> http://system-image.ubuntu.com/trusty-proposed/mako/
[16:30] <mhr3> robru, i included it in the scopes 0.4 landing ask, so no longer necessary
[16:30] <robru> mhr3, ok thanks
[16:31] <davmor2> ogra_: ota says http://www.televisiontunes.com/Family_Fortunes_-_Wrong_Buzzer.html
[16:32] <ogra_> well, even the index has it
[16:32] <ogra_> http://system-image.ubuntu.com/trusty-proposed/mako/index.json
[16:32] <ogra_> (scroll to the bottom)
[16:32] <davmor2> ogra_: I'm wondering if updates is broken
[16:33] <davmor2> ogra_: I just keep getting software is up to date
[16:33] <ogra_> i dont have a phone near me
[16:34]  * ogra_ can test after the session
[16:34] <sil2100> robru: ACK
[16:34]  * sil2100 is busy both debugging and coding now anyway
[16:35] <davmor2> ogra_: rebooted now it shows up
[16:40] <popey> does #234 still have the issue that click packages cannot be started?
[16:40] <popey> qmlscene: failed to check version of file 'calendar.qml', could not open...
[16:40] <popey> getting that starting calendar
[16:42] <ogra_> popey, shouldnt
[16:42] <popey> qmlscene: failed to check version of file 'ubuntu-clock-app.qml', could not open...
[16:42] <popey> same for clock...
[16:43] <popey> current build number: 234
[16:43] <sergiusens> popey, that's not from a clean install I take it
[16:43] <popey> no, OTA
[16:43] <popey> i can re-flash from clean if you want.
[16:44] <pmcgowan> popey, thats the original issue still
[16:44] <pmcgowan> reflash wont show the issue
[16:47] <mhr3> robru, so, trying to reconfigure myself, so i just copied all the mps, do i need to provide all the src pkgs too? isn't that automatic?
[16:48] <robru> mhr3, you only need to indicate source packages that aren't among the MPs, eg if you depend on a project that canonical is not upstream of, need it in the silo for testing, but don't have a launchpad branch for it. usually only for Xorg or whatever.
[16:48] <mhr3> robru, ah, cool
[16:49] <robru> mhr3, silo 2 still cleaning
[16:50] <mhr3> robru, right, and didrocks's magic ignore flag isn't there for me (cause stuff is in 006 too), so i guess you have to do it anyway?
[16:51] <didrocks> ah, reconfiguring when you have a conflict
[16:51] <didrocks> that can be easily solved
[16:51] <didrocks> one sec
[16:52] <robru> mhr3, humm, if youre conflicting with silo 6 I would ask Mirv really nicely if you can break his qt5.2 landing ;-)
[16:52] <mhr3> robru, already done, got his blessing :)
[16:52] <robru> mhr3, ahhhh ok
[16:52] <mhr3> with a condition that i need to rebuild 006 then :)
[16:53] <didrocks> pushed, let me deploy that
[16:53] <robru> mhr3, ok, what line is the new request?
[16:53] <didrocks> robru: let mhr3 self-reconfigure in a moment
[16:54] <mhr3> robru, 21, but didier is doing some magic ^^
[16:54] <robru> didrocks, oh ok
[16:54] <didrocks> mhr3: please retry :)
[16:57] <didrocks> pfff, mhr3 is taking more time to retry than me fixing this :p
[16:57]  * didrocks is soooo disappointing
[16:57] <didrocks> and siappointed
[16:57] <didrocks> disappointed*
[16:57] <mhr3> didrocks, shuush :P it's already done
[16:57] <robru> didrocks, lol yeah, you disappoint me a lot ;-)
[16:57] <didrocks> (but for sure, disappointing as well :p)
[16:57] <didrocks> robru: I was sure of that! :p
[16:59] <didrocks> ok, cool #234 testing started
[16:59] <didrocks> ogra_: I'm sure I can type #234 without any typo!
[17:00] <ogra_> heh
[17:00]  * didrocks opens g+ and breathes
[17:01] <sil2100> :)
[17:01]  * ogra_ crosses fingers
[17:02] <ogra_> did someone tell cjwatson that the issue is still there btw ?
[17:02] <didrocks> ogra_: urgh, really? :/
[17:02] <cjwatson> muh?
[17:02] <didrocks> or are you just kidding?
[17:02] <ogra_> according to popey
[17:02] <cjwatson> popey: elaborate
[17:02] <popey> cjwatson: going to reflash to previous stable and reproduce to confirm, my phone is a mess
[17:02] <cjwatson> I'm pretty sure it's not the same thing
[17:04] <cjwatson> popey: I'm going for dinner now and then will be around for about half an hour of the session afterwards before I have to go
[17:04] <popey> ok
[17:04] <popey> will take a while for me to get into the same state
[17:05] <didrocks> popey: aren't you supposed to be in bed btw?
[17:05] <cjwatson> popey: is it possible that you attempted to manually work around the previous issue?
[17:05] <cjwatson> popey: for example by creating directories?
[17:05] <popey> i did not cjwatson
[17:05] <cjwatson> ok
[17:05] <cjwatson> if you haven't reflashed yet I would appreciate seeing the error message
[17:06] <popey> 16:40:47 < popey> qmlscene: failed to check version of file 'calendar.qml', could not open...
[17:06] <cjwatson> you know
[17:06]  * popey ctrl+C's the update
[17:06] <cjwatson> when you lot say "the previous issue", it would be really helpful to say *which one*
[17:06] <cjwatson> that's *yesterday*'s problem
[17:06] <ogra_> sorry i only reacted to popey :)
[17:07] <cjwatson> popey: find /usr/share/click/preinstalled /opt/click.ubuntu.com /var/lib/apparmor /var/cache/apparmor -ls
[17:07] <popey> Sorry, I was just asking why calendar didn't start. Was afk yesterday.
[17:07] <cjwatson> (if you're quick I can do a snap analysis before dinner)
[17:07]  * popey runs that
[17:08] <popey> cjwatson: http://paste.ubuntu.com/7080279/
[17:08] <cjwatson> popey: also dpkg-query -W click, just to confirm
[17:09] <popey> click	0.4.18.3
[17:10] <cjwatson> popey: grep ^Path= /home/phablet/.local/share/applications/com.ubuntu.calculator_calculator_0.1.3.224.desktop
[17:10] <popey> Path=/usr/share/click/preinstalled/.click/users/@all/com.ubuntu.calculator
[17:10] <cjwatson> so that all looks fine to me
[17:11]  * ogra_ doesnt have any issues on flo on 234
[17:11] <cjwatson> it's not the same pattern as yesterday
[17:11] <cjwatson> popey: could you pastebin /var/lib/apparmor/profiles/click_com.ubuntu.calculator_calculator_0.1.3.224 ?
[17:11] <ogra_> but i didnt have any with the former image either
[17:11] <elopio> Mirv: so, autopilot job running. I will rerun it again once it finishes. And I
[17:11]  * sil2100 jumps out to the vet again
[17:11] <cjwatson> that's the only other thing I can think of to check
[17:11]  * rsalveti is flashing 234 as well
[17:11] <elopio> Mirv: I'm flashing my phone to try to reproduce the bugs your reported. Do you need something else from me?
[17:12]  * ogra_ thinks the clock app is trying to make jokes with him ... 
[17:12] <ogra_> it shows a different city every time i open it
[17:13] <Mirv> elopio: I guess poking of upstream for fixes if they're reproducable and also still happen with the current automated AP run
[17:13] <popey> cjwatson: http://paste.ubuntu.com/7080315/
[17:13] <cjwatson> popey: ok, that all looks completely fine to me
[17:13] <cjwatson> popey: it might be worth seeing if it still happens after a simple reboot
[17:13] <popey> ok, shall I reflash to make sure I'm not doing silly things?
[17:13] <Mirv> elopio: maybe apt-get install gallery-app gallery-app-autopilot and trying running those? since gallery-app was still an unknown - but I don't know if it works like that, since after that there's two gallery-app:s installed.. (one can start the correct one by clicking the 2nd icon in the app list)
[17:13] <cjwatson> popey: reboot first
[17:13] <popey> k
[17:14] <cjwatson> but everything seems to be consistently referring to /usr/share/click/preinstalled as the root
[17:14] <cjwatson> which is as it should be here
[17:14] <elopio> Mirv: I should be able to run the gallery app tests by branching them.
[17:14] <popey> btw I probably have an anomoly in that I would have the same click in preinstalled and opt/
[17:15] <popey> cjwatson: same version I mean, due to testing stuff I use pkcon to install-local a bunch of clicks. some of which will be dupes of the preinstalled ones
[17:15] <cjwatson> popey: I know but you have no observable problems arising from that
[17:15] <elopio> I'm not sure about that, but I'll check. Worst-case scenario, I'll manually explore it.
[17:15] <popey> ok
[17:15] <cjwatson> popey: https://lists.launchpad.net/ubuntu-phone/msg06867.html
[17:15] <Mirv> elopio: you need a rebuilt gallery-app anyway since it seems to need a rebuild - that is, the gallery-app that comes preinstalled doesn't work since it's a click app since last Friday. apt-get install gallery-app gives you a rebuild from the Qt PPA
[17:15] <popey> ta
[17:15] <cjwatson> popey: that was yesterday's problem, but as far as I can tell my fix for all that has comprehensively taken here
[17:15] <cjwatson> popey: you could probably check syslog for apparmor denies too
[17:15] <cjwatson> anyway, gone for dinner
[17:15] <popey> k
[17:16] <popey> [Wed Mar 12 17:15:53 2014] type=1400 audit(1394644555.125:242): apparmor="DENIED" operation="open" parent=1931 profile="com.ubuntu.calendar_calendar_0.4.201" name="/usr/share/click/preinstalled/com.ubuntu.calendar/0.4.201/calendar.qml" pid=2980 comm="qmlscene" requested_mask="r" denied_mask="r" fsuid=32011 ouid=104
[17:16] <popey> bingo
[17:16] <didrocks> davmor2: do you mind take great care if you can reproduce popey's issue? ^
[17:17] <popey> i would like to wipe this phone and start from 226 again if poss, because I dont trust it 100% as it's been used for qt5.2 testing
[17:18] <elopio> Mirv: with the ppa from the silo 006, do we need a dist-upgrade?
[17:18] <davmor2> didrocks: Popey's phone is bastardised to hell I was going to do a fresh install and see if the apps were all there and open after testing key features from the upgrade
[17:19] <didrocks> :)
[17:19] <Mirv> elopio: I'm not sure, there is one package removed (libqt5core5) so possibly yes?
[17:20] <Mirv> elopio: I haven't tried other than dist-upgrade
[17:20]  * popey reflashes
[17:20] <elopio> Mirv: ok, I'll just do it. I have just found that all our jenkins runs are using both the qt5-beta2 ppa and the silo 006 ppa
[17:21] <Mirv> elopio: wooow :) qt5-beta2 overrides so it's missing fixes from silo 006 then
[17:22] <Mirv> elopio: only landing-006 please
[17:22] <elopio> Mirv: yes, stoping and re-running.
[17:22] <Mirv> qt5-beta2 might get reused for 5.3 testing but in general
[17:22] <Mirv> cool, great :)
[17:22] <didrocks> elopio: to remove the package, you need to dist-upgrade
[17:22] <didrocks> and not upgrade
[17:22] <didrocks> yeah
[17:23] <elopio> didrocks: yes, veebers has this hook which does all that. I just need to make sure that the qt5-beta2 ppa is not used anywhere.
[17:23] <mhr3> robru, eh, help with row 21
[17:23] <robru> mhr3, what's up?
[17:24] <mhr3> robru, silo has unity8, but i configured it away
[17:24] <mhr3> needs to be manually deleted from the ppa i guess
[17:24] <didrocks> (\o/ info messages are working)
[17:25] <mhr3> didrocks, it should have deleted it automatically though ;P
[17:25] <didrocks> mhr3: not really
[17:25] <didrocks> mhr3: the goal is for people to check the config
[17:25] <didrocks> maybe they forgot to add it?
[17:25] <robru> mhr3, didrocks: i don't have permission to delete from the PPA.
[17:25] <didrocks> robru: really?
[17:25] <didrocks> let me fix that
[17:25] <robru> didrocks, thank you ;-)
[17:26] <didrocks> robru: done (and sorry :))
[17:26] <mhr3> robru, you're welcome, you get extra powers because of me ;)
[17:26] <didrocks> and extra logs of build failures :p
[17:26] <robru> mhr3, muahahah! I have a shocking amount of power in launchpad as it is ;-)
[17:26] <mhr3> plus with extra powers comes extra responsibilities :P
[17:27] <didrocks> even some seb128 revocated himself :)
[17:27] <seb128> indeed
[17:27] <didrocks> cyphermox: no reason for you to escape that as well, added :p
[17:27] <robru> seb128, what did you revoke? I just remember certain managers revoking some stuff from me over christmas...
[17:28] <seb128> team membership on launchpad to reduce spamming
[17:28] <robru> ah
[17:28] <didrocks> robru: you have no idea into what world you just entered :)
[17:29] <robru> didrocks, the world of gmail filters?
[17:29] <didrocks> well, I was never impressed to not be able to filer on custom headers from gmail
[17:29] <robru> mhr3, ok i requested that deletion, i guess it's a bit slow though
[17:29] <didrocks> that's why I keep maildrop
[17:29] <didrocks> robru: yeah, takes some time
[17:30] <davmor2> didrocks: all the basic features work so now I'm flashing to see if the click issue is resolved
[17:30] <robru> didrocks, yeah, not being able to filter on headers does suck for sure, but most launchpad mails have so much boilerplate text that you can just filter on body keyword searches and it's just as effective
[17:30] <didrocks> davmor2: great! keep us posted on the ML as well about #234 with thumb up or not :)
[17:30] <popey> ffs
[17:30] <popey> just clean wipe flashed #226
[17:31] <popey> the touch screen isn't working at all
[17:31] <davmor2> popey: clean or bootstrap?
[17:31] <didrocks> popey: are you so sick to hallucinate? :p
[17:31] <popey> i am pressing *quite* hard
[17:31] <didrocks> wipe didn't work for me, only bootstrap
[17:31] <popey> wipe, not bootstrap
[17:31] <davmor2> popey: press the power button 3 times
[17:31] <popey> pressed it once
[17:31] <popey> now works
[17:31] <popey> stupid OS
[17:32] <popey> ☻
[17:32] <didrocks> robru: yeah, if I can avoid getting back into that, I'll be happy :)
[17:32]  * didrocks quotes popey
[17:32] <davmor2> popey: I blame android
[17:32] <didrocks> or we should make a pool, "what OS was popey talking about?" :p
[17:32] <popey> right, so calendar starts fine on #226
[17:33] <robru> mhr3, ok, it looks like unity8 is gone from the silo. need anything else?
[17:34] <mhr3> robru, yea, what do i do now? build again?
[17:34] <mhr3> or watch_only?
[17:37] <dbarth> didrocks: re-reading your email: could I reload a silo or two with our webapps and html5 stuff now?
[17:38] <dbarth> robru: ^^
[17:38] <robru> dbarth, last I heard from Mirv was that qt5.2 is gonna land tomorrow. so cloooose!
[17:39] <didrocks> mhr3: if you don't have anything else to build, just watch only
[17:39] <didrocks> (to monitor the current builds)
[17:39] <dbarth> robru: so you saying, we should wait for tomorrow?
[17:40] <robru> dbarth, yeah, qt5.2 will land sooner if we don't disrupt it. then once it lands we can really open the floodgates
[17:43] <davmor2> cjwatson, didrocks, popey: I noticed an odd issue just if I have no network connection none of the installed apps (click) appear as soon as there is a 3g/wifi connection they do
[17:44] <pmcgowan> davmor2, thats a known issue in the app scope, they will appear after around 10 secs then disappear again
[17:44] <pmcgowan> not sure why it got no attention
[17:45] <didrocks> pmcgowan: because there is no automated test maybe?
[17:45] <pmcgowan> davmor2, https://bugs.launchpad.net/unity8/+bug/1249255
[17:46] <pmcgowan> hmm, I marked it confirmed again,
[17:47] <pmcgowan> alecu, is that your bug? ^^
[17:51] <cjwatson> popey: sorry, I was looking at calculator earlier, but I don't see any obvious problems with calendar of the kind I was looking at yesterday either
[17:51] <cjwatson> davmor2: no problem of that kind is related to me as click doesn't care about the network :-)
[17:52] <cjwatson> davmor2: (i.e. scope bug)
[17:52] <cjwatson> but yeah, I noticed the same thing this morning when I ran out of 3g quota
[17:52] <davmor2> cjwatson: I'll let you off this time but don't do it again ;)
[17:53] <davmor2> cjwatson: popey had an interesting experience with that on the way to the office a couple of weeks back
[17:53] <popey> yeah, on my list of bugs to file, but bug 1249255 looks like it
[17:53] <alecu> pmcgowan: yes, that sounds like a clickscope bug. We have done a rewrite of the scope to use the new api; we'd have to check if that bug is still there.
[17:54] <davmor2> alecu: and the new scopes are blocked by Qt5.2 right?
[17:54] <alecu> pmcgowan: the rewritten scope was used for the mwc demo, but is not used yet in the main image. I guess that will happen after the new scopes are landed, yes.
[17:55] <alecu> I'm expecting new and exciting bugs after that ;-)
[17:56] <davmor2> alecu: Oh don't worry popey and I will be more than happy to oblige you :D
[17:56] <alecu> davmor2: sir, I'm counting on that :-)
[17:58] <davmor2> didrocks, popey: so image 234 click appear and open \o/
[17:58] <davmor2> cjwatson: ^ that one is you fixing it though right :)
[17:58] <cjwatson> hopefully
[17:59] <davmor2> popey: open terminal on a first run do you still get the 0 font size bug?
[18:00] <pmcgowan> davmor2, I still have the click bug on my calculator app in 234, is that known?
[18:00] <davmor2> pmcgowan: it's opening fine here
[18:01] <pmcgowan> davmor2, well, on a fresh flash it would
[18:01] <ogra_> works fine for me with OTAed devices
[18:01] <ogra_> (all three)
[18:01]  * didrocks rebootstrap for the 2nd time
[18:01] <davmor2> pmcgowan: I'd already tested on ota too
[18:02] <pmcgowan> davmor2, where can I see the log of what its doing again?
[18:02] <cjwatson> pmcgowan: find /usr/share/click/preinstalled /opt/click.ubuntu.com /var/lib/apparmor /var/cache/apparmor -ls
[18:02] <mhr3> robru, 003 tested, rdy to publish
[18:02] <robru> mhr3, thanks, on it
[18:03] <davmor2> pmcgowan: /home/phablet/.cache/upstart/com.ubuntu.calculator
[18:03] <davmor2> .log
[18:03] <davmor2> missed that bit
[18:03] <pmcgowan> cjwatson, http://paste.ubuntu.com/7080573/
[18:03] <robru> mhr3, naughty boy! look at all these packaging diffs! http://162.213.34.102/job/landing-003-2-publish/
[18:03] <robru> cyphermox, can I get a packaging ack? http://162.213.34.102/job/landing-003-2-publish/
[18:04] <popey> ok. so the issue I have is:- fresh flash #226, start calendar - starts fine. Install click packages "pkcon install-local *.click" (from http://popey.mooo.com/mirror/clicks/2014-03-09-100001/ ), reboot, calendar no longer opens
[18:04] <cjwatson> 218061    0 lrwxrwxrwx   1 root     root           75 Mar 12 12:56 /var/lib/apparmor/clicks/com.ubuntu.calculator_calculator_0.1.3.224.json -> /usr/share/click/preinstalled/com.ubuntu.calculator/0.1.3.224/apparmor.json
[18:04] <popey> [Wed Mar 12 18:02:23 2014] type=1400 audit(1394647344.351:243): apparmor="DENIED" operation="open" parent=1917 profile="com.ubuntu.calendar_calendar_0.4.201" name="/opt/click.ubuntu.com/com.ubuntu.calendar/0.4.201/calendar.qml" pid=2982 comm="qmlscene" requested_mask="r" denied_mask="r" fsuid=32011 ouid=104
[18:04] <cjwatson> that at least looks good
[18:04] <mhr3> robru, not naughty, doing our jobs properly! :P
[18:04] <cjwatson> pmcgowan: could you pastebin /home/phablet/.local/share/applications/com.ubuntu.calculator_calculator_0.1.3.224.desktop, and the tail of /var/log/syslog ?
[18:05] <pmcgowan> doesnt seem to be a local version now
[18:05] <robru> mhr3, making more work for me though, it's naughty ;-)
[18:05] <robru> mhr3, good job fixing that FIXME though ;-)
[18:05] <pmcgowan> cjwatson, http://paste.ubuntu.com/7080599/
[18:06] <popey> cjwatson: see above two lines, sorry, I don't know if I should expect image #226 (current stable) to do this.
[18:06] <pmcgowan> and http://paste.ubuntu.com/7080601/
[18:06] <cjwatson> popey: can I please debug these two separately
[18:06] <popey> sure, I'll wait. sorry.
[18:06] <cjwatson> popey: oh, that was #226?
[18:06] <popey> the above is
[18:06] <cjwatson> popey: yes, that's absolutely expected to do that, that's what I fixed yesterday
[18:07] <popey> ok, so if I OTA update to latest proposed that should go away? - or I should be in the same state as pmcgowan ?
[18:07] <cjwatson> I don't know yet
[18:07] <popey> ok
[18:07]  * popey waits then
[18:07] <pmcgowan> still getting the same denial
[18:07] <cjwatson> no apparmor denies in the syslog you posted
[18:07] <pmcgowan> cjwatson, let me give you a fresh one
[18:08] <cjwatson> and the .desktop file seems to have the right path
[18:08] <pmcgowan> http://pastebin.ubuntu.com/7080612/
[18:08] <pmcgowan> I did a tail as I opened it
[18:08] <cjwatson> hm, possibly suspicious timestamps
[18:09] <cjwatson> jdstrand: should /var/lib/apparmor/profiles/click_com.ubuntu.calculator_calculator_0.1.3.224 have a newer timestamp than /var/cache/apparmor/click_com.ubuntu.calculator_calculator_0.1.3.209 ?
[18:09] <cjwatson> err
[18:09] <cjwatson> I can't read
[18:10] <cjwatson> different versions
[18:10] <cjwatson> jdstrand: ^- need your help on this, I'm not sure I know what questions to ask next
[18:12] <Wellark> didrocks, robru: thanks! \o/
[18:12] <robru> Wellark, you're welcome!
[18:12] <didrocks> Wellark: yw ;)
[18:13]  * jdstrand looks
[18:15] <jdstrand> pmcgowan: can you paste /var/lib/apparmor/profiles/click_com.ubuntu.calculator_calculator_0.1.3.224?
[18:15] <jdstrand> oh, I bet I know what it is
[18:15] <jdstrand> cause the version didn't change, the profile didn't get regenerated
[18:15] <pmcgowan> http://paste.ubuntu.com/7080658/
[18:16] <robru> didrocks, hummm, cyphermox isn't around... can you ack some packaging for me? http://162.213.34.102/job/landing-003-2-publish/ the diffs are big but I didn't see anything too troubling
[18:16] <jdstrand> yeah: @{CLICK_DIR}="/opt/click.ubuntu.com"
[18:16] <jdstrand> 'sudo aa-clickhook -f' should fix it
[18:16] <popey> sounds plausible, would explain the issue I see too
[18:16] <cjwatson> jdstrand: right, I'm sure I advised ages ago to go by the timestamps
[18:16] <cjwatson> this is why :)
[18:17] <cjwatson> so, great, click-apparmor bug not click
[18:17] <jdstrand> I don't recall that discussion, but I also didn't write the early code
[18:17]  * cjwatson nods
[18:17] <cjwatson> I think you need to go by the timestamp *of the symlink*
[18:17] <cjwatson> i.e. lstat
[18:18] <cjwatson> for most hooks it doesn't matter, they aren't trying to care about the package location in so much detail, they just need file content
[18:18] <cjwatson> but click-apparmor is delving into a fair bit of detail
[18:18] <popey> jdstrand: cjwatson that fixed the issue for me - running aa-clickhook..
[18:19] <jdstrand> popey: you did use *-f*, correct?
[18:19] <popey> yes
[18:19] <jdstrand> yeah
[18:19] <jdstrand> this gets tricky
[18:20] <jdstrand> cause we really don't want to regenerate the profiles unless we have to, cause it is expensive
[18:20] <cjwatson> right, but the symlinks won't change often
[18:20] <cjwatson> I think going by lstat.st_mtime should be fine
[18:21] <cjwatson> and it seems technically correct too since you care about the target of the symlink
[18:23] <mhr3> didrocks, need core-dev to ack the scopes pkging changes... pretty pls? :)
[18:24] <didrocks> mhr3: I really can't, in session so can't focus properly if the changes are invalid
[18:24] <jdstrand> hmm
[18:24] <jdstrand> that changes things quite a bit
[18:24] <robru> I'm off for lunch / doctor's appt, back in ~2hrs
[18:25] <didrocks> mhr3: can you get me the unity-scope-mediascanner2 package content?
[18:25] <didrocks> mhr3: seems you have private libs there?
[18:25] <jdstrand> maybe not
[18:26] <mhr3> didrocks, think it's remnant from the old scope
[18:26] <didrocks> mhr3: hum, they are just added
[18:28] <jdstrand> cjwatson: so you're saying that if the lstat.st_mtime is newer than the generated profile, regenerate the profile
[18:28] <mhr3> didrocks, http://pastebin.ubuntu.com/7080713/
[18:28] <jdstrand> that actually is straightforward
[18:29] <jdstrand> popey, pmcgowan: is there a bug for this?
[18:29] <popey> not yet, but there can be
[18:29] <popey> what package do you want it filed against?
[18:29] <jdstrand> popey: click-apparmor
[18:29] <popey> k
[18:30] <pmcgowan> jdstrand, I will keep my busted app for testing ;)
[18:30] <cjwatson> jdstrand: right
[18:30] <jdstrand> ok, working on a fix
[18:30] <cjwatson> jdstrand: seems like it should be easy, indeed :)
[18:30] <cjwatson> thanks
[18:30] <jdstrand> yep, I know where to do it. just had to think about it for a sec
[18:31] <didrocks> mhr3: ok, sounds good
[18:32] <didrocks> mhr3: published
[18:32] <didrocks> robru: ^
[18:32] <mhr3> didrocks, cheers, appreciated
[18:32] <didrocks> yw
[18:32]  * didrocks goes back to listen the session
[18:32] <robru> didrocks, thanks
[18:32]  * robru -> lunch for real
[18:37] <popey> jdstrand: bug 1291549
[18:37] <jdstrand> popey: thanks
[18:37] <popey> np
[18:39] <jdstrand> cjwatson: so, let's say I have foo_0.1 on image r20. I upgrade to image r21 but foo is still 0.1, is click going to update the symlink when I reboot?
[18:40] <cjwatson> feel free to test but I don't believe it will
[18:40] <boiko> robru: hey, would it be possible to build the MR on line 32 before the Qt 5.2? it is really low risk and it would help us getting some other MRs built/tested
[18:40] <jdstrand> cause if it does, that will be a boot performance regression
[18:40] <jdstrand> s/boot/first boot/
[18:41] <jdstrand> but I guess click could be made to not do that
[18:41] <jdstrand> it is clear that I need to look at the symlink cause click will update them from time to time
[18:42] <jdstrand> (ie, preferring preinstall over /opt)
[19:07] <didrocks> jdstrand: do you mind refreshing the phone ML with your findings so that we know if it's a regression from latest promoted image and if we push or don't push #234?
[19:08] <pmcgowan> didrocks, not a regression, just not the full fix for the uncovered bug from the other day
[19:13] <popey> davmor2: do you have a bug for the "press power 3 times"?
[19:15] <davmor2> popey: I'm not sure what the cause is so no I think it is the guid that causes it but it doesn't hit everytime
[19:32] <jdstrand> I updated the phone ML for the click/click-apparmor issue
[19:33] <jdstrand> I have a test case and a branch. am running through my testing checklist now
[19:43] <Mirv> mhr3: you're handling the merge&clean + 3 package rebuilds now?
[19:43] <Mirv> good night
[19:45] <Mirv> mhr3: added to comments "landing-006 needs to rebuild (force rebuild) 3 packages - unity-scope-click unity-scopes-api unity-scopes-shell - after merge and clean here complete (= trunks updated)."
[19:52] <sergiusens> popey, have you pin pointed the click app launch failing? I just got it by going back and forth between devel and devel-proposed
[19:52] <popey> sergiusens: bug 1291549
[19:52] <sergiusens> popey, ah, nice find
[19:52] <pmcgowan> sergiusens, fix in testing now
[19:53] <sergiusens> pmcgowan, great;
[19:53] <popey> sergiusens: j dstrand and c jwatson  did the work
[19:53] <sergiusens> pmcgowan, I'll just phablet-config autopilot --dbus-probe enable for now
[19:53] <pmcgowan> sergiusens, what the heck does that do?
[19:54] <sergiusens> pmcgowan, it reruns the apparmor profiles but enables autopilot to export on the bus as well
[19:54] <pmcgowan> ah
[19:54] <ogra_> it will sing a song for you (if you give it the right secret options)
[19:54] <sergiusens> pmcgowan, so it basically reruns the click apparmor hooks
[19:56] <sergiusens> who works on media scanner? I found a weird bug (2 actually); if I put in an mp3 without a year, it restart continuously crashing and apport runs non stop (1-2 hour battery life and really hot)
[19:56] <sergiusens> so another request would be to only have apport run wth quotas and not when the device isn't plugged
[20:00] <pmcgowan> sergiusens, thomas strahls team, jussi and james
[20:01] <sergiusens> thanks
[20:22] <mhr3> Mirv, yea, doing it
[20:25] <jdstrand> ok, fix is tested and reviewed
[20:25] <jdstrand> I get to do my first silo :)
[20:30] <jdstrand> can someone review https://wiki.ubuntu.com/Process/Merges/Checklists/ClickAppArmor and https://wiki.ubuntu.com/Process/Merges/TestPlans/ClickAppArmor?
[20:32] <jdstrand> robru, cyphermox: ^
[20:32] <cyphermox> sure
[20:32] <jdstrand> I'm doing my first silo. I went through training, but may need some help
[20:32] <jdstrand> thanks
[20:34] <jdstrand> cyphermox: I don't know if you saw backscroll. this is a minimal fix for bug #1291549, which should fix the recently click issue once and for all (the fix spanned click and click-apparmor. all the click fixes are already in)
[20:35] <jdstrand> cyphermox: not sure if you also want - https://code.launchpad.net/~jdstrand/click-apparmor/click-apparmor.lstat/+merge/210671
[20:42] <jdstrand> cyphermox: looking at my notes, I should ask for a silo now.
[20:45] <cyphermox> jdstrand: correct
[20:46] <jdstrand> cyphermox: ok, so assuming my checklist and plan are good, may I have a silo?
[20:47] <jdstrand> cyphermox: now, this is my first one, and I know normally that I would wait for the meeting. I am asking now cause it seems the click issue may be blocking promotion. I responded on the list, but didn't hear back
[20:47] <cyphermox> jdstrand: sure, could you add your request to the spreadsheet?
[20:47] <jdstrand> yep
[20:48] <cyphermox> in the pending tab you have lines for the test plan and MP and all of this, from there I can assign a silo
[20:50] <jdstrand> cyphermox: do I fill in the last column, or do you?
[20:50] <jdstrand> 'Ready?'
[20:51] <cyphermox> you can fil lthat in, if your stuff is ready to be assigned a silo
[20:51] <jdstrand> ok. done. line 33
[20:51] <cyphermox> thanks
[20:51] <jdstrand> err, row 33
[20:51] <robru> i'm back, anybody need anything?
[20:55] <cyphermox> robru: no, all good
[20:55] <jdstrand> cyphermox: do I just keep an eye on the 'Status' line?
[20:56] <robru> boiko, sorry for the delay, i was on lunch. yeah I can push that through quick if you can test it quick ;-)
[20:57] <cyphermox> jdstrand: pretty much
[20:57] <boiko> robru: sure I can :)
[20:57] <cyphermox> jdstrand: this is touch only right?
[20:57] <jdstrand> cyphermox: yes
[20:58] <jdstrand> cyphermox: how long does it typically take for the status to tell me what silo I am assigned?
[20:59] <cyphermox> not long, just reviewing everything ;)
[20:59] <jdstrand> ah, ok. sorry
[21:00] <robru> boiko, ok, bumping ofono-qt from silo 6, takes a minute
[21:01] <cyphermox> robru, oh boy
[21:01] <robru> cyphermox, yeah? ;-)
[21:08] <robru> boiko, ok! you got silo 2 and I even clicked build for you: http://162.213.34.102/job/landing-002-1-build/77/console ;-)
[21:09] <boiko> robru: that was nice of you, thanks :D
[21:09] <robru> boiko, oh, you need to sync the changelog from distro into your MP
[21:09] <jdstrand> what isn't clear to me is once I have a silo, I know I get a ppa. do I upload packages to that ppa?
[21:09] <boiko> robru: let me ask tiago to do that
[21:09] <robru> boiko, ok. just hit rebuild when it's ready
[21:09] <boiko> robru: ok, thanks
[21:10] <robru> jdstrand, if you have MPs, citrain will build those MPs in the ppa.
[21:10] <jdstrand> robru: how does it handle orig.tar.gz?
[21:10] <robru> jdstrand, you only upload packages manually in the case that we are not upstream and don't have launchpad branches for the package. Eg Xorg gets manual uploads to silos
[21:10] <jdstrand> hmm
[21:10] <robru> jdstrand, it doesn't. packages are built in split mode, which means we take the branch and cut out debian/ directory, and *that* is orig.tar.gz
[21:11] <boiko> robru: so, where should I get the changelog from? https://code.launchpad.net/~phablet-team/ofono-qt/trunk?
[21:11] <robru> boiko, hmmm
[21:11] <jdstrand> I have a feeling that I may have an issue with apparmor, but I'm not doing a silo for apparmor right now, so I'll wait
[21:11] <robru> jdstrand, we're here to help when you're ready
[21:12] <jdstrand> robru: so, if it builds it, am I supposed to publish it straight from the silo or upload to the archive?
[21:12] <jdstrand> s/upload/upload separately/
[21:12] <robru> boiko, take this: http://launchpadlibrarian.net/162145805/ofono-qt_1.5%2Bgit20120419%2Bbcf0c04-0ubuntu1_1.5%2Bgit20120419%2Bbcf0c04-0ubuntu2.diff.gz
[21:13] <boiko> robru: nice thanks!
[21:13] <robru> jdstrand, if you hit 'publish' on the silo, archive robot copies it from the silo to the archive. easier than a manual upload
[21:13] <jdstrand> robru: hrm, but who signs that upload?
[21:13] <robru> jdstrand, the jenkins bot I guess?
[21:14] <jdstrand> I think that is not ideal
[21:14] <robru> jdstrand, i'm not familiar with the signing details but unless you've noticed an enormous volume of unsigned package uploads lately, there's a bot that's signing stuff.
[21:14] <jdstrand> that is also a separate issue
[21:15] <jdstrand> the problem with a bot doing the signing is the machine with the bot is a very attractive target for attack
[21:15] <robru> jdstrand, this is true. luckily it's running ubuntu ;-)
[21:16] <jdstrand> well, sure, but ubuntu doesn't protect against misconfiguration. I'll put this in a TBD column
[21:16] <robru> jdstrand, oh, are you security auditing the CI Train?
[21:17] <jdstrand> not explicitly, but I can't hlep myself from thinking about these things as I am going through the process for the first time
[21:17] <robru> jdstrand, ahhh ok. well didrocks is the mastermind so forward all complaints to him ;-)
[21:17]  * jdstrand nods
[21:18] <robru> jdstrand, here's an example of a ci train upload in archive: https://launchpad.net/ubuntu/+source/unity-mir/0.3+14.04.20140311.2-0ubuntu1 I see the dsc file has a PGP signature on it. too busy to verify it myself but you can if you are curious
[21:20] <boiko> robru: it seems this changelog comes from this other branch:  https://code.launchpad.net/~ubuntu-core-dev/ofono-qt/ubuntu
[21:21] <jdstrand> public key "PS Jenkins bot <ps-jenkins@lists.canonical.com>"
[21:21] <boiko> robru: but I am pretty sure the one on phablet-team (lp:ofono-qt) is the correct one
[21:21] <robru> boiko, so that branch was uploaded direct to distro without ci train?
[21:21] <robru> boiko, oh, you mean that upload is wrong / should be reverted?
[21:22] <boiko> bfiller: do you know why we have  https://code.launchpad.net/~ubuntu-core-dev/ofono-qt/ubuntu and https://code.launchpad.net/~phablet-team/ofono-qt/trunk ?
[21:22] <boiko> robru: to be honest I don't know :)
[21:22] <jdstrand> robru: so, if I wanted to upload my own signed package, am I allowed to? Ie, I simply don't press the Publish button?
[21:22] <robru> boiko, if it turns out that you want to revert that upload, there's a flag for that in the build job, 'IGNOREVERSIONDESTINATION" or something.
[21:23] <boiko> robru: ok, so talking to tiago, it seems I was wrong, the lp:ofono-qt one is the wrong one
[21:23] <jdstrand> I mean, I know I am capable/allowed being core-dev. I just mean, would I mess up machinery, etc, etc
[21:23] <boiko> robru: tiago is going to propose the change again, and in this case, you can drop the line and the silo for this one
[21:23] <boiko> robru: sorry about that
[21:24] <jdstrand> ah
[21:24] <robru> jdstrand, mmmmmm... well kind of the whole point of CI train is that the package you test in the silo goes unmodified into the archive, so we have some confidence that the package being tested is binary identical to the package being released. So as long as you download thesame package, sign it, and upload it, i guess it's ok. extra work though
[21:24] <jdstrand> "In silo landing-001. Silo ready"
[21:24] <boiko> robru: I will propose that again in the correct branch tomorrow morning
[21:25] <jdstrand> I appreciate that point. I also like knowing that the thing that has my name on it was signed by me
[21:25] <robru> jdstrand, not sure if that would mess things up. I guess we'd just run merge & clean with the 'ignore step' flag checked to ignore the fact that publish job never happened. it should work if you want to do it that way
[21:25] <robru> boiko, so abort your silo then?
[21:25] <boiko> robru: yes, please
[21:25] <robru> boiko, ok
[21:26] <robru> jdstrand, ok, if you silo is ready, you can click the build button on the silo tab
[21:26] <boiko> robru: I will keep the line in the spreadsheet though, I just changed it as not being ready, will update it again tomorrow
[21:26] <robru> boiko, ok no worries
[21:27] <jdstrand> meh, noscript said there was an XSS
[21:28] <robru> jdstrand, at which point? the spreadsheet uses a lot of JS but I don't think jenkins does
[21:28] <jdstrand> I clicked 'Build' in the jenkins page
[21:29] <jdstrand> it took me to 2fa, which was the XSS
[21:29] <robru> hmmm
[21:29] <robru> surely 2fa is a good thing ;-)
[21:29] <jdstrand> so I jsut accepted it
[21:29] <robru> jdstrand, maybe it's just the redirect? the link goes to jenkins but it will redirect you to 2fa if you're not already signed in
[21:30] <jdstrand> it took me back to the jenkins page (ie, the one with the Build button), but it doesn't seem to have done anything
[21:30] <jdstrand> probably. I guess I should click Build again
[21:30] <jdstrand> yes
[21:30] <jdstrand> build #59
[21:31] <robru> alright
[21:31] <jdstrand> hmm
[21:31] <jdstrand> There is no commit message in https://code.launchpad.net/~jdstrand/click-apparmor/click-apparmor.lstat. Please check that you set a commit message on all your MPs.
[21:31]  * jdstrand goes back to MP
[21:32] <robru> jdstrand, also be aware that the commit message goes directly into the debian/changelog, so don't write an essay in there ;-)
[21:32] <jdstrand> yeah
[21:33] <jdstrand> robru: how much of debian/changelog do I need, just the '  * message here (LP: #...)'?
[21:34] <jdstrand> yikes, I'm lost in jenkins
[21:34] <robru> jdstrand, don't even put the star, jenkins adds that. just write one line "Fixes that bug we hate (LP: ####)"
[21:35] <jdstrand> ok, got back to where I needed via the spreadsheet
[21:35] <jdstrand> robru: thanks
[21:36] <robru> jdstrand, you're welcome!
[21:36] <jdstrand> http://162.213.34.102/job/landing-001-1-build/61/console seems to be prgressing
[21:36] <jdstrand> ok, I have to step away for a bit. I'll let this build
[21:36] <jdstrand> I'll come back later to test
[21:37] <robru> jdstrand, great
[21:39] <jdstrand> that's a bummer
[21:39] <robru> jdstrand, hummm, your build just failed. i don't understand the failure though, looks infrastructural. trying it again just in case it's temporary: http://162.213.34.102/job/landing-001-1-build/62/console
[21:40] <jdstrand> bzr: ERROR: Inconsistency between source format and version: version is not native, format is native.
[21:41] <robru> jdstrand, heh, i didn't read that far back ;-)
[21:41] <robru> jdstrand, was just looking at the traceback
[21:41] <jdstrand> it is a native package
[21:41] <jdstrand> I have to go though. I'll sort it out later
[21:41] <robru> jdstrand, ok
[21:43] <robru> jdstrand, hmmm, your package is native. i'm not sure exactly how we handle that. we didn't used to support that at all, until dobey hacked it in. i guess you should poke dobey to support this...
[21:46] <robru> jdstrand, right, so ci train autogenerated version number for you is '0.1.15+14.04.20140312-0ubuntu1', which is not native (but this is the standard format for version numbers that we use everywhere in ci train).
[21:47] <robru> so ci train is trying to force your native package to have a non native version number, hence the conflict. huh
[21:49] <robru> jdstrand, easiest solution I can think of would be to just change your package to a non native format (according to our standards: https://wiki.ubuntu.com/DailyRelease/InlinePackaging) but if you insist on staying native we might have to wait for didrocks to resolve this, I'm not sure how
[22:21] <cjwatson> jdstrand: I checked - click won't update a hook symlink that already exists and points to the correct target, so you shouldn't have a boot perf regression from doing this
[22:21] <cjwatson> jdstrand: talk with stgraber about how he's set up CI Train for click - it's probably closer to what you want for click-apparmor
[22:22] <cjwatson> X-Auto-Uploader: no-rewrite-version etc.
[22:28] <mhr3> robru, hmmm, any idea what did i break in the qt5.2 silo?
[22:28] <mhr3> robru, was just rebuilding the scopes pkgs against 5.2, and the status is full of errors now
[22:28] <robru> mhr3, what?
[22:29] <mhr3> i have a feeling i'm in trouble
[22:30] <robru> mhr3, more my fault. I wasn't aware of IGNORECONFLICTS despite you having just used it in front of me this morning, so I poked around in silo 6 when i shouldn't have
[22:31] <mhr3> yey, so i'm off the hook :)
[22:31] <robru> mhr3, yeah
[22:33] <cjwatson> popey: just for clarity, your repro recipe in bug 1291549 may possibly still fail even with jdstrand's fix, because you're specifically asking for #226 and *part* of the fix (just not all) was in the click changes I've landed since then
[22:33] <cjwatson> popey: and your recipe probably won't work with #234, because click now spots that you're trying to install a version that's already preinstalled, and just registers it for you rather than unpacking another copy
[22:39] <robru> mhr3, double checked, the silo looks fine... i think that error is stale. or at least, i'm pretty sure i got it back to how i found it.
[22:39] <mhr3> robru, hm, maybe time to run a watch-only build?
[22:40] <mhr3> but maybe not...
[22:41] <robru> mhr3, nah... there are packages in the silo that aren't listed in the MP list, so the error is technically correct. but the important thing is that i checked the last prepare job before I got there, and I called it with the same arguments, so the current state should be identical to how it was before I touched it ;-)
[22:42] <mhr3> robru, but they are listed in the sources list
[22:43] <robru> mhr3, crap, thanks. didn't notice that because the stupid spreadsheet scrolls it off the bottom of the screen
[22:44] <mhr3> yea.. +1 on the spreadsheet hiding stuff... would need 23" inch monitor to see it all
[22:45] <robru> mhr3, nope, I have a 24" and it still scrolls
[22:45] <robru> mhr3, no wait, this is my 27"... still scrolls
[22:46] <robru> mhr3, suffice to say, qt5.2 is really pushing the limits of what CI Train is capable of
[22:46] <mhr3> robru, but at least i'm sure you have more than 768 pixel height ;)
[22:46] <robru> mhr3, well, HD.
[22:48] <mhr3> robru, so anyway what was the problem? you were reconfiguring the silo and forgot to copy the extra sources?
[22:50] <robru> mhr3, yep, exactly
[22:50] <robru> mhr3, fixing it now
[22:51] <mhr3> ok
[22:52] <robru> mhr3, ok, "silo ready" ;-)
[22:53] <mhr3> robru, run watch_only build so it knows it's actually ready
[22:53] <robru> mhr3, smart
[23:17] <popey> cjwatson: thanks
[23:28] <bregma> robru, good day, it's time for my daily silo assignment, line 30 if it pleases you
[23:28] <robru> bregma, sure thing! I saw that one early and wondered when it would be ready
[23:29] <bregma> getting everyone to sign off and resolve conflicts is an act of cat herding
[23:31] <robru> bregma, have you had any reports of the new lock screen inhibiting screens from powering off? i noticed this morning that all my screens were on all night
[23:31] <robru> bregma, and you got silo 2
[23:32] <bregma> robru, I haven't heard that one yet, but there are a number of issues that have come up in real-world testing
[23:33] <robru> bregma, didn't have time to troubleshoot it properly, just noticed it was the first night since installing the new unity update and my screens were on all night. then when I unlocked the screens, they powered down then powered back on. really weird.
[23:33] <robru> bregma, i'll file a bug if today's round of fixes doesn't fix it ;-)
[23:35] <bregma> I had trouble coming back from suspend: it suspended again almost immediately and I had to unlock again, so there may be a problem with signals going over dbus