=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== chihchun_afk is now known as chihchun
[06:53] <zzarr> kalikiana, it doesn't say
[07:44] <zzarr> kalikiana, I get this error error: Unknown module(s) in QT: qml
[07:53] <dholbach> good morning
[07:54] <zzarr> good morning
[08:00] <zzarr> I have a problem with upgrading to a vivid click target to xenial, I have created a vivid click target, ran an update & upgrade
[08:01] <zzarr> then I changed vivid to xenial everywhere in /etc/apt/sources.list
[08:01] <zzarr> after that I ran an update and dist-upgrade
[08:02] <zzarr> but now I have some issues with conflicting dependencies
[09:17] <mcphail> zzarr: maybe xenial click targets aren't supported yet? For development, everyone is still on vivid+overlayPPA
[09:20] <mcphail> zzarr: you shouldn't be able to directly upgrade from vivid to xenial anyway, without going via wily. Ubuntu has only ever allowed skipping releases when going from LTS to LTS
[09:31] <zzarr> mcphail, I have precisely done a do-dist-upgrade -d twice
[09:31] <zzarr> mcphail, so vivid -> wily -> xenial
[09:32] <mcphail> zzarr: OK. I'd be surprised if xenial was in a working state, to be honest. What are you trying to achieve?
[09:33] <zzarr> I'm trying to compile an application using Qt 5.5.1 specific code
[09:33] <zzarr> should I use vivid+overlay instead?
[09:34] <mcphail> zzarr: no idea how you're going to handle that. Sorry
[09:35] <zzarr> mcphail, no problem, thanks in any way
[09:37] <zzarr> mcphail, I get this error now "error: Unknown module(s) in QT: qml" what package am I missing?
[09:37] <zzarr> I have installed qtdeclarative5-dev
[09:39] <mcphail> is this from a stock dev environment click chroot, or some awful hybrid with extra PPAs? Have never seen that error myself
[09:39] <zzarr> stock without PPA's
[09:40] <mcphail> zzarr: but you have the up to date SDK PPA etc?
[09:40] <zzarr> the host is running xenial
[09:40] <zzarr> but it's the click target that's missing something
[09:41] <mcphail> zzarr: I can't give any advice, then. Xenial isn't released, supported or expected to work
[09:42] <zzarr> I know it's not released but it's as stable as wily (not the stable branch thought)
[09:43] <mcphail> zzarr: no, it isn't
[09:44] <zzarr> mcphail, what I meant was I haven't ran in to any problem that didn't exist in wily
[09:45] <mcphail> zzarr: well, you've just described a problem which doesn't exist in wily. Xenial is for testing and experimentation at this stage. It is not expected to actually work
[09:45] <mcphail> zzarr: I've no idea id the SDK guys even have a proper xenial build yet
[09:45] <zzarr> true true, but I meant on the host
[09:46] <mcphail> zzarr: yes, but the host has the infrastructure for the click chroot builds. They're all cross-compiled by the host
[09:48] <zzarr> yes, but there is no official framework for 16.04 yet
[09:50] <zzarr> I'll try the vivid+overlay way now
[09:51] <mcphail> zzarr: If you want to build something, without a fight and a struggle, Wily (or Trusty) host with vivid+overlay chroot is the only game in town
[09:52] <zzarr> I still need a qmake for 5.5.1 which thanks to xenial I got
[09:53] <zzarr> I have tried to cross compile Qt 5.5.1 for armhf but it isn't easy
[09:54] <mcphail> if you do manage to get it compiled, what's the strategy to get it on the device?
[09:54] <zzarr> well it's a special device, so I have to make sure it's compatible
[09:55] <mcphail> aah - so this is a one-off deployment rather than something which is going up on the store?
[09:55] <zzarr> yes
[09:56] <zzarr> that's why I'm going this way
[09:56] <mcphail> zzarr: I wish you the best of luck ;)
[09:56] <zzarr> thank you, I'll need it :D
[10:24] <zzarr> I get the same error with vivid+overlay
=== _salem is now known as salem_
=== la_juyis` is now known as la_juyis
[13:19] <zzarr> hello again!
[13:21] <zzarr> I now realize that my kit (ubuntu-kit) do not search for libraries in the correct path some how
[13:27] <zzarr> the kit may be outdated, I'll make a new one
[13:34] <zzarr> I need help, Ubuntu SDK does not find any devices or emulators
=== chihchun is now known as chihchun_afk
=== Wellark_ is now known as Wellark
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== salem_ is now known as _salem
=== _salem is now known as salem_
[18:28] <ilhami> hey :)
[19:04] <zatreanu> Hello.  I am right now focusing on adding some shortcut features to okular, but for some reason i cant get it working.
[19:05] <zatreanu> Ive modified the pageview.cpp file in the UI folder, adding functionalities to other keys.
[19:05] <zatreanu> But even though i'm building it, after running /shell/okultar, the keys are not doing anything.
[19:05] <zatreanu> Is there anything "obviously wrong" that im doing :) ?
[19:05] <zatreanu> Thanks in advance.
[19:36] <tgm4883> Is this a good place to ask questions about packaging conf file for mysql-server?
[19:37] <pmcgowan> tgm4883, try ubuntu-devel
[19:37] <tgm4883> pmcgowan: will do, thanks
[19:52] <momken> hello
[19:53] <momken> I am learning the packaging method in ubuntu to make some ppa packages for myself
[19:53] <momken> I am reading this article: http://packaging.ubuntu.com/html/udd-intro.html
[19:54] <momken> but I can't get an Ubuntu branch with "bzr branch ubuntu:kdetoys"
[19:54] <momken> How could I get a sample bzr branch for an ubuntu package?
[20:29] <mhall119> bzoltan: are we still going to get image-based kits/chroots for the SDK?
[20:29] <mhall119> momken: you might try asking in #ubuntu-devel, there are more people who are familiar with the UDD process there
[22:09] <dobey> momken, mhall119: you can't use UDD any more. it's really never worked that well. but yes, #ubuntu-devel is the right place to ask about such packaging issues
[23:38] <mhall119> dobey: UDD = Ubuntu Distributed Development, right?