[02:08] <hevyhomie> hello everyone
[02:15] <hevyhomie> Would you be kind to help me with how to build apparmor for moto E as given by the porting to new device link: https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
[04:40] <lotuspsychje> http://linux.softpedia.com/blog/Next-Ubuntu-Touch-OTA-Update-Should-Arrive-in-July-Says-Canonical-483826.shtml
[05:01] <sturmflut2> tathhu: I'm just forwarding relevant information to my loyal crowd of followers ;)
[05:18] <sturmflut2> dholbach: Good morning!
[05:25] <dholbach> hey sturmflut2
[06:31] <zyga> bzoltan: hey
[06:31] <zyga> bzoltan: do you have a moment to talk
[06:44] <bzoltan> zyga: yes
[06:46] <zyga> bzoltan: thanks, I'm interested in the binary runtime for SDK apps
[06:46] <zyga> bzoltan: for LTS releases
[06:47] <zyga> bzoltan: I'm curious as to how apps are supposed to use it
[06:47] <zyga> bzoltan: ahd what kind of testing was performed on it
[06:48] <bzoltan> zyga: Right...I am almost done with the prototype package.https://launchpad.net/~canonical-qt5-edgers/+archive/ubuntu/qt5-beta-proper/+sourcepub/5119834/+listing-archive-extra
[06:48] <bzoltan> zyga:  It compiles, builds, but i need to fix up the packaging and stuff
[06:49] <bzoltan> zyga:  The apps need to figure out the whereabout of the Qt. Env vars are there for that
[06:49] <zyga> bzoltan: do you have an idea when it will be ready?
[06:49] <zyga> bzoltan: I'd like to give it a try with checkbox
[06:49] <bzoltan> zyga: Is there a rush?
[06:49] <zyga> bzoltan: no, just planning
[06:50] <zyga> bzoltan: we're about to end one cycle and I wonder if I should reserve some time to work on this next week
[06:50] <bzoltan> zyga:  hobby or real planning? peaple tend to plan before concept and feasibility study in these days :D
[06:50] <zyga> bzoltan: real planning
[06:51] <zyga> bzoltan: we have a production app that runs on 14.04 but we want to replace it with one that relies on current SDK
[06:51] <bzoltan> zyga:  for real planning i would not commit anything for this week. What we do is still an early prototyping. I know it works, I know it is good, but i would not jump on production just yet
[06:52] <zyga> bzoltan: ok, thank you
[06:52] <zyga> bzoltan: as soon as you think it's something that you consider ready for broader testing, please tell me
[06:52] <zyga> bzoltan: we'd like to unify our apps across LTS and non-LTS releases
[06:52] <bzoltan> zyga:  if we release a Qt 5.4 with 1.3 UITK for LTS then we are commited to it ... we can not change paths and modules anymore. So I would do the proper base work.
[06:54] <bzoltan> zyga:  that is a brilliant plan and I am sure that our Qt and UITK are up to the job. But we need to be super careful not to commit to an API or a modul what might change.
[06:54] <zyga> bzoltan: understood
[06:55] <brunch875> Why do I always seem to miss ubuntuonair?
[06:55] <brunch875> :C
[06:56] <zyga> bzoltan: one last question, will you release something before the end of 15.10 development?
[06:56] <zyga> bzoltan: a vivid version of SDK -libs would be useful for our needs
[06:57] <zyga> (so current, not next)
[06:58] <bzoltan> zyga: to release a vivid version via the SDK PPA is easy ... to the archive is close to impossible. Sadly not because of me.
[06:58] <bzoltan> zyga:  but the latest UITK on vivid is fresh
[06:58] <zyga> bzoltan: ppa is fine
[07:08] <zyga> bzoltan: so which is it? is your plan to wait for 15.10 development to finish and then release a set of libraries to let apps to run on 14.04
[07:10] <bzoltan> zyga:  I plan to release much earlier
[07:11] <bzoltan> zyga:  in optimal case in weeks ... at least the prototype package what would be good for concept validation and testing.
[07:11] <bzoltan> zyga:  the first package will come with a major _DISCLAIMER_ that the content and paths are subject to change
[07:12] <zyga> bzoltan: thank you, that's all I need now
[07:13] <zyga> bzoltan: and I'm very grateful for your work
[07:14] <bzoltan> zyga:  My pleasure :) You push this ship to the right direction ... rolling release of the developer offering. that was my ambition since the beginning  :)
[07:24] <zyga> ara: do you have any plans to adopt asana?
[07:25] <ara> zyga, not currently, why?
[07:25] <zyga> ara: I used it a little lately to track lp development, I'm just curious to see what our plans are
[07:26] <ara> zyga, the current plans probably involve trello, rather than asana
[07:54] <sturmflut2> Does anybody have a vegetahd device at hand and could test a click app for me? You can ping me in private if you don't want to reveal yourself ;)
[09:03] <JamesTait> Good morning all; happy Ball Point Pen Day! 😃
[09:21] <popey> JamesTait: oddly a fountain pen just dropped through my letter box :)
[09:22] <JamesTait> popey, nice! Anything to do with Ronnie Tucker's series of reviews?
[09:22] <popey> yes :)
[09:23] <popey> el cheapo one from ebay
[09:23] <popey> then realised I have no ink :)
[09:23]  * JamesTait prefers fountain pens.
[09:26] <JamesTait> I haven't watched any of the reviews yet, but I intend to just out of curiosity. I have a cherry wood fountain pen that my wife bought me as an anniversary present, and I like that.
[09:32] <jgdx> seb128, this [1] now passes. Could you take a look at it? [1] https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/fix-1441192/+merge/255402
[09:33] <davmor2> popey: JamesTait I prefer rotary pencils.  I find them smoother to write with than pens
[09:33] <popey> me too usuaally
[09:33] <popey> I generally only use pencils, but I want to try something different, not used a fountain pen for 30 years
[09:34] <jgdx> seb128, also, I can't run system settings locally due to the file exists fix of yours. Not sure how to recover.
[09:35]  * sturmflut2 can only write in block letters and had to train his hand for three weeks before every written exam at university
[09:35] <davmor2> I also don't tend to break the nibs so easily
[09:38]  * JamesTait has replacement nibs handy with the cartridges, just in case.
[09:38] <popey> Mirv: is this something you can help get tested / landed? https://bugs.launchpad.net/ubuntu/+source/qtpim-opensource-src/+bug/1462989
[09:39] <jgdx> sturmflut2, highly recommend learning lower case letters.
[09:40] <sturmflut2> jgdx: I hardly ever write anything by hand. Too many devices available.
[09:41] <jgdx> sturmflut2, but you went to elementary school, right? :p
[09:45] <Mirv> popey: I can help getting it landed, but it's renatu's package so I'd like him to accept it and test the landing
[09:46] <Mirv> popey: I'll add a landing line for it but it seems renatu is not online
[09:46] <popey> ok, thanks Mirv
[09:46] <popey> I'll poke him when he's around
[09:46] <Mirv> popey: it needs overlay too? I mean to vivid images (well probably obviously...)
[09:47] <Mirv> captain obvious
[09:48] <JamesTait> popey, davmor2: https://www.flickr.com/photos/jamestait0/18047069764/ <-- My essential equipment.
[09:49] <seb128> jgdx, you didn't reply to my review comment in that mp, did you?
[09:50] <popey> JamesTait: is that an ubuntu plectrum?
[09:50] <Mirv> popey: so, ping him to review the patch and add his comment to the bug. I subscribed to the bug now so when I see his review approval of the patch, I'll do a silo with that patched added and ask renatu to test it.
[09:50] <popey> awesomesauce, thanks Mirv
[09:50] <JamesTait> popey, yes it is! From barry, at UDS Budapest!
[09:50] <popey> nice
[09:50] <jgdx> seb128, no, I thought the pass constituted an answer. :p
[09:51] <seb128> jgdx, well, currently tests don't fail, so I'm unsure why they need to be skipped
[09:51] <jgdx> seb128, commented
[09:51] <seb128> jgdx, also what issue do you have with my file exists change?
[09:52] <jgdx> seb128, no tests are skipped right now if they can pass. Some cannot pass due to lacking NM mock support.
[09:52] <jgdx> seb128, http://pastebin.ubuntu.com/11689223/
[09:52] <seb128> jgdx, ldd /usr/bin/system-settings | grep libS
[09:55] <davmor2> JamesTait: now be lefthanded and heavy handed and see how long a nib lasts ;)  Apparently the ones you can stab through can don't do so well if you just use them :D
[09:56] <jgdx> seb128, libSystemSettings.so.1 => /usr/local/lib/libSystemSettings.so.1
[09:56] <seb128> jgdx, that's your issue, /usr/local custom install taking over the system version
[09:56] <seb128> jgdx, just delete /usr/local/lib/libSystemSettings.so.1
[09:56] <JamesTait> I think it's just you, davmor2. 😝
[09:56] <jgdx> seb128, haven't used /usr/local in ages, but makes sense
[09:56] <seb128> jgdx, yeah and the lib didn't change in ages
[09:56] <jgdx> oh
[09:56] <seb128> so you probably didn't notice before
[09:57] <jgdx> seb128, worked, thanks!
[09:57] <seb128> jgdx, yw!
[09:59] <seb128> jgdx, k, approved your changes, can you link the bug to the branch maybe, so it gets listed in the changelog/closed on upload
[10:01] <jgdx> seb128, oh, sure.
[10:01] <seb128> jgdx, thanks
[10:20] <jgdx> seb128, shouldn't we use USS (RTM) to track these landings in bugs?
[10:21] <seb128> jgdx, as you want, is that needed/bringing any value?
[10:21] <jgdx> seb128, it's just a bit tedious looking at the linked branch to figure out whether or not it's in vivid or not
[10:23] <seb128> jgdx, you mean? if that's a mp against vivid is that the change is not in vivid :-)
[10:24] <Ytivarg> Hi, videocalling work on uphone?
[10:24] <bzoltan> didrocks:  May I have a packaging question? I have a project with an orig.tar.gz on a http server, the debian/watch has the correct data. Is there a way to create a source package without creating a local orig.tar.gz?
[10:25] <jgdx> seb128, that's not true though ;p
[10:25] <seb128> oh?
[10:25] <didrocks> bzoltan: you mean, you want to force downloading the orig.tar.gz from the server, right?
[10:25] <jgdx> it can be landed in vivid but still have an mp against vivid :p
[10:25] <didrocks> bzoltan: or you want to even skip that download?
[10:26] <didrocks> (you can't, you need to have the orig.tar.gz locally so that it can create the diff.tar.gz)
[10:26] <didrocks> (so you can download it with "uscan --force-download")
[10:35] <Ytivarg> Hi, vocalsearch work on uphone?
[10:37] <popey> what's vocalsearch?
[10:37] <popey> (and probably no)
[10:38] <sturmflut2> mzanetti: Ping
[10:39] <bzoltan> didrocks: Ok, so there is no way to convince the packaging tools that the orig.tar.gz is up there and it should not create/download huge files and then upload it to the builder?
[10:41] <Ytivarg> Vocalassistent ... sorry
[10:41] <popey> Ytivarg: still no idea what that is :)
[10:41] <popey> Ytivarg: can you link to it
[10:42] <didrocks> bzoltan: no, because to generate your diff.tar.gz, you need to compare your current directory and the orig.tar.gz files
[10:42] <didrocks> and so, it couldn't do that without downloading it :)
[10:43] <didrocks> popey: I guess Ytivarg is talking about something like a google now search (voice recognition)
[10:43]  * popey shrugs
[10:44] <bzoltan> didrocks: but if the project has only the debian directory without any patch ... then the diff.tar.gz can not be other then an empty file.
[10:44] <Ytivarg> With my voice found my contact
[10:44] <popey> Ytivarg: no, we don't have that yet
[10:44] <didrocks> bzoltan: or orig.tar.gz can be empty, and diff.tar.gz would contain then all debian/ dir :)
[10:45] <didrocks> bzoltan: there is nothing magic about any dir, so any combination can exist
[10:46] <bzoltan> didrocks:  I would just love to save bandwidth  by using the watch feature and let the PPA download the orig.tar.gz when i do only debian space hackaround
[10:48] <didrocks> bzoltan: if you only do packaging changes, (and so, create a -0ubuntuX where X>1), it doesn't reupload the .orig.tar.gz file
[10:48] <bzoltan> didrocks: all right, that is comforting .. let me try it
[10:50] <didrocks> bzoltan: look at your .changes file, it lists the packages it would upload
[10:50] <Ytivarg> Popey: Okkey but this tecnology are 10 years old
[10:50] <popey> Ytivarg: So?
[10:53] <Ytivarg> For any people are fondamental ... sorry my very bad english
[10:55] <bzoltan> didrocks:  thanks, cool
[11:03] <mzanetti> sturmflut2, hey
[11:03] <sturmflut2> mzanetti: Welcome back!
[11:04] <mzanetti> have I been away?
[11:14] <Ytivarg> didrocks: thanks and good day at all
[11:41] <mcphail> Are updates from Ubuntu Store going to switch to binary diffs rather than redownloading the full thing?
[11:46] <mcphail> (and, as an extension to that, is the versioning under /opt/click/packagename going to change to some form of COW arrangement?)
[11:51] <mcphail> I'm a bit worried apps developed for convergent devices (particularly if delivered as fat packages with armhf, i386 and amd64 arch) are going to kill my poor little bq
[11:52] <ogra_> snap packages will get binary diffs ...
[11:52] <ogra_> afaik
[11:52] <mcphail> ogra_: i _thought_ I'd heard that somewhere. Good to hear. Any plans on how the versioning will work when installed?
[11:53] <ogra_> the versioning ?
[11:53] <mcphail> ogra_: yes - just now we have dirs for v0.1 and v0.2, both with complete copies of all binaries
[11:53] <ogra_> ah, snappy doesnt have that
[11:54] <mcphail> ogra_: how does snappy handle rollbacks etc?
[11:54] <sturmflut2> cking: Ping
[11:55] <cking> sturmflut2, hiya
[11:56] <sturmflut2> cking: I've looked at your fix for forkstat, great! I'll put the new version on my device and continue with the article
[11:57] <cking> sturmflut2, excellent!
[13:01] <jgdx> kenvandine, hey Ken, could you take a look at the backport spreadsheet and tell me if there's something missing?
[13:02] <kenvandine> jgdx, you mean the landing spreadsheet?
[13:03] <kenvandine> jgdx, for row 63, just the dest ppa
[13:03] <jgdx> kenvandine, no, https://docs.google.com/spreadsheets/d/1F6eKzwpobzoAW1JyvFt_nacFltQiIMCniA793F1z2Lc/edit#gid=0
[13:03] <kenvandine> i fixed it
[13:03] <kenvandine> oh
[13:03]  * kenvandine looks
[13:03] <barry> JamesTait: actually, i think it was steve conklin who made those.  i got a big bag of picks and i've been slowly losing them ever since.  but they are really cool (and great picks)
[13:04] <kenvandine> jgdx, list is shorter than i would think..
[13:04] <jgdx> kenvandine, yeah, maybe I missed something
[13:07] <jgdx> kenvandine, also, landing 33 fails to build due to tst-update-manager segfault: https://launchpadlibrarian.net/208645434/buildlog_ubuntu-wily-powerpc.ubuntu-system-settings_0.3%2B15.10.20150609.1-0ubuntu1_BUILDING.txt.gz
[13:07] <jgdx> kenvandine, idas?
[13:07] <jgdx> s/idas/ideas
[13:10] <kenvandine> jgdx, these fixes aren't listed https://launchpad.net/ubuntu/+source/ubuntu-system-settings/0.3+15.10.20150604-0ubuntu1
[13:11] <jgdx> kenvandine, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1461624
[13:11] <kenvandine> jgdx, no idea about tst-update-manager segfault, nothing in your branch changed that
[13:11] <brunch875> Which notes program should I use on the desktop if I want it to synchronize with "Reminders" on ubuntu touch?
[13:11] <brunch875> evolution?
[13:12] <jgdx> seb128, the libsystemsettings1 change's not being backported?
[13:13] <brunch875> AAh, there's a reminders app for the desktop too; nevermind
[13:14] <seb128> kenvandine, listed where?
[13:14] <kenvandine> on the backport spreadsheet jgdx linked
[13:15] <seb128> jgdx, no, that's only for snappy purposes, I don't see the point of backporting
[13:15] <jgdx> seb128, kenvandine, listed the battery rendering one. It's in silo 6
[13:16] <jgdx> seb128, won't it also be helpful for the convergence story?
[13:16] <JamesTait> barry, I just remember you having loads and telling me to "take a handful" - I have one, my sons have one each, the rest found their way into geocaches as swaps. ☺
[13:16] <seb128> jgdx, I doubt we ever build a snappy image from < wily
[13:17] <barry> JamesTait: that's awesome!  how cool would it be to find one in a geocache?
[13:17] <seb128> too much changing, wily is supposed to be where the snappy works is going
[13:17] <jgdx> seb128, k
[13:17] <barry> JamesTait: yeah, i think i snapped up all the leftovers :)
[13:17] <jgdx> makes sense
[13:17] <kenvandine> seb128, jgdx: i guess we won't be able to switch to dual landings then, i had hoped to
[13:17] <kenvandine> but makes sense
[13:18] <kenvandine> my hope was to remove the delta then dual land for everything new
[13:18] <seb128> kenvandine, jgdx, well we can also merge in for the sake of dual landing, I don't know how much vivid+overlay is freeform for non ota-targetted changes
[13:18] <JamesTait> barry, the real shame is that I didn't tag them before dropping them - it'd be cool to have had them as trackables and see where in the world they ended up!
[13:18] <barry> :)
[13:18] <seb128> kenvandine, jgdx, like I'm also unsure where is convergence work, display panel, etc going to go
[13:18] <seb128> kenvandine, jgdx, it's likely going to require new MIR, is that going to overlay?
[13:19] <kenvandine> all good questions
[13:19] <jgdx> delta is inversely proportional with ken's ability to sleep at night
[13:19] <jgdx> uuh
[13:20] <seb128> jgdx, ken never liked sleep anyway
[13:20] <seb128> :-p
[13:21] <kenvandine> i'm learning to like it :)
[13:21] <jgdx> heh
[13:21] <seb128> :-)
[13:21] <seb128> kenvandine, anyway the delta is small enough that I would be fine backporting the remaining changes in another landing
[13:22] <seb128> then we can dual land for a while
[13:22] <kenvandine> seb128, it would be nice
[13:22] <seb128> then see what happens with the convergence work
[13:22] <jgdx> seb128, silo 3 for the fileexist thing, then?
[13:22] <jgdx> since yours is tested already
[13:22] <seb128> jgdx, we already have another silo?
[13:22] <jgdx> seb128, yes
[13:22] <seb128> is that on top of what I'm trying to land?
[13:22] <seb128> or how does that work?
[13:22] <jgdx> seb128, I'll wait until your stuff has landed
[13:23] <seb128> k
[13:23] <seb128> kenvandine, what was your thing about overlay ppa flag?
[13:24] <jgdx> kenvandine, did you see I'm landing the device_name branch? You okay with that?
[13:24] <seb128> kenvandine, oh, I saw you replied on -ci-eng
[13:24] <kenvandine> jgdx, i'm good with that
[13:25] <kenvandine> seb128, yeah, makes sense?
[13:25] <jgdx> seb128, I tested silo 6, btw. All green
[13:25] <kenvandine> seb128, it's best to set that before the silo is created
[13:25] <kenvandine> but we can change it after if needed
[13:26] <kenvandine> jgdx, i just wonder what QA will say about a landing with that many branches :)
[13:26] <kenvandine> but i think unity8 has done bigger landings
[13:26] <jgdx> kenvandine, silo 6, 3 or both?
[13:27] <kenvandine> jgdx, silo 6
[13:27] <kenvandine> hopefully they'll let it through
[13:28] <seb128> kenvandine, yes, I just didn't know about it, I wondered when I created the landing
[13:28] <seb128> I looked twice at the target distro combos
[13:29] <kenvandine> seb128, :)
[13:29] <seb128> also I wonder if I a proper SRU would make sense
[13:29] <seb128> there is a string change in there
[13:30] <seb128> and we didn't figure out how to deal with string updates in the overlay ppa
[13:30] <kenvandine> oh... how are we handling string changes from the ppa?
[13:30] <seb128> the langpacks come from vivid
[13:30] <kenvandine> ugh
[13:30] <seb128> we don't
[13:30] <kenvandine> pmcgowan, ^^^ that's a real problem
[13:30] <seb128> we noticed that when testing the ota4 candidate
[13:30] <seb128> kenvandine, he knows, that was discussed a lot monday and yesterday
[13:30] <kenvandine> ok
[13:30] <seb128> we distro patched langpacks manually for the new strings for ota4
[13:30] <kenvandine> we probably need to SRU a bunch of stuff...
[13:31] <seb128> or figure out another way to update translations
[13:31] <seb128> like merging wily strings back in langpacks or something
[13:31] <seb128> but that would assuming that wily and overlay have no string mismatch at all
[13:31] <pmcgowan> yeah we need to fix that asap, even if it means ditching the ppa
[13:31] <jgdx> kenvandine, reminds me, I'm landing the connection type fixdesign in wily in it's own silo. :)
[13:32] <kenvandine> pmcgowan, agreed... we'll go into big time translation debt if we don't
[13:32] <kenvandine> jgdx, cool
[13:34] <pmcgowan> abeato, did you verify silo 31 already? awe ?
[13:34] <jgdx> seb128, kenvandine: https://code.launchpad.net/~system-settings-touch/ubuntu-system-settings/15.04/+activereviews :)
[13:35] <awe> pmcgowan, abeato tested krillin and it looks good.  I wanted to do some more testing on arale & mako this morning
[13:35] <abeato> pmcgowan, yes, I installed and tested, see comment in https://code.launchpad.net/~phablet-team/network-manager/lp1461593/+merge/261450
[13:35] <awe> pmcgowan, I'll ping you when I'm done
[13:35] <pmcgowan> awe, abeato great thanks
[13:35] <awe> ( and will also add my test results to the mp above )
[13:35] <awe> thanks abeato!
[13:36] <abeato> yw
[13:38] <sturmflut2> Hmmm, I suppose there are scripts to build the "ubuntu" tarball in an image from .deb packages, and the "custom" tarball is probably mostly built manually, but how does "device" come together? Who creates the boot images, the Android container etc.? And how?
[13:50] <kgunn> jhodapp: hey there, so seems we're still needing a media hub fix to make player controls for audio show up in indicator panel
[13:51] <kgunn> is that being worked? or had you thot we were all good ?
[13:51] <jhodapp> kgunn, I'm working on the prerequisite tasks right now of background playlists
[13:51] <jhodapp> kgunn, once that's done, then the player controls can come back
[13:52] <kgunn> jhodapp: just checking on time stack up, so pmcgowan looking at another freeze around mid july...
[13:54] <jhodapp> kgunn, yeah, we will need some changes to the indicator-sound to make it a little more intelligent (like hiding next/prev buttons when appropriate, etc)
[13:54] <pmcgowan> kgunn, jhodapp I need to make tasks to track the music player and indicators for that
[13:54] <pmcgowan> jhodapp, do you have that bug handy?
[13:54] <jhodapp> pmcgowan, I don't, not sure if there was one filed for that or not
[13:55] <pmcgowan> let me look
[13:57] <pmcgowan> jhodapp, there is this one https://bugs.launchpad.net/media-hub/+bug/1373313
[13:58] <jhodapp> pmcgowan, that needs updating, let me do that
[13:59] <pmcgowan> jhodapp, does it also need a uitk bug? or qtubuntu?
[13:59] <pmcgowan> task that is
[13:59] <jhodapp> pmcgowan, not to my knowledge, I'll redo the description as it's not quite accurate anymore, and include the sound menu again
[14:00] <pmcgowan> jhodapp, I included indicator-ound
[14:00] <pmcgowan> do not think sound menu is the right thing
[14:00] <jhodapp> pmcgowan, right, cool thanks
[14:01] <pmcgowan> popey, can you get that attention on the music app side once the api is working ^^
[14:02] <jhodapp> pmcgowan, trying to target this for the next ota?
[14:02] <popey> pmcgowan: sure.
[14:03] <popey> pmcgowan: do we have a bug tracking it that I can point the guys at? is 1373313 the right one?
[14:03] <jgdx> kenvandine, that tst-update-manager fails in trunk it seems
[14:03] <kgunn> jhodapp: i had hoped to target next ota, but if we can't we can't
[14:03] <pmcgowan> popey, yes I added a music-app task to it
[14:03] <pmcgowan> jhodapp, yes
[14:03] <jgdx> kenvandine, http://pastebin.ubuntu.com/11690383/
[14:03] <pmcgowan> or joe's head will explode
[14:03] <jhodapp> kgunn, pmcgowan ok, might need to see if I can get some help on this to accelerate it
[14:04] <kgunn> this is true ^^
[14:04] <jhodapp> lol
[14:04] <jhodapp> kgunn, also helping dednick to unblock him on the scope stuff
[14:05] <pmcgowan> jhodapp, I thought we loicm to help, the indicator stuff wont be bad
[14:05] <pmcgowan> thats why I thought there was qtubuntu work
[14:05] <popey> pmcgowan: ok
[14:05] <kenvandine> jgdx, interesting, but in CI it was a segfault?
[14:07] <jgdx> kenvandine, yes, but I don't know if that's accurate.
[14:07] <kenvandine> ok
[14:07] <jhodapp> pmcgowan, ok I can keep giving him stuff :)
[14:07] <kenvandine> has any of that code changed recently in trunk?
[14:10] <dobey> hmm, does anyone know if QtNetwork is using the modularized SSL stuff that uses libcurl-gnutls or libcurl-nss?
[14:10] <jgdx> kenvandine, device_name touched on that stuff, as well as seb128's if file exist-stuff
[14:10] <dobey> or perhaps just gnutls?
[14:11] <seb128> jgdx, touched what?
[14:11] <jgdx> seb128, system-update
[14:12] <seb128> hum
[14:12] <seb128> is it failing consistently?
[14:12] <seb128> the CI was fine on the mr
[14:13] <jgdx> seb128, right. Probably something wrong with the silo then.
[14:14] <kenvandine> jgdx, are you running the tests on wily of vivid?
[14:15] <kenvandine> i'm doing a trunk build to run the tests on vivid now
[14:15] <jgdx> kenvandine, trunk. I don't get failures if I run using ctest
[14:15] <jgdx> weird, all points towards silo now
[14:15] <kenvandine> ah
[14:15] <kenvandine> weird
[14:16] <jgdx> kenvandine, is it possible to go back to start in that silo?
[14:16] <jgdx> possibly collect $500
[14:20] <jgdx> seb128, new icon in silo 3 then?
[14:21] <dobey> jgdx: so i see your silo is having the same segfault issue as i am having
[14:21] <kenvandine> jgdx, can you review https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/wifi_activate_on_click/+merge/261425
[14:22] <kenvandine> dobey, oh?
[14:22] <seb128> jgdx, seems so ;-)
[14:22] <dobey> kenvandine: new gnutls/libnettle6 in wily appears to be broken: http://paste.ubuntu.com/11690433/
[14:22] <kenvandine> that could do it!
[14:22] <dobey> at least, on armhf and powerpc
[14:22] <kenvandine> jgdx, ^^
[14:23] <jgdx> look at that
[14:23] <dobey> sigh @ lack of autopkgtests for migration on armhf/powerpc
[14:23] <kenvandine> jgdx, i just confirmed that trunk passes on vivid
[14:24] <dobey> so anything that uses gnutls is going to segfault on phone, on wily images :-/
[14:24] <dobey> ugh, and no dbgsym for libnettle6 on ddebs :-/
[14:25] <ogra_> improve your guessing skills then :)
[14:25] <dobey> seb128: any suggestions on whom to poke to get this debugged further, and fixed?
[14:25] <Elleo> popey: heya, when building clicks for filemanager what do you do about the libsmbclient dependency? it doesn't look like it bundles libsmbclient.so with the package by default (unless I'm building it wrong in some way?)
[14:26] <popey> Elleo: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2015-June/015566.html
[14:26] <popey> I can't even build it!
[14:26] <Elleo> ah, heh
[14:26] <popey> looks to me like there's a problem with libsmbclient packaging, but I need someone else who knows more to take a look
[14:28] <seb128> dobey, unsure, try #ubuntu-devel, maybe mdeslaur since he's the most recently uploader for gnutls
[14:36] <kenvandine> jgdx, i added another backport to the spreadsheet
[14:53] <kenvandine> Elleo, my all_content_type branch is ready for review, when you get a chance
[14:55] <Elleo> kenvandine: cool, will take a look as soon as I've hacked together something to get this click package bundling libsmbclient
[14:56] <kenvandine> Elleo, thx
[14:56] <kenvandine> i'd like to see that too :)
[14:56] <kenvandine> Elleo, any plans to remove any of that code that we don't need?
[14:56] <kenvandine> i guess not any of that code
[14:57] <Elleo> kenvandine: I figured it made sense to leave the plugins alone, so we could share them between the projects
[14:57] <kenvandine> yeah
[14:57] <Elleo> kenvandine: most of it is upstream from nemo mobile's folderlistmodel plugin anyway
[14:58] <Elleo> kenvandine: although, it looks like that might have been rolled in to Qt.labs.folderlistmodel now
[14:59] <Elleo> kenvandine: so it might be worth rewriting a bit to use that instead
[14:59] <kenvandine> yeah
[14:59] <kenvandine> but we don't ship that?
[14:59] <kenvandine> we'd have to bundle that
[14:59] <Elleo> kenvandine: not sure, it's installed on my device without me remembering installing it myself
[15:00]  * kenvandine checks
[15:00] <kenvandine> what's the package?
[15:00] <Elleo> kenvandine: but I don't think its officially part of any framework
[15:00] <kenvandine> qml-module-qt-labs-folderlistmodel
[15:00] <kenvandine> i have it too
[15:00] <Elleo> yeah
[15:00] <kenvandine> so must be included
[15:01] <kenvandine> ubuntu-sdk-libs and unity8 depends on it
[15:01] <kenvandine> and webbrowser-app
[15:01] <kenvandine> seems pretty safe :)
[15:02] <Elleo> ah, cool
[15:02] <Elleo> will just see quickly if it works with a straight substition of the two modules
[15:02] <kenvandine> cool
[15:04] <jgdx> kenvandine, cool. I am eod but will check in later
[15:05] <Elleo> kenvandine: ah no, looks like it doesn't have everything we'd need; doesn't support things like the file selection model
[15:06] <kenvandine> ok
[15:06] <kenvandine> jgdx, thx
[15:36] <awe> pmcgowan, almost finished with testing.  Also, created this: https://wiki.ubuntu.com/Process/Merges/TestPlans/network-manager
[15:38] <pmcgowan> awe, great I pointed jibel at you earlier for that
[15:39] <awe> pmcgowan, ok.  Although I still don't quite understand our testing strategy(s) and who's supposed to run what test plans...
[15:40] <awe> this plan is something that we ( as phone engineers ) will run whenever we do new uploads of NM
[15:40] <pmcgowan> awe, if we gate all nm landings via CI we can do better, per previous discussions
[15:42] <awe> pmcgowan, sure... but we had no test cases previously.  Also CI still isn't fully defined for packages like network-manager
[15:42] <awe> I have to manually upload to the phablet-team telephony PPA, and then we do a binary sync to a silo
[15:42] <awe> also still trying to work out what happens in wily
[15:58] <MoPac> Hello; I hope this is the right channel. I just tried out the Unity8/touch LXC container in a desktop. I'm wondering: is the expected behavior is for more or less everything to be broken?  I wasn't sure if the lack of usability coudl be down to an installation problem or if there's ust not much of anything you're meant to be able to do in this version at the moment
[16:17] <BonobosSake> Hi !
[16:18] <BonobosSake> I need some help in my porting
[16:57] <kenvandine> jgdx, fyi, dobey filed bug 1463875 for that segfault
[17:05] <jgdx> kenvandine, cool
[17:09] <jgdx> kenvandine, your silo failed (30)
[17:15] <cedian_linux> How do I include AppArmor in a kernel port?
[17:28] <jjohansen> cedian_linux: https://wiki.ubuntu.com/SecurityTeam/AppArmorForPreviousKernels
[17:28] <cedian_linux> thanks
[17:29] <ice9> after  while of running "phablet-dev-bootstrap  phablet", it exited with error.GitError: manifests rev-list ('^5287c048fd4b6f1df66ee21ecb7eb54b6bf83085', 'HEAD', '--'): fatal: bad revision 'HEAD'
[17:31] <kenvandine> jgdx, yeah... :(
[17:32] <kenvandine> jgdx, same old segfault...
[17:35] <ice9> how can I fix the above error?
[17:35] <ice9> I'm creating the env for the first time
[18:08] <ice9> I need expert in setting up the dev env! :D
[18:32] <cedian_linux> what kernel backport do I need for the apparmor?
[18:33] <jjohansen> cedian_linux: it will depend on the device/kernel
[18:33] <cedian_linux> I use the oneplus one it's a phablet oc
[18:33] <jjohansen> look at the presquash branches
[18:34] <jjohansen> the patches will say for which kernels
[18:35] <cedian_linux> thanks
[18:35] <jjohansen> so say it is a 3.10 kernel you will need 3.10 and later back port patches, but not the 3.2 ones
[18:38] <lotuspsychje> do we have cutegram on ubuntu-touch ?
[18:39] <cedian_linux> what's the diference between the backports and peesquash
[18:40] <cedian_linux> sorry presquash
[18:41] <davmor2> lotuspsychje: no just the telegram app and I think a web app in the store too
[18:42] <lotuspsychje> davmor2: ok tnx
[18:46] <cedian_linux> jjohansen what is the difference between presquash and normal backports and how do I get the files?
[18:48] <jjohansen> cedian_linux: the presquash is the set of backport patches split out into individual patches so you can pick and choose which ones are needed for your platform, eg. maguro had cherry-picked some upstream fixes so it didn't need some of the the 3.2 backport patches
[18:48] <ice9> phablet-dev-bootstrap throws "error.GitError: manifests rev-list ('^5287c048fd4b6f1df66ee21ecb7eb54b6bf83085', 'HEAD', '--'): fatal: bad revision 'HEAD'", how can I clone the repo?
[18:49] <DonkeyHotei> peesquash is when you drown an insect in urine instead of squashing it would be my guess
[18:49] <cedian_linux> I need 3.4 patches
[18:49] <jjohansen> cedian_linux: the squash is just squashing all the patches down into 1 for the platform so that it is easier to manage, there shouldn't be any difference in the code
[18:50] <cedian_linux> thanks, can I also use the linux-apparmor-backports
[18:50] <jjohansen> squashing, has its disadvantages so whether you do it is up to the person maintaining the branch
[18:50] <jjohansen> cedian_linux: not yet, I am in the process of getting that set up
[18:50] <cedian_linux> Thanks
[18:51] <jjohansen> hopefully I will finish that today
[18:51] <jjohansen> then you will be able to use it and it will be the tree we point people at
[18:51] <cedian_linux> can I use this one? ubuntu-vivid.git
[18:52] <jjohansen> cedian_linux: yes, though IIRC ubuntu-vivid.git didn't have the backport patches split out
[18:52] <cedian_linux> Ok
[18:52] <cedian_linux> Then I should use utopic, don't I?
[18:53] <jjohansen> cedian_linux: if you can wait a few hours there should be something in the linux-apparmor-backports tree you can use
[18:53] <cedian_linux> I can't wait a few hours
[18:53] <jjohansen> cedian_linux: it is being setup to be very easy to use, so you just pick a branch that is close to your kernel
[18:53] <cedian_linux> thanks
[18:54] <jjohansen> cedian_linux: ack, so I would use a mix of ubuntu-vivid and ubuntu-utopic
[18:54] <jjohansen> vivid for the latest apparmor, utopic for the broken out backport patches
[18:55] <jjohansen> cedian_linux: of course you could probably just grab, ubuntu-vivid mako or gold fish apparmor dir
[18:55] <cedian_linux> thanks
[18:55] <jjohansen> and not worry about the individual patches
[18:55] <cedian_linux> thank you, I'll do that
[19:08] <cedian_linux> error: pathspec 'mako-aa3-backport-presquash' did not match any file(s) known to git.
[19:09] <cedian_linux> sorry was looking at Utopic
[19:14] <cedian_linux> what is git checkout
[19:49] <jgdx> kenvandine, ping
[19:50] <jgdx> kenvandine, can USS pick contacts using contacthub? I.e., does contact hub support that?
[19:51]  * jgdx brb, GOT
[20:00] <cedian_linux> can't run make at my config
[20:00] <cedian_linux> gives this error: warning: (DRM && ION) selects DMA_SHARED_BUFFER which has unmet direct dependencies (EXPERIMENTAL)
[20:01] <cedian_linux> warning: (ACPI_HOTPLUG_CPU) selects ACPI_CONTAINER which has unmet direct dependencies (ACPI && EXPERIMENTAL)
[20:01] <cedian_linux> #
[20:01] <cedian_linux> # configuration written to .config
[20:01] <cedian_linux> #
[20:01] <cedian_linux> warning: (DRM && ION) selects DMA_SHARED_BUFFER which has unmet direct dependencies (EXPERIMENTAL)
[20:01] <cedian_linux> warning: (ACPI_HOTPLUG_CPU) selects ACPI_CONTAINER which has unmet direct dependencies (ACPI && EXPERIMENTAL)
[20:01] <cedian_linux> make[1]: Nothing to be done for 'all'.
[20:01] <cedian_linux> make[1]: Nothing to be done for 'relocs'.
[20:01] <cedian_linux>   CHK     include/linux/version.h
[20:01] <cedian_linux>   CHK     include/generated/utsrelease.h
[20:01] <cedian_linux>   CALL    scripts/checksyscalls.sh
[20:01] <cedian_linux>   CHK     include/generated/compile.h
[20:01] <cedian_linux>   CC      arch/x86/kernel/pci-dma.o
[20:01] <cedian_linux> arch/x86/kernel/pci-dma.c: In function ‘dma_generic_alloc_coherent’:
[20:01] <cedian_linux> arch/x86/kernel/pci-dma.c:112:8: warning: assignment makes pointer from integer without a cast
[20:01] <cedian_linux> error, forbidden warning: pci-dma.c:112
[20:01] <cedian_linux> scripts/Makefile.build:307: recipe for target 'arch/x86/kernel/pci-dma.o' failed
[20:01] <cedian_linux> make[2]: *** [arch/x86/kernel/pci-dma.o] Error 1
[20:01] <cedian_linux> scripts/Makefile.build:443: recipe for target 'arch/x86/kernel' failed
[20:01] <cedian_linux> make[1]: *** [arch/x86/kernel] Error 2
[20:01] <cedian_linux> Makefile:950: recipe for target 'arch/x86' failed
[20:01] <cedian_linux> make: *** [arch/x86] Error 2
[20:05] <dobey> cedian_linux: please use a pastebin site like paste.ubuntu.com for future pastes like that
[20:05] <cedian_linux> ok
[20:09] <hevyhomie> can anyone point me in the right direction? I am porting touch to moto e (can't find an image anywhere on the net), and I am stuck after 1) . build/envsetup.sh 2) lunch 3) pick #. After which I get build/core/product_config.mk:222: *** Can not locate config makefile for product "condor" something about a product spec?
[20:12] <lotuspsychje> hevyhomie: did you try the XDA forums for existing projects?
[20:13] <hevyhomie> i did no luck
[20:13] <hevyhomie> i mean no existing projects are under development
[20:14] <lotuspsychje> hevyhomie: ok then your pretty on your own for this i think :p
[20:15] <lotuspsychje> hevyhomie: i presume you found the porting guide also: https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
[20:17] <hevyhomie> yes i copied relevant files from cyanogenmod(respect to them) into the phablet folders respectively
[20:18] <hevyhomie> device, hardware and vendor i believe
[20:19] <hevyhomie> then I ran the kernel config script :check-config <defconfig file> -w
[20:19] <hevyhomie> i decided not use apparmor3 yet
[20:20] <JimHatley> testing... testing... Am I connected to #ubuntu-touch?
[20:21] <hevyhomie> then i decided to build,
[20:21] <JimHatley> I think I'm connected...
[20:22] <hevyhomie> btw i found a thread on xda, but no dev project currently:http://forum.xda-developers.com/ubuntu-touch/android-ports/port-request-ubuntu-touch-moto-e-gen1-t3043485
[20:22] <JimHatley> Hey guys... Not sure of protocol here, but I have a couple of minor questions if anyone has any answers...
[20:23] <lotuspsychje> hevyhomie: cant really help you more, im just a happy touch user here
[20:23] <lotuspsychje> hevyhomie: idle here for the devs to awaken :p
[20:23] <hevyhomie> lotuspsychje: thanks for answering :)
[20:24] <JimHatley> Ahh... Yeah, might need a dev. Need to know the command name for the lock screen notification circle so I can kill it. And, preferably, kill it for good. It doesn't tell me anything I need to know, and blocks my sweet wallpaper at the only time I can actually see iy!
[20:24] <JimHatley> *it
[20:27] <hevyhomie> brb
[20:41] <cedian_linux> What did I do wrong jjohansen?
[20:41] <jjohansen> cedian_linux: give me a minute to read back scroll
[20:41] <cedian_linux> Ok
[20:42] <ogra_> cedian_linux, looks like you are building an x86 kernel there ... was that what you wanted ?
[20:42] <cedian_linux> No
[20:43] <cedian_linux> That's the problem then, I'll report it
[20:43] <jjohansen> you will need to setup your cross compile environment
[20:43] <cedian_linux> Ok
[20:44] <jjohansen> cedian_linux: I think https://wiki.ubuntu.com/KernelTeam/ARMKernelCrossCompile should have what you are looking for
[20:45] <ogra_> jjohansen, thats pretty ubuntu .deb centric though ...
[20:45] <jjohansen> true
[20:45] <ogra_> export CROSS_COMPILE=arm-linux-gnueabihf- ... export ARCH=arm  are the two vars you want to have set ...
[20:46] <ogra_> (and indeed make sure to have the gcc-arm-linux-gnueabihf compiler installed ... that should be enough)
[20:51] <cedian_linux> Shouldn't it be armhf ogra_
[20:52] <ogra_> no, arm is correct (thats a kernel variable ... while armhf is a debian architecture)
[20:52] <cedian_linux> Thanks
[20:52] <ogra_> (the latter refers to packaging)
[20:52] <cedian_linux> I'll leave for now sent myself a mail and I'll go to sleep
[20:52] <ogra_> well, good luck :)
[20:52] <ogra_> meh
[21:09] <ice9> I'm trying to create env dir using phablet-dev...  but after it downloaded about 3.5GB I get "error.GitError: manifests rev-list ('^5287c048fd4b6f1df66ee21ecb7eb54b6bf83085', 'HEAD', '--'): fatal: bad revision 'HEAD'"