[00:40] <dejello> Hey all, I don't suppose there's any update to the porting process?
[00:40] <annerajb> I have a question what should be the output of the flipped image build? should there be a zip file on the out/target/samsung/epicmtd or w/e?
[00:45] <annerajb> dejello: i havent heard anything except probably by the end of this week a updated guide. been waiting the whole week to finish this port thought i am still on the building phase.
[00:53] <dejello> Thanks, I've been waiting as well and trying to see if I could get a build working :)
[00:58] <annerajb> dejello: what device you porting too?
[01:06] <dejello> Nook Tablet (acclaim) and Nook HD+ (ovation) and after I get ovation again will be the HD (hummingbird).  I've had acclaim for a bit, just had ovation a day before they added the ubuntu-boot.img stuff.  Admittedly I haven't worked too terribly much as I have been exhausted from work and such...
[01:07] <dejello> I am learning all this as I go as well, new to building and porting so it's an experience
[01:07] <dejello> reading, reading and more reading
[01:11] <asac> rsalveti: you think .2 is good? :)
[01:11] <asac> doanac: maybe do some love to the QA jobs in case they are stalled :)
[01:11] <asac> mako/maguro .2
[01:11] <asac> i guess
[01:13] <rsalveti> asac: needs testing still
[01:15] <asac> rsalveti: yeah. lets hope :)
[01:17] <sergiusens> rsalveti: is it ok if live-build hooks are in python?
[01:18] <rsalveti> sergiusens: don't know, something to try, only used it with shell scripts
[01:19] <sergiusens> rsalveti: ok, I'm guessing yes because of the shebang, either that or I need to install curl or similar, hmmm, or cat > < EOF a python script :-P
[01:20] <rsalveti> sergiusens: why do you need to run python in there?
[01:20] <sergiusens> rsalveti: because I get urllib out of the box
[01:21] <sergiusens> rsalveti: to download click packages
[01:21] <rsalveti> oh, right =\
[01:22] <sergiusens> rsalveti: right now I just hacked in curl to the install list, seems I have a different problem to solve first :-P http://pastebin.ubuntu.com/5882703/
[01:25] <rsalveti> oh, weird
[01:37] <sergiusens> rsalveti: solved, was a permission issue
[01:38] <rsalveti> sergiusens: great
[01:39] <sergiusens> rsalveti: so if we have curl added to the ubuntu-touch meta I can get this script in to see if it can work from the builders (++ chances it would)
[01:39] <sergiusens>  or use a python script, going to give that a go right now
[01:39] <sergiusens> to avoid adding unnecesary deps
[01:40] <rsalveti> sergiusens: right, as a hack you could just install curl before running your script
[01:40] <rsalveti> but yeah, if python is a go it should probably be a better way to go
[01:40] <sergiusens> rsalveti: yeah, and uninstall post, feel dirtier :-P
[01:40] <rsalveti> sure, just a temporary hack
[01:57] <annerajb> rsalveti: or anyone is this the correct output of a working build? http://pastebin.com/mdHB7s0C or should there be a zip file somewhere in there?
[02:00] <rsalveti> annerajb: most files are correct, but in the end you should also get a zip file called cm-10.1-<date>-UNOFFICIAL-<device>.zip
[02:00] <rsalveti> I'd probably guess that the build failed at some point
[02:00] <rsalveti> http://paste.ubuntu.com/5882777/
[02:01] <rsalveti> this is how it looks here after successfully finishing up a build
[02:02] <annerajb> rsalvetti: yeah it failed but every time i ran make again it worked and got me to this point so i thought running make again was fixing it. apparently is making it skip the failed target.
[02:02] <annerajb> rsalveti: ill run again a make clean and log the places that it's failling
[02:02] <rsalveti> right, might be easy to track, just need the failed output
[02:03] <rsalveti> usually a broken dependency somewhere
[03:08] <sergiusens> rsalveti: can you check https://code.launchpad.net/~sergiusens/livecd-rootfs/click/+merge/175178 ?
[03:11] <rsalveti> sergiusens: sounds fine, just "scares" me that we're pulling stuff from your people.canonical (in the official images), but other then that it looks fine
[03:11] <rsalveti> sergiusens: you might want to ping cjwatson to review it
[03:12] <sergiusens> rsalveti: ack, although he was the one with the original idea to copy them to my people/~
[03:12] <rsalveti> yeah, just to get this reviewed by someone that knows more about the image policies than me
[03:12] <sergiusens> rsalveti: would be good to get a final ack from him
[03:13] <sergiusens> rsalveti: or ogra_ when he wakes up
[03:13] <sergiusens> :-)
[03:13] <rsalveti> yeah :-)
[03:13] <DaveSpex> hellow
[03:14] <sergiusens> rsalveti: well if you can add a comment so the MR doesn't feel so lonely that would be nice :-)
[03:15] <DaveSpex> anybody can tell me, how can i install apps and where to find it?, and any google hangout alternatives?
[03:17] <rsalveti> sergiusens: sure
[03:18] <annerajb> rsalveti: http://paste.ubuntu.com/5882904/ It didnt require me to do make multiple times. i just typed make clean and make and it compiled on the first pass. or at least it didnt stopped building.
[03:20]  * rsalveti trying to open paste.u.c
[03:20] <rsalveti> sergiusens: just added a comment there
[03:21] <rsalveti> annerajb: interesting, might be because the image uses the yaffs2 format
[03:22] <rsalveti> not sure if you'd get a zip file because of that
[03:22] <rsalveti> which phone is this?
[03:22] <annerajb> epicmtd
[03:24] <sergiusens> annerajb: what command did you run?
[03:24] <sergiusens> annerajb: mka bacon?
[03:25] <annerajb> sergiusens: . build/envsetup.sh;repo sync; brunch epicmtd; make;
[03:26] <sergiusens> annerajb: brunch or breakfast? as brunch would do the build and not need to run make after
[03:26] <sergiusens> annerajb: do a 'make bacon' now
[03:26] <rsalveti> hm, but cyanogenmod produces a zip, something might be missing in our env
[03:26] <rsalveti> sergiusens: there's the entire build log in http://paste.ubuntu.com/5882904/
[03:26] <annerajb> i ran mka showcommands and it didnt show the commands, but let me run make bacon now.
[03:27] <sergiusens> rsalveti: yeah I'm seeing it
[03:27] <rsalveti> make otapackage might be useful as well
[03:28] <sergiusens> rsalveti: make has droid as the default target
[03:28] <annerajb> sergiusens: this is the last lines of the mka bacon
[03:28] <annerajb> i thought that was fixed on a commit done friday
[03:28] <sergiusens> rsalveti: you need bacon for the zip
[03:28] <rsalveti> sergiusens: right, bacon calls otapackage first
[03:28] <sergiusens> bacon is also the target when doing brunch
[03:29] <annerajb> sergiusens: also found this after the last lines make: *** Waiting for unfinished jobs....No command 'arget' found, did you mean:
[03:29] <sergiusens> arget?
[03:29] <annerajb> this is a fresh install so there may be missing dependencys dpkgs
[03:30] <rsalveti> yeah, you should get 'Running custom releasetool' or 'Running releasetool' printed at least
[03:30] <annerajb> let me save the output of mka bacon
[03:30] <rsalveti> build/core/Makefile, check the INTERNAL_OTA_PACKAGE_TARGET rules
[03:31] <annerajb> sergiusens: this is the output http://pastebin.com/wAi6EpQ7
[03:31] <annerajb> rsalveti: ack
[03:31] <sergiusens> ah, if that's disabled it may be why no zip
[03:32] <sergiusens> annerajb: isn't that trimmed?
[03:32] <rsalveti> should have more
[03:32] <rsalveti> maybe it just stopped
[03:32] <rsalveti> while it's downloading the initrd
[03:32] <annerajb> sergiusens: doubt it (thought it's not a make clean); i ran mka bacon > output.log
[03:32] <annerajb> rsalveti: i see what you mean.
[03:34] <annerajb> rsalveti: sergiusens i confirmed if i run mka bacon it ends at http://pastebin.com/Ky5SA5h9
[03:35] <rsalveti> now need to debug why the ota rules are not being used
[03:35] <rsalveti> might be disabled by your device config files
[03:36] <annerajb> rsalveti: where is that file?
[03:37] <annerajb> rsalveti: this is the output of mka otapackgage http://pastebin.com/36pb3W41
[03:37] <sergiusens> device/$vendor/$device
[03:38] <rsalveti> check if it's setting TARGET_RELEASETOOL_OTA_FROM_TARGET_SCRIPT for example
[03:38] <rsalveti> but that would still echo something
[03:38] <rsalveti> would need some not so fun makefile debugging
[03:39] <annerajb> rsalveti: grep -RiI 'TARGET_RELEASETOOL_OTA_FROM_TARGET_SCRIPT' BoardConfig.mk:TARGET_RELEASETOOL_OTA_FROM_TARGET_SCRIPT := ./device/samsung/epicmtd/releasetools/epicmtd_ota_from_target_files
[03:39] <sergiusens> mka showcommands otapackage
[03:41] <rsalveti> that's new to me
[03:41] <sergiusens> rsalveti: it unhides all the hides
[03:41] <rsalveti> cool
[03:42] <rsalveti> quite verbose indeed
[03:42] <sergiusens> fginther: https://code.launchpad.net/~sergiusens/cupstream2distro-config/messaging_and_dialer/+merge/175184
[03:42] <rsalveti> that should help
[03:42] <annerajb> sergiusens: http://pastebin.com/MS2ExEkq
[03:42] <sergiusens> fginther: some will fail to build, but we can't land in PPAs anymore
[03:43] <sergiusens> ake: *** No rule to make target `/home/annerabj/android/out/target/product/epicmtd/ubuntu-boot.img', needed by
[03:43] <sergiusens> cm_epicmtd-target_files-eng.annerabj.zip
[03:43] <sergiusens> annerajb: rsalveti seems a zip is possible
[03:43] <rsalveti> yeah, this is the issue
[03:43] <sergiusens> I say repo sync if you haven't in the past 6 days
[03:45] <rsalveti> and then run mka showcommands bacon
[03:45] <rsalveti> that will show if it was able to download the package successfully
[03:48] <annerajb> sergiusens: i repo sync quite a few times in the past few days since i installed this vm yesterday. but ill do it again
[03:48] <sergiusens> oh, vm
[03:48] <sergiusens> annerajb: make sure it has networking and that you can reach launchpad
[03:49] <annerajb> sergiusens: it has network because repo sync donwnloaded stuff which launchpad url should it reach the http one?
[03:53] <sergiusens> annerajb: if when you do a . build/envsetup.sh you get a hybris download, you are ok
[03:53]  * sergiusens is off to bed
[03:53] <sergiusens> way past bed time
[03:53] <annerajb> same here thanks for the help
[03:55] <rsalveti> annerajb: after repo sync, paste the output of 'mka showcommands bacon'
[03:55] <rsalveti> that should help finding the issue as well
[03:57] <annerajb> rsalveti: this is the output of mka showcommands bacon after the repo sync http://pastebin.com/TS9Ebi5a
[03:58]  * annerajb be back in 15 minutes
[03:59] <rsalveti> yeah, it's trying to use ubuntu-boot.img before downloading the file
[04:00] <annerajb_> rsalveti: this is the latest message i got from you since i DC [23:59] <rsalveti> yeah, it's trying to use ubuntu-boot.img before downloading the file
[04:00] <annerajb_> BRB
[04:00] <rsalveti> which was in theory fixed with http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_build.git;a=commitdiff;h=93a7af46f77e0f05187b9aabefa6c72b37a49511;hp=38f399e8bd0292024cdae7cabbdab5aa04fa141b
[04:17] <annerajb__> rsalveti: back
[04:18] <rsalveti> annerajb: which was in theory fixed with http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_build.git;a=commitdiff;h=93a7af46f77e0f05187b9aabefa6c72b37a49511;hp=38f399e8bd0292024cdae7cabbdab5aa04fa141b
[04:18] <rsalveti> can you check if you have such commit as part of your 'build' repository?
[04:20] <annerajb> i saw that on the mailing list and i think it was there when i checked two hours ago
[04:21] <annerajb> rsalveti: your change is on my working copy
[04:23] <rsalveti> right, your board declares BOARD_CUSTOM_BOOTIMG_MK
[04:23] <rsalveti> probably because it's creating the fs as yaffs2
[04:24] <annerajb> i assume that should be removed for ubuntu so it can create a zip right?
[04:24] <rsalveti> no, guess that's just a corner case I'm not yet handling properly, let me investigate that more
[04:25] <annerajb> rsalveti: all right
[04:26] <rsalveti> annerajb: just to check if this is indeed the issue, remove line 1217 from build/core/Makefile
[04:27] <rsalveti> annerajb: http://paste.ubuntu.com/5883021/
[04:27] <annerajb> rsalveti: and run what?mka bacon? or mka showcommands bacon
[04:27] <rsalveti> could be the showcommands
[04:28] <annerajb> rsalveti: that fixed it
[04:28] <annerajb> Package complete: /home/annerabj/android/out/target/product/epicmtd/cm-10.1-20130717-UNOFFICIAL-epicmtd.zip md5: 6010ed46fff7db28d07b7830297b00af
[04:29] <rsalveti> annerajb: that's why: http://paste.ubuntu.com/5883028/
[04:29] <rsalveti> your device defines BOARD_CUSTOM_BOOTIMG_MK, which is basically then using a custom tool to build the image
[04:29] <rsalveti> that's from device/samsung/epicmtd/shbootimg.mk
[04:30] <annerajb> hmm i see. so is that zipe file and flashing recovery all i need?
[04:30] <rsalveti> annerajb: are you trying with flipped or unflipped?
[04:31] <annerajb> rsalveti: no idea dont know how to know which one i am using
[04:32] <rsalveti> you should probably try unflipped first, which would mean you now need to install the produced zip via your recovery
[04:32] <rsalveti> and then install the ubuntu zip, which you can get from http://cdimage.ubuntu.com/ubuntu-touch-preview/raring/monthly-06/raring-preinstalled-phablet-armhf.zip
[04:33] <rsalveti> your case is a bit special, as the file system is yaffs2 (mtd)
[04:33] <annerajb> all right so to try the unflipped image i use regular clockwork recovery (not the recovery on the out folder)
[04:34] <annerajb> after that install the zip i just built
[04:34] <annerajb> and then raring-preinstalled-phablet-armhf.zip
[04:34] <rsalveti> yeah, then the ubuntu zip
[04:34] <rsalveti> let me also reply the mailing list
[07:18] <mattyw> When I try to follow the instructions on number 1 here: http://developer.ubuntu.com/get-started/ I get an error Depends: Dropping letters, anyone else seen this?
[07:50] <AskUbuntu> Depends dropping-letters error when trying to get the ubuntu-touch sdk preview | http://askubuntu.com/q/320989
[08:32] <JamesTait> Good morning all, happy International Criminal Justice Day! :-D
[08:37] <jcollado> Today I'm not seeing any /etc/device-services file in a nexus4 device. Is this because of a change in the image?
[08:38] <jcollado> ogra_: Maybe you know this? ^
[08:43] <ogra_> jcollado, we switched to upstart user sessions (actually on monday iirc)
[08:44] <jcollado> ogra_: I'm not sure of what do you mean, but phablet-test-run still relies on those files to enable/disable the shell.I guess I'm missing something.
[08:47] <ogra_> jcollado, do you know if you use phablet-flash -b for provisioning the devices for the dashboard tests ? (i.e. if home gets wiped)
[08:47]  * ogra_ was kind of assuming that, but the test failures for the last image indicate otherwise
[08:50] <ogra_> asac, so it looks like  $HOME isnt cleared for the dashboard tests , which means there is an old .bashrc sourcing dbus info from the wrong place, i just uploaded a fix for that case (but it might not make the new build since that runs already it seems, i'll trigger a new one immediately after)
[08:51] <ogra_> jcollado_afk, right, to disable the shelll you need to use upstart commands now
[08:54] <ogra_> yay, my new S4 arrived
[08:57] <kalikiana> I guess "When working on flipped images, detection does not work and would require -d" is an outdated error message at this point?
[08:57] <kalikiana> got it just now because the phone preferred to stay charging and phablet-flash doesn't like it
[08:57] <ogra_> yes, it should work now
[08:58] <popey> ogra_: do we have a new image from last night?
[08:58] <kalikiana> a more appropriate message might be "If the phone is charging, shut it down and try again"
[08:59] <kalikiana> fwiw "adb reboot" is what I do to resolve the situation
[08:59] <ogra_> popey, yes, but it has dbus issues still, and i wasnt fast enough with the fix to get it into the running build either i fear
[09:00] <timp> when are builds created? from when (what time+timezone) is 20130716 ?
[09:02] <popey> ogra_: ok
[09:02] <ogra_> timp, the default cronjob starts at  08:32 UTC and runs ~50min-1h
[09:03] <timp> ogra_: ok, thanks. so 20130716 is more than a day old
[09:03] <ogra_> timp, note that there is job queuing though, which means that if a former build runs longer we start delayed
[09:03] <ogra_> yes
[09:04] <ogra_> there were 16.1 and 16.2 builds
[09:04] <timp> ok, thanks. then probably the image that I need is building right now
[09:04] <asac> jcollado_afk: ogra_: so can we do the cleaning in the test suite?
[09:04] <asac> or in some infra script
[09:04] <asac> sounds easy enough i fthats the case
[09:04] <asac> but... did you reproduce?
[09:04] <timp> ogra_: that is odd, phablet-flash downloads 20130716 for me, not .2
[09:05] <kalikiana> https://bugs.launchpad.net/phablet-tools/+bug/1202126
[09:06] <ogra_> timp, because phablet-flash by default downloads the blessed image from /current ... 16.2 wasnt tested, so it wasnt blessed ... running phablet-flash --pending would give you .2
[09:06] <asac> ogra_: rsalveti: so guys  can you take a device, learn how to reproduce what is runon infra
[09:07] <asac> and do that?
[09:07] <timp> ogra_: ok. I need something that went into ui toolkit yesterday late, so I'll wait for 17 :
[09:07] <asac> and in the meantime stopp the presses
[09:07] <asac> nothing more going int
[09:07] <asac> all stopped
[09:07] <ogra_> asac, well, whatever autopilot does atm to stop the shell (why is that needed and not being fixed btw) needs to be switchedd to initctl/upstart
[09:07] <timp> but I guess I'll need --pending for that
[09:07] <xnox> ogra_: "blessed" gives me shiver flashbacks of trying to boot apple's crippled EFI, with partitions required to be "blessed"
[09:07] <asac> ogra_: well, stop the presses
[09:07] <asac> didrocks: ^^
[09:07] <ogra_> asac, ?
[09:07] <asac> we have to stop daily-release or something i guess
[09:07] <didrocks> hum
[09:07] <didrocks> what?
[09:07] <ogra_> what ???
[09:07] <asac> ogra_: nothing more goes in until we have fixed the dashboard
[09:08] <asac> we seem to still not know whats going on
[09:08] <asac> more stuff flows in
[09:08] <asac> we haven't backed out
[09:08] <ogra_> asac, without the upload i just did the dashboard wont be fixable
[09:08] <didrocks> asac: sorry, can you give context?
[09:08] <ogra_> so please let me go on building
[09:08] <ogra_> asac, we dont need to release the builds
[09:08] <asac> didrocks: dashboard is read. autopolit doesnt run. folks broke it with a dbus related upload
[09:08] <asac> they have been digging around
[09:08] <asac> no success
[09:08] <ogra_> nonsense
[09:08] <asac> we had no green on dashboard since last week
[09:09] <didrocks> asac: here, some tests are passing
[09:09] <asac> didrocks: that doesnt matter
[09:09] <didrocks> asac: well, I think ogra_ just don't rebuild any image
[09:09] <didrocks> or publish them
[09:09] <asac> sometghing might run somewhere.... what matters is that what we run doesnt work
[09:09] <ogra_> asac, the dbus issues are clear, what wasnt clear was that autopilot doesnt run on freshly provisioned devices
[09:09] <asac> didrocks: no
[09:09] <asac> no more packages
[09:09] <asac> only packages related to fix this problem
[09:09] <didrocks> asac: well, you are telling we have "false red"
[09:09] <didrocks> not "false green"
[09:10] <asac> didrocks: depends
[09:10] <ogra_> asac, so there is old config cruft in ~/ which the new upload works around
[09:10] <asac> good
[09:10] <ogra_> but
[09:10] <asac> so lets wait till that stuff is in
[09:10] <asac> and we hit green
[09:10] <ogra_> when i uploaded the new daily build was already running
[09:10] <ogra_> (and we cant stop live builders)
[09:10] <asac> in the meantime we cannot accept other stuff.
[09:10] <ogra_> so the next iage is needed
[09:11] <ogra_> *image
[09:11]  * didrocks is finding the discussion puzzling
[09:11] <didrocks> or confusing at best
[09:11] <ogra_> asac, just calm down, its all known and being handled, just takes a bit
[09:11] <asac> ogra_: well, every day all was known and handled, but then something new happened before we hit green
[09:12] <ogra_> give the fixes a chance :)
[09:12] <asac> so if now mr. Y uploads something else
[09:12] <asac> and it busts you
[09:12] <asac> the story continues
[09:12] <ogra_> how are we supposed to debug if not with having the dashboard tests run
[09:12] <ogra_> i dont upload something else
[09:13] <ogra_> i react to a flaw in the test setup
[09:13] <asac> ogra_: you are not doing that
[09:13] <asac> but others
[09:13] <asac> are uploading still
[09:13] <didrocks> http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/469/
[09:13] <asac> so right now didrocks might just have uploaded the next bomb
[09:13] <asac> or someone else
[09:13] <ogra_> thats fine as long as they dont add additional breakage
[09:13] <ogra_> the issues are in one specific area nothing else touches
[09:13] <didrocks> if everything in the sdk is passing tests and that's wrong, we should really question our tests
[09:13] <asac> how can we get this uynder control after 4 days of constant breakage if not by saying that folks have to stop something?
[09:13] <ogra_> and none of the other uploads will touch that area
[09:14] <asac> just looking for answers
[09:14] <didrocks> asac: do you mind sending an email to everyone telling that we are not releasing anything anymore?
[09:14] <asac> ogra_: but they might juyst shoot yoru stuff
[09:14] <ogra_> asac, there was definitely a communication issue
[09:14] <didrocks> asac: I don't want to be help responsible for that
[09:14] <didrocks> as last time I asked for a freeze, everyone got crazy
[09:14] <asac> well, if folks would be willing to back stuff out
[09:14] <didrocks> I'm fine putting everyone on manual publication meanwhile
[09:15] <didrocks> everything*
[09:15] <asac> then we could continue uploading and backout everything one by one
[09:15] <didrocks> asac: just please warn them so that I don't get a ping every 30s about "why dailies didn't happen for us?"
[09:15] <asac> didrocks: sure... if we do it we warn them..
[09:15] <ogra_> asac, i dont know if anybody warned QA about the switch to upstart user sessions, thats the firs issue here .... the other is that a hack was dropped that exports the dbus info into non local logins since there was no knowledge that the tests depend on it
[09:15] <asac> ogra_: so lets wait for this
[09:15] <Mihir__> Hey any one who is working on Calculator core app there ?
[09:16] <didrocks> asac: so, ack on putting everything on manual publication?
[09:16] <asac> if this doesnt fix it, we do it and start backing out.
[09:16] <ogra_> asac, what jcollado_afk mentioned above might have additional impact though ...
[09:16] <ogra_> which backing out wont solve
[09:16] <didrocks> ok, I'll wait for asac's red alert ;)
[09:16] <asac> jcollado_afk: can you coome to keyboar?
[09:17] <ogra_> autopilot needs to be ported to use upstart session mgmt to kill the shell ....
[09:17]  * didrocks puts his red phone next to his laptop
[09:17] <ogra_> seems we cant run it while the shell runs
[09:17] <asac> lol
[09:17] <ogra_> and atm they use a hack that rips unity8 out of the session startup
[09:17] <timp> Mihir__: I think most app-development talk goes on in #ubuntu-app-devel
[09:17] <asac> gema: is there anyone else who knows about autopilot and utah who is available right now?
[09:17] <ogra_> as i understand
[09:18] <asac> we need to teach ogra and folks how how to use utah and exactly reproduce what we see there
[09:18] <ogra_> asac, well, i can read logs
[09:18] <gema> ogra_: do you have access to the lab?
[09:18] <ogra_> no need to run it for that :)
[09:18] <ogra_> gema, i have vpn access
[09:18] <gema> cool
[09:19] <ogra_> no magners account though ... in case thats needed
[09:19] <gema> ogra_: so whilst jcollado comes back I will show you how to find the right job
[09:19] <gema> and utah command
[09:19] <ogra_> ok
[09:19] <gema> ogra_: then he can tell you how to set up your devices and stuff if it is not clear from the job
[09:19] <sil2100> gusch: ping! Hi!
[09:20] <gusch> sil2100: pong
[09:20] <gema> ogra_: give me an autopilot job as an example?
[09:20] <gema> whichever you are trying to figure out
[09:20] <sil2100> gusch: since today, one AP test for gallery-app seems to fail
[09:20] <ogra_> gema, for what issue exactly ?
[09:20] <sil2100> gusch: gallery_app.tests.test_photo_viewer.TestPhotoViewer.test_nav_bar_share_button
[09:20] <sil2100> gusch: http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/470/testReport/
[09:20] <gema> ogra_: I don't know, I guess you are trying to diagnose something
[09:20] <gusch> sil2100: and I have no idea why
[09:21] <ogra_> gema, not really, diagnosis should be done already :)
[09:21] <sil2100> gusch: nothing changed in the UITK by any chance?
[09:21] <gema> ogra_: or else why does asac wants it right now
[09:21] <gema> what is the rush ?
[09:21] <asac> ogra_: the problem is that you still guess when looking at logs. doanac explained how to run the stuff exactly like in utah yesteday
[09:21] <gusch> sil2100: and it's not the only one, there have been some other (random) failing ones as well
[09:21] <sil2100> 'NoneType' object has no attribute 'visible'
[09:21] <asac> gema: ogra thinks the current seen problem is now fixed
[09:21] <ogra_> gema, one was a dbus issue https://jenkins.qa.ubuntu.com/job/saucy-touch-maguro-smoke-gallery-app-autopilot/8/console.... for which fixes are in but not in an image yet ... the other is a code issue that running wont solve
[09:22] <asac> but we of course dont know what is next without runnign exactly what utah runs a few times
[09:22] <ogra_> s/running/running utah/
[09:22] <asac> and reproducig the issue
[09:22] <gusch> sil2100: well - the sharing component - no idea if that got an update, or the SDK
[09:22] <gusch> sil2100: works fine locally for me
[09:22] <ogra_> asac, we know what is next but i need jcollado_afk to fconfirm, then we can fix utah
[09:22] <asac> gema: so that :)
[09:23] <gema> asac: understood
[09:23] <asac> we need someone to land stuff in utah for us. folks have been digging around for days
[09:23] <asac> and when we landed a fix another breakage came etc.
[09:23] <gema> asac: who is digging?
[09:23] <ogra_> asac, in multiple different issues
[09:23] <asac> everyone here
[09:23] <ogra_> asac, dont mix them up :)
[09:23] <asac> sure, just saying that if we cannot get it under control
[09:23] <gema> asac: ok, what do you mean land stuff in utah?
[09:23] <asac> we have to set all development to manual
[09:23] <asac>  mode
[09:23] <asac> e.e.g nothing goes in until we fix this issue etc.
[09:23] <sil2100> gusch: did you try with the most recent SDK and stuff?
[09:23] <ogra_> asac, we can and we will
[09:24] <gema> asac: ok, so you want people to be able to reproduce with utah locally
[09:24] <asac> gema: they say they cannot see the issue
[09:24] <gema> asac: not necessarily manually, but definitely on their devices
[09:24] <gusch> sil2100: at least with what's in saucy
[09:24] <asac> i forwarded a mail to them telling how to run utah-autopilot not sure if they tried it
[09:24] <gema> ok, I can work with andy in creating a video training
[09:24] <gema> for that
[09:24] <gema> asac: us teaching every developer one by one doesn't escale
[09:24] <sil2100> gusch: it might be a recent change, so maybe try adding ppa:ubuntu-unity/daily-build and use the SDK components from there
[09:25] <sil2100> gusch: since I didn't publish SDK yet because I want to make sure all Apps are ok
[09:25] <gusch> sil2100: "file:///usr/share/gallery-app/rc/qml/MediaViewer/MediaViewer.qml:459: ReferenceError: caller is not defined" that is weired - and weired it's only for the sharing
[09:26] <asac> gema: i dont know how you do that.
[09:26] <asac> its just that we need to know whats going on right now
[09:26] <gema> asac: we create a hangout and make it public, andy explains exactly how to run those things locally on their devices
[09:26] <asac> ogra_ and rsalveti upload without having ever reproduced this
[09:26] <gema> maybe we have someone like ogra or rsalveti asking questions
[09:26] <asac> so its completely digging in the dark
[09:26] <gema> and then we make it available to everyone for watching
[09:26] <asac> i am not swure. i have sent instructions
[09:26] <gema> asac: ok, then let's see if those have any effect
[09:27] <gema> first
[09:27] <ogra_> gema, asac, the current issue is that the exiting dbus fix assumes the tests run on a freshly installed device that has no pre-existing stuff in $HOME
[09:27] <gusch> sil2100: "ppa:ubuntu-unity/daily-build" will kill my machine - I played that game way too often - sorry
[09:27] <ogra_> which doesnt seem to be the case, so it still fails
[09:27] <asac> ogra_: you got myu mail from last night?
[09:27] <ogra_> asac, yes
[09:27] <asac> it has the instructions how to run autopilot in utah style
[09:27] <ogra_> again i dont need to run utah to know whats wrong
[09:27] <gema> ogra_: the tests right now are not reprovisioning
[09:27] <asac> ogra_: but you can check now if after your upload everything is good
[09:28] <gema> ogra_: and that is done on purpose to have a more realistic environment
[09:28] <asac> this would calm me down
[09:28] <ogra_> gema, yeah, there is a fix that will handle that on our side
[09:28] <asac> and give me believe :)
[09:28] <ogra_> gema, just waiting for it to hit an image
[09:28] <gema> ogra_: ok, sounds good
[09:28] <asac> if folks look at log, upload the symptom they see, they might hit another symptom
[09:28] <gema> asac: all is good, ogra_ and I have an understanding
[09:28] <asac> ok super
[09:28] <gema> that things are going to be better
[09:28] <gema> and I will track that
[09:28] <ogra_> gema, but there is another issue that jcollado_afk pointed out
[09:28] <asac> so will we test before upload if our upload fixes stuff?
[09:29] <gema> ogra_: yes, I know, the apps crashing sometimes
[09:29] <ogra_> gema, no
[09:29] <gema> ogra_: not handling options properly
[09:29]  * asac goes off for a bit
[09:29] <gema> ogra_: ok, another one?
[09:29] <asac> to not make everyone completely zero productive :)
[09:29] <ogra_> there is some weird bug in unity8 that forces you to stop the shell to test apps
[09:29] <gema> asac: thanks ;)
[09:29] <asac> what i need are new dashboard results
[09:29] <asac> thats all i need
[09:29] <asac> freseh, well run dashboard results :-P
[09:29] <ogra_> due to that bug you guys have a hack in autopilot that stops the shell before running tests
[09:29] <gema> ogra_: yes
[09:29]  * asac looks away to not see how that is done
[09:30] <ogra_> the code for stoppin the shelll needs to be adjusted to work with upstart sessions
[09:30] <gema> ogra_: do you have a bug for that?
[09:30] <ogra_> asac, well, the underlying bug needs to be fixed
[09:30] <gema> I can nag thomi and veebers to get this fixed overnight
[09:30] <ogra_> gema, no, i didnt have a chance to file one since asac hammers me on IRC since i heard about the issue :P
[09:31] <gema> ogra_: no worries he is going to be quiet for a while, make sure you file a bug that is clear and has all the info in it (or the NZ timezone will not allow this to happen quick) and I will make sure it does
[09:32] <ogra_> right, i need to look at the code and can probably even come up with a patch
[09:32] <gema> ogra_: that'd be even better
[09:32] <ogra_> first i want to see if the fiormer fix makes the dbus issues pass though ... it is uploaded and needs a new image (missed the currently building one, so it will take another 90min or so)
[09:33] <gema> ack
[09:34] <gema> ogra_: I understand that you and doanac are in touch regarding starting to run tests on --pending?
[09:34] <ogra_> yep
[09:34] <gema> cool
[09:34] <sil2100> gusch: well, if you only enable it for a moment and install UITK from it and then disable it, there's no risk
[09:35] <sil2100> gusch: since the UITK and SDK elements in daily-build are now ready for publishing
[09:35] <sil2100> So today you'll have the same thing in saucy anyway
[09:37] <gusch> sil2100: well then - there is no difference in waiting a bit ;)
[09:38] <gusch> sil2100: I'm in no hurry :p
[09:39] <sil2100> gusch: but I don't want to publish the SDK if I have no 100% surness that it doesn't break apps! ;p
[09:39] <gusch> sil2100: argh - we really need to run app-tests when integrating SDK ...
[09:40] <sil2100> gusch: we run, but not all of them
[09:40] <sil2100> gusch: the ones that we run did not fail, but hm
[09:40] <gusch> sil2100: as part of jenkins? really? nice
[09:40] <sil2100> Actually I wonder what could be the problem with that test
[09:40] <sil2100> gusch: we run them daily, before daily release
[09:41] <timp> would be even better to run apps tests before approving a merge for SDK
[09:41] <timp> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1192944
[09:43] <sil2100> gusch: I also poked om26er to help out, so maybe he'll know what could be up
[09:46] <ogra_> hmm, whats up with the milaing list ?
[09:46] <ogra_> *mailing list
[09:46]  * ogra_ just got a bunch of really old mails
[09:46] <gusch> sil2100: there is no newer SDK in the daily build
[09:52] <xnox> ogra_: somebody cleared unapproved / non-member posts?
[09:52] <ogra_> yeah, probably
[09:52] <ogra_> do you see it too ?
[09:53] <ogra_> else i might have to blame my mailserver
[09:53] <didrocks> gusch: there is: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages?field.name_filter=ubuntu-ui-toolkit&field.status_filter=published&field.series_filter=
[09:54] <xnox> ogra_:
[09:54] <xnox> ogra_: yeah...
[09:54] <ogra_> ah, good
[09:55] <xnox> ogra_: well ubuntu-phone mailing list is the one i guess you are referring to.
[09:55]  * ogra_ fires off a 20130717.1 build
[09:55] <ogra_> xnox, yep, thats the one
[09:55] <davmor2> Morning all
[09:55] <ogra_> moin moin
[09:55] <davmor2> how are the images this morning :)
[09:56] <sil2100> gusch: you did an update first? Since I remember I was fixing things due to new dependencies in the UI toolkit
[09:56] <ogra_> davmor2, ignore 20130717 and wait for 20130717.1 (currently building)
[09:56] <sil2100> om26er: could you coordinate with gusch about the AP issues of gallery-app?
[09:57] <davmor2> ogra_: good to know thanks :)
[09:58] <om26er> sil2100, I am working on fixing that test and for future I think you can ping me for test failures for Apps
[09:58] <gusch> sil2100 didrocks weired, now it's there ... installing
[10:00] <dpm> mardy, are you around and can you join us on #ubuntu-app-devel for a question on Online Accounts?
[10:01] <gusch> sil2100: even with this latest SDK, it works fine locally
[10:01] <gusch> om26er: what's the issue with that test?
[10:02] <om26er> gusch, the mouse moved to the share button on the toolbar but the click somehow did not register hence the menu did not appear
[10:02] <om26er> mostly due to slowness in jenkins
[10:03] <om26er> gusch, I think the workaround (fix?) would need to happen in click_item() increase in the delay before clicking will likely fix
[10:04] <om26er> "hey go to the share button but wait Xseconds before clicking because our VM is slow"
[10:06] <gusch> om26er: we should start using "self.pointing_device.click_object()" instead of the click_item()
[10:06] <om26er> gusch, I created that method to workaround this issue in jenkins before
[10:07] <gusch> om26er: no idea if that would help, but it would be the proper function to use
[10:07] <gusch> om26er: ah - I thought it's a part of autopilot
[10:07] <om26er> gusch, click_object() would result in more failures
[10:11] <veebers> gema, ogra_: Hi, my ears were burning :-) Are you talking about the code in phablet-test-run that stops the shell etc.?
[10:11] <gema> veebers: I think ogra_ is , yes
[10:12] <om26er> sil2100, hey, so all these tests run in a single VM, one after the other? how much ram does the VM have?
[10:12] <veebers> gema, ogra_: I believe sergiusens or om26er would be the ones to talk to re: that. I think they're familiar w/ that code
[10:12] <gema> om26er: if you are running tests on a VM on an overloaded jenkins server and the tests do not pass because it is too slow
[10:12] <om26er> veebers, gema I am supposed to fix that, once service unity8 start/stop works
[10:13] <gema> om26er: the solution is not to increase the timeout
[10:13] <gema> om26er: we need to talk about that
[10:13] <veebers> om26er:  ah cool
[10:13] <gema> om26er: cool
[10:13] <ogra_> om26er, should work with the next image
[10:13] <ogra_> 17.1
[10:14] <om26er> ogra_, would it work with dist-upgrade or something android side will be needed? aka reflash
[10:15] <om26er> gema, I think its fine for the cases where there is only one app' tests are run. but for the cases where we run autopilot tests for the whole image, we may need to increase the RAM of the VM
[10:15] <ogra_> dist upgrade to the latest ubuntu-touch-session (0.59) whould do it
[10:15] <ogra_> *should
[10:15] <gema> om26er: no, if VMs are too slow for this kind of testing then we test on bare metal
[10:15] <om26er> ogra_, I reported a bug yesterday where 'service restart ubuntu-touch-session' would break dbus somehow i.e. qdbus says connection refused
[10:16] <gema> om26er: but we don't mess with reasonable timeouts that will then make failed tests pass in hw
[10:17] <gema> om26er: it doesn't matter how much memory you give to the VM if the server that runs them is overloaded, that is an environmental issue that needs to be resolved outside the tests
[10:17] <gema> om26er: unless you think the timeouts are unreasonable even for HW
[10:17] <om26er> gema, timeouts are not needed for our desktops as all tests pass. so its indeed an environment issue
[10:18] <gema> om26er: then don't change them, let's figure out where to run those VM tests
[10:18] <om26er> gema, i mean if i run tests locally they always pass, but they do have a tendency to fail in jenkins (due to slowness)
[10:18] <om26er> gema, ok, great
[10:18] <gema> om26er: that is a confusing statement, since jenkins is just a glorified cron
[10:18] <gema> om26er: tests fail on the virtualised environment , rather
[10:18] <gema> right?
[10:18] <gema> om26er: do the tests pass when you run them on a VM at home?
[10:18] <om26er> gema, yep, I meant that
[10:19] <gema> om26er: let's try to be precise with these things or else we all end up blaming jenkins or utah or the lab and get confused
[10:19] <om26er> gema, never tried in a VM here, always run natively
[10:19] <gema> om26er: try on a VM
[10:20] <om26er> gema, will do
[10:20] <gema> om26er: thanks
[10:21] <om26er> np :)
[10:21] <jcollado> asac, ogra_: I'm back.
[10:22] <gema> jcollado: I think we don't need you
[10:22] <gema> jcollado: ogra_ has everything under control
[10:22] <jcollado> gema: Ok. Thanks.
[10:22] <ogra_> jcollado, thanks for pointing it out though
[10:23]  * ogra_ wasnt aware you hacked /etc/device-services, i thought you just killled unity8
[10:33] <sergiusens> asac: gema ogra_ it's still failing because the change that was mentioned yesterday didn't happen here: http://bazaar.launchpad.net/~utah/utah/dev/view/head:/examples/run_utah_phablet.py#L142
[10:36] <ogra_> sergiusens, ah, yeah, the dbus-session needs to be sourced from the new location ... and it needs to use initctl to stop unity8
[10:48] <popey> I spy 20130717.1
[10:48] <om26er> ogra_, hey! I have the latest ubuntu-touch-session now but: 'service unity8 restart' still says "unity8: unrecognized service"
[10:49] <ogra_> om26er, are you the phablet user ?
[10:49] <ogra_> you need to be in the users session
[10:49] <ogra_> (root cant see user sessions)
[10:49] <om26er> tried both way. as phablet user with ssh, and over adb as root
[10:49] <ogra_> and you used "initctl stop unity8" ?
[10:50] <om26er> ogra_, THAT, I was using 'service unity8 stop' now it works
[10:50] <ogra_> (initctl list should also list all apps in the session)
[10:50] <ogra_> yay
[10:50] <didrocks> om26er: they are not running on VM but on real hardware, beefy machines with 4 to 8G of RAM…
[10:52] <ogra_> hmm
[10:52] <ogra_> phablet@ubuntu-phablet:~$ initctl list|grep unity
[10:52] <ogra_> unity7 stop/waiting
[10:52] <ogra_> unity-panel-service stop/waiting
[10:52] <ogra_> unity8 start/running, process 632
[10:52] <ogra_> now thats really intresting
[10:52] <om26er> I just noted that
[10:52] <didrocks> om26er: most of the thing which induced slowliness is autopilot itself when run with rmd
[10:52] <ogra_> where do unity7 and unity-panel-service come from
[10:52] <ogra_> its not a biggie since they dont run, but something seems to register them in upstart
[10:53] <om26er> didrocks, I am thinking what's going to be the solution for that. should we just delay the click ?
[10:53] <didrocks> om26er: not sure, you can ssh/use kvm on the machine, you should have videos as well
[10:53] <didrocks> on the jenkins job
[10:53] <om26er> didrocks, I saw the video
[10:53] <didrocks> ok, maybe this delay is induced by unity7
[10:54] <didrocks> as we are seeing a lot of stuff running slowly on it
[10:54] <didrocks> om26er: does the video seems slow?
[10:54] <om26er> didrocks, the video seems to also show that the environment is loaded quite heavily given the video is slow
[10:54] <om26er> didrocks, yeah
[10:54] <didrocks> om26er: the video is 7fps
[10:54] <om26er> http://<IP_ADDRESS>:8080/job/autopilot-saucy-daily_release/label=autopilot-intel/470/artifact/results/autopilot/videos/gallery_app.tests.test_photo_viewer.TestPhotoViewer.test_nav_bar_share_button%20(with%20mouse).ogv
[10:54] <didrocks> om26er: otherwise rmd was getting crazy
[10:55] <om26er> didrocks, i am sure if that suite is run again the same test will pass. it wen't haywire that time only due to environmental issue
[10:55] <didrocks> om26er: hum, weird though that one both config, it failed, isn't it?
[10:56] <om26er> didrocks, that's the head scratching part :/
[10:56] <asac> sergiusens: ok... don't give up getting that in :)
[10:56] <asac> thanks!
[10:56] <om26er> didrocks, i do think increase in the delay will fix though
[10:57] <didrocks> om26er: so I don't trust a new run will fix those, autopilot doesn't introspect the app to know that something is loading?
[10:57] <asac> sergiusens: maybe you can tell gema exactly what was discussed?
[10:57] <asac> unkless you already did
[10:57]  * asac out again doing other stuff
[10:58] <om26er> didrocks, we do make sure (in the test) that before moving the mouse make sure the toolbar is fully visible. What we may need to also assert is that the toolbar is not animating before moving the mouse
[10:58] <didrocks> om26er: yeah, not sure how feasable it is though
[10:59] <om26er> It could be that the "spread" state of the toolbar becomes true even when the minor part of the toolbar is visible on screen.
[10:59] <didrocks> om26er: I would do either way: have a WI to have this done and implemented. If the media apps team needs to get their stuff quickly, timeout as workaround, but noted as such and removed timely :)
[10:59] <didrocks> om26er: right, that would make sense
[11:00] <didrocks> sil2100: so at leat, it confirms we can publish the sdk stack ^
[11:01] <om26er> didrocks, sil2100 can you point me to the sdk change? I want to run this specific test with the latest sdk you guys talking about
[11:01] <didrocks> om26er: oh, you didn't try with it? I thought you did
[11:01] <didrocks> om26er: ubuntu-unity/daily-build
[11:01] <didrocks> grab latest sdk packages
[11:01] <didrocks> sil2100: wait then! ^
[11:04] <dinky_> Hi everyone, just trying to sort out google contacts sync with syncevolution. Not having muuch luck. The directions here spew errors at me: http://sergiusens.github.io/posts/google-contacts-on-ubuntu-touch.html Anyo
[11:04] <dinky_> Anyone sort this on a recent build?
[11:06] <om26er> didrocks, that's actually a regression in the sdk :p
[11:06] <om26er> oh the irony
[11:06] <didrocks> om26er: ah, so sil2100 was right to refrain it :p
[11:06] <om26er> file:///usr/share/gallery-app/rc/qml/MediaViewer/MediaViewer.qml:459: ReferenceError: caller is not defined
[11:06] <didrocks> om26er: stop blaming jenkins/the machines running tests :p
[11:06] <didrocks> Kaleo: timp ^
[11:07] <didrocks> sil2100: so, no forced release of the sdk please :)
[11:07] <om26er> didrocks, right ;) it has happened for us in ps-qa jenkins jobs in the past though
[11:07] <didrocks> om26er: I wonder why gusch can't reproduce though
[11:07] <didrocks> om26er: trust daily-release infra ;)
[11:09]  * greyback hates that nasty click when his nexus seems to get stuck in a reboot loop
[11:09]  * om26er didn't knew there was a UI toolkit update in the context as well.
[11:13]  * ogra_ notes popey answers to mails from feb.
[11:14] <popey> oh
[11:14] <popey> didnt see the date
[11:14] <popey> has someone let a load of moderated mail through?
[11:15] <om26er> ogra_, hey
[11:16] <om26er> ogra_, can we pass arguments while starting a service? I would like to start unity8 with -testability for example
[11:16] <gusch> didrocks: I see that "caller" error only on jenkins (and I do have meanwhile the new SDK)
[11:16] <ogra_> om26er, hmm, i think so, i guess through a variable parameter that you need to export when callin initctl... xnox do you happen to know that ?
[11:16] <om26er> gusch, I have the same issue here as well.
[11:17] <ogra_> popey, looks like, there are really ancient mails among them
[11:17] <popey> i blame callum
[11:18] <xnox> om26er: start unity8 MY_VAR=foobar
[11:18] <xnox> om26er: will make $MY_VAR available in the environment.
[11:19] <ogra_> xnox, what would MY_VAR be for a command option
[11:19] <ogra_> i.e. if you want unity8 --foople
[11:19] <xnox> om26er: your job file, then should use a variable.
[11:19] <xnox> om26er: alternatively you can use an override file "echo 'exec unity8 --foople' > unity8.override"
[11:20] <ogra_> xnox, ah, thanks, i guess we should change the unity8 job then to accept something like $OPTIONS and use it if set
[11:20] <xnox> om26er: you can place override files in any of XDG_CONFIG_DIRS/upstart or XDG_CONFIG_HOME/upstart locations: ~/.config/upstart, /etc/xdg/xdg-ubuntu/upstart, /etc/xdg
[11:21] <om26er> xnox, cool, thanks. Will try and let you know
[11:21] <ogra_> i guess ~/.config/upstart will do
[11:23]  * popey updates https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0ArLs7UPtu-hJdDZDNWliMmV1YUJ3Zk1pQlpDdGp4VFE#gid=0
[11:26] <sil2100> didrocks: :D
[11:26]  * sil2100 sometimes learns from experience
[11:27] <didrocks> sil2100: nice call ;)
[11:28] <Laney> sergiusens:
[11:28] <Laney> Preparing to replace phablet-tools 0.15+13.10.20130712-0ubuntu1 (using .../phablet-tools_0.15+13.10.20130716-0ubuntu1_all.deb) ...
[11:28] <Laney> Unpacking replacement phablet-tools ...
[11:28] <Laney> dpkg: error processing /var/cache/apt/archives/phablet-tools_0.15+13.10.20130716-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/lib/python2.7/dist-packages/tests/__init__.py', which is also in package hud-tools 13.10.1+13.10.20130717-0ubuntu1
[11:32] <xnox> Laney: bug in both packages, as top level "tests" module should never be shipped.
[11:32]  * xnox was pondering to write lintian check for it, as too much automatic setup-tools does that a lot.
[11:32] <Laney> yes
[11:36] <ogra_> gema, https://code.launchpad.net/~ogra/utah/fix-dbus-location/+merge/175254 ... (not sure who can approve it, but that should solve all dbus issues)
[11:37] <ogra_> (it wouold be a lot better if it would just rely on the users environment that explicitly exporting though)
[11:38] <ogra_> (but before asac wants to stop everything again, i rather leave the hack in since it is known to work :P )
[11:39] <gema> jcollado: ^^
[11:39] <gema> jcollado: can you review and approve?
[11:39] <gema> or reject, whichever you feel is better :P
[11:40] <jcollado> gema: Yes
[11:40] <gema> jcollado: thanks
[11:40] <ogra_> the get_phone_shell_cmds()  function needs to go or at least be rewritten from the ground up
[11:40] <ogra_> but thats something jcollado knows already :)
[11:42] <ogra_> (in shell i would just do something like: "pgrep unity8 >/dev/null 2>&1 && initctl stop unity8"
[11:42] <ogra_> )
[11:43] <om26er> sergiusens, do we still want to keep compatibility for non-flipped images in phablet-test-run or should I just remove it ?
[11:44] <ogra_> just drop it
[11:44] <popey> ogra_: 20130717.1 seems good here
[11:44] <ogra_> non flipped will be completely dead by end of the week
[11:44] <ogra_> (it is currently in a weird zombie state)
[11:45] <ogra_> popey, yeah, but i fear we will still see red tests on utah ...
[11:45] <om26er> xnox, ogra_ thanks, that worked fine.
[11:45] <ogra_> there are teo fixes that need to go in .... (one is the MP above, the other the unity8 initctl stuff above)
[11:46] <popey> k
[11:46] <ogra_> s/teo/two/
[11:46] <jcollado> ogra_: Ok, so no more updates to /etc/device-services (which doesn't exist anymore) and just "initctl start/stop unity8" ?
[11:46] <xnox> ogra_: is dbus-session hack specific to ubuntu touch?
[11:46] <xnox> ogra_: cause i don't have ~/.cache/upstart/dbus-session here =) but wish I had.
[11:47] <xnox> ogra_: it's for autopilot ubiquity, in my case.
[11:47] <ogra_> jcollado, right, you should be able to test with initctl status unity8 (or pgrep as shown above) if it runs
[11:47] <ogra_> xnox, dbus creates it
[11:47] <xnox> ogra_: but that location seems odd, shouldn't it be, $XDG_RUNTIME_DIR/dbus-session ?
[11:47] <ogra_> make sure to have the latest
[11:47] <xnox> ogra_: ah, I didn't log out in a while.
[11:48] <ogra_> xnox, feek free to improve, but note that utah currently hardcodes the location
[11:48] <ogra_> *feek/feel/
[11:48] <ogra_> not sure if XDG_RUNTIME_DIR always reliably points to ~/.cache/upstart/
[11:49] <jcollado> ogra_: "pgrep unity8" returns a pid, but any initctl command returns "initctl: Unknown job: unity8"
[11:49] <xnox> ogra_: no, it points to a logind assigned location in /run/, e.g. /run/user/1000/
[11:50] <ogra_> jcollado, how do you call it ?
[11:50] <jcollado> ogra_: $ initctl status unity8
[11:50] <jcollado> initctl: Unknown job: unity8
[11:50] <ogra_> hablet@ubuntu-phablet:~$ initctl status unity8
[11:50] <ogra_> unity8 start/running, process 1459
[11:50] <xnox> ogra_: as we don't want to keep that file persistent acroos multiple logins.
[11:50] <ogra_> jcollado, are you the phablet user ?
[11:50] <ogra_> it only works in the users env
[11:50] <xnox> jcollado: you are probably not running as the phablet user. You need to be on the same UPSTART_SESSION.
[11:50] <ogra_> not as root
[11:50] <jcollado> ogra_: Yes
[11:51] <ogra_> phablet@ubuntu-phablet:~$ env |grep UPSTART
[11:51] <ogra_> UPSTART_SESSION=unix:abstract=/com/ubuntu/upstart-session/32011/532
[11:51] <ogra_> you shoudl see something similar
[11:51] <xnox> jcollado: initctl list-sessions
[11:52] <xnox> jcollado: and then export UPSTART_SESSION=$whatever is above, e.g. "unix:abstract=/com/ubuntu/...."
[11:52] <jcollado> $ env | grep UPSTART
[11:52] <jcollado> UPSTART_INSTANCE=
[11:52] <jcollado> UPSTART_EVENTS=filesystem
[11:52] <jcollado> UPSTART_JOB=android-tools-adbd
[11:52] <jcollado> phablet@ubuntu-phablet:~$ initctl list-sessions
[11:52] <jcollado> 547 unix:abstract=/com/ubuntu/upstart-session/32011/547
[11:52] <jcollado> xnox: Let me try that export
[11:52] <ogra_> jcollado, make sure to have ubuntu-touch-session 0.59 or bigger installed
[11:52] <ogra_> from there on the var should be in the users env
[11:53] <jcollado> xnox: After the export, seems to work fine.
[11:54] <ogra_> hmm, ubuntu-touch-session definitely should do that export
[11:54] <ogra_> in all cases
[11:54] <jcollado> ogra_: Version 0.58
[11:54] <ogra_> ah, phew
[11:54] <ogra_> :)
[11:54] <ogra_> upgrade it then and all should be fine
[11:55] <jcollado> ogra_: From what I see in the channel, my understanding was that I needed to "phablet-flash -b", but the flash failed (not sure why). Do I need to re-flash or just upgrade the packages?
[11:56] <ogra_> just apt-get update && apt-get install ubuntu-touch-session
[11:57] <ogra_> that should give you even 0.60
[11:59] <om26er> is there a way to login as user (and not root) with adb on flipped images
[11:59] <ogra_> nope
[11:59] <jcollado> ogra_: Upgraded to 0.60, rebooted to make sure and still I get the "Unknown job: unity8"
[11:59] <ogra_> only sudp -u phablet -i
[11:59] <ogra_> *sudo
[11:59] <ogra_> jcollado, do you see UPSTART_SESSION in your env ?
[12:00] <jcollado> ogra_: Nope. Same output as above:
[12:00] <jcollado> $ env | grep UPSTART
[12:00] <jcollado> UPSTART_INSTANCE=
[12:00] <jcollado> UPSTART_EVENTS=filesystem
[12:00] <jcollado> UPSTART_JOB=android-tools-adbd
[12:01] <ogra_> ls /etc/profile.d/
[12:01] <ogra_> is there an upstart-phablet.sh file ?
[12:01] <popey> http://popey.com/~alan/device-2013-07-17-125732.png  made me smile today ☻
[12:01] <popey> I did indeed take 1 photo!
[12:02] <om26er> ogra_, cool, this did what I wanted: adb shell '$@' sudo -u phablet -i initctl start unity8
[12:02] <ogra_> yay
[12:02] <ogra_> popey, well, does it change if you take another one ?
[12:04] <popey> ogra_: i haven't dared take another photo :D
[12:04] <ogra_> heh
[12:04] <popey> (yes)
[12:04] <popey> love this
[12:04] <jcollado> ogra_: Yes
[12:05] <jcollado> $ ls /etc/profile.d/
[12:05] <jcollado> dbus-source.sh  upstart-phablet.sh
[12:05] <ogra_> hmm, then i dont get why it isnt executed for you
[12:05] <ogra_> jcollado, it clearly works for om26er
[12:05] <ogra_> (and for me)
[12:06] <ogra_> jcollado, is that via adb (and then sudp -u phablet -i) or via ssh
[12:06] <ogra_> *sudo
[12:06] <jcollado> ogra_: adb
[12:06] <om26er> flipped ?
[12:06] <ogra_> hopefully
[12:06] <ogra_> unflipped on nexus is dead and done since weeks
[12:06] <ogra_> :)
[12:07] <ogra_> phablet@ubuntu-phablet:~$ env|grep XDG
[12:07] <ogra_> XDG_RUNTIME_DIR=/run/user/32011
[12:07] <ogra_> do you have XDG_RUNTIME_DIR in your env ?
[12:08] <jcollado> ogra_: I tried using ssh and that works
[12:08] <ogra_> well, adb should too
[12:08] <jussi> Is Mirv on holidays?
[12:08] <ogra_> jcollado, did you log out and in after installing the new package ? it indeed needs a new login for the changes to take effect
[12:09] <jcollado> ogra_: I rebooted
[12:09] <ogra_> since we source from /etc/profile.d
[12:09] <ogra_> hmpf
[12:09] <ogra_> thats really strange
[12:09] <jcollado> $ env | grep XDG
[12:09] <jcollado> XDG_SESSION_ID=c3
[12:09] <jcollado> XDG_RUNTIME_DIR=/run/user/32011
[12:09] <jcollado> (with adb)
[12:09] <ogra_> ok, thats good
[12:10] <ogra_> i dont get why UPSTART_SESSION isnt there though, it is exported from the exact same place that sets XDG_RUNTIME_DIR
[12:12] <ogra_> jcollado, /sbin/initctl list-sessions | awk '{ print $NF; quit }'
[12:12] <ogra_> does that retunr anything
[12:13] <ogra_> unix:abstract=/com/ubuntu/upstart-session/32011/532 is what i get here
[12:14] <ogra_> (and thats also what the prifile.d snippet should put into UPSTART_SESSION
[12:14] <ogra_> )
[12:14] <jcollado> $ /sbin/initctl list-sessions | awk '{ print $NF; quit }
[12:14] <jcollado> unix:abstract=/com/ubuntu/upstart-session/32011/547
[12:14] <ogra_> *profile
[12:14] <ogra_> wow, so weird
[12:14] <ogra_> why is it not exported then
[12:14] <ogra_> like for everyone else
[12:16] <xnox> ogra_: jcollado: we only setup upstart-user session for graphical login, adb / ssh / sudo will not get you an upstart-session.
[12:16] <ogra_> xnox, wrong :)
[12:16] <xnox> thus initctl list-sessions hack is needed to fetch the currently running session.
[12:16] <xnox> ogra_: what have you done ogra and where?! =)))))
[12:17] <ogra_> root@ubuntu-phablet:/# cat /etc/profile.d/upstart-phablet.sh
[12:17] <ogra_> # Join the phablet Upstart session
[12:17] <ogra_> uid=$(getent passwd "$USER"|cut -d: -f3)
[12:17] <ogra_> export XDG_RUNTIME_DIR="/run/user/$uid"
[12:17] <ogra_> export UPSTART_SESSION=$(/sbin/initctl list-sessions | awk '{ print $NF; quit }')
[12:17] <xnox> the best of upstart cookbook =)
[12:18] <ogra_> xnox, every login in touch should automatically join the session that way
[12:18] <xnox> ogra_: but that assumes that a session is present. if the session leader is topped (e.g. unity8) the session dies.
[12:18] <ogra_> the session leader isnt unity8 :)
[12:18] <ogra_> its ubuntu-touch-session
[12:19] <ogra_> unity8 is just one app in it
[12:19] <ogra_> s/app/job/
[12:19] <ogra_> so you can kill the shell and still have the rest of the session up
[12:19] <ogra_> (and can restart the shell etc)
[12:19]  * xnox clearly needs to upgrade to latest image and poke around it.
[12:20] <xnox> this all sounds way too awesome =)
[12:20] <ogra_> yeah, we started actually making use of upstart :)
[12:20] <ogra_> though that still doesnt tell what jcollado's issue is
[12:20] <ogra_> i dont get that
[12:21] <ogra_> jcollado, initctl list
[12:21] <ogra_> doe that return a list of jobs ?
[12:21] <ogra_> (if not, whats the error)
[12:21] <xnox> ogra_: initctl --user list
[12:22] <xnox> is better, as that restricts to talking to user-session init only.
[12:22] <ogra_> not if i actually am the user and UPSTART_SESSION exists
[12:22] <ogra_> the export should properly restrict it already
[12:23] <jcollado> ogra_: http://pastebin.ubuntu.com/5884013/
[12:23] <xnox> ogra_: sure the default is to look at environment vars, but if we are troubleshooting a problem with environment..... without vars $ initctl list will default to system init.
[12:23] <ogra_> jcollado, that looks like you are not properly sudoed to phablet
[12:23] <xnox> jcollado: yeah, that's system wide init.
[12:23] <ogra_> jcollado, how did you become phablet ?
[12:23] <jcollado> su phablet
[12:24] <ogra_> ah no
[12:24] <xnox>  /o\
[12:24] <ogra_> sudo -u phablet -i
[12:24] <om26er> jcollado, hey
[12:24] <ogra_> or su phablet - (but that will likely mess up your path)
[12:25] <xnox> jcollado: don't use su =) ever. it doesn't setup / enherit proper environment. Unless that's your goal to get a clean environemnt, which doesn't correspond to user environment at all.
[12:25] <om26er> jcollado, have you recently run autopilot tests on touch ?
[12:25] <jcollado> ogra_, xnox: That was indeed the problem. Thanks a lot.
[12:25] <ogra_> YAY !!!
[12:25]  * ogra_ dances
[12:25] <xnox>  \o/ win
[12:26] <om26er> I see this http://paste.ubuntu.com/5884025/
[12:27] <xnox> om26er: does DISPLAY=:0 help at all?
[12:27]  * xnox checks
[12:27] <ogra_> om26er, oh, wow, why would autopilot fire up dbus at all ? it shoudl just attach to the runnign session bus
[12:27] <jcollado> om26er: I'm kind of desperate with that. phablet-test-run doesn't work for me right now. At first I though it was because of phablet-test-run not being updated to use the upstart commands and ignore the /etc/device-services file. However, even running autopilot from a terminal app in the phone itself return dbus problems.
[12:28] <ogra_> where is the autopilot source
[12:28] <xnox> ogra_: it does everything over dbus, and it can / should connect to running one. but it depends on how the wrapper is written.
[12:28] <om26er> ogra_, lp:autopilot
[12:28] <xnox> om26er: i'd like to know where is phablet-test-run is at?
[12:28] <ogra_> xnox, yeah, i suspect another hardcoded dbus session address case
[12:29] <om26er> xnox, lp:phablet-tools
[12:29] <ogra_> xnox, phablet-tools
[12:29] <xnox> om26er: cause you are launching that from host system, instead of the phablet@ user.
[12:29] <sergiusens> om26er: where is your MR?
[12:29] <om26er> sergiusens, didn't propose yet, its without the MR
[12:30] <ogra_> xnox, it should sudo -u phablet during run ...
[12:30] <sergiusens> om26er: branch?
[12:30] <xnox> om26er: jcollado: do not use phablet-test-run, it's for unflipped / legacy only....
[12:30] <sergiusens> xnox: no, it should work on both
[12:31] <jcollado> xnox, sergiusens: Yes, there's some code to detect if the image is flipped or not.
[12:31] <om26er> sergiusens, http://bazaar.launchpad.net/~om26er/phablet-tools/adapt_to_latest_changes_in_touch_image/revision/131
[12:31] <sergiusens> xnox: there's a chroot check, it will fail wrt to the new dbus/upstart change
[12:33] <om26er> tests run fine if logged into the phone, they only fail for phablet-test-run
[12:33] <om26er> this error: DBusException: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
[12:34] <om26er> that error appears when autopilot tests are tried to run as root
[12:35] <ogra_> om26er, make phablet-test-run switch to the phablet user first
[12:35] <ogra_> at least for all tests that need dbus
[12:35] <sergiusens> om26er: that should be the default
[12:35] <sergiusens> ogra_: ^^
[12:35] <sergiusens> let me see if anyone changed that
[12:35] <ogra_> what should be the default ?
[12:35] <xnox> sergiusens: but exec_with_adb is not guarded, and does chrootcmd.
[12:35] <ogra_> running as root ?
[12:35] <xnox> ogra_: all autopilot tests need dbus
[12:35] <sergiusens> ogra_: ssh phablet@localhost "autopilot ..."
[12:36] <ogra_> ah
[12:36] <xnox> well it's not "just" that.
[12:36] <xnox> ssh -o NoHostAuthenticationForLocalhost=yes -t $USER@$TARGET_IP -p $TARGET_SSH_PORT "bash -ic \"$@\""
[12:36] <ogra_> yeah, that shoould work unless you then firsse up a subshell with cleared env
[12:36] <popey> ogra_: ???????? no permissions
[12:36] <sergiusens> xnox: autopilot depends on dbus, the object tree is exported there
[12:36] <ogra_> *fire
[12:36] <popey> what does that usually indicate?
[12:36] <ogra_> popey, no permissions i would guess :)
[12:36]  * xnox ponders if "bash -ic" wrapping is playing up.
[12:36] <om26er> popey, fastboot ?
[12:36] <sergiusens> popey: device keys need to be accepted
[12:36] <popey> FUNNY MAN
[12:37] <popey> thats from doing adb devices
[12:37] <popey> on a samsung galaxy
[12:37] <sergiusens> popey: against pure android ?
[12:37] <popey> no, its one i flashed yesterday
[12:37] <popey> remember ☻
[12:37] <ogra_> popey, it indicates that the udev rule is not catching ut
[12:37] <popey> er, monday
[12:37] <ogra_> *it
[12:37] <popey> raring machine with adb tools from ppa
[12:37] <sergiusens> also that
[12:37] <popey> unplug/replug maybe
[12:37] <om26er> popey, sudo adb kill-server;sudo adb start-server (used to fix for me)
[12:37] <popey> yeah ta
[12:37] <ogra_> restart adb as root
[12:38] <ogra_> right, what om26er said
[12:38] <popey> kk thanks chaps
[12:38] <ogra_> (you could figure out the right runes and send a patch for adb's udev rule if you feel like
[12:39] <popey> unfortunately the device is remote from me, in london
[12:39] <popey> if I get hold of a device at oscon next week I may
[12:39] <ogra_> ah, well, then restarting adb should just do
[12:41] <popey> ogra_: is 20130717.1 safe for me to recommend to design people to flash?
[12:41] <ogra_> popey, yes, it will only fail autopilot until we fixed that
[12:41] <sergiusens> asac: ogra_ jcollado gema heads up that once the new image upgrader is in, all this may break again
[12:41] <popey> great, will still need --pending yes?
[12:41] <ogra_> popey, meaning by asac definition it wouldnt be safe to release :)
[12:42] <ogra_> sergiusens, yeah
[12:42] <popey> pfffft, he worries too much
[12:42] <ogra_> dont tell me :)
[12:43] <ogra_> well, he wants all gree on the dashboard (which is what we are working on atm)
[12:43] <ogra_> *green
[12:43] <ogra_> but a broken testsuite doesnt necessarily mean bad image :)
[12:44] <asac> sergiusens: who lands that?
[12:44] <Kaleo> didrocks: what?
[12:44] <ogra_> asac, foundations
[12:44] <asac> sergiusens: whoever lands that should prep with QA so that doesnt happen
[12:44] <asac> and coordinate that
[12:44] <ogra_> asac, there will likely bee a massive breakage once that happens
[12:44] <asac> slangasek: cjwatson: stgraber: ^
[12:45] <ogra_> due to the fact that so many parts use hardcoded assumptions all over the place
[12:46] <ogra_> (and due to the fact that likely not every single bit is prepared to have the rootfs completely readonly)
[12:46] <cjwatson> asac: I believe that's on stgraber
[12:47] <asac> stgraber: can you comment on that?
[12:47] <ogra_> sergiusens, so once we have that autopilot stuff back running, i'd like to merge your click package installer ... note that it would be nicer to not use the hooks for new cod but properly integrate it into live-build/auto/config|build ... but we can do that later
[12:48] <asac> stgraber: lets chat a bit later... have to run to something for 1.5h
[12:48] <sergiusens> ogra_: sure, I will fix on cjwatson comments I'm just reading now
[12:49] <ogra_> asac, stgraber will likely not be able to do much, the tests will fail and need adjustment etc ... i guess that should be a cross team effort across all teams
[12:49] <om26er> jcollado, sorry missed you message, so you have your device running flipped image right ?
[12:49] <ogra_> sergiusens, oh, i didnt notice colin had commented
[12:49] <asac> ogra_: yes, but not in cowboy/firedrill mode inside the archive; prep outside, accept some pain, keep everyone happy
[12:49] <asac> good deal :)
[12:50] <sergiusens> ricmm: can you send an email to the lists wrt upstart user session changes?
[12:50] <ogra_> asac, too many pieces to do it outside of the archive ... we should instead prepare for a day or two with broken image to speed it up ... after we have one rocksolid build (imho)
[12:50] <ogra_> asac, but your call in the end :)
[12:51] <asac> no ... we have been through that discussion :)
[12:51] <ogra_> yes, it will cost us a lot more time to land it then
[12:51] <asac> a firedrill is more expensive than anything else
[12:51] <asac> people bleeding out, working all night etc.
[12:51] <asac> having less energy afterwards
[12:52] <asac> so that must never be the plan.
[12:52] <ogra_> if it is planned in advance i dont see an issue
[12:52] <ogra_> the unplanned breakage harms us
[12:52] <ogra_> not the planned one
[12:52] <asac> we cnanot have images broken without a firedrill mode
[12:52] <asac> thje costs for that are engineering wide
[12:53] <asac> doing it properly is always more efficient long term
[12:53] <asac> properly meaning without breaking the main integration baseline
[12:53] <ogra_> we dont release broken images ... there will just not be an update released for one or two days (i belibve we can even do it in one with poroper planning and reviews in advance)
[12:54] <asac> thats not acceptable. we want to get confirm about issues fixed from the images in dashboard each and every day. every day we dont see that we have to get folks do stuff manuallyt etc. eg.g. costs all over the place
[12:54] <asac> anyway have to run
[12:54] <asac> bbiab
[12:57] <om26er> mzanetti, ping
[12:59] <Saviq> om26er, he's away on Qt Contributors' Summit
[12:59] <om26er> Saviq, ok, thanks
[12:59] <Saviq> om26er, he does pop in sometimes, but not often
[12:59] <Saviq> mzanetti, can we help maybe?
[13:00] <Saviq> om26er, btw, the unity8 job for upstart is a user-session one, so it's there in /usr/share/upstart/sessions
[13:00] <Saviq> om26er, but unfortunately it's not working due to some ways the session is set up
[13:01] <om26er> Saviq, that fixed now. I have it working
[13:01] <sergiusens> Saviq: should be working today
[13:01] <Saviq> om26er, ah cool
[13:01] <Saviq> sergiusens, cheers
[13:01] <om26er> Saviq, there is a feature request for the unity8 upstart job though. we should be able to give command line parameter
[13:03] <Saviq> sergiusens, om26er shouldn't the unity8 upstart job live with unity8 btw?
[13:03] <Saviq> !!! infographics are real !!!!
[13:03] <Saviq> pete-woods, you ROCK
[13:03] <Saviq> "1 photos captured today"
[13:03] <popey> hehe
[13:03] <popey> Saviq: please confirm bug 1202165 ☻
[13:04] <Azelphur> Does anyone know if Ubuntu phone plans to have xmir in the future?
[13:04] <om26er> Azelphur, the phone will run mir
[13:04] <Azelphur> om26er: doesn't it already run mir?
[13:04] <om26er> Azelphur, not yet, I hope a few weeks (if not days)
[13:05] <Azelphur> o.O, what is it running on now?
[13:05] <sergiusens> Saviq: that's an open question, I may think so
[13:05] <om26er> Azelphur, SurfaceFlinger currently
[13:06] <sergiusens> om26er: I'm going to reconstruct your MR and drop unflipped
[13:06] <Azelphur> I see :)
[13:06] <om26er> sergiusens, ok
[13:06] <ogra_> Azelphur, and i dont think there are plans to installl XMir by default (only Mir) ... but you will be able to do that yourself in developer mode
[13:06] <Azelphur> are the apps in the additional downloads section supposed to work? I clicked on most of them and nothing happens
[13:07] <sergiusens> 14.04 might have it
[13:07] <Azelphur> ogra_: sweet
[13:07] <ogra_> nah, they are just pretty pictures
[13:07] <marcoceppi> So, tethering support on the roadmap at all?
[13:07]  * marcoceppi uses this feature extensively
[13:07] <ogra_> click package integration is on its way, then there will be installlable apps in the shell too
[13:07] <om26er> sergiusens, also fix exec_with_ssh() :)
[13:07] <sergiusens> om26er: I'm on that
[13:07] <Saviq> popey, indeed
[13:08] <popey> ta
[13:08]  * cjwatson is sweating through revising the click hooks design/implementation at the moment
[13:08] <Azelphur> ogra_: sweet, it's looking cool, might dual boot my phone so I can watch the development
[13:08] <sergiusens> om26er: but it's easier without unflipped
[13:08] <kalikiana> Azelphur, I think of them as teasers. every cuple days more teasers turn into nice things :-D
[13:08] <cjwatson> (literally; heatwave)
[13:08] <ogra_> heh, here too
[13:08] <Azelphur> kalikiana: yea haha, I noticed how the stuff that is done is really nice, and the stuff that isn't is non-existent :P
[13:08] <ogra_> not that hot though ... we're still below 30
[13:09] <kalikiana> Azelphur, the settings app is like that. I love the looks but many pieces don't work just yet
[13:09] <ogra_> sergiusens, seriously, drop all that unflipped code
[13:09] <ogra_> we wont go back :)
[13:09] <Azelphur> kalikiana: yea, I went around pressing all the buttons :P
[13:09] <cjwatson> only barely below here; it's 29
[13:09] <ogra_> phew
[13:09] <sergiusens> ogra_: I know, I'm dropping :-)
[13:09] <Azelphur> Is there a page with documentation for Ubuntu phone app developers?
[13:09] <ogra_> :)
[13:09] <pete-woods> Saviq: :D
[13:10] <popey> Azelphur: developer.ubuntu.com
[13:10] <kalikiana> Azelphur, this one maybe http://developer.ubuntu.com/get-started/
[13:10] <popey> thats the startpoint
[13:10] <Azelphur> cool, ty
[13:10] <pete-woods> Saviq: now we just need to get lots more data sources added!
[13:10] <popey> Azelphur: and feel free to ask in here or #ubuntu-app-devel
[13:11]  * Saviq needs to get the freakin' microSIM adapter to start dogfooding... :/
[13:11] <Azelphur> cool :)
[13:12] <ogra_> i would borrow you mine, but my arm is to short to hand it to you
[13:12]  * ogra_ streches .... see ...
[13:16] <didrocks> Kaleo: I think sil2100 already told you, but the sdk stack regressed some media autopilot tests
[13:17] <sil2100> didrocks: not yet, but now you did ;) I think I need to add this one test to the list of tests ran on SDK
[13:17] <sil2100> Since it slipped through our fingers
[13:17] <didrocks> sil2100: yep
[13:18] <Kaleo> didrocks: so, what's the bug report
[13:18] <Kaleo> ?
[13:18] <sil2100> om26er: ^ ?
[13:19] <didrocks> Kaleo: just the messenger here when people don't transmit the message :p
[13:19] <om26er> Kaleo, in the gallery-app clicking on the share-button does not show the dialog
[13:20] <om26er> Kaleo, terminal says: file:///usr/share/gallery-app/rc/qml/MediaViewer/MediaViewer.qml:459: ReferenceError: caller is not defined
[13:20] <sil2100> didrocks: https://code.launchpad.net/~sil2100/cupstream2distro-config/media_stack_fix/+merge/175278 <- fix packages list and that one additional test
[13:21] <didrocks> sil2100: great! approving, feel free to deploy once merged :)
[13:21] <didrocks> kenvandine: FYI, sil2100 refreshed the list ^
[13:22] <kenvandine> sil2100, thanks!
[13:22] <sil2100> kenvandine: ah, you're online! Np ;)
[13:26] <sergiusens> xnox: ogra_ what am I doing wrong? http://pastebin.ubuntu.com/5884222/
[13:27] <ogra_> sh -c probably ?
[13:28] <jibel> what is the upstart event on touch to know that wlan is ready to use?
[13:28] <didrocks> sergiusens: $DBUS_SESSION_BUS_ADDRESS is interpreted by bash/sh before you executes sudo
[13:28] <didrocks> execute*
[13:29] <didrocks> (so it's $DBUS_SESSION_BUS_ADDRESS from root's env)
[13:29] <sergiusens> didrocks: makes sense!
[13:29] <sergiusens> thanks
[13:29] <didrocks> yw ;)
[13:31] <sergiusens> ogra_: didrocks what about now? http://pastebin.ubuntu.com/5884232/
[13:31] <sergiusens> reason autopilot is failing is because the env isn't being exported
[13:31] <didrocks> ah, this is more interesting :)
[13:31] <ogra_> quoting ...
[13:32] <didrocks> yep, what ogra says
[13:32] <ogra_> root@ubuntu-phablet:/# sudo -u phablet -i sh -c 'env |grep DBUS'
[13:32] <ogra_> DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-nRITxeJvsr
[13:34] <Kaleo> didrocks: the people being sil2100 ?
[13:34] <Kaleo> sil2100: where is the bug report?
[13:34] <Kaleo> or om26er ?
[13:35] <sergiusens> ogra_: a copy/paste of that returns SUDO_COMMAND=/bin/bash -c sh -c env\ |grep\ DBUS
[13:35] <sil2100> Kaleo: well, I don't know the exact problem, but om26er would know more
[13:35] <sergiusens> let me see what's going on with my env
[13:35] <Kaleo> sil2100: that's not my question :)
[13:35] <sil2100> Kaleo: I just found that newer SDK caused an AP failure
[13:35] <Kaleo> sil2100: didrocks: om26er: when there is a failure, first thing to do is bug report
[13:35] <ogra_> sergiusens, well, worst case just read the file direclty and source it
[13:35] <sil2100> Kaleo: right ;) om26er should do that, as he probably knows most
[13:36] <Kaleo> sil2100: good
[13:36] <Kaleo> om26er: you there? :)
[13:36] <om26er> reporting
[13:36] <sil2100> Kaleo: I would just submit a bug report like 'AP test fails'
[13:36] <sergiusens> ogra_: yeah, but I was trying to avoid that
[13:36] <Kaleo> om26er: thanks
[13:36] <ogra_> sergiusens, from /home/phablet/.cache/upstart/dbus-session
[13:36] <ogra_> yeah, thats definitely better indeed
[13:36] <sergiusens> ogra_: yeah, read it in .bashrc
[13:36] <Kaleo> sil2100: om26er: so I assume then that nobody has been working on the issue then?
[13:36] <sil2100> Kaleo: moooost probably
[13:36] <Kaleo> sil2100: om26er: when did we notice?
[13:37] <om26er> Kaleo, an hour ago
[13:37] <Kaleo> om26er: ok :)
[13:37] <Kaleo> fresh
[13:38] <didrocks> Kaleo: hum, we did notice 4 hours ago rather, gush tried first to reproduce it but couldn't
[13:38] <didrocks> Kaleo: then, om26er reproduced it 2h30 ago
[13:38] <Kaleo> didrocks: so there is something wrong in the process
[13:38] <didrocks> from the logs
[13:38] <Kaleo> didrocks: first, bug report should be made
[13:38] <sergiusens> ogra_: if I add what's in .bashrc to .profile it works fine
[13:39] <Kaleo> didrocks: then I think since it seems that SDK is marked as culprit, a person from the SDK should work on it right away
[13:39] <Kaleo> didrocks: how can we make sure that happens?
[13:39] <om26er> didrocks, Kaleo previously we have been thinking it a general test failure, the dialog not appearing was discovered ~1h ago or a bit longer
[13:39] <didrocks> Kaleo: you and timp were pinged for that on that channel, not sure if any other communication has been done
[13:40] <didrocks> 13:06:09      om26er | didrocks, that's actually a regression in the sdk :p
[13:40] <didrocks> om26er: it's 15:40 now here
[13:40] <om26er> didrocks, wow time flied or something
[13:41] <didrocks> Kaleo: I don't know, I hope that sdk will have better regression tests soon to not rely on autopilot tests from apps
[13:41] <ogra_> sergiusens, ??
[13:42] <ogra_> sergiusens, we ship whats in bashrc in /etc/profile.d/ snippets now
[13:42] <Kaleo> didrocks: that's unrelated
[13:42] <stgraber> ogra_, asac, sergiusens: What's QA doing that'll fail with read-only? Read a good chunk of the backlog but I'm still confused :)
[13:42] <Kaleo> didrocks: if there is an issue, it needs to be dealt with properly
[13:42] <ogra_> sergiusens, are you on the last ubuntu-touch-session package ?
[13:42] <didrocks> Kaleo: it clearly is seeing the regressions we had lately
[13:42] <sergiusens> stgraber: installation of additional things without enabling developer mode
[13:42] <ogra_> stgraber, we dont know, thats the point :)
[13:42] <didrocks> Kaleo: and the workaround we had to put in place in the tests with that
[13:42] <Kaleo> didrocks: it's not
[13:43] <ogra_> stgraber, we switched to upstart sessions and the whole testing fell over ... now we try to remove all the hardcoded paths etc
[13:43] <Kaleo> didrocks: so timp did not see the ping because his internet & irc died
[13:43] <om26er> bug 1202201
[13:43] <Kaleo> didrocks: I did not because I was sleeping
[13:43] <ogra_> stgraber, i expect that switching to image upgrades will cause similar issues
[13:43] <stgraber> sergiusens: ah yeah, that'll definitely fail unless they can get their stuff running from a standalone directory on the data partition (so not installing extra stuff) or run in developer mode (which would be bad as test results will likely differ due to / being rw)
[13:44] <ogra_> stgraber, due to the readonly nature, due to different FS structure, due to no apt available etc
[13:44] <om26er> Kaleo, is it fine for gallery-app or should I add ubuntu-ui-toolkit as well ?
[13:44] <ogra_> stgraber, the point is that we need to check in advance
[13:44] <asac> stgraber: what you should do is really check with qa how the run the image and which tools
[13:44] <stgraber> ogra_: fs structure "should" be fine, we've got a bunch of extra stuff but in theory I have at least the same stuff as you currently do, but yeah, they'll have to cope with readonly, I don't think switching to devel mode is the right thing for them to do
[13:44] <asac> and give it a try and see
[13:44] <asac> if there are issues work with them
[13:45] <asac> in that way you can protect from the most issues. there might be more if it hits real infra
[13:45] <ogra_> stgraber, right, which means we will likely need changes in the test suites
[13:45] <MacSlow> tmoenicke, ping
[13:45] <ogra_> stgraber, and we need to identify them
[13:45] <asac> but :)... we caan minimize the risk by prepping
[13:45] <stgraber> asac: who's writing those tools/tests?
[13:45] <ogra_> QA
[13:46] <tmoenicke> MacSlow: pong
[13:46] <stgraber> ogra_: QA is a rather big team ;)
[13:46] <asac> stgraber: gema can connect you to someone to assist you... right now we work with doanac and jcollado, but there might be someone better.
[13:46] <asac> gema: stgraber would like to check with someone to see how he can see what impacts his big landing has
[13:47] <ogra_> stgraber, well, there are plety f areas we are currently fixing just for the upstart switch
[13:47] <ogra_> stgraber, (they all use the same hardcoded paths etc)
[13:47] <ogra_> stgraber, so it really spans across a multitured of code trees
[13:48] <ogra_> *multitude
[13:49] <stgraber> asac: ok, I'll see if I can find some time to test that QA stuff, though I only have two days of work left before I leave for London and then I'll be on vacation and conferences for 3 weeks after that (well, still working 1-2days a week) and unfortunately I have higher priority bugs and features to get to by then, so I can definitely help someone in QA setup a readonly device and give pointers as to how to fix the tests but I doubt I'll be
[13:50] <stgraber> oh, I have a feeling that one will get cut... let me know where and I'll paste the rest...
[13:50] <asac> stgraber: well, we definitely don't want to land stuff that will break our QA infrastructure
[13:51] <seb128> Cimi, Saviq: overlay-scrollbar bug fix commited, jfyi
[13:51] <Saviq> seb128, cheers
[13:53] <ogra_> stgraber, ... give pointers as to how to fix the tests but I doubt I'll be  ...
[13:53] <ogra_> thats where it was cut
[13:53] <stgraber> ogra_: thanks
[13:53] <stgraber> "I'll be able to do much more than that"
[13:55] <ogra_> stgraber, did you ever try to run the tests that are shipped with phablet-tools ?
[13:55] <ogra_> i think getting that to work would be a good start
[13:55] <ogra_> if there are changes required they should be easy to port over to utah and other bits
[13:55] <stgraber> asac: sure and I'm certainly not for rushing the feature in. On paper we're only supposed to have the thing working end-to-end on all devices by end of August (deadline for landing the UI), until then, I don't really mind having both systems in parallel and switch once the blockers have been resolved (proper testing on all devices, regression free and click packages working by default at least)
[13:56] <ogra_> (at least thats the case for the dbus and upsatart changes we fix atm)
[13:56] <annerajb> hello
[13:56] <ogra_> stgraber, oh, please not parallel images again
[13:56] <asac> stgraber: i would suggest to check whats going on now
[13:56] <asac> and then we can assess looking on the details
[13:57] <ogra_> stgraber, also landing it in august will be way to late to shake out bugs
[13:57] <stgraber> ogra_: well, that's what I'm doing at the moment ;) but yeah, I'd like to avoid having half the users on each
[13:57] <ogra_> this is a massive architectural change of the whole image foundation
[13:57] <asac> what we need to check though if that decision then has good/complete enough data, e.g. did we check what the impact on our QA infrastructure is? are there other areas with impact that we haven't thought about
[13:57] <ogra_> there will surely be lots of bugs to shake out we will only get through user testing
[13:58] <ogra_> so landing as early as possible is a req. imho
[13:59] <asac> it really depends on the impact. hence i would like to know the impact first :)
[13:59] <stgraber> asac: yeah, I plan on testing the phablet tests as soon as I can, which likely means late this afternoon (today is my meeting day so I'm stuck until 2:30pm)
[13:59] <asac> stgraber: yeah. if you have questions just ping me... happy to talk
[14:00] <ogra_> asac, the impact of switching in august only  and thus having bad bugs by release is surely worse than switching asap and having time to shake them out
[14:00] <asac> I don't have enough details to make such assessment. but note that you also imply that the only other solution from landing today will be to land it late in august :)
[14:00] <asac> or something'
[14:00] <asac> thats also not decided
[14:00] <asac> known
[14:00] <asac> etc.
[14:01] <ogra_> asac, well, we change the complete underlying architecture of the image to something we never did before
[14:01] <ogra_> in the past such a change would have happened across two cycles
[14:02] <ogra_> just leaving us 6 week to fix the issues (in case we switch end of august) is extremely risky
[14:02] <ogra_> not to mention that this is only the preparation for another heavyweight change that will come after this
[14:03] <ogra_> (repartitioning the device and working with partitions instead of images)
[14:03] <ogra_> we would only do the second part mid sept. then
[14:03] <sil2100> jhodapp: hi! Do you know if I can build/compile qtubuntu-sensors on amd64? Since it's missing some headers it seems
[14:03] <ogra_> which well, might give us less then 4 weeks to fix issues
[14:03] <asac> so as you say, the risk is very risky, because we cannot even assess the risk yet :)
[14:03] <asac> e.g. hence, we need to prep better
[14:04] <asac> check exactly what will be broken
[14:04] <ogra_> asac, well, then we should not release by 13.10
[14:04] <asac> ensure we have a plan and resourcing to really address that. then make a decision where to do that
[14:04] <ogra_> these two changes are so massive that they would have deserved a full release cycle for testing them imho
[14:05] <ogra_> it looks all good on paper but we have no real world testing yet
[14:06] <ogra_> they are as bad as the container flip was ... which we are far from having shaken out completely yet
[14:06] <stgraber> ogra_, asac: just took a look at phablet-test-run, it indeed won't work at all on readonly images as it relies on being able to do in-place changes to files and install packages with apt and dpkg. I expect this would work perfectly if in developer mode but then we'd be in a pretty different mode from our standard devices so I'm not sure how much value the test results would have
[14:06] <ogra_> yeah, that wont test what the enduser gets at all
[14:07] <asac> stgraber: right. we need overlayfs or massive rewrite of infrastructure?
[14:07] <ogra_> ugh
[14:07] <asac> we basically need to be able to produce custom images outside and then flash those
[14:07] <ogra_> overlayfs is a no no
[14:07] <asac> an-overlay-fs ... thats about approach
[14:07] <stgraber> it could be changed to do a first prepartion pass where it installs everything in devel mode, then reboot in user mode (readonly) and run the tests which should work for most of the cases, however that means we wouldn't be able to test the upgrader (as the delta images won't work on a device that has been in devel mode)
[14:08] <ogra_> it will kill your battery and performance
[14:08] <asac> how to ensrure we can reasonably well test our read-only iamges
[14:08] <ogra_> asac, by completely reworking the test suite
[14:08] <stgraber> asac: overlayfs would effectively mean writable / (even if not persistent) which would still hide most of the bugs we hope in catching through QA
[14:08] <asac> stgraber: yeah. better would really move the isntall and prep stuff out so we can run them up front
[14:08] <ogra_> we need to test the actual setup the enduser gets
[14:08] <asac> before flashing the image
[14:08] <ogra_> else the tests  are pointless
[14:08] <stgraber> asac: so effectively the same thing as running in devel mode except that you also get the overlayfs bugs on top :)
[14:09] <asac> yeah.
[14:09] <ogra_> and you need to have hacked up kernels
[14:09] <ogra_> and someone needs to maintain overlayfs for 3.0 kernels ...
[14:09] <asac> i think we need an officially vetted way to oproduce customized image derivates
[14:09] <asac> that add tests
[14:09] <asac> and also daily-release stuff
[14:09] <ogra_> for 14.04 that sounds like a good plan
[14:09] <asac> so that the image we test is as close as it can get
[14:10] <asac> or we move all tests to click packages
[14:10] <stgraber> asac: ideally, QA should rework their tools to be runnable from a standalone directory and not require package installation, that way we can run them on a perfectly clean device and at the end just flush the directory without any impact on the device
[14:10] <ogra_> the image we test needs to be the image the enduser gets
[14:10] <ogra_> asac, the testsuiote needs to be adjusted
[14:10] <asac> yeah. so they would want a testing pack
[14:10] <asac> that we unpack
[14:10] <sergiusens> ogra_: can you add curl to the touch meta?
[14:10] <ogra_> instead of the images
[14:10] <asac> that would include autopilot stuff and libs
[14:10] <asac> and stuff
[14:10] <ogra_> sergiusens, uh, shudderm, cant we use wget ?
[14:10] <asac> and the tests
[14:10] <asac> that thing can then be unpacked to a directory
[14:10] <asac> stgraber: ? or what would you imagine?
[14:10] <sergiusens> ogra_: oh yeah, sorry, let's use wget
[14:10] <ogra_> sergiusens, only half the deps and so much saner
[14:11] <ogra_> :)
[14:11] <ogra_> asac, so we should have a test click package
[14:11] <stgraber> asac: yeah, that'd work fine. We have writable persistent directories they can use (/userdata/...), so they'd need to rework their setup to be self contained and ship it as a tarball or something that's unpacked there, test runs and then we flush it
[14:11] <stgraber> asac: with the advantage that anyone can run that on their device without leaving any trace of the testing tools afterwards
[14:11] <asac> stgraber: ok. however
[14:11] <ogra_> instead of fiddlign with the image architecture to have something completely non std which makes testing moot
[14:11] <asac> thats nowhere shorterm
[14:11] <asac> also we cannot afford to turn off dashboard for amonth :)
[14:12] <asac> so compromise MUST be that we start testing with developer mode
[14:12] <ogra_> ++
[14:12] <asac> so gyuess yoiu just need to focus on checking whether dev mode can be enabled well
[14:12] <ogra_> but need to move the suite asap
[14:12] <asac> and that it works with that
[14:12] <asac> and we will pickup the next level after getting this in
[14:12] <ogra_> dev mode will be the same as you have today
[14:12] <stgraber> asac: right, we can run in developer mode for now, it's just a "touch /userdata/.developer_mode && reboot" away, so that's easy, however this will hide bugs for sure (any bug triggered by the device being in read-only mode)
[14:12] <asac> yeah i know i know :)
[14:13] <ogra_> (except that yoou have loop mounted imgs instead of the weird setup we use now)
[14:13] <asac> stgraber: ok then just check in your testing discussed above that your landing doesnt cause autopilot regressions
[14:13] <annerajb> rsalveti, hey i got the bootstrap to install fine this time.
[14:13] <asac> otherwise talk to QA folks to address whatever that is
[14:14] <asac> doanac: awake?
[14:14] <asac> :)
[14:14] <stgraber> asac: if we have regressions it'll likely be bugs on my side, my goal from the beginning was to be identical to flipped images but read-only, so if they run in read-write, the result should be identical (or we indeed have something to fix)
[14:14] <stgraber> asac: anyway, have to go to my meetings now but can help run tests later
[14:15] <asac> stgraber: yeah, so lets try to check before landing so we know the impact and then decide later today or tomorrow whats next
[14:15] <asac> yeah
[14:15] <asac> lets check later
[14:15] <asac> ogra_: do you know if the infrastructure stuff for the dbus dashboard thing landed?
[14:15] <annerajb> rsalveti, unfortunately the ubuntu raring link you told me to install goes on a reboot loop and ends the third time on the recovery
[14:16] <ogra_> asac, i submitted an MP ... one sec didnt check if jcollado has landed that
[14:16] <jcollado> ogra_, asac: Not yet.
[14:16] <asac> jcollado: whats up?
[14:16] <ogra_> asac, not yet then :)
[14:16] <asac> stuck?
[14:17] <jcollado> asac: No, I just want to check with doanac since he knows that code better than me.
[14:17] <asac> doanac: !! :)
[14:17] <ogra_> sergiusens, seeded and updating meta now
[14:17] <sergiusens> ogra_: thanks
[14:18] <jcollado> asac: We have our daily meeting in 12 minutes, so I'll talk to him then.
[14:18] <asac> so you waited all these hours?
[14:19] <asac> anyway
[14:20] <asac> check with him quickly and also kick off all those jobs again once it landed
[14:20] <asac> thx
[14:20] <annerajb> sergiusens :how can i debug a reboot loop since this phones have no serial?
[14:21] <ogra_> well, at least these 15 tests that ran were all successful :)
[14:22] <ogra_> I: Checking Release signature
[14:22] <ogra_> gpgv: Signature made Mi 17 Jul 2013 16:06:44 CEST using DSA key ID 437D05B5
[14:22] <ogra_> gpgv: BAD signature from "Ubuntu Archive Automatic Signing Key<EMAIL_ADDRESS>[14:22] <ogra_> E: Invalid Release signature (key id 40976EAF437D05B5)
[14:22] <asac> network issue
[14:22]  * ogra_ glares at his scree
[14:22] <ogra_> n
[14:22] <asac> most likely
[14:22] <asac> or not?
[14:22] <ogra_> well, you can still see me
[14:22] <ogra_> or not ?
[14:22] <asac> lol
[14:22] <ogra_> same machine :)
[14:22] <asac> thought you saw that on the phones in lab
[14:22] <diwic> Device detected as /bin/bash: getprop: command not found
[14:22]  * ogra_ tries again
[14:22] <asac> just run update one more time
[14:23] <ogra_> oh
[14:23] <ogra_> yeah, it is the new PPA
[14:23] <ogra_> we had that during image build too last night
[14:25] <ogra_> silly coreapps PPA ... has to go .... we need click !
[14:25] <sergiusens> it's very common with ppas
[14:25] <ogra_> :)
[14:25] <sergiusens> ogra_: comming
[14:25] <diwic> any idea where I can find the "getprop" command?
[14:25] <ogra_> sergiusens, i lierally saw that the first time last night ... in 8 years that i work with our infrastructure
[14:28] <diwic> okay, using -d
[14:28] <sergiusens> ogra_: 20% perhaps of the jenkins build failures come from that
[14:29] <ogra_> wow
[14:29] <ogra_> i'm lucky we never used PPAs in images before then i guess
[14:29] <ogra_> bah, i clashed with Laney
[14:30]  * ogra_ fixes his liecd-rootfs branch
[14:33] <mattyw> anyone else encountered this? http://askubuntu.com/questions/320989/depends-dropping-letters-error-when-trying-to-get-the-ubuntu-touch-sdk-preview
[14:33] <popey> yes
[14:33] <popey> working to fix it
[14:34]  * popey leaves same as a comment ☻
[14:36] <mattyw> popey, ok cool, thanks, no need to be sorry :)
[14:36] <mhall119> popey: what's the issue with it?
[14:37] <popey> mhall119: read your email ☻
[14:37] <popey> morning btw
[14:39] <mhall119> popey: that's just precise though right?
[14:39] <cjwatson> Silly question: does PolicyKit work at all on ubuntu-touch?
[14:39] <cjwatson> Not as in can you actually get prompted, but does it know that the phablet user is active?
[14:40] <popey> yes mhall119 and quantal
[14:40] <mhall119> ah,I didn't notice that tha AU question specified 12.04
[14:47] <asac> jcollado: did doanac show up?
[14:47] <asac> can we land and try if that helps?
[14:48] <ogra_> no need to "try" we know it does :P
[14:48] <Kaleo> didrocks: gusch: om26er: this bug (https://bugs.launchpad.net/gallery-app/+bug/1202201) I have seen for weeks on the device; nothing new there
[14:48] <asac> ogra_: well, then it should just land
[14:49] <sergiusens> cjwatson: it doesn't work
[14:49] <asac> and someone should still ensure that the jobs finish successfully
[14:49] <annerajb> how important is this?? on the ubuntu bootloader i get E: Cant' open /cache/recovery/ubuntu_command sergiusens ?
[14:49] <Kaleo> gusch: om26er: is that the issue you are working on for a few hours now?
[14:49] <sergiusens> annerajb: not important
[14:49] <om26er> Kaleo, it was working for me today, till I updated the sdk
[14:49] <ogra_> asac, my MP is only half of it, i think jcollado was working on the other bit (stopping the shell to be able to run the tests)
[14:49] <Kaleo> om26er: it was not on my phone for weeks really
[14:49] <didrocks> Kaleo: yeah, om26er did before/after comparison
[14:49]  * annerajb wonder why it dosnt boot raring then...
[14:50] <Kaleo> om26er: you testing on the nexus S?
[14:50] <ogra_> asac, i dont know the status of that second part (though i know jcollado had the right fix)
[14:50] <sergiusens> ogra_: I updated the MR/MP btw for click
[14:50] <sergiusens> annerajb: you need to use saucy
[14:50] <ogra_> sergiusens, will merge after meeting
[14:50] <annerajb> sergiusens, oh that's what rsalveti gave me yesterday
[14:50] <asac> ogra_: ok. well i would at least like a status update
[14:50] <sergiusens> annerajb: my guess is missmatch of hybris and platform api
[14:50] <om26er> Kaleo, desktop
[14:50] <gusch> didrocks Kaleo om26er working on that one (Action.onTriggered does not have the caller)
[14:50] <ogra_> asac, you need a secretary ... :)
[14:50] <Kaleo> om26er: not good :)
[14:51] <annerajb> sergiusens, wait i am using raring
[14:51] <Kaleo> om26er: I actually have yesterday's image on my phone
[14:51] <Kaleo> om26er: and it's broken too
[14:51] <pmcgowan> Kaleo, I agree its been broken last 5 images
[14:51] <annerajb> raring-preinstalled-phablet-armhf.zip
[14:51] <pmcgowan> fwiw
[14:51] <Kaleo> pmcgowan: more I think :)
[14:51] <om26er> Kaleo, so what you are seeing on the phone is a dialog that depends on having a sharing service setup
[14:51] <Kaleo> gusch: so is it an issue in the gallery or the toolkit according to you? do you need help?
[14:51] <om26er> Kaleo, that's why you see a transparent black thingy on the phone
[14:51] <gusch> Kaleo: btw. ToolbarButton can't be disabled
[14:52] <Kaleo> gusch: it can be I guess: enabled: false
[14:52] <gusch> Kaleo: well - no Idea if Actions should pass the caller or not
[14:52] <Kaleo> gusch: (do you mean it does not *look* disabled?)
[14:52] <sergiusens> annerajb: I'm 99% sure it's because of a missmatch in libs or missing hw drivers for graphics
[14:52] <gusch> Kaleo: it grays out, but onTriggered is still fired
[14:52] <Kaleo> gusch: ok, bug report
[14:52] <annerajb> sergiusens, how can i debug this since this is not a desktop i can attach a serial too :(
[14:52] <doanac> asac: i'm on. in a meeting, but am going to fix things today
[14:52] <gusch> Kaleo: where are your bugs?
[14:53] <sergiusens> annerajb: adb logcat?
[14:53] <Kaleo> om26er: so that means that the whole feature has been broken for a long time
[14:53] <Kaleo> gusch: https://bugs.launchpad.net/ubuntu-ui-toolkit
[14:53] <asac> doanac: today might be not before my end of day
[14:53] <gusch> Kaleo: thx (just discovered 5 minutes ago)
[14:53] <ogra_> well, the fixes are well known
[14:53] <Kaleo> gusch: so, do you need help?
[14:53] <ogra_> shouldnt take long to merge them
[14:53] <asac> i want to see it go green and get the results
[14:53] <om26er> Kaleo, well the share menu on the desktop is just a dummy icon. on the device however its W.I.P.
[14:53] <asac> right. hence we should merge them
[14:53] <asac> :)
[14:53] <gusch> Kaleo: I can sort it out
[14:53] <Kaleo> gusch: ok
[14:54] <Kaleo> gusch: I'll leave you to it then
[14:54] <annerajb> sergiusens, i am at the bootloader right now and it says exec line 1 logcat not found.and when the phone is restarting i cannot connect to it thru adb since it's restarting
[14:54] <gusch> Kaleo: but is the Action{ onTriggered()} supposed to pass the caller, or not?
[14:54] <gusch> Kaleo: the ToolBarButton{ onTriggered()} does, but for Actions it might not be the case - no idea about the design there
[14:55] <gusch> Kaleo: but for consistency it should be the same I'd say
[14:55] <Kaleo> gusch: I don't understand what you mean
[14:55] <annerajb> sergiusens, every time i reboot i endup on the ubuntu logo cwm based recovery menu
[14:55] <Kaleo> gusch: you are taking about http://developer.ubuntu.com/api/devel/ubuntu-13.10/qml/ui-toolkit/qml-ubuntu-components0-actionitem.html#triggered-signal ?
[14:55] <Kaleo> gusch: it gives you the caller when fired, yes
[14:55] <gusch> Kaleo: ah - ok - so it should
[14:55] <sergiusens> annerajb: flipped or unflipped?
[14:56] <Kaleo> gusch: same for http://developer.ubuntu.com/api/devel/ubuntu-13.10/qml/ui-toolkit/qml-ubuntu-components0-action.html#triggered-signal
[14:56] <gusch> Kaleo: but no - does not anymore since yesterdays SDK
[14:56] <annerajb> sergiusens, rsalveti told me yesterday to try unflipped first if i recall correctly how can i be sure which one i have?
[14:56] <asac> doanac: ok thats good... once the stuff land, please repoke the jobs of todays image etc.
[14:56] <asac> and get everything "greenish" :)
[14:56] <gusch> Kaleo: and that's why this bug showed up: https://bugs.launchpad.net/gallery-app/+bug/1202201
[14:56] <ogra_> annerajb, do you end up an an android root with adb shell ?
[14:56] <ogra_> annerajb, that would be unflipped
[14:57] <Kaleo> gusch: I think I understand
[14:57] <apw> ogra_, the 4 devices which of those did we have problems with the kernel command ling just not being changable ... when we wanted to turn off apparmour we just couldn't do it from the kernel command line cause it had no effect one of the devices
[14:57] <Kaleo> timp: still around? :)
[14:57] <annerajb> ogra_, when i type adb shell i endup at ~ #
[14:57] <gusch> Kaleo: so according to the documentation, that's another bug
[14:57] <ogra_> apw, manta iirc
[14:57] <Kaleo> gusch: so solving this would solve the gallery issue right?
[14:57] <Kaleo> gusch: so it's definitely a toolkit bug; can you add that info to the bug report?
[14:57] <gusch> Kaleo: yep - from my POV it's a regression
[14:58] <gusch> Kaleo: yep
[14:58]  * ogra_ relocates for meeting
[14:58] <apw> ogra_, ok thanks ... and for any of the others are we seeing the bootload always slamming on any other parameters ?
[14:58] <gusch> Kaleo: I could move that bug to the SDK
[14:59] <annerajb> sergiusens, when i type adb shell i endup at ~ # is this a flipped image??
[14:59] <ogra_> apw, not sure, i think rsalveti saw them having no effect with mako recently
[15:00] <apw> these bootloaders SUCK
[15:01] <ogra_> apw, ++
[15:04] <popey> annerajb: root@ubuntu-phablet:/#
[15:04] <popey> thats what a flipped image shows for me
[15:05] <annerajb> then i guess i have a unflipped image. since i dont see that. thought i am not at the OS since the OS dosnt boot i think i am at the bootloader/recovery adb shell
[15:08] <gusch> Kaleo: but anyway I will add my workaround, as I knowh who's calling (and I like it more to use the id directly)
[15:09] <stgraber> rsalveti, ogra_, sergiusens: so I have some work planned to add a image bootstrap option to phablet-flash so that people can use that to retrieve the latest recovery partition image, flash it, push the latest full image and get a working image based system. Is phablet-flash the right place to add that or would you prefer a standalone tool?
[15:10] <sergiusens> stgraber: everyone will want to use that, although there is a lot of legacy stuff in there
[15:10] <sergiusens> stgraber: if you outline the process I can get it going if you want
[15:12] <stgraber> sergiusens: that'd be great, I can give you a bit of python code that does what I want when passed the model name, then if you can add that as a --bootstrap-image option (or similar), that'd save me quite a bit of time
[15:12] <sergiusens> stgraber: sounds good to me
[15:12] <Kaleo> gusch: thanks for all the work, we'll take it from there
[15:12] <ogra_> stgraber, any reason for that ?
[15:13] <ogra_> stgraber, i thought we will have the new recovery in all builds anyway
[15:13] <sergiusens> ogra_: we do, that's why I want the outline ;-)
[15:13] <ogra_> so a normal phablet-flash -b would get you what you need
[15:13] <ogra_> sergiusens, oh sorry, didnt read all of it
[15:14] <gusch> Kaleo: thank sil2100 didrocks and om26er
[15:14] <didrocks> gusch: no worry, thanks you!
[15:15] <gusch> didrocks: I would have kept blaming jenkins ;)
[15:15] <stgraber> ogra_: yeah, I expect we already have code to grab the recovery image, the bits I'll need to add is basic parsing of system-image.ubuntu.com and initial flash of those files. It's going to be a bootstrap-only option as once that's done, you should update from the device with system-image-cli instead of phablet-flash on your machine
[15:16] <ogra_> stgraber, yeah
[15:16] <stgraber> ogra_: I'll also make that option flush any existing data on the device and put it behind a pretty scary warning to avoid most people using it until we make it the default
[15:16] <didrocks> gusch: ahah, trust it ;)
[15:16] <ogra_> stgraber, uuh, evil
[15:16] <ogra_> stgraber, that means people that want to keep their data wont test it
[15:16] <stgraber> (I mostly want it there so I can get QA and other very advanced testers to use it instead of having to manually push stuff to their device with fastboot and adb)
[15:16] <stgraber> ogra_: that's kind of the point at the moment ;)
[15:17] <ogra_> also note that QA actually seems to require to keep stuff in the homedir
[15:17] <ogra_> so you would break that
[15:17] <stgraber> ogra_: right, initial flash will flush their data, but upgrades done after that (from the device) won't
[15:18] <stgraber> ogra_: so I guess that'll be fine for QA. For the other testers, once we're confident enough that the image setup works, we can drop the "format data" call to the upgrader and add some data transition code
[15:18] <annerajb> how do i know if my bootloader is installed correctly if the recovery menu has the ubuntu logo at the background??
[15:18] <jhodapp> sil2100, I don't know about qtubuntu-sensors on amd64, although I'm not sure what the point is in building it for amd64
[15:18] <ogra_> stgraber, right, but as i understand the data needs to be on the phone before flashing
[15:19] <ogra_> stgraber, we wouldnt have had so many issues today if we culd just have wiped /home/phablet/
[15:22] <stgraber> ogra_: hmm, ok, I guess I'll see what I can do once I understand how their stuff works... I'd have expected they run the --bootstrap-image which wipes the device clean, then boot it, push stuff to /home/phablet, install all their tools and then from there on, it's going to be persistant (unless they call --boostrap-image again instead of using system-image-cli for the updates)
[15:22] <sil2100> jhodapp: I built it already, but there seem to be some problems with headers - but that's a different story
[15:22] <sil2100> Thanks!
[15:23] <stgraber> ogra_: I mean, it's simple enough not to wipe /data clean, but then we have to figure out exactly what to move where which is much trickier, so as a first implementation, having bootstrap wipe everything is much easier ;)
[15:23] <Chocanto> mhall119: Hey ! :) So I tried the Argument api by the SDK team. It work nice ! But I will have to ask them an I/O Api to manipulate files :) So I can't really implement the arguments api for now
[15:23] <ogra_> stgraber, no, i was told they want "real world tests" which means they only flash but dont bootstrap (which preserves all of /home plus the network connections)
[15:23] <jhodapp> sil2100, np
[15:24] <stgraber> ogra_: ok, then on the image based devices, they'll just call "adb shell system-image-cli" which will update the device but won't flush the data
[15:24] <ogra_> stgraber, i guess its fine if home is preserved over all subsequent upgrades
[15:24] <ogra_> so they have to bootstrap once
[15:24] <stgraber> ogra_: with the image based setup they should really only use phablet-flash for the very first flash, not after that
[15:24] <ogra_> just need to make sure thats the case indeed
[15:24] <stgraber> right, good, so we agree
[15:36] <annerajb> http://pastebin.com/yhwdivmp this is theoutput i get when i type adb shell on what I think is the boot loader does it look correct?
[15:37] <ogra_> annerajb, thats clearly an android environment
[15:39] <sil2100> bfiller: hi!
[15:39] <bfiller> sil2100: hey
[15:40] <sil2100> bfiller: since Ugo seems to be away, could I poke you about something? Since there is the ubuntu-ui-extras project, which lp:ubuntu-ui-extras is an empty branch, but there are some sub-branches in it
[15:40] <sil2100> bfiller: I would like to know what is the status, and if any of the sub-branches should be pushed and made as lp:ubuntu-ui-extras ? What about daily-releasing this?
[15:40] <sil2100> https://code.launchpad.net/ubuntu-ui-extras
[15:41] <bfiller> sil2100: going to have to look into this after I finish the call I'm on. will get back to you soon
[15:41] <sil2100> bfiller: ok, thanks
[15:42] <ogra_> sergiusens, wget is seeded and meta uploaded, so only  your MP is missing (and an image rebuild)
[15:43] <sergiusens> ogra_: and colin's latest click upload (if it's not in yet)
[15:43] <sergiusens> there was a tiny bug
[15:45] <ogra_> ah, k
[15:46] <annerajb> ogra_, that means that my image is unflipped right?
[15:46] <ogra_> annerajb, do you have a google logo on screen while adb'ed in ?
[15:46] <ogra_> or is it just black
[15:47] <annerajb> ogra_, on the backgroudn of the cellphone i have the ubuntu circle logo and it says at the top cwm-based recovery v<IP_ADDRESS>
[15:48] <ogra_> annerajb, well, thats recovery, what do you get in a normal boot
[15:50] <annerajb> ogra_, i dont think i get a normal boot. this is the only thing it boots too no matter how many restarst i do. it always ends up here
[15:51] <ogra_> annerajb, what devie was that ?
[15:51] <annerajb> epicmtd
[15:51] <ogra_> *device
[15:51] <ogra_> and you are porting it yourself ?
[15:51] <annerajb> ogra_, yeah
[15:52] <ogra_> so did you produ.ce a zip for the device already ?
[15:54] <annerajb> ogra_, yes yesterday with the help of sergiusens and rsalveti i got the makefiles to produce cm-10.1-20130717-UNOFFICIAL-epicmtd.zip
[15:54] <ogra_> ok
[15:54] <ogra_> and did you flash it already too ?
[15:55] <sil2100> gusch: hello!
[15:55] <sil2100> gusch: can I poke you about one more thing? This time related to qtubuntu-cameraplugin-fake
[15:55] <gusch> sil2100: shoot
[15:56] <sil2100> gusch: would you mind if I got rid of the cameraplugin-fake-tests package? Since it only installs unit tests, and I don't think we need a package that installs unit tests
[15:56] <WebVisitor-0> hello.
[15:56] <sil2100> Those should be only ran during build, right?
[15:57] <WebVisitor-0> Does anyone know what is needed for providing multitouch support under Debian 6.0?
[15:57] <WebVisitor-0> Currently it's only supporting single touch operation.
[15:57] <WebVisitor-0> Using kernel 3.10.1
[15:57] <annerajb> ogra_, yes yesterday and after i flashed it it changed the backgroudn logo from the cyanogen mod one to the ubuntu one.
[15:57] <popey> WebVisitor-0: kinda offtopic here ☻
[15:57] <ogra_> WebVisitor-0, linkely nobody in thei channel ...
[15:57] <gusch> sil2100: get rid of them - truth is - they are only there, becauso I didn't manage to get rid of them ;)
[15:57] <ogra_> *this
[15:58] <sil2100> gusch: ACK ;)
[15:58] <popey> WebVisitor-0: maybe ask in #debian on oftc ?
[15:58] <ogra_> annerajb, right, but recovery is different from the normal boot ... so if you boot, do you see thr google logo for a while, then it reboots and goes into recovery ?
[15:58] <WebVisitor-0> Already asked in Debian foruns. But no response in there.
[15:59] <ogra_> WebVisitor-0, well, this channel is rather for the ubuntu phone OS
[15:59] <ogra_> (and tablet OS) ....
[15:59] <annerajb> ogra_, i see the samsung logo and after that the galaxy s and cyanogen mod animation and then it ends up on recovery.
[16:00] <WebVisitor-0> I got this link from the bottom page of https://wiki.ubuntu.com/Multitouch
[16:00] <WebVisitor-0> Thats why I asked here :-(
[16:00] <popey> ahh, we stole the channel from that project
[16:00] <ogra_> annerajb, ok, try the following from your pc: adb shell cat /proc/last_kmsg >logfile.txt
[16:01] <ogra_> annerajb, then dump the content of that file to a pastebin
[16:01] <popey> http://popey.com/~alan/device-2013-07-17-170108.png <- note "Carrier" is "Aubergine". My carrier is Orange in the UK. Has someone done a global s/Orange/Aubergine/g or something?
[16:02] <WebVisitor-0> popey do you know where can I get more info on MultiTouch then?
[16:02] <annerajb> ogra_, been asking for that the whole morning let me go ahead and get the paste bin last line says attempting watch dog reset.
[16:02] <ogra_> popey, that would be awe_ then :)
[16:02] <WebVisitor-0> Is there some dedicated channel for that?
[16:02] <popey> WebVisitor-0: no
[16:02] <ogra_> annerajb, yeah, the last line doesnt help much :)
[16:03] <annerajb> ogra_, also a bunch of messages about permission denied http://pastebin.com/XqxGp3Bv
[16:05] <WebVisitor-0> OK guys
[16:05] <WebVisitor-0> I will keep looking
[16:05] <WebVisitor-0> thanks
[16:06] <ogra_> annerajb, so by the stuff it tries to start this looks like you are actually not building the userspace for your device (looks like it tries to start some services a maguro device would use)
[16:07] <ogra_> init: cannot execve('/system/vendor/bin/pvrsrvinit'): Permission denied
[16:07] <ogra_> this is the first error i see
[16:08] <popey> awe_: a possibly amusing bug for you https://bugs.launchpad.net/touch-preview-images/+bug/1202279
[16:09] <ogra_> annerajb, pvrsrvinit is a tool used by OMAP chips , you rarely find them in samsung phones ...
[16:09] <ogra_> annerajb, i think while you already build the right kernel, your userspace does not use the right repo yet
[16:09] <annerajb> hmm thats weird because i only did breakfast epicmtd so i should have anything thats from another device unless my device makefiles are wrong
[16:09] <annerajb> ogra_, is the user space the raring-preinstalled zip?
[16:10] <ogra_> no
[16:10] <ogra_> thats the ubuntu userspace
[16:10] <ogra_> what i'm talking about is the minimal android rootfs you need
[16:10] <ogra_> which is in your cm-10.1-20130717-UNOFFICIAL-epicmtd.zip
[16:10] <annerajb> which is the one produced by brunch epicmtd
[16:10] <ogra_> right
[16:10] <ogra_> something is wrong there
[16:11] <annerajb> ogra_, so i should start looking into why my userspace is using omap tools like pvrsrvinit
[16:11] <awe_> popey, looks like a bug for seb128
[16:11] <awe_> popey, no i18n translations in the ofono layer
[16:11] <awe_> ;)
[16:11] <ogra_> you seem to use the maguro build in userspace while using the epicmtd kernel
[16:12] <ogra_> awe_, oh, so a french aubergine is an english orange ... now that finally makes sense :)
[16:12] <seb128> awe_, popey: the backend of that screen is simply not implemented
[16:12] <popey> haha
[16:12] <popey> ah okay
[16:12] <seb128> awe_, how do we can the carrier name btw? ;-)
[16:12] <annerajb> ogra_, which makefile specifies that maguro is what it should build?
[16:12] <seb128> popey, nothing on that screen actually do anything (maybe we should try to communicate that)
[16:13] <awe_> seb128, pretty sure it comes thru as a latin-1 string from the operator
[16:13] <ogra_> annerajb, i think you simply miss some CM branch for your device in the manifest.xml
[16:13] <ogra_> i guess the build just falls back to maguro
[16:13] <seb128> awe_, what I mean is "does ofono provide a dbus api I can call to get the info" ;-)
[16:13] <ogra_> because that bit is missing
[16:13] <annerajb> ogra_, i used the automatic tools i never touched the manifest.xml myself let me open it up
[16:14] <ogra_> annerajb, you didnt follow the porting guide ?
[16:14] <awe_> seb128, yes... you should.  Looks like that's already being used though...
[16:14] <awe_> seb128, I think the issue is that settings gets the operator name from ofono, and it's "Orange". and it
[16:14] <kriskropd> #machinelearning
[16:14] <awe_> it gets translated to Aubergine?
[16:14] <annerajb> ogra_, i did so if the porting guide tool (i think it was brunch) didnt got the right file itś the tools fault :P
[16:15] <seb128> awe_, no, "Aubergine" is a placeholder label, we just did the UI in the panel
[16:15] <awe_> lol
[16:15] <ogra_> WOW !
[16:15] <seb128> awe_, if you tell me what I can call I can replace that by actual datas
[16:15] <seb128> awe_, which is why I'm asking if you have a dbus method or something I can call :p
[16:15] <xnox> doanac: jcollado: not so long ago ^^^^^ very far in the morning here we were discussing how to make autopilot tests work and properly source dbus-session var from the new location and properly stop unity8 inside the user session init.
[16:15] <xnox> =))))
[16:15]  * ogra_ just accidentially hit enter when typing porting into chromiums url bar (instead of navigating to the right line)
[16:15] <awe_> seb128, one sec...
[16:16] <ogra_> guess what the second hit on google for "porting" is
[16:16] <doanac> xnox: i'm try to test people's patches right now
[16:16] <ogra_> :D
[16:16] <annerajb> ogra_, phablet-dev-bootstrap i think was the command that i ran
[16:16] <ogra_> right after wikipedias description of the word
[16:16] <cyphermox_> rsalveti: https://code.launchpad.net/~mathieu-tl/phablet-tools/exclude-tests/+merge/175328
[16:16] <annerajb> ogasawara, after that i typed breakfast epicmtd
[16:16] <ogra_> annerajb, well, you need to tell the tree that it should build for yur device somehow
[16:16] <awe_> seb, you need to query org.ofono.NetworkRegistration properties for the current operator details
[16:16] <cyphermox_> ^ I ran into a file conflict with hud-tools as I upgraded.
[16:16] <rsalveti> sergiusens: ^^^
[16:17] <annerajb> ogra_, :i passed my device name to both of those commands
[16:17] <awe_> seb128, if you haven't, install 'ofono-scripts', and run ./list-modems on a phone with a valid SIM
[16:17] <ogra_> annerajb, well, cross check against https://wiki.ubuntu.com/Touch/Porting#Manual_.28deprecated.29
[16:17] <awe_> or 'get-operators'
[16:17] <annerajb> ogra_, already on it
[16:18] <ogra_> annerajb, if the automatic way doesnt work, follow the manual one to check what the automatic one did wrong :)
[16:18] <awe_> seb128, I'll assign the bug to you.  You can close it out if we have a work-item for the task already
[16:18] <seb128> awe_, ok, thanks for the info
[16:18] <seb128> awe_, yeah, assign the bug to me
[16:20] <awe_> seb128, done
[16:20]  * awe_ really goes for lunch now
[16:20] <seb128> awe_, thanks
[16:20] <seb128> awe_, enjoy ;-)
[16:32] <annerajb> ogra_, this is how my .repo looked before doing it by hand http://paste.ubuntu.com/5884766/
[16:36] <sil2100> tvoss_: piiing!
[16:36] <sil2100> tvoss_: hello ;)
[16:37] <sil2100> tvoss_: we're having some problems with using the platform-api headers
[16:37] <asac> doanac: jcollado: any status update? i saw a few results coming in, but not sure if that was luck :)
[16:37] <asac> will drop off soon (so dont worry:))
[16:38] <sil2100> ricmm: ping
[16:39] <sil2100> ricmm: maybe you would be able to help, as libplatform-api-headers on amd64 installs the headers to /usr/include/ubuntu-1, but all headers inside use ubuntu/blabla.h
[16:39] <doanac> asac: i'm trying to get my phone set up to test
[16:39] <doanac> its running now
[16:40] <asac> awesome
[16:40] <jono> popey, hey
[16:40] <jono> popey, are you QAing the phone images?
[16:40] <ogra_> popey, hide !
[16:40] <jono> lol
[16:40]  * jono puts hand in front of ogra_ :-)
[16:40] <tvoss_> sil2100, how come? about to jump onto a hangout. Mind pinging ricmm?
[16:41] <ogra_> jono, popey and i currently do manual tests  until the automated ones fullly work
[16:41] <jono> ogra_, right
[16:41] <jono> ogra_, so phablet-flash only installs the blessed daily?
[16:42] <jono> does --pending bring in the auto-built daily?
[16:42] <ogra_> right, --pending gives you the most recent build
[16:42] <ogra_> default installs what is in /current on cdimage instead
[16:42] <sil2100> tvoss_, ricmm: libplatform-api-headers installs, for instance, /usr/include/ubuntu-1/status.h
[16:42] <ogra_> (which is the blessed one)
[16:42] <sil2100> tvoss_, ricmm: while insides have things like: #include <ubuntu-1/status.h>
[16:42] <tvoss_> sil2100, ack, what's the issue?
[16:43] <sil2100> Sorry
[16:43] <sil2100> #include <ubuntu/status.h>
[16:43] <tvoss_> sil2100, yeah, there is a symlink created on package installation
[16:43] <sil2100> (since I modified by hand to point to ubuntu-1
[16:43] <sil2100> )
[16:43] <sil2100> Oh
[16:43] <davmor2> ogra_: did 17.1 build in the end and does it work?
[16:43] <sil2100> tvoss_: could it be that during upgrade the old directory was not removed and now the symlink cannot be installed?
[16:43] <doanac> ogra, asac: what image do i need? I'm running 20130717.1 and it still uses /home/phablet/.dbus-session
[16:44] <tvoss_> sil2100, not sure ... didrocks ^, can you help here?
[16:44] <rsalveti> apw: I only had issues (cmdline) with manta, there others worked fine when changing the kernel cmdline in the abootimg config file
[16:44] <sil2100> tvoss_: siiince, I have /usr/include/ubuntu, but it's a directory
[16:44] <rsalveti> apw: so yeah, we can't necessarily trust we'll be able to dynamically change the boot arguments
[16:44] <sil2100> didrocks: ^
[16:44] <doanac> ogra_, asac: n/m
[16:44] <popey> davmor2: see last link in the topic
[16:44] <tvoss_> sil2100, weird, then your theory should be correct
[16:44] <apw> rsalveti, thanks thats what i wanted to know for what i am being asked to do anyhow, thanks
[16:44] <ogra_> doanac, it just doesnt delete it if it exists :)
[16:44] <didrocks> tvoss_: sil2100: do we need to have ubuntu-1, do we expect installing/supporting multiple version of the -dev API?
[16:45] <rsalveti> annerajb: so does it work after just flashing the cm zip?
[16:45] <rsalveti> I mean, you should at least get a black screen
[16:45] <rsalveti> if so, please paste your logcat output
[16:45] <tvoss_> didrocks, you told me that having a versioned include-dir is good style :)
[16:45] <rsalveti> once we know everything in there is working as expected, we can test it with the ubuntu image
[16:45] <annerajb> rsalveti, ogra_ has been helping me out and apparently my userspace is different than the kernel
[16:45] <didrocks> tvoss_: are you sure? I bet you mix people :p
[16:45] <annerajb> rsalveti, http://pastebin.com/XqxGp3Bv thatś the log cat
[16:45] <rsalveti> ogra_: annerajb's device might be a pain to port to flipped, as it's the 'mtd' type (using yaffs2 instead of ext4)
[16:46] <rsalveti> might have some other specifics as well, we need to check that in detail later on
[16:46] <tvoss_> didrocks, you said on the mp your eyes are bleeding less :)
[16:46] <xnox> tvoss_: didrocks: i'm not sure there is any point in having versioned include-dirs. If sonames are different, runtime is co-installable. We can even name libfoo1-dev if we want, and some packages do that. But don't use versioned header paths, in the source tree.
[16:46] <ogra_> rsalveti, argh
[16:47] <tvoss_> xnox, didrocks otp now, will come back to you later
[16:47] <rsalveti> annerajb: oh, a bunch of permission denied, weird
[16:47] <xnox> tvoss_: didrocks: instead, configury / cmake /pkgconfig can point to -I /usr/include/ubuntu-sdk/1/
[16:47] <didrocks> tvoss_: interesting, maybe I didn't express myself good enough, but I think we shouldn't
[16:47] <ogra_> rsalveti, well, his log shows a lot of maguro stupp (pvrsrvmgr)
[16:47] <ogra_> rsalveti, or are there other samsung omap devices ?
[16:47] <didrocks> xnox: we need to have a stragegy for those headers, we'll discuss it
[16:47] <xnox> tvoss_: didrocks: but developers in their source code should still simply write #include <ubuntu/magic.h>
[16:48] <rsalveti> ogra_: should have, let me find what is the soc used there
[16:48] <rsalveti> might even be omap3
[16:48] <tvoss_> xnox, +1
[16:48] <ogra_> rsalveti, ouch ...
[16:48] <xnox> tvoss_: didrocks: throught magic of gcc -isystem they can be anywhere, even in a local dir / repo /checkout / anywhere on filesystem.
[16:48] <ogra_> annerajb, so ignore what i said then, seems your usespace might be fine
[16:49] <annerajb> rsalveti, Platform:	Samsung Exynos 3 < that?
[16:49] <xnox> tvoss_: didrocks: e.g. it's used a lot around android. From gcc point of view all paths are relative, and flags determine the locations of what is "considered systemwide", don't think too much in terms of Debian Policy and typical packaging properties. but instead look at other sdk's.
[16:49] <rsalveti> ogra_:  1GHz Samsung-Intrinsity S5PC110, with PowerVR SGX540
[16:49] <xnox> e.g. all of apple's andorid's window's SDKs, simply ship a tarball with "usr/include" in it.
[16:49] <ogra_> ah
[16:49] <ogra_> ok
[16:50] <rsalveti> Hummingbird
[16:50] <rsalveti> annerajb: yeah
[16:50] <ogra_> that explains the pvrsrvmgr stuff then
[16:50] <xnox> and then you just point your compiler: gcc -isystem path/to/my/local/unpakced/../current/(symlink)/usr/include
[16:50] <annerajb> ogra_, but we still have the permission issue
[16:50] <ogra_> yes
[16:50] <xnox> thus a package in it self should just installer headers into $prefix/include without any versioned dependenices, those are added later.
[16:50] <sil2100> tvoss_, ricmm: can you guys change that in lp:platform-api then? I think that sounds safer than ln -s, as it just prooved to be buggy ;p
[16:51] <rsalveti> annerajb: so first goal is to have a useful android image, which can start surface flinger and such
[16:51] <tvoss_> sil2100, yup
[16:52] <tvoss_> sil2100, mind filing a bug and assigning it to me?
[16:52] <rsalveti> you can even use the surface flinger tests we have
[16:52] <rsalveti> then once we know it all works, we can flash the ubuntu one
[16:52] <sil2100> tvoss_: working on it!
[16:52] <annerajb> rsalveti, all right link to the surface fligner test image?
[16:52] <xnox> sil2100: hardlinks should be acceptable, soft links not so much.
[16:52] <ogra_> rsalveti, he cant even boot into android userspace yet
[16:52] <rsalveti> ogra_: yeah, that's the first step :-)
[16:52] <ogra_> :)
[16:53] <rsalveti> annerajb: mmm ubuntu/hybris/compat/surface_flinger/
[16:53] <xnox> sil2100: e.g. andoird's 14 abi/api levels are generated by "adding changes into lowest possible level , and hardlinking into upper ones"
[16:53] <rsalveti> that should give you /system/bin/direct_sf_test
[16:53] <didrocks> xnox: maybe you should just do the MP to fix this? It seems it will be the quickest :p
[16:53] <xnox> didrocks: where is the MP in question? me just jumped into a conversation? =))))
[16:54] <didrocks> xnox: there is none, it's something that needs to be fixed
[16:54] <didrocks> in lp:platform-api
[16:54] <didrocks> so that sil2100 can land https://code.launchpad.net/~sil2100/qtubuntu-sensors/lib_private/+merge/175331
[16:54] <davmor2> popey: the last link is wrong I tell you ;)
[16:55] <annerajb> rsalveti, my /system/bin/ is empty
[16:55] <rsalveti> what? something is very wrong in there
[16:55] <rsalveti> maybe if failed when flashing your zip?
[16:56] <annerajb> rsalveti, yay foudn something critical process service manager exited 4 times in 4 minutes rebooting into recovery
[16:56] <rsalveti> annerajb: check if out/target/product/epicmtd/system has everything in there
[16:56] <rsalveti> you can also extract the zip file to compare
[16:56] <rsalveti> and then understand why it might have failed the flashing via recovery
[16:57] <popey> davmor2: fixed! :D
[16:57] <annerajb> rsalveti, you mean the zip i build or the one i downloaded from ubuntu.com?
[16:58] <rsalveti> annerajb: the one you built
[16:59] <rsalveti> you don't need the ubuntu one yet
[16:59] <xnox> didrocks: sil2100: right i need to poke that in-depth. I'm EOD and need to run out. Can I just claim bug #1190698 as I don't think rpath is the right answer here.
[16:59] <davmor2> popey: Nexus Status: Pop :D
[16:59] <annerajb> rsalveti, ok so there must have been a issue flashing because the zip/system/bin contains a bunch of binaries
[17:00] <rsalveti> right
[17:00] <didrocks> xnox: sure, add the platform-api bug task then to fix the ubuntu-1
[17:00] <didrocks> tvoss_: FYI ^
[17:00] <xnox> didrocks: ubuntu-1 is a well typo, and has been removed from proposed fix already.
[17:01] <popey> davmor2: /topic
[17:01] <popey> bah
[17:01] <popey> davmor2: you don't see  "Nexus Status: http://bit.ly/18kIrhM"
[17:02] <cyphermox_> renato_: can you please clear this up?? what piece of the stack for the network indicator actually talks to NM to list access points and stuff?
[17:03] <davmor2> popey: I see pop http://ubuntuone.com/2BYe6VAgirY0lV2nOwztAz
[17:03] <annerajb> rsalveti, what should i clear before trying to flash the recovery?
[17:03] <annerajb> rsalveti, wipe cache? data/factory?
[17:03] <popey> davmor2: file a bug in your irc client ☻
[17:03] <rsalveti> annerajb: both
[17:03] <rsalveti> annerajb: which recovery are you using as well?
[17:04] <sil2100> tvoss_: https://bugs.launchpad.net/platform-api/+bug/1202309
[17:04] <rsalveti> cwm?
[17:04] <davmor2> popey: my just be a refresh thing
[17:04] <ogra_> rsalveti, he has an ubuntu logo, so that part worked
[17:04] <annerajb> rsalveti, yes <IP_ADDRESS> but it has a ubuntu logo on the background
[17:04] <rsalveti> oh, so it's our own recovery
[17:04] <tvoss_> sil2100, thx
[17:04] <davmor2> popey: hmmm no .17 builds for my phone then and will this auto update each day?
[17:05] <annerajb> rsalveti, yes should i be using it? itś the one that was part of the  build i did yesterday
[17:05] <rsalveti> annerajb: in theory, yes :-)
[17:05] <rsalveti> annerajb: I know recovery dumps the log in /cache/recovery
[17:06] <rsalveti> you can get inside that when booted in recovery, adb shell
[17:06] <rsalveti> maybe you can find more there about what might be happening