=== ablasche_ is now known as ablasche [09:53] Good morning all! Happy Monday, and happy Chinese New Year! 😃 [10:15] Hello there, I have a question about unity js scopes. Maybe it's a bug or simply a not yet implemented functionality: When creating a scope, I pass "perform_action" in "runtime_config". According to the docs this should be a callback for preview actions. For me this is not working. [10:25] marcustomlinson ^ ? [11:31] zbenjamin_, ping [12:29] balloons: is the jenkins build bot chroot busted again? (samba) https://code.launchpad.net/~popey/ubuntu-filemanager-app/fix-1543058/+merge/285327 [12:29] balloons: it builds fine locally on my shoddy chroot, but seems to have borked in jenkins chroot [14:10] !ping [14:10] pong! === zbenjamin_ is now known as zbenjamin [15:11] zbenjamin, ping [15:11] nik90: \o/ [15:12] zbenjamin, hey, how is it going? [15:12] nik90: all good, lots of work :D [15:12] I am having some trouble with chroots in a fresh 14.04 setup. Need some help with that [15:12] nik90: right, its not creatable right [15:12] appdevs ping (need help setting up qtcreator) [15:12] I have a new 14.04 setup, I added the sdk release ppa and installed ubuntu-sdk. I couldn't create a armhf chroot due to dependency errors. [15:12] So I created a amd64 chroot. But when I try to compile a project, it doesn't seem to run on my 14.04 desktop [15:12] I thought https://developer.ubuntu.com/en/blog/2015/11/19/here-comes-brand-new-ubuntu-sdk-ide-tools/ should make this process easier for LTS users. [15:13] I created a amd64 chroot which is creatable [15:13] but I cannot use it to build and run apps on my 14.04 [15:13] I get /var/lib/schroot/chroots/click-ubuntu-sdk-15.04-amd64/usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene: symbol lookup error: /var/lib/schroot/chroots/click-ubuntu-sdk-15.04-amd64/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0: undefined symbol: g_option_group_unref [15:14] nik90: well the new SDK ships a extra Qt with the ubuntu-sdk-dev package. But it is really only good for the basic QML modules + UITK. [15:14] zbenjamin, ah ... strange..installing ubuntu-sdk did not install ubuntu-sdk-dev [15:14] or may be that's intentional? [15:14] nik90: i think its suggested ... [15:15] zbenjamin, If I install ubuntu-sdk-dev will that resolve the symbol error I get? [15:15] nik90: you can try to run your app with the ubuntu desktop kit then, but you maybe will miss qml modules [15:15] nik90: how do you execute the app now? do you log into the chroot and execute it in there? [15:16] zbenjamin, I just created a default cmake template app and then used the ubuntu-sdk-amd64 kit to build and run it. [15:16] all using the gui (green triangle) [15:17] nik90: running against a chroot is what we are working on right now. We want to get completely rid of supporting to run on the host system libraries [15:17] nik90: its just broken and confusing to app devs [15:17] agree [15:17] nik90: for now you'd need to use a emulator if you want to use the amd64 chroot kit [15:18] zbenjamin, oh, I cannot use amd64 chroot kit against the desktop? [15:18] http://imgur.com/SLO2ciC [15:18] nik90: no, it would try to use the system libraries :/ [15:18] nik90: except you set LD_LIBRARY_PATH correctly [15:19] nik90: but thats probably more painful than anything else [15:20] nik90: you can create a chroot for armhf, add the -k switch (keep broken chroot) then ping me when its done [15:20] zbenjamin, I'm in a place where I have a very low internet cap. [15:21] chroots eat up so much bandwidth [15:21] * popey waves to nik90 [15:21] hi popey :) [15:21] want me to post you a usb stick full of chroots? :) [15:21] * nik90 waves frantically [15:21] popey, lol...nah I just need to wait until feb 18th (getting back to netherlands) [15:22] Oh! [15:22] popey: i think i got a workaround if you really want to create a chroot dynamically [15:22] zbenjamin: go on...? [15:23] popey: let me quicky verify [15:24] popey: ok, create the chroot with: "click chroot -a armhf -f ubuntu-sdk-15.04 create -k" <<< -k == keep broken chroot [15:25] thanks zbenjamin will try that [15:25] popey: after its done edit the file /var/lib/schroot/chroots/click-ubuntu-sdk-15.04-armhf/finish.sh and add the following packages to the apt-get: liboxideqt-qmlplugin:armhf libandroid-properties1:armhf libhybris:armhf libmedia-hub-client4:armhf liboxideqtquick0:armhf [15:25] popey: last step: log in the chroot with: schroot -u root -c source:click-ubuntu-sdk-15.04-armhf and run /finish.sh [15:26] ok. [15:26] * popey makes notes [15:27] popey: http://pastebin.ubuntu.com/14993738/ [15:28] ta [15:29] zbenjamin, installed ubuntu-sdk-dev..and I now see Ubuntu Desktop Kit :D [15:29] popey: just wait a sec, dbarth said that workaround has some issues :D [15:29] on building though, I get http://paste.ubuntu.com/14993751/ [15:29] nik90: cool , try to add it to your project and hit run, if you are lucky all modules you need are there :D [15:30] nik90: meh :D [15:30] :P [16:01] balloons: did you see my earlier ping about file manager? [16:08] popey, feel free to repeat it; I don't remember it, it might be in the scrollback [16:10] balloons: looks like the chroot is busted, I don't think repeating will fix it [16:11] ouch, let's fix it together then if so [16:18] balloons: i think it's the usual thing where it can't install samba due to the dependencies [16:18] balloons: so maybe it needs your magic script running against it ? (twice) 😃 [17:37] popey, I wonder if it broke because of the upgrades that run on the chroot [17:37] otherwise there's no reason it should have changed eh [17:37] almost certainly [17:37] i re-ran it and it failed the same way unsurprisingly [17:37] but if indeed that's the reason it broke, how can we fix it permnanently, heh [17:37] besides you know, fixing the package :-) [17:48] balloons: can you run your magic script to un-break the chroot for now? [17:48] I'm doing so indeed [17:48] balloons: medium term we could run that regularly (like, after updates) [17:48] just thinking aloud [17:48] Longer term, yeah, I completely agree, fix that package [17:48] yea, I'll just schedule it to run right after [17:48] (or the other option is not use debs at all) [17:48] and just yank the libs and put them somewhere - which is a horrid solution [17:49] snappy solves everything [17:49] (C) Ogra 2014-2016 [17:49] too lazy to dig out the unicode (c) [17:49] balloons: I'll dig out the debian bug on samba, and see if we can poke that with a stick [17:49] not necessarily. most devs use static depends [17:49] only updating when they need to [17:50] true [17:50] could patch samba, and put it in our ppa [17:50] which is what we do for libreoffice effectively [17:50] ahh, actually that's a good medium term solution [17:50] put it in the overlay ppa [17:51] nah, overlay ppa would surely need to be sane packagin [17:51] this needs to be a bit insane [17:52] sanity is the ine eye of the beholder :P [17:53] mmm [17:53] fyi, magic script is struggling.. I'm playing with it [17:55] actually this highlights an issue [17:55] that if there was a samba update, we'd not notice [17:55] (in the archive) [17:55] (not that there likely will be in vivid or the overlay) [17:55] but I do think we should move the to the community team ppa (or somewhere else sane) [17:56] well, sitting in vivid is a problem actually [17:57] it's past EOL and the archive will go away at some point [18:46] balloons: so I'll take a look at building samba in the community team ppa without the odd python parts that it doesn't seem to really need. [18:46] balloons: and if that works we can use that instead of the archive version for now [18:46] it should be as simple as repackaging, but changing the depends [18:46] heck, even moving the depends to recommended instead of required would save us [18:48] popey: fyi https://bugs.launchpad.net/oxide/+bug/1543215 [18:48] Launchpad bug 1543215 in oxide-qt (Ubuntu) "oxide breaks 15.04 chroot installs?" [Undecided,New] [18:49] balloons: ok, will do that [18:49] and test [18:49] zbenjamin: ta [19:01] hola, "That’s it, you can go to the store page, and upload your scope.".. where is this store page? [19:01] https://developer.ubuntu.com/en/scopes/tutorials/prepare-your-scope-for-publication/ [19:03] Is it this => https://apps.ubuntu.com/cat/ ? [19:05] elijah: https://myapps.developer.ubuntu.com/ is where you publish apps. I haven't published a scope, though. I don't know if it is the same place [19:05] mcphail: Thanks, I wonder if it is only accessible on phones right now? [19:06] elijah: don't think so. Seems to be working here [19:07] mcphail: I can access that link. But I can't search submitted scopes. [19:07] elijah: aah. That link is just for publishing [19:08] mcphail: yeah, do you know where I can find a store of the published apps, scopes. [19:08] https://uappexplorer.com/apps?type=scope [19:08] mcphail: thank you! [19:08] elijah: enjoy ;) [22:23] balloons: did you manage to fix the chroot? shall I re-run?