[00:11] <cpyarger> rsalveti, Do you have any information on this?
[00:13] <cpyarger> sergiusens, I believe you have worked with the maguro build, as you have a bug report submitted for it. May you offer some advice?
[00:14] <sergiusens> cpyarger: from an ubuntu engineering perspective, maguro isn't supported anymore
[00:17] <cpyarger> sergiusens, officially it isn't, But are there any unofficial builds? I have tried following the porting guide, but It seems to be unclear or incomplete, and I am unsure of how to get a running utopic with my device, or even one that supports basic cellphone functionality.
[00:17] <sergiusens> cpyarger: if you build from the official repos; mostly everything should be there already
[00:17]  * sergiusens checks
[00:18] <cpyarger> I may also be having issues to by device being a "toro" not an official maguro.
[00:18] <sergiusens> https://code-review.phablet.ubuntu.com/#/admin/projects/aosp/device/samsung/maguro
[00:18] <sergiusens> cpyarger: oh; you will have no radio
[00:19] <sergiusens> cdma200 == no radio support in ofono
[00:20] <cpyarger> I see, I am interested in getting this working, But to be perfectly honest I have no idea where to start other than flashing the official stable maguro.
[00:30] <sergiusens> cpyarger: if you want to build just https://wiki.ubuntu.com/Touch/Porting#Set_up_your_development_environment
[00:30] <sergiusens> you will already get maguro there
[00:30] <sergiusens> then just extract the drivers
[00:32] <sergiusens> https://developers.google.com/android/nexus/drivers
[00:32] <sergiusens> the maguro ones
[00:32] <cpyarger> or should it be the toro ones due to me having a toro?
[00:32] <sergiusens> just get both
[00:32] <cpyarger> ok
[00:33] <sergiusens> should be an issue; but the maguro build target will ref the maguro ones
[00:33] <sergiusens> they are overlapping everywhere except for the radio chip iirc
[00:35] <cpyarger> with phablet-dev-bootstrap should i be pulling phablet-4.4.2_r1
[00:43] <sergiusens> cpyarger: pass in the options as mentioned in the wiki
[00:49] <cpyarger> ok
[00:58] <cpyarger> sergiusens, I will let you know when the phabletdev-bootstrap command completes
[00:59] <sergiusens> cheers
[01:03] <cpyarger> sergiusens, One of the steps that has been confusing me is what to put in for the roomservice.xml file as i am once again running a tuna/torl rather than maguro. or even what to put for maguro.
[01:03] <sergiusens> cpyarger: that's only if you are using targets not provided by aosp
[01:04] <cpyarger> Oh! ok.
[01:04] <sergiusens> cpyarger: feel free to edit the wiki with makes it clearer
[01:06] <cpyarger> I will probably do that after i get some modicum of success ^_^ No need to add bad edits.
[02:40] <lotuspsychje> http://itsfoss.com/meizu-unveils-ubuntu-smartpones-mobile-asia-expo/
[05:07] <leszek> hi all
[05:10] <lotuspsychje> leszek: hello
[05:33] <tomheng> is Ubuntu touch based on Android 4.4.2 now ?
[05:39] <lotuspsychje> no ubuntu touch is much safer
[05:39] <lotuspsychje> its a different Os then android
[05:58] <RAOF> tomheng: Yeah, looks like.
[05:58] <RAOF> android-headers/utopic,utopic,now 4.4.2-1-0ubuntu2
[06:02] <tomheng> q
[06:02] <tomheng> ls
[06:03] <tomheng> ls
[06:03] <tomheng> ls
[06:21] <tomheng> hardware/qcom/display/msm8960/libgralloc/gpu.cpp:49:5: error: 'allocSize' was not declared in this scope
[06:22] <tomheng> what is the error mean and how to fixed it
[06:24] <tomheng> whois
[06:24] <tomheng> ls
[07:00] <dholbach> Guten Morgen Berlin! :)
[07:00] <dholbach> oops
[07:00] <dholbach> good morning
[08:34] <JamesTait> Good morning all; happy Colour TV Day! :-D
[09:30] <DexterF> hi
[09:32] <toto976> hi
[09:32] <DexterF> need a new handset anyway, so I'd like to get one I can try Ubuntu Touch on. nexus4 is out for not having removable storage and non-removable battery. in terms of specs (display, size, cpu) it's roughly what I'm after. recommendations
[09:32] <DexterF> ?
[09:34] <tomheng_> is Ubuntu touch based on cm or AOSP, NOW /
[09:37] <tomheng> anyone can answer me ?
[09:38] <ogra_> tomheng, AOSP
[09:39] <ogra_> (well, the few android bits in the container are ... ubuntu touch is based on ubuntu ;) )
[09:39] <tomheng> base on AOSP 4.4.2 ？
[09:39] <ogra_> yes
[09:41] <tomheng> can i build it from cm 11.0 device source code ?
[09:41] <ogra_> not sure that works ... you will need to kind of merge your tree with the ubuntu one
[09:42] <ogra_> so you might hit some issues to get that going
[09:42] <tomheng> now, the wiki(https://wiki.ubuntu.com/Touch/Porting) is weird.
[09:42] <ogra_> yes
[09:43] <ogra_> it only got randomly updated in the past when we switched from CM to AOSP and when we changed technologies
[09:44] <ogra_> once the devices are released and the platform doesnt move as much anymore we will likely find some time to update it properly
[09:45] <tomheng> but the wiki is still introduced how to build ut from cm source code.
[09:45] <ogra_> there is a link for the AOSP build somewhere
[09:45] <tomheng> https://wiki.ubuntu.com/Touch/AOSPBuild , this one ?
[09:45] <ogra_> yeah
[09:46] <tomheng> it is still newest and work ?
[09:47] <ogra_> no idea
[09:47] <ogra_> it refers to the current trr though
[09:47] <ogra_> *tree
[09:50] <tomheng> thanks, i will try it later according to that tutorial. hope it still work.
[10:14] <ricmm> seb128: hi
[10:14] <ricmm> seb128: my fixes from yday landed to distro, care to give them a shot?
[10:15] <seb128> ricmm, hey, I upgraded this morning, my unity8-desktop is back to working, thanks ;-)
[10:17] <ogra_> does it rotate properl now as well ?
[10:17] <ogra_> :)
[10:18] <Laney> on desktop we prefer the user to rotate him or herself
[10:18] <ogra_> haha
[10:19] <ricmm> :)
[10:27] <daker> Saviq: yo, just found the size of shape holding the icons on the dash is not fixed
[10:27] <Saviq> daker, I know
[10:27] <daker> Saviq: ok :)
[10:27] <Saviq> daker, the dash toolkit never allowed for it...
[10:27] <Saviq> daker, I'm thinking we'll have to hardcode
[10:29] <daker> Saviq: and since we don't fix the size of the icon metionned in .desktop, that would be a problem, their is a webapp called "DigitallyRadio" that has this issue
[10:31] <Saviq> daker, yeah, that icon is completely broken ;)
[10:31] <daker> Saviq: yes
[10:31] <ogra_> daker, oh, wrt your ping from tonight, yes, phablet-screenshot is working fine with the patest phablet-tools
[10:32] <daker> ogra_: ok so i need to check why it's not working for me
[10:33] <ogra_> make sure to have phablet-tools 1.0+14.10.20140616-0ubuntu1  or newer
[10:33] <daker> ok thanks
[11:00] <dednick> Saviq: do qml apps get notification when they're focused/unfocused, suspended/resumed, etc?
[11:07] <mpt> ogra_, hi, I’m working on the design for Developer Mode. What are the pros and cons for the user of turning it on?
[11:11] <Saviq> dednick, focus/unfocus they should, yes, suspended/resumed not yet
[11:12] <Saviq> dednick, they will receive it through http://qt-project.org/doc/qt-5/qt.html#ApplicationState-enum
[11:13] <Saviq> or well, http://qt-project.org/doc/qt-5/qguiapplication.html#applicationStateChanged to be correct
[11:17] <Cimi> seb128, https://code.launchpad.net/~cimi/ubuntu-system-settings/wizard.privacy/+merge/213124
[11:17] <ogra_> mpt, a simple on<7off switch should be enough ... the plan is to only allow enabling developer mode if a lockscreen password/pattern/number is set up though ...
[11:17] <ogra_> *on/off
[11:18] <dednick> Saviq: thanks
[11:18] <mpt> ogra_, sure, but for someone wandering into this screen, I’d like to write an explanation of why they might not want to turn it on just for fun
[11:18] <seb128> Cimi, yes?
[11:18] <Cimi> seb128, review! :D
[11:18] <seb128> Cimi, oh, ok ;-)
[11:19] <Cimi> seb128, I don't think the location backend is working
[11:19] <Cimi> seb128, so I commented my code and put a label instead
[11:19] <seb128> k
[11:19] <Cimi> seb128, design agrees
[11:19] <ogra_> mpt, ah ... well, probably something like: "this option allows developer access via an USB cable attached to your computer"
[11:19] <seb128> check with tvoss though, location should be working
[11:20] <mpt> ogra_, and how does that differ from the usual MTP access?
[11:20] <ogra_> it gives you shell access (adb) ... not sure how/if you want to have something like that in your description though
[11:20] <mpt> ogra_, can a phone be wiped over USB with one but not the other?
[11:21] <ogra_> yes
[11:21] <mpt> Can any part of storage be accessed over one but not the other?
[11:21] <ogra_> you have full console acccess to all data of the phablet user
[11:21] <ogra_> mtp only gives you access to a set of predefined exported dirs
[11:22] <seb128> ogra_, isn't adb giving you root access to the device?
[11:22] <mpt> Excellent, that’s what I wanted to know
[11:22] <ogra_> seb128, yes, currently ... that will be gone though, you will have to sudo
[11:22] <seb128> well, that's still access, how you get it is a detail
[11:22] <ogra_> right
[11:23] <seb128> it means you get access to the data, not restricted to the phablet user
[11:23] <ogra_> you will only be able to enable adb if you have changed your PW though
[11:23] <Cimi> seb128, I don't have the page in system settings in my phone
[11:23] <seb128> Cimi, oh, that is not implemented indeed, but I think the backend are available now so it could
[11:24] <Cimi> seb128, well, let's do it when we have those pages
[11:24] <seb128> k
[11:25] <Cimi> seb128, when we have them, we can test uncommenting code from the wizard
[11:26] <mpt> ogra_, so would this warning be accurate and comprehensive? “When Developer Mode is on, anyone can access, change, or delete any data on this phone without unlocking it, by connecting it to another device.”
[11:26] <ogra_> mpt, i would say "to another computer"
[11:26] <ogra_> but yeah
[11:27] <mpt> They could also connect it to a tablet, right? (Convergence!:-)
[11:27] <ogra_> theoretically yes, technically not possible unles you solder a special cable yourself :)
[11:28] <mpt> or have a tablet with a USB port
[11:28] <ogra_> heh, right ..
[11:33] <Cimi> seb128, on the phone plugin
[11:33] <Cimi> seb128, I believe we don't know if we have a sim slot or not?
[11:35] <seb128> Cimi, not sure, seems like a question for awe/the ofono team
[11:35] <seb128> Wellark, do you know ^ ?
[11:42] <Wellark> Cimi, seb128: pong
[11:42] <Wellark> what's the question again?
[11:42] <Cimi> Wellark, if there is a way to see if we have a phone or a tablet wifi only
[11:43] <Wellark> well, you could ask the number of modems from ofono
[11:43] <Cimi> Wellark, SimManager on the system settings boolean present property is false
[11:43] <Cimi> ok
[11:45] <Cimi> Wellark, serviceNumbers is more than 0?
[11:46] <Wellark> Cimi: no service number or anything. those are per modem values which you don't have at all if you don't have a modem
[11:46] <Wellark> what api are you using
[11:46] <Wellark> ?
[11:46] <Cimi> Wellark,
[11:47] <Cimi> import Ubuntu.SystemSettings.Phone 1.0
[11:48] <Cimi> actually no
[11:48] <Cimi> this is different story
[11:48] <Cimi> so yeah we have no API
[11:49] <Cimi> will patch this
[11:51] <Wellark> Cimi: yeah, that API will not cut it
[11:52] <Cimi> Wellark, where is this code?
[11:52] <Cimi> ofono/
[11:52] <Wellark> don't know
[11:52] <Wellark> just checked the plugins/phone
[11:52] <Wellark> but don't know where the ofono classes are coming from
[12:01] <tomheng> hardware/qcom/audio/legacy/alsa_sound/AudioUsbALSA.cpp:44:17: fatal error: jni.h: No such file or directory
[12:02] <tomheng> why jni.h can not found ?
[12:03] <ogra_> tomheng, because there is no java in our tree at all
[12:04] <tomheng> how to fixed it ?
[12:05] <ogra_> no idea ... disable the bit of the build perhaps
[12:05] <ogra_> s/the/that/
[12:05] <ogra_> (we wouldnt have any support for alsa vis USB anyway in ubuntu)
[12:05] <ogra_> *via
[12:06] <tomheng> I am trying to port Ubuntu Touch to my phone, but i dont know what should i modify to suit for building.
[12:07] <ogra_> well, yuo need to have some experience with the adnroid build system to do a port ...
[12:07] <ogra_> for the issue above just disable the USB alsa supprt in the build scripts
[12:08] <tomheng> sorry,i am newbie to that. but i want to study to build ubuntu touch.
[12:08] <ogra_> well, the porting part is more "build a minimal android" than doing any ubuntu stuff :)
[12:09] <ogra_> which means you need some experience with building android
[12:10] <tomheng> if there is a wiki tell me what should i remove and modify maybe helpful.
[12:18] <sergiusens> popey: do you recall ever having a 'load more tweets' button/label in the twitter webapp?
[12:18] <Macer> any news on any type of release for an actual device? only thing i can find is from march and it says "fall of this year" so is that at all solid?
[12:19]  * sergiusens notices that disabling the nautilus new storage connected event triggered window popup was his decision yet
[12:37] <popey> sergiusens: pass
[12:40] <mpt> ogra_, this still needs review by another designer, but it’s complete now: https://wiki.ubuntu.com/AboutThisDevice#developer-mode
[12:41] <ogra_> mpt, how do i get to that page ? is there an icon on the front page or is it hidden somewhere in the system-info page ?
[12:41] <ogra_> (like on android)
[12:41] <mpt> ogra_, scroll up :-)
[12:41] <ogra_> mpt, ah, perfect, thanks :)
[12:46] <tomheng> hardware/qcom/display/msm8960/libgralloc/gpu.cpp:49:5: error: 'allocSize' was not declared in this scope
[12:46] <tomheng> what does the error mean and how to fixed it ?
[12:53] <tomheng> Could anyone give me some tips?
[12:57] <pete-woods> hey all, can anyone tell me how to take a screenshot on the phone?
[12:58] <pete-woods> I've tried googling, but can't find anything that actually worked
[13:01] <popey> pete-woods: phablet-screenshot in phablet-tools
[13:01] <pete-woods> ahh
[13:01] <pete-woods> I was looking for tools on the device itself
[13:01] <pete-woods> popey: thanks!
[13:19] <oSoMoN> anyone running image #96 is seeing the browser crash on startup like I do?
[13:21] <ogra_> oSoMoN, i stearted it but didnt use it on 96 ... it started fine
[13:21] <ogra_> *started it
[13:22] <tomheng> Unable to find a valid linux-image dependency from the meta package linux-image-aries
[13:22] <tomheng> i had fixed last error, but a new old occur.
[13:22] <ogra_> oSoMoN, trying it again here i can browse the ubuntu shop just fine
[13:26] <oSoMoN> ogra_, thanks for the testing, I can reliably reproduce the crash here, it seems the segfault is in fontconfig, which I see was upgraded in #96…
[13:26] <ogra_> hmm, i test on flo here btw
[13:26] <ogra_> let me try some other pages
[13:28] <ogra_> works fine too
[13:28] <ogra_> ricmm, the rotation stuff is sooo much better !!!
[13:52] <sergiusens> dbarth: thanks for the release of the gmail webapp that allows multiple accounts
[13:53] <dbarth> sergiusens: yw ;)
[13:53] <dbarth> sergiusens: the latest one also lets you work with their recent account url changes
[14:02] <AskUbuntu> ubuntu is doomed | http://askubuntu.com/q/488052
[14:02] <tedg> cjwatson, Can I make a click hook that is package based (i.e. not based on a particular entry in "hooks")
[14:03] <cjwatson> tedg: don't think so
[14:27] <ricmm> ogra_: yup its nice
[14:36] <blackenedgod> hi everyone is there any support of ubuntu touch for xperia sola phone ?
[14:40] <blackenedgod> hi everyone is there any support of ubuntu touch for xperia sola phone ?
[14:48] <cwayne> mardy: ping
[14:59] <mterry> sarnold, hello!  Do you have time today to chat about bug 1234983?
[15:54] <Cimi> mterry, https://code.launchpad.net/~cimi/ubuntu-system-settings/wizard.privacy/+merge/213124
[15:54] <ogra_> slangasek, i understood doko works on the corrupt backtraces ... which is a result of a version skew between gdb/gcc and the libs ?
[15:55] <ogra_> slangasek, oh, btw, there was a request to seed gdbserver (so devs dont need to make the image writable for live debugging) ... any objections from the foundations side to that ?
[15:55] <slangasek> ogra_: where did you hear that?
[15:56] <slangasek> ogra_: no objections from our side to gdbserver seeding
[15:56] <ogra_> slangasek, in a hangout meeting and it was initially found in malta by Wellark iirc
[15:56] <ogra_> cool, thanks
[15:56] <slangasek> ogra_: well, I think that's random speculation; we have a general problem with armhf backtracing unrelated to libstdc++
[15:56] <ogra_> oh, ok
[15:56] <pmcgowan> slangasek, there is some work on your team to land libqofono in the archive for our system settings work, was wondering if you knew the status
[15:57] <ogra_> that was the explanation i heard multiple times
[15:57] <ogra_> didnt mean to cause confusion
[15:57] <slangasek> pmcgowan: nobody's said anything about libqofono to me; can you give me a more precise pointer? (person / bug report / branch / problem description)
[15:57] <slangasek> ogra_: right, I don't think that explanation came from foundations though? :)
[15:57] <pmcgowan> slangasek, sil2100 was working on it earlier this week based on packaging Ken had done
[15:57] <ogra_> yeah, i'm not sure anymore
[15:57] <ogra_> ETOOMANYHANGOUTS
[15:58] <ogra_> if we had kept IRC meetings i could gerp a log now ...
[15:58] <ogra_> *grep
[16:05] <slangasek> pmcgowan: ok; I knew from sil2100 that he was looking at some libqofono cleanup, didn't realize that was related to blocking the system settings work.  And I don't find any in-progress code branches anywhere in launchpad for anything called "libqofono" or "qofono".  So I think this will have to wait for his return tomorrow
[16:05] <pmcgowan> slangasek, thats fine thank you
[16:06] <slangasek> I assume that since it's a new package, all the in-progress stuff is offline somewhere
[16:10] <cwayne> is there plans to be common component for app devs to implement bottom swipe?
[16:25] <davmor2> ogra_: you need a hangout irc bot that transcribes the audio to text and then pushes it to a channel.  There's a itch for you to scratch if ever I saw one :D
[16:25] <ogra_> haha, yeah
[16:26] <ogra_> *just* need to write that speech recognition SW
[16:26] <ogra_> might do it on the weekend :P
[16:45] <dednick> boiko: hey. couple of comments on your dialer-app MP.
[16:45] <boiko> dednick: hello
[16:46] <boiko> dednick: let me check
[16:47] <boiko> dednick: so, as I explained to you before, this flag should only be used when the dialer is in focus
[16:48] <boiko> dednick: because if dialer crashes for whatever reason, the flag won't be set, that's why I didn't bother making it work when in background
[16:49] <dednick> boiko: sigh... so i have to check the dialer is in focus. that's kind of crap.
[16:50] <dednick> boiko: but ok.
[16:50] <dednick> ls
[16:50] <boiko> dednick: I'm open to suggestions on a better way to solve this
[16:51] <boiko> dednick: is there a public API telephony-service could use to query if dialer-app is running/active?
[16:52] <boiko> dednick: the only way I see to fix this is to register dialer-app in dbus, and make telephony-service check whether it is registered
[16:53] <boiko> dednick: but creating a dbus object just to check if the app is alive seems a little too much
[16:53] <dednick> boiko: i guess what we have is fine for the moment.
[16:54] <boiko> dednick: so, when dialer is in focus, you can rely on the callIndicatorVisible, and when it is not, you check the hasCalls
[16:56] <dednick> boiko: we can revisit if we ever need other apps to use the property.
[16:57] <boiko> dednick: yep, ok
[17:29] <ahayzen> fginther, ping
[17:30] <fginther> ahayzen, pong
[17:31] <ahayzen> fginther, i think i broke jenkins last night with one of my mps...it has got stuck on generic-update_mp for 20hrs
[17:31] <ahayzen> fginther, http://91.189.93.70:8080/job/generic-update_mp/3507/console
[17:31] <ahayzen> fginther, are you able to resolve that or do i need to talk so someone else?
[17:31] <sarnold> mterry: hello :)
[17:32] <fginther> ahayzen, I aborted the job, it should try again
[17:32] <mterry> sarnold, hi!  Do you have time for a quick hangout?
[17:32] <ahayzen> fginther, ok thanks, there should have been other ones after i guess they would have been queued as well?
[17:32] <fginther> ahayzen, yeah, they were stuck. Jenkins doesn't deal with this very well :-(
[17:33] <sarnold> mterry: sure
[17:33] <ahayzen> fginther, ok well thanks for unblocking it :)
[18:49]  * genii makes more coffee
[19:35] <budders893> Hello all!
[19:35] <boiko> mterry: hi, do you have a silo for the greeter active property already?
[19:35] <mterry> boiko, no
[19:35] <budders893> would ubuntu touch be stable enough to do basic stuff on? like watching youtube, surfing the web etc
[19:36] <boiko> mterry: what would be the easiest way for me to test this? just build unity8 from your MR?
[19:36] <boiko> mterry: or do I need more things?
[19:36] <mterry> boiko, yeah that should be all you need
[19:37] <boiko> mterry: nice! btw, I have branches for telephony-service and dialer-app already, they are untested yet though
[19:38] <boiko> mterry: https://code.launchpad.net/~boiko/telephony-service/greeter_active and https://code.launchpad.net/~boiko/dialer-app/emergency_mode
[19:39] <boiko> mterry: the dialer one has some mocking code that switches from greeter to non-greeter mode every 3s
[20:07] <sil2100> boiko: hello :)
[20:08] <boiko> sil2100: hi
[20:09] <sil2100> boiko: do you know if you could find someone to do a landing of the gallery-app fix for toolbars? From what I heard Bill is not around, and we would like to get rid of that regression finally ;)
[20:09] <boiko> sil2100: as far as I know oSoMoN is taking care of that
[20:10] <boiko> sil2100: well, to get rid of that regression we need also the fix on Mir, what was done on gallery was just a workaround
[20:10] <sil2100> boiko: ok, so it seems all our regressions are Mir-related then ;)
[20:10] <sil2100> boiko: so let me poke oSoMoN in the morning about that then
[20:11] <ogra_> https://code.launchpad.net/~artmello/gallery-app/gallery-app-fix_toolbar_device/+merge/224013
[20:11] <ogra_> thats the MP for the issue
[20:11] <ogra_> just failed CI anyway
[20:12] <oSoMoN> sil2100, I’m testing the fix, I should be able to give an ack for landing soon
[20:13] <sil2100> oSoMoN: o/
[20:13] <sil2100> oSoMoN: thank you!
[20:15] <boiko> sil2100: regarding the AP failures on dialer and messaging, I still don't have fixes for those, I'm trying to finish the emergency mode on dialer before working on that
[20:16] <oSoMoN> sil2100, silo 5 can be published
[20:16] <boiko> sil2100: well, actually I have already taken a look at the failures and why they might be happening, just don't have MRs for that yet
[20:16] <sil2100> boiko: ok, thanks for looking into those in overall, it's not super urgent but we would like to get those fixed somewhere in the future
[20:16] <sil2100> oSoMoN: \o/
[20:17] <sil2100> robru: ^
[20:17] <boiko> sil2100: they will at some point :)
[20:17] <sil2100> boiko: I love the sound of that ;)
[20:18] <boiko> sil2100: hehe
[20:31] <robru> oSoMoN, sorry about that, was in a meeting. published
[20:32] <oSoMoN> robru, thanks!
[20:33] <robru> oSoMoN, you're welcome
[20:33] <Elleo> sil2100: heya, if you have a minute to do some reviewing, I've got a branch that works around that keyboard issue now (plus fixes a build issue with the new qt packages): https://code.launchpad.net/~michael-sheldon/ubuntu-keyboard/fix-1332624/+merge/224419
[20:40] <sil2100> Elleo: hey! Let me try looking into that :)
[20:40] <sil2100> Elleo: thanks for the fix btw.!
[20:41] <Elleo> sil2100: thanks :)
[20:41] <pmcgowan> sil2100, I was looking for you earlier, to get a libqofono update
[20:42] <sil2100> pmcgowan: hey! I already got an e-mail from slangasek and we discussed how to proceed further - so, the package was ready, but then I noticed that Ken disabled the tests for the package, and they seem to fail right now
[20:43] <sil2100> pmcgowan: so slangasek proposed to fix the tests and only then publish the package
[20:43] <pmcgowan> sil2100, ah, well that makes sense
[20:43] <sil2100> pmcgowan: the ETA is tomorrow morning - if I won't be able to resolve it by then, we'll think of something (like publishing with those disabled for now)
[20:43] <pmcgowan> sil2100, any idea on whats wrong with the tests?
[20:44] <sil2100> pmcgowan: the qmake file is a bit strangely written so it might be some 'paths' missing in our debian/rules file, but I'll know more once I sit down finally and look into the details
[20:44] <pmcgowan> sil2100, thanks much
[20:44] <sil2100> pmcgowan: sorry for the delay, wanted it to happen today but then I had to take almost a day off
[20:44] <pmcgowan> np
[20:44] <pmcgowan> appreciate the help
[20:54] <pmcgowan> sil2100, can you help with https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1334177
[20:55] <pmcgowan> or robru ^^
[20:55] <robru> pmcgowan, what do you need? a silo?
[20:55] <pmcgowan> robru, we need a patch applied to that package
[20:55] <pmcgowan> robru, as mirv is out we have no one to do it
[20:56] <robru> pmcgowan, does that branch of mzanetti contain the diff you want to apply?
[20:56] <pmcgowan> robru, yes, thats my understanding
[20:57] <robru> pmcgowan, ok that branch looks legit. what I'll do is assign a silo and then upload that package, then you can test it
[20:57] <pmcgowan> robru, perfect thanks
[20:57] <mzanetti> thanks robru, pmcgowan
[20:58] <mzanetti> sorry, just prepared the branch before and had to leave
[21:06] <robru> mzanetti, pmcgowan: ok guys, you're building in silo 3: https://ci-train.ubuntu.com/job/landing-003-1-build/82/console
[21:43] <NightHawk877> Hi
[21:44] <NightHawk877> I'm running into a problem with my Ubuntu-Touch install on my Nexus 7. I am getting a blank screen after installing it.
[22:36] <popey> mandel: do we have docs for using u-d-m from qml?