[00:17] <Makalak> i just built ubunto touch for my phone and after flashing the boot.img and calling ./rootstock-touch-install, i rebooted to be stuck at the boot screen with HTC logo, adb works, but nothing booted, is there something im missing?
[01:54] <aquarius> Elleo, if you're around tomorrow for the conversation with nik90_ then I'd love to hear your thoughts.
[01:54] <aquarius> but it's 2am now so I'm going to sleep :)
[01:58] <Elleo> aquarius: will probably be out a tomorrow afternoon/evening, but if I'm around will gladly join in :)
[01:58] <Elleo> -a*
[01:59] <aquarius> nice one. nik90_ said he was around tomorrow; I'll try and yank you both into a discussion where I explain what I've done and what remains, and wait fr you both to pick it apart. :)
[02:00] <Elleo> okay, cool
[02:00] <nhaines> aquarius: off topic, but did you ever make any progress with that qt datapath issue for the Amazon Cloud Reader webapp?
[02:24] <Snizzo> anyone knows some tips to increase battery on utouch n5?
[02:31] <nhaines> Snizzo: I suspect if anyone knew that, they'd include it in the N5 images.
[02:34] <Snizzo> nhaines, that make really sense. Thanks for replying. I'd like to use utouch as DD :)
[02:34] <nhaines> Snizzo: It's really nice.  If it had Bluetooth support, I very likely may have been using it as a DD too.  :)
[02:36] <Snizzo> I'm writing from irc webapp right now and I'm anapp developer so I'd like to use it and develop every day
[03:33] <amahoola> hi
[06:03] <wirahetaubuntu10> Hello
[06:03] <lotuspsychje> hi
[06:04] <wirahetaubuntu10> I honestly dont know what this chat is for. Do you?
[06:04] <wirahetaubuntu10> @lotuspsychje
[06:05] <lotuspsychje> this is for all ubuntu touch discussions
[06:05] <lotuspsychje> ubuntu running on tablets/phones
[06:05] <lotuspsychje> !devices | wirahetaubuntu10
[08:18] <lappitoppi1> i hope i found right channel
[08:18] <lappitoppi1> MY MOBILE BROKE I NEED A NEW ONE
[08:19] <lappitoppi1> i waited as long as i could
[08:19] <lappitoppi1> ;-)
[08:20] <lappitoppi1> is there any with an not android linux on it???
[08:20] <lappitoppi1> exspecially ubuntu ;-)
[08:21] <lappitoppi1> cause ive to buy one NOW
[08:21] <lappitoppi1> and i waited for release .....whole 2014
[08:22] <nhaines> I suspect bq will sell the bq Aquaris in Germany in February.
[08:23] <lappitoppi1> *sign* i need a phone and i waited so long and now ONE MONTH nooooooooooooo
[08:24] <lappitoppi1> theres smthn about meizu hdys but i didnt read sthn instead of flyme
[08:24] <nhaines> Yes, but no dates mentioned with Meizu.
[08:30] <lappitoppi1> so if i would like to have a mobile with ubuntu on it I... wait(which i couldnt?;-) orrrrr???? buy which mobile which functions propably the best with self installed?
[08:32] <nhaines> Nexus 4.
[08:32] <lappitoppi1> k thx it will be an nexus4 thx very much
[08:34] <uhhimhere> hi guys i have a project:
[08:34] <uhhimhere> http://forum.cyanogenmod.org/topic/103336-dtsi-compiling-vanilla-linux-on-samsung-gt-s7580/
[08:34] <uhhimhere> can someone help me out
[08:43] <lappitoppi1> sry bothering again on nexus 4 its an android-kernel isnt it?
[08:44] <nhaines> lappitoppi1: I don't understand what you mean.
[08:44] <lappitoppi1> i mean ubuntu runs with android kernel
[08:44] <lappitoppi1> im not an crack sry
[08:44] <nhaines> Yes, after Ubuntu boots, it spawns an LXC container with a minimal Android kernel for driver support.
[08:45] <nhaines> Other than graphics, sound, and Bluetooth drivers (maybe radio, too), everything's Ubuntu.
[08:46] <lappitoppi1> kk ;-)
[09:06] <lappitoppi1> bebe
[09:22] <aquarius> nhaines, isn't something I can progress, the dataPath issue; it just needs to be fixed by Oxide. Elleo did say he had a C++ workaround, which maybe I can get him to package up as a component once I have a working component store ;)
[09:24] <nhaines> aquarius: ah, I thought you might've been able to look at the workaround.
[09:25] <aquarius> nhaines, not so far... and, honest truth, this *ought* to be a web app, not a QML app with an Oxide widget. I gain nothing by sticking it in a box :)
[09:26] <nhaines> aquarius: well, you gain that it works.  :)  But I agree.  Webapp is way, way better.
[09:26]  * aquarius laughs
[09:26] <aquarius> that's why I looked at doing it with oxide.
[09:26] <nhaines> I should've bookmarked the oxide bug.
[09:26] <aquarius> having both paths to success be blocked was pretty frustrating
[09:27] <aquarius> nhaines, https://bugs.launchpad.net/webbrowser-app/+bug/1405844
[09:28] <nhaines> Thanks!
[09:29] <nhaines> I'm glad to see no one's done anything with it yet.
[09:31] <aquarius> well, I was all poised to get quite irate about that, until I noticed that Elleo filed it on Boxing Day. So every day since then has been Christmas holidays :)
[09:34] <nhaines> Eh, sure.  :)
[10:13] <noob2> hi, i'm new and i have never filed bugs and stuff before. what would be the best way to complain about that updater-popup saying i have to restart which annoys me every 90 seconds?
[10:28] <aquarius> noob2, you can file a bug about it, but it's that way by design: when you get warned that you need to restart, you really do actually need to restart. You can continue using your machine, but various subtle things under the surface are now inconsistent, and there is the potential for that to cause big problems later on; restarting fixes that.
[10:28] <aquarius> noob2, you are only told to restart if an update you've installed actually needs it; most updates don't.
[10:32] <noob2> aquarius: telling me one time is ok, interrupting presentations or movies every 90 seconds makes me want to change the distro
[10:33] <nhaines> noob2: alternatively, don't run updates unless you are willing to restart if required.
[10:34] <aquarius> noob2, hang on, perhaps I'm not understanding here. You should get a popup window with "Restart now" and "Restart Later" buttons (I think?). Are you saying that you press Restart Later and then it comes back 90 seconds later?
[10:35] <noob2> yes, 'restart later' and then it keeps coming back
[10:35] <aquarius> ok, coming back after 90 seconds seems aggressive, indeed
[10:38] <aquarius> noob2, and this is running normal Ubuntu 14.04?
[10:39] <noob2> yes, pretty default ubuntu 14.04
[10:39] <aquarius> noob2, if you wanted to report a bug, then you can do so at https://bugs.launchpad.net/ubuntu/+source/update-manager/+filebug or by opening a Terminal window and typing "ubuntu-bug update-manager".
[10:45] <noob2> aquarius: ok, thank you. i'll use the website, apport seems to collect to much personal data
[12:05] <aquarius> nik90_, when you're around, let me know :)
[12:45] <aquarius> Elleo, dunno if you're around either
[12:45] <Elleo> aquarius: I am at the moment, but not for very much longer
[12:46] <aquarius> Elleo, does http://bazaar.launchpad.net/~sil/component-store/community-components/view/head:/docs/contribute-community.rst make sense to you?
[12:50] <aquarius> (also, refresh and it should be wrapped better :))
[12:52] <aquarius> oops, I forgot to define the ubuntu_component_store.json file. :)
[12:52] <Elleo> aquarius: looks good to me; only query I have is if "bin/" should actually be "lib/"?
[12:53] <aquarius> Elleo, the reason it's not /lib is that you may have things in /lib which your project is depending on
[12:53] <aquarius> and then we can't tell the difference between "this is the thing I am publishing" and "this is stuff that the thing I'm publishing needs"
[12:53] <Elleo> ah, okay
[12:54] <aquarius> happy to rename it to something else, though
[12:54] <Elleo> what about qmllib? or something like that?
[12:54] <aquarius> that seems fine to me; I have no real preference for the name, so if you think that'd make it clearer, I'm fine wiht it :)
[12:54] <Elleo> just a little concerned with bin/ since that's likely to be where compiled executables from the user's projects will go for fat packages
[12:55] <aquarius> good thought
[12:55] <aquarius> qmllib it is then :)
[12:58] <nik90_> aquarius: hey, I am here now
[13:04] <aquarius> nik90_, heya, pal!
[13:04] <aquarius> basically, I plan to brain dump at you. How would you like to receive this stuff? :)
[13:10] <nik90_> however you wanted to send it :)
[13:10] <nik90_> aquarius: I am up for anything
[13:11] <aquarius> nik90_, ok. Basically, what I've done is branched component-store trunk to https://code.launchpad.net/~sil/component-store/community-components. That branch has many changes in it! I shall outline them here, and you ask questions.
[13:11] <nik90_> ok
[13:11] <aquarius> 1. I reorganised things so there aren't a zillion top level things
[13:12] <aquarius> that is: the app got moved into a folder called "app", rather than being at the top level of the repo.
[13:12] <aquarius> that might screw things up for something you've done. I hope not.
[13:13] <aquarius> 2. I moved script/ucs to script/ucs.sh so we still have it around, and wrote script/ucs in Python, because it's quite a bit more complicated now. :)
[13:13] <aquarius> you can try it out; it implements ucs install and, newly, ucs search.
[13:13] <nik90_> ooh nice
[13:14] <aquarius> and it knows about both curated and community repositories.
[13:14] <aquarius> two things missing, there: it does not implement ucs update yet (but if you ucs install a thing that's already installed, we'll just overwrite it)
[13:15] <aquarius> and I have not touched the debian package stuff which is needed to make it a working package in the PPA. This is because I don't understand debian packaging, and no doubt that will have to change because it's now a python app which depends on bzrlib
[13:15] <nik90_> ok I can fix that
[13:16] <aquarius> 3. I have implemented the community server -- the place that receives "ucs submit" calls. Basically, to submit to the community store you publish an LP branch with files in a particular place, and then ucs submit lp:~sil/whatever/whatever. The server, which is currently at PythonAnywhere and is a simple Python Flask server, grabs that branch, does some checks, and then adds the new component to the JSON list.
[13:17] <nik90_> aquarius: we can actually merge GallerySRC and app into one folder since they both require one other.
[13:17] <nik90_> so one less top level folder
[13:17] <aquarius> (I tried fairly hard to not touch any of your stuff in case I screwed it up :))
[13:17] <nik90_> ok I will propose a merge against your branch later today
[13:18] <aquarius> the community store is defined by the JSON list of all components. This list is, itself, stored in Launchpad, in a new branch, https://code.launchpad.net/~ubuntu-touch-community-dev/component-store/community-components-json which contains one file: the big JSON list.
[13:18] <aquarius> so when you ucs submit a component, the community server checks it's OK, gets the metadata from it, adds it to the big JSON list, and pushes the big JSON list back to Launchpad.
[13:18] <nik90_> ok
[13:19] <aquarius> when you do ucs search or ucs install, your local ucs downloads the big JSON list from launchpad and gets the component data from it locally, sorta like apt does with Packages files -- it then knows the LP branch to get the component from.
[13:19] <nik90_> aquarius: btw you are fine with distributing the ucs.sh script via PPA to allow for easy installation?
[13:19] <aquarius> ucs script. ucs.sh shoudl go away now, I think
[13:20] <aquarius> PPA, yeah, is definitely the way for this )
[13:20] <aquarius> :)
[13:20] <nik90_> yeah that's what I meant
[13:20] <aquarius> 4. ucs install needs to download the component from launchpad (this is the same for curated and community components), install it in an appropriate place, and then tell the project you're in that it's there.
[13:21] <aquarius> There are three types of projects (qml, qmake, cmake) and two types of components (qml, binary), so there are six different ways that can happen. Some are implemented, some are not. :)
[13:21] <nik90_> ack.
[13:22] <aquarius> QML component, QML project: component goes in projectroot/ubuntu_component_store/username/ComponentName/. (The "username" for curated components is "Curated".) We construct a qmldir file, and then everything works.
[13:23] <aquarius> Binary component, QML project: component goes in lib/$arch/ubuntu_component_store/username/ComponentName. We construct a qmldir file and we explicitly add this arch to qmlproject:importPaths.
[13:24] <nik90_> are the binary components already built? or source files?
[13:24] <aquarius> already built.
[13:24] <aquarius> QML component, qmake project:  component goes in projectroot/ubuntu_component_store/username/ComponentName/. We construct a qmldir file, and we add the ubuntu_component_store folder to qmake so that it gets copied into the build folder.
[13:24] <nik90_> ok so we need to inform submitters to build and upload it to their branch before uploading to store
[13:24] <aquarius> (we do. I'll get to that in a sec. :))
[13:25] <aquarius> binary components for qmake projects, and all components for cmake projects, aren't done yet, because I haven't worked out *how* to do them. :)
[13:26] <nik90_> The clock app (cmake) builts its binary components during runtime and copies it into the build folder
[13:27] <aquarius> 5. I have updated the documentation. We now clarify the difference between curated and community components (while leaning slightly on the idea that curated components are better because they require tests, etc), and how to create and submit a community component is documented at http://bazaar.launchpad.net/~sil/component-store/community-components/view/head:/docs/contribute-community.rst
[13:28] <aquarius> that file is very clear that you're uploading a binary, and also says "and add the source to the branch as well!"
[13:28] <nik90_> cool
[13:28] <nik90_> btw this is the same documentation that we use in http://ubuntu-component-store.readthedocs.org/en/latest/ /
[13:28] <aquarius> what I would like is a Qt Creator template which is just for building binary components, which puts everything in the correct places. But I don't know how to do that.
[13:29] <aquarius> the clock app does that because it knows which components it has. What we need is a way to tell the project build scripts "copy this folder into the build folder". I know how to do that for qmake, now, but not for cmake.
[13:29] <nik90_> ah yes
[13:30] <aquarius> Anyway, that's everything, I think. You should, right now, if you have my ucs python script, be able to cd to anywhere inside a pure qml project and say "ucs install <curated component>" and then "import ubuntu_component_store.Curated.ComponentName 1.0" and have it work.
[13:30] <aquarius> (the same for community components, except there are only two: my genericpodcastapp and a stupid binary component which prints your home dir, and is only compiled for amd64 :)
[13:31] <aquarius> only compiling for amd64 is against the rules, btw; I only did that because I'm testing.
[13:31] <nik90_> yeah yeah ofc
[13:31] <aquarius> but it all works, I think, and is all documented.
[13:32] <aquarius> from your perspective, I think the only thing I've changed is that now you use a curated component with import ubuntu_component_store.Curated.ComponentName 1.0, rather than import "ubuntu_component_store".
[13:32] <aquarius> which is a change, but I think it's for the better.
[13:32] <aquarius> So: that's the brain dump. Ask questions. :-)
[13:32] <nik90_> aquarius: I will give the permissions for readthedocs as well so that you can rebuild the docs on the website whenever you make changes to the docs
[13:32] <aquarius> is anyone actually using this stuff yet?
[13:33] <aquarius> bear in mind that if they are, we'll break them with these changes.
[13:33] <aquarius> I don't think anybody is...
[13:33] <DanChapman> aquarius, i'm using it for dekko
[13:33] <aquarius> DanChapman, ooh, really?
[13:33] <aquarius> that is useful info!
[13:33] <aquarius> DanChapman, are you installing components with ucs?
[13:33] <nik90_> pretty sure michael hall is using it...
[13:33] <nik90_> I also saw few others using the radial bottom edge component
[13:34] <aquarius> nik90_, right, so you want to avoid merging my stuff until we have a transition plan. :)
[13:34] <DanChapman> aquarius, yeah using what nik90_ demoed at UOS. I actually have a few components i'd like to submit :-D
[13:34] <nik90_> DanChapman: ooh cool...
[13:34] <nik90_> aquarius: he could be a good test subject :P
[13:34] <aquarius> DanChapman, cool!
[13:34] <aquarius> he could indeed :)
[13:35]  * DanChapman signs up to be a lab rat
[13:35] <aquarius> you can submit to the community store first, if you like, and then later have those components graduate into being curated if you want them to be.
[13:35] <nik90_> aquarius: actually it would be prefereable that all components enter the community store first
[13:35] <nik90_> stay there and then graduate to the curated store when it has sufficient interest
[13:35] <aquarius> I agree with that, I just didn't want to stipulate it ;)
[13:36] <nik90_> this way we can reduce the load on ourselves
[13:37] <nik90_> aquarius: in the json file, I see type: [ "qml" ]....wouldn't it be better as type: "qml" ?
[13:37] <nik90_> in this file http://bazaar.launchpad.net/~ubuntu-touch-community-dev/component-store/community-components-json/view/head:/community_components.json
[13:38] <aquarius> nik90_, I'm keeping the possibility open for a component which is both qml and binary; that's why it's a list.
[13:38] <nik90_> is that possible?
[13:38] <nik90_> as in would components be both qml and binary?
[13:39] <aquarius> yep. You publish a binary component which provides, say, a Triangle item, and then RedTriangle.qml which is: Triangle { color: "red"; }
[13:39] <aquarius> then someone can use RedTriangle { } in their code.
[13:39] <nik90_> ah yes
[13:39] <aquarius> I'm not sure it's *useful*, but I think it will be, as people develop more complex components
[13:40] <aquarius> and if I restrict a component to being either binary or qml, then it'll sod us up later on. A list leaves possibilities :)
[13:40] <DanChapman> aquarius so do you want me submit components using the current method or this new proposed method?
[13:40] <nik90_> yeah ... a change later would be difficult indeed
[13:40] <nik90_> DanChapman: new proposed method
[13:40] <DanChapman> ok cool
[13:40] <nik90_> old method is only for the curated store
[13:40] <aquarius> DanChapman, the new one, but bear in mind that it's not even merged to ucs trunk yet ;)
[13:41] <nik90_> DanChapman: yes, we first need to release the new ucs to the ppa so you get it...only then would you get the new method
[13:41] <aquarius> DanChapman, and, to be clear, this is very very new indeed, so expect there to be problems and so on :)
[13:41] <aquarius> DanChapman, does http://bazaar.launchpad.net/~sil/component-store/community-components/view/head:/docs/contribute-community.rst make sense to you?
[13:43] <DanChapman> aquarius: just reading through it now
[13:45] <nik90_> aquarius: can you create an account on readthedocs and give me the username...I can then add that to the admin list of ucs docs
[13:46] <aquarius> nik90_, username: sil
[13:46] <nik90_> aquarius: done
[13:47] <nik90_> it is already connected to the ucs launchpad branch..all that needs to be done is press build to see the updated docs
[13:47] <nik90_> ofc only after your branch is merged in
[13:52] <DanChapman> aquarius, first thing that jumps out at me is the "your component is expected to
[13:52] <DanChapman> use `qmlRegisterType <http://doc.qt.io/qt-5/qqmlextensionplugin.html#details>`_" should it not be that it is expected the component registers a "Type" to make it accessible in qml. Someone may want to provide their component as a singleton type or an additional uncreatable type that provides enums for there binary component.
[13:52] <aquarius> DanChapman, er.
[13:52] <aquarius> perhaps
[13:52] <aquarius> I don't know much about this stuff
[13:52] <aquarius> you obviously know a lo more than I do :)
[13:53] <aquarius> I'm going by http://doc.qt.io/qt-5/qtqml-tutorials-extending-qml-example.html#chapter-6-writing-an-extension-plugin
[13:53] <aquarius> but if there's better wording for that, I'm happy to hear it!
[13:54] <aquarius> as long as what comes out the far end is a .so file which we can import into QML, I'm happy -- wording for how that should be built and advice is basically up to you, I think; you're a lot more clueful about this than I am
[13:55] <DanChapman> aquarius: :-D take a look at the "Related Non-Members" section http://doc.qt.io/qt-5/qqmlengine.html to see all the types that can be registered
[13:56] <aquarius> cor
[13:56] <aquarius> I don't even know what 90% of that is ;)
[13:56] <aquarius> DanChapman, you may want to take the lead on helping to define this stuff, if you have time, as well as cntributing components to it :)
[13:59] <DanChapman> aquarius: hah! sure I can help out with it. i'll make a MP against what you have there at the moment
[13:59] <nik90_> aquarius: can you propose a MP to make it easier to see the code diff. Atm I am testing out the commands.
[14:00] <aquarius> nik90_, I'm happy to, if you're happy :)
[14:00] <gcollura> nik90_, hey :) could you please see if this  https://code.launchpad.net/~gcollura/ubuntu-ui-toolkit/fix-1341814-and-1400297 fixes the bugs linked? (I'm asking you since you were affected by the first one of the two :)
[14:00] <gcollura> thanks :)
[14:01] <nik90_> aquarius: I haven't looked at the code, but the funtionality that we need seems to be there and I am excited
[14:01] <nik90_> gcollura: sure
[14:01] <aquarius> DanChapman, the two big things that I'm missing at the moment are having ucs be able to add components to qmake and (particularly) cmake projects, and a Qt Creator template which sets up and builds a component with the correct filesystem layout
[14:01] <aquarius> DanChapman, along with correct documentation ;-)
[14:05] <aquarius> nik90_, https://code.launchpad.net/~sil/component-store/community-components/+merge/245510 MP added
[14:06] <nik90_> thnx
[14:17] <Cardiomyopathy> Hello
[14:34] <nik90_> aquarius: if I have 2 components that I install from either the community or curated store, what would the import statement be?
[14:35] <nik90_> would "import ubuntu_component_store.Curated" work?
[14:39] <fastbooter> Trying to install Ubuntu Touch to an RCA Voyager 7. Device is in FASTBOOT mode but using the command ubuntu-device-flash --channel=devel --bootstrap results in 'device not found on server'
[14:40] <fastbooter> Is there a way to install from a local image? Is there better documentation for 'ubuntu-device-flash'? None of the options seem to work
[14:47] <aquarius> nik90_, I don't think I understand the question?
[14:47] <nik90_> aquarius: let say I install RadialBottomEdge and PageWithBottomEdge from the curated store. How do I import them into my app?
[14:47] <nik90_> would "import ubuntu_component_store.Curated" suffice?
[14:48] <aquarius> nik90_, oh, as in, you install two Curated components? You have to import them both individually. So import ubuntu_component_store.Curated.RadialBottomEdge 1.0; import ubuntu_component_store.Curated.PageWithBottomEdge 1.0;
[14:48] <aquarius> you can't just import ubuntu_component_store.Curated because it doesn't have a version number.
[14:48] <nik90_> ah
[14:49] <aquarius> we currently do not handle version numbers very well at all, and we need to decide how to do that.
[14:49] <aquarius> it's easy for community components; we'll just require a version number in the json metadata file, and then use it (at the moment it's all hardcoded to 1.0, oops).
[14:49] <aquarius> but curated components don't have metadata.
[14:49] <nik90_> understood
[14:50] <nik90_> btw can I rename the "app" folder to something like "curated-store" to make it more specific?
[14:50] <aquarius> to whatever you want, indeed
[14:50] <aquarius> I don't do anything which relies on it
[14:50] <aquarius> I just wanted to move that stuff somewhere other than the root :)
[14:51] <nik90_> you should be using it in your python script to tell it where to download the files from? no?
[14:52] <aquarius> crap. yes
[14:52] <aquarius> :)
[14:52] <nik90_> I will leave it as such then
[14:52] <nik90_> we can change it later
[14:52] <nik90_> I proposed https://code.launchpad.net/~nik90/component-store/fix-gallerysrc/+merge/245512 which only moves the gallerySRC folder
[14:52] <aquarius> lines 251-232
[14:53] <aquarius> 251-252
[14:53] <aquarius> at the moment, the ucs tool points at trunk
[14:53] <aquarius> which is why it didn't change :)
[14:53] <aquarius> good catch.
[14:53] <aquarius> so line 252 will need to change from COMPONENTS_ROOT = "ComponentStore" to COMPONENTS_ROOT = "curated-store/ComponentStore" or similar
[14:54] <nik90_> ok, let me change it quickly then and test
[14:55] <aquarius> if you wanna propose that as a mege to my branch, I'll merge it in, and then I'll fix ucs.
[14:55] <aquarius> (which means that ucs won't work until it hits trunk, but that's OK)
[14:56] <nik90_> I will fix both and add the changes to https://code.launchpad.net/~nik90/component-store/fix-gallerysrc/+merge/245512
[14:56] <nik90_> should be faster
[14:57] <aquarius> ah, I've just merged that branch :)
[14:57] <nik90_> no worries then
[14:57] <aquarius> but if you wanna just tidy everything up, that's fine :)
[14:58] <nik90_> I am just tidying up whatever is necessary to make the transition like the debian folder, curated-store etc..
[15:01] <Makalak> hi, I'm still trying to get my build of ubuntu working on HTC One X, but as the phone starts its stuck at the HTC logo and i can access adb...I figured the problem is due to a failure in finding the data partition, thus cant find the system.img to mount it etc, this is the kmsg of that boot http://pastebin.com/H8662k5E
[15:04] <Makalak> i tried editing /scripts/touch as it seems like the script in charge of finding and mounting that partition, but that causes a bootloop, doesnt even make a last_kmsg... could the bootloop be caused by invalid page size? we always use 2048 but is it different for ubuntu?
[15:04] <nik90_> aquarius: does this look good? https://code.launchpad.net/~nik90/component-store/rename-app-folder/+merge/245514
[15:05] <nik90_> I will later in the nite do the debian folder fixes
[15:05] <aquarius> nik90_, I think so certainly
[15:06] <aquarius> brb
[15:09] <DanChapman> aquarius: nik90_ how is versioning going to work for backwards compatability? See i'm thinking that all these components qml/js/binary should be imported as plugins. I think the components should have a qmldir module definition file and then all that's needed is to import the plugin/module by adding it to the QML2_IMPORT_PATH and this also provides versioning capabilities. let me find a link to the qmldir docs
[15:09] <aquarius> DanChapman, ucs creates a qmldir file for it
[15:09] <DanChapman> ahh right
[15:10] <aquarius> DanChapman, my plan, which isn't done yet, is that a community component provides its version number in its metadata, and then ucs uses that when it creates the qmldir file
[15:10] <aquarius> (at the moment it just hardcodes version 1.0. :-))
[15:13] <DanChapman> aquarius: right I didn't realise it does that now... So i presume just bumping the metadata will still preserve the previous version in the qmldir?
[15:13] <aquarius> DanChapman, a good question and one that needs thinking about
[15:14] <aquarius> my *inclination* is to say that if I change my component to say it's version 2.0, and someone ucs updates it, we overwrite the old version with the new one. Maybe
[15:14] <aquarius> or, actually, better, you can put version numbers on the ends of component folders
[15:14] <aquarius> so atm we have ubuntu_component_store/sil/MyComponent/MyComponent.qml
[15:15] <aquarius> and we'd change that to ubuntu_component_store/sil/MyComponent1.0/MyComponent.qml
[15:15] <aquarius> and then a new version installs to ubuntu_component_store/sil/MyComponent2.0/MyComponent.qml
[15:15] <aquarius> the qml importer understands version numbers on folder names
[15:15] <nik90_> aquarius: I would prefer ubuntu_component_store/sil/MyComponent/1.0/MyComponent.qml
[15:15] <aquarius> nik90_, the qml importer doesn't understand that
[15:16] <nik90_> ah yes
[15:17] <nik90_> aquarius: so for the debian folder, I would just need to update the dependencies and the changelog
[15:17] <nik90_> I am still going  to install the python script into /usr/bin
[15:17] <aquarius> cool
[15:17] <nik90_> people should be able to call it still by "ucs" so we maintain backwards compatibility there
[15:18] <nik90_> the only regression (change) is not being to install multiple components with one command like "ucs install component1 component2", but this can be added later on
[15:18] <nik90_> or we just leave entirely
[15:19] <nik90_> s/leave entirely/leave that entirely
[15:20] <aquarius> ya
[15:20] <aquarius> that ought to be doable fine, I just didn't do it
[15:21] <aquarius> it's a relatively trivial fix
[15:21] <aquarius> but it's simpler to not have it at first
[15:21] <nik90_> yeah lets leave it for now
[15:21] <aquarius> hence me tweaking the docs slightly to not use it as an example :)
[15:21] <nik90_> :)
[15:21] <aquarius> we need to talk about ucs update as well
[15:21] <aquarius> and how it should work
[15:22] <aquarius> that's totally not implemented, right now :)
[15:22] <nik90_> we need versioning for that
[15:22] <aquarius> we do
[15:22] <nik90_> in the community json file, we already have rev no
[15:22] <aquarius> I know how to do versioning for the community stuff
[15:22] <aquarius> we don't use revno for qml versioning
[15:23] <nik90_> I meant here http://bazaar.launchpad.net/~ubuntu-touch-community-dev/component-store/community-components-json/view/head:/community_components.json
[15:23] <aquarius> we need to add a required version to the ubuntu_component_store.json file in each component
[15:23] <aquarius> the server grabs the version number when you ucs submit a component, to make sure that it checks out *the submitted version*, not HEAD
[15:23] <aquarius> it grabs the revno, I mean
[15:23] <aquarius> we need both
[15:24] <aquarius> but what do we do about version numbers for curated components?
[15:25] <nik90_> would following the same .json structure for curated components make it possible?
[15:25] <aquarius> it would, but we have to fetch the json file for each of the components... which is not that fast
[15:26] <aquarius> on the other hand, we can cache the revno of each of those files, can't we?
[15:26] <aquarius> so we don't need to fetch them again
[15:26] <aquarius> that would be a good idea
[15:26] <aquarius> then curated components can have descriptions, too
[15:26] <nik90_> yeah
[15:26] <nik90_> we cache when the user installs those components?
[15:26] <aquarius> version numbers in directory paths: "It is possible to store different versions of a module in subdirectories of its own. For example, a version 2.1 of a module could be located under com/mycompany/mymodule.2/qmldir or com/mycompany/mymodule.2.1/qmldir. The engine will automatically load the module which matches best." http://doc.qt.io/qt-5/qtqml-modules-identifiedmodules.html
[15:26] <aquarius> at the moment we do not cache anything about when a component was installed
[15:27] <aquarius> this is why we need to talk about how that'll work and what ucs update should do :)
[15:27] <aquarius> because if you ucs update and get new versions of your components, you'll have to also poke your code to *use* the new versions.
[15:28] <nik90_> well since they are curated, we can assume that we will maintain backwards compatability similar to the sdk?
[15:28] <nik90_> or nvr mind that is too complicated...
[15:29] <nik90_> when a dev updates, he will receive the new and old version. His code will continue to work since it is using the old version. If he wants new stuff, he needs to use the new version after making changes to his code
[15:29] <aquarius> right
[15:29] <aquarius> I think we just put a version number in ubuntu_component_store.json
[15:29] <aquarius> and ucs install checks stuff out to that version number
[15:30] <aquarius> and then everything works
[15:30] <nik90_> does it override what the dev has? or appends the new files to it?
[15:31] <aquarius> if it's a new version, it'll be in a new folder, because components will now go in sil/ComponentName.1.0
[15:31] <Makalak> is anyone here to help
[15:31] <nik90_> aquarius: understood
[15:32] <nik90_> Makalak: not sure if the devs who can help with debugging adb and rooting are here
[15:33] <aquarius> big question I have: how do you remove a component from the community store without deleting the branch?
[15:33] <aquarius> I can't work out how to do that :(
[15:34] <Makalak> nik90_: out of 200 ppl no one :/
[15:35] <nik90_> aquarius: why not something like "ucs unregister componentname" and it simply removes the entry from the json file after parsing it?
[15:35] <nik90_> Makalak: actually a lot of ppl are logged in 24x7, but they are not necessarily online..besides it was just new year few days back...so may be still in vacation :)
[15:35] <aquarius> nik90_, because the ucs community server does not require authentication, so it can't stop me removing your components.
[15:35] <nik90_> oh crap yes
[15:36] <aquarius> this is why I can't owrk out how to do it ;)
[15:36] <nik90_> aquarius: how about using launchpad id as authentication?
[15:36] <aquarius> at the moment the best I can come up with is: delete/rename ubuntu_component_store.json in your branch, then ucs submit it again, and we'll see that it's dead and remove it.
[15:36] <aquarius> nik90_, I can't do that; you can't use launchpad oauth to prove to a third party server that you are a launchpad ID.
[15:37] <aquarius> you can prove it *to launchpad*, but not to anyone else.
[15:38] <aquarius> (currently adding version number requirements to everything)
[16:01] <aquarius> excellent. Community components now require version numbers in the metadata, and we use them when we ucs install. Victory.
[16:02] <aquarius> nik90_, what do you think of the idea of adding ubuntu_component_store.json files to the curated components?
[16:02] <aquarius> and I'll have ucs download and cache them
[16:02] <aquarius> (based on revno)
[16:03] <nik90_> aquarius: I am fine with adding it to the curated components as well
[16:04] <aquarius> ok, I'll add them
[16:04] <aquarius> you want me to MP them, or are you OK with me just committing to trunk?
[16:05] <nik90_> just commit to trunk
[16:05] <nik90_> although atm if i install a component, it will pull the json file as well
[16:06] <nik90_> did you mean adding it to your branch or the trunk?
[16:08] <aquarius> I thought I'd put them direct into trunk
[16:08] <aquarius> since trunk is what ucs looks at to get curated components :)
[16:09] <nik90_> ok
[16:20] <DanChapman> aquarius, i don't think it makes sense to be building the qmldir locally and creating a new directory for each version, instead why not get the component author to include one. I think something like this http://bazaar.launchpad.net/~dpniel/+junk/ucs-component/files would be better and it means there would only be one qmldir file to support multiple versions.
[16:22] <aquarius> DanChapman, because we need to include the ubuntu_component_store stuff in module, or it breaks
[16:23] <aquarius> DanChapman, and we know how to create that, and component authors shouldn't have to -- and if they do it wrong, their component is not usable
[16:33] <DanChapman> aquarius hmmm ok I understand it needs the ubuntu_component_store :-) so what should happen in the case that the author wishes to set other qmldir commands. For instance they may want to set the classname of a c++ plugin the component depends on. It needs to have a way that all these commands can be set somehow http://doc.qt.io/qt-5/qtqml-modules-qmldir.html (some food for thought)
[16:38] <DanChapman> aquarius: could it just be a case of an author could override ucs creating a qmldir by providing one in the source tree should they need the extra functionality? (and on their head be it, if it doesn't work)
[16:39] <aquarius> DanChapman, hm, that's interesting.
[16:39] <aquarius> perhaps if there's a qmldir file already in the folder, we add to it?
[16:40] <nik90_> DanChapman: its possible to add component dependencies in the qmldir file?
[16:41]  * aquarius winces
[16:41] <aquarius> no component dependencies
[16:41] <aquarius> not for version 1 anyway
[16:41] <aquarius> dependencies are a nightmare.
[16:41] <nik90_> aquarius: but I agree with DanChapman that the developer should be allowed to create the qmldir file themeselves since they might want to choose a different name
[16:42] <nik90_> for instance, I might have a file Triangle10.qml but in the qmldir I might want to rename it as 1.0 Triangle
[16:42] <aquarius> can you give me an example of when you want to choose a name that isn't your component name?
[16:43] <nik90_> the ubuntu sdk does this with the Page component...they have files named as Page10.qml, Page11.qml....but in qmldir it is renamed as Page
[16:43] <nik90_> which is what we all use
[16:43] <aquarius> I am pretty firmly of the opinion that in that situation you should just name your file Triangle.qml rather than playing silly tricks with the qmldir :)
[16:44] <aquarius> ucs (in my branch) now caches curated component metadata and displays it when searching, hooray
[16:44] <nik90_> the file name tricks are done to allow for multiple component versions
[16:44] <nik90_> ooh nice
[16:44] <aquarius> there's still slowness while it gets the current revno from LP, though. Can't avoid that :)
[16:44] <nik90_> true, that's up to lp servers
[16:44] <aquarius> ya, but if you want multiple component versions *of a ucs installable component* then you just publish a new version.
[16:45] <aquarius> the core SDK needs this sort of trickery so they can ship ten different versions of a thing in the same folder.
[16:45] <aquarius> we do not.,
[16:45] <aquarius> if you want a new version of a component, then submit a new version. Done. Our versions are parallel-installable (now) because the folder names get a version number in.
[16:46] <aquarius> $ ~/Programs/Others/ubuntu-component-store/community-components/script/ucs install RadialBottomEdge
[16:46] <aquarius> (installing RadialBottomEdge from curated repository)
[16:46] <aquarius> $ ls ubuntu_component_store/Curated/RadialBottomEdge.1.0/
[16:46] <aquarius> qmldir                       RadialBottomEdge.qml
[16:46] <aquarius> RadialAction.qml             ubuntu_component_store.json
[16:46] <aquarius> victory )
[16:46] <aquarius> :)
[16:46] <aquarius> nik90_, feel free to change the component descriptions in the metadata files
[16:46] <aquarius> I just took the first sentence or so off the web docs.
[16:47] <aquarius> also, I have added a documentation_url key to the metadata for the curated components
[16:47] <aquarius> we don't do anything with it yet
[16:47] <aquarius> but it strikes me that it might be useful :)
[16:47] <nik90_> yeah it will
[16:47] <nik90_> we can show in the search output command in the terminal
[16:47] <nik90_> this way the user can check the docs to see more about a component if they are interested after reading the 1 line description
[16:48] <nik90_> but I had this idea to do this after we do the transition first
[16:50] <aquarius> totally
[16:50] <aquarius> I just put it in because I was editing the files anyway :)
[16:51] <aquarius> DanChapman, so, what about we add to an existing qmldir file if there's one in there
[16:51] <aquarius> and add a stern warning to the docs saying: don't write your own unless you know what you're doing. :)
[16:53] <DanChapman> aquarius yeah I think that would make sense for now :-)
[16:55] <aquarius> DanChapman, are there rules about the order that a qmldir file goes in?
[16:58] <aquarius> DanChapman, also, do you know about cmake?
[17:00] <DanChapman> aquarius: i'm not sure if there are any rules but i've never come across any issues in the ordering.
[17:00] <DanChapman> aquarius: yeah i know a bit about cmake
[17:02] <aquarius> DanChapman, OK. When we install a component, we download it and put it in a particular folder in the project. We then need to poke the project to do two things: 1) make sure that folder is on the QML import path (ideally we do this by placing the folder in the corrrect place so it's *already* on the import path) and 2) tell the build system that that folder needs to be copied to the build output folder.
[17:02] <aquarius> I do not know how to do (2) with cmake
[17:02] <aquarius> with qmake, we edit /app/app.pro and add a QMAKE_POST_LINK line which does the copying.
[17:02] <aquarius> what's the best way to do this with cmake?
[17:03] <aquarius> I was thinking that a good way would be to add a CMakeLists.txt file *to the ubuntu_component_store folder* which copies itself, then it's all self-contained.
[17:03] <aquarius> is that doable?
[17:05] <DanChapman> aquarius: are we taking the assumption that the app uses the sdk template? that would work as long as it's included as a subdirectory in the app's cmake files somewhere
[17:07] <aquarius> DanChapman, I am happy to make that assumption, at least for version 1
[17:07] <aquarius> DanChapman, anybody who is good enough to set up their own build setup can just grab a component straight out of launchpad, at least for now :)
[17:08] <aquarius> or can ucs install it and then integrate it themselves
[17:09] <aquarius> so, what would we need to do? After ucs install gets a component from launchpad and puts it in /ubuntu_component_store, I can have it add /ubuntu_component_store/CMakeLists.txt -- what would need to be in that file? And is that enough, or do we also need to add /ubuntu_component_store to the top level CMakeLists.txt as well?
[17:15] <DanChapman> aquarius: you would need something like http://paste.ubuntu.com/9671987/ and then adding add_subdirectory(ubuntu_component_store) to a parent CMakeLists.txt file
[17:16] <aquarius> nice!
[17:16] <aquarius> let me give that a try.
[17:16] <aquarius> DanChapman, two questions
[17:16] <DanChapman> and if it's compiled add *.cpp to the GLOB_RECURSE part
[17:16] <aquarius> 1. that recurses into subdirs, right?
[17:16] <DanChapman> aquarius: yeah
[17:16] <aquarius> 2. why can't i just put * rather than naming file types?
[17:17] <aquarius> there are lots of potential files -- not just qml and js, but images, the qmldir files (!), etc
[17:17] <aquarius> listing them all seems like doom, and I am pretty confident that copying all the files is not a problem
[17:17] <DanChapman> aquarius: tbh i've never tried that 2 secs i'll try it
[17:18] <aquarius> we definitely need to copy qmldir files :-)
[17:19] <DanChapman> the copy_directory copies *everything* in that directory the GLOB_RECURSE just collects a list of files to make visible in QtC
[17:20] <aquarius> oh! cool :)
[17:20] <DanChapman> aquarius: for instance in dekko http://bazaar.launchpad.net/~dpniel/dekko/0.4/view/head:/CMakeLists.txt#L677 i use it to copy the whole qml dir
[17:31] <aquarius> ok, pushed a revision which adds to cmakelists for cmake-based projects when adding pure qml components, cheers DanChapman
[17:31] <aquarius> still need to handle adding binary components to each -- specifically, how to get them on the import path
[17:31] <aquarius> but we make progress, anyway :)
[18:59] <_1_andrewc> hi
[19:01] <_1_andrewc> hi
[19:01] <k1l_> hi
[19:03] <_1_andrewc> hi
[20:19] <ulrichard_> Are the ubuntu phones for sale yet?
[20:20] <nhaines> No.
[20:21] <popey> "Soon"
[21:02] <Kebabfish> ulrichard_: februari
[21:26] <ahayzen> Hey, does anyone else in their system settings have the 'wifi address' and 'bluetooth address' the wrong way around?
[21:27] <ahayzen> oh ignore me that would be bug 1399723