[07:02] <soee> a lot of fixes after latest updates
[07:03] <soee> all icons in homerun kicker, no need to move mouse when icon on taskbar clicked to show app, all icons in system settings :) weee :D
[07:03] <soee> now if only locales would work 
[07:03] <soee> and activities are finished :)
[07:50] <apachelogger> Riddell: plasma-workspace depends on 
[07:50] <apachelogger>          qtquick1-5-dev,
[07:50] <apachelogger>          qttools5-dev-tools,
[07:50] <apachelogger> I'd like to know why please
[07:50] <apachelogger> because that is somewhat excessively wrong
[07:53] <apachelogger> in fact what's up with all the runtime deps
[07:53] <apachelogger> some of them have no history and make me go :O
[07:53] <apachelogger>          oxygen-icon-theme,
[07:53] <apachelogger> ^ that should be a dependency/recommends of breeze-icon-theme
[07:53] <apachelogger>          libkf5service-bin,
[07:53] <apachelogger> that just shouldn't be explicitly mentioned at all
[07:54] <apachelogger> libkf5declarative5 neither should this
[07:54] <apachelogger> udisks2 also a big fat why (considering solid and what have you)
[07:54] <apachelogger> plasma-framework more why
[07:55] <yofel> whatever has startkde in it should at least recommend udisks2 as it's used there
[07:56] <yofel> ... if the disk detection patch got ported
[07:57] <ovidiu-florin> shadeslayer, ScottK thank you
[07:57] <apachelogger> ah that would solve that mystery, probably should be changed to solid eitherway that patch
[07:57] <ovidiu-florin> shadeslayer: shall we meet at the BSP ?
[07:57] <ovidiu-florin> in Munich?
[07:57] <apachelogger> ah yes, welcome ovidiu-florin
[08:00] <ovidiu-florin> apachelogger: thank you
[08:00] <ovidiu-florin> shadeslayer: but you have to promise to drink more than one glass
[08:01] <yofel> he have to organize the drinking better this time :P
[08:02] <apachelogger> everyone does I say
[08:03] <apachelogger> shadeslayer: the ubiquity from ppa should land in archive
[08:03] <Riddell> apachelogger: qtquick1-5-dev qttools5-dev-tools dunno, remove them and see what breaks
[08:03] <Riddell> oxygen-icon-theme should be dep of breeze-icon-theme and libkf5kicontheme5 I think
[08:04] <apachelogger> icontheme5 would actually be wrong right now ;)
[08:04] <Riddell> if you remove libkf5service-bin make sure libkf5service5 symbols file adds a dependency onto it
[08:04] <apachelogger> https://bugs.kde.org/show_bug.cgi?id=336739
[08:04] <Riddell> apachelogger: why?  it falls back to oxygen
[08:04] <apachelogger> kicontheme does not
[08:04] <Riddell> that bug is wrong
[08:04] <apachelogger> oxygen does the fallback
[08:04] <Riddell> breeze is nowhere near complete enough for kicontheme
[08:05] <apachelogger> that's why it has a fallback
[08:05] <apachelogger> right now unless you manually configure things or have kde4breeze run you get the oxygen icon set
[08:05] <apachelogger> which is why rohan had problems with the icons in systemsettings
[08:06] <apachelogger> they were only present in breeze but due to a bug in kde4breeze the icon set wasn't explicitly flipped to breeze, so the icons simply were unresolvable
[08:06] <apachelogger> anywho
[08:07] <apachelogger> dep chain should look like this I think: p-w -> p-d -> breeze -> breeze-icon-theme -> oxygen-icon-theme
[08:07] <Riddell> I don't really get why frameworkintegration is needed, but it is
[08:07] <apachelogger> it provides the qt platform plugin
[08:08] <apachelogger> without it qicon::fromtheme cannot resolve from whatever icon set is configured in default
[08:08] <apachelogger> equally I think qfiledialogs will not use kio's filedialog gui etc.
[08:08] <apachelogger> also I think the widget style will not follow kde settings
[08:08] <Riddell> yep
[08:08] <apachelogger> i.e. all the things will not integrated with frameworks ^^
[08:09] <Riddell> wish someone had told me about it sooner
[08:13] <apachelogger> dependency resolution by crowd sourcing :P
[08:24] <soee> guys does the progress bar (in systray) works for you when copying files  ?
[08:24] <soee> *plasma5
[08:26] <Riddell> yep
[08:27] <apachelogger> didn't work terribly well yesterday, might have been my broken plasma though
[08:33] <soee> :/
[08:40] <apachelogger> this sort stuff in debian/control is very fing annoying
[08:40] <apachelogger> open file, get to hit pagedown 5 times to see useful stuff...
[08:41] <apachelogger> http://paste.ubuntu.com/7834883/ *shrug*
[08:42] <apachelogger> also it causes commits like http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging-next/plasma-desktop/revision/17 obstructing bzr annotate.....
[08:43] <apachelogger> Riddell: why does plasma-desktop depend kde-style-oxygen-qt5,
[08:48] <Riddell> apachelogger: so that stuff has a nice widget theme?
[08:50] <apachelogger> ah, no qtcurve
[08:50] <apachelogger> should be recommends eitherway IMO :P
[08:50] <apachelogger> Riddell: why does plasma-desktop depend on gdb?
[08:59] <Riddell> apachelogger: hmm, does it
[08:59] <Riddell> apachelogger: it used to depend on gdb-minimal which is needed by drkonqi
[08:59] <Riddell> that clashes with gdb so it should now depend on gdb-minimal | gdb
[09:00] <apachelogger> Riddell: drkonqi lives in workspace
[09:00] <Riddell> that seems silly
[09:00] <Riddell> apachelogger: will you fix that?
[09:00] <apachelogger> yeah
[09:01] <apachelogger> also about the sillyness... the separation between desktop and workspace I do not get
[09:02] <apachelogger> Riddell: also, do we want all other workspace packages as dependency or recommends
[09:03] <Riddell> well that's upstream, so you can have plasma mediacentre installed without desktop
[09:03] <Riddell> apachelogger: plasma packages are mostly depends in the seeds, what are you thinking of?
[09:04] <apachelogger> Riddell: that doesn't help the actual packages having crap relationship
[09:04] <apachelogger> if I install plasma-desktop I should get a plasma-desktop
[09:04] <apachelogger> not a half broken thing of madness
[09:05] <apachelogger> so I was thinking recommends khotkeys, kinfocenter, kmenuedit, ksysguard.... and depends only for kio-extras, kde-cli-tools, breeze, plasma-workspace (which is sort of the core you want for a somewhat working desktop)
[09:05] <apachelogger> that way one could still make a seed conflict a specific package if one of the apps is not desired on the iso
[09:14] <Riddell> apachelogger: ok if you think so
[09:15] <apachelogger> Package: plasma-widget-milou-kf5
[09:15] <apachelogger> why the suffix?
[09:17] <Riddell> apachelogger: a mistake, feel free to fix
[09:33] <apachelogger> so much work
[09:33] <apachelogger> Riddell: I am actually wondering about simply renaming it to milou
[09:33] <apachelogger> because it contains a lib, the widget and a qml module
[09:34] <apachelogger> you know, with this pile of different deps for different reasons I'd totally appreciate if we outsourced everything into substvars :S
[09:35] <Riddell> apachelogger: go for it
[09:35] <apachelogger> give them meaningful names and such
[09:35] <apachelogger> Riddell: the renaming or the substvaring? :P
[09:35] <Riddell> renaming to milou
[09:35] <Riddell> I don't get what you're thinking with substvars
[09:36] <apachelogger> I'll show you in a bit
[09:36] <apachelogger> once I find the documentation for it again ^^
[09:40] <apachelogger> Riddell: http://paste.ubuntu.com/7835072/
[09:40] <apachelogger> note line 158
[09:40] <apachelogger> oh, actually plasma-framework belongs there as well, incidentially that's why a bit of clarity would help :P
[09:43] <Riddell> apachelogger: a magic shlibs for qml files would be great, but not a very easy task
[10:06] <apachelogger> Riddell: IMHO qml modules should create custom entries in the control listing their actuall addressing names i.e. milou would have 'XB-QMLModule: org.kde.milou, org.kde.kittens'
[10:06] <apachelogger> that doesn't cover things perfectly (since an app can bend the import dirs) but in general this would work well
[10:07] <Riddell> apachelogger: why not just an shqmllibs that reads qmldir files?
[10:07] <apachelogger> also possible I guess
[10:08] <apachelogger> Riddell: having it as a control entry allows ondemand installation of deps though
[10:09] <apachelogger> e.g. I install a plasmoid via plasma itself and that module wants QtQuickMultimedia which is not yet installed, plasma/qt could catch the failed module lookup and provided an installer similar to what we do with gstreamer codecs
[10:10] <apachelogger> but for that you need the metadata on what imports are provided by a package
[10:11] <Riddell> I think that's overengineering
[10:11] <Riddell> just an shlibs equivalent so the depends are set right it all anyone needs
[10:12] <apachelogger> Riddell: they are *exactly* the same thing
[10:12] <apachelogger> except my proposal would do it on the module package while yours would do it on every package trying to use a module
[10:12] <Riddell> apachelogger: you're talking about runtime installing, I'm talking about package build time surely?
[10:12] <apachelogger> they are also exactly the same, except that your solution is impossible to use runtime :P
[10:12] <Riddell> "just" it's obviously not very easy especially if you're snobby about python what will you say to coding in perl :)
[10:13] <apachelogger> which is why I argue that defining them as control entries is the way to go
[10:13] <Riddell> good, I don't want popups all the time saying "now you need to install this, go and fetch someone with the root password"
[10:13] <apachelogger> Riddell: if you install a plasmoid via plasma and a dep is not there then that is the desired scenario
[10:14] <apachelogger> because the status quo is "yo, we missing org.kde.yolo.kittens.meow, can't do nothing"
[10:14] <Riddell> yes
[10:15] <Riddell> but if you install it via muon or apt you expect it to work without installing more stuff
[10:15] <apachelogger> yes
[10:15] <apachelogger> which is why my suggestion is superior :P
[10:15] <apachelogger> you can use it on a package level and you can use it at runtime for dep resolution inside plasma itself
[10:16] <apachelogger> a simple shlibs-like thing cannot be used at runtime because it requires the package to be already installed (which is the other crux with that btw... you do not actually need the qml modules at build time, so you'd have to install them as bdeps just to be able to resolve their import names)
[10:28] <apachelogger> actually that is something for ubuntu phone as well
[10:28] <apachelogger> xnox: do you any automated qml module dependency generation or do you leave that up to app developers to figure out?
[10:29] <apachelogger> Riddell: why does milou bdep on everything ever?
[10:30] <xnox> apachelogger: app developers -> for clicks they depend on framework which guarantees the deps.
[10:30] <xnox> apachelogger: for debs, i don't think there is anything that auto-generates ${qml:Depends}
[10:31] <apachelogger> k, less useful for clicks then
[10:31] <Riddell> apachelogger: probably it was packaged because I set all the frameworks -dev to dep on what they require
[10:31] <ovidiu-florin> apachelogger, Riddell, I'd like your aproval for something
[10:31] <xnox> apachelogger: i guess creating a debhelper addon for that, would be useful.
[10:31] <apachelogger> ovidiu-florin: approved
[10:31] <ovidiu-florin> :D
[10:31] <ovidiu-florin> I'd like to make a Kubuntu Board related to Promotion
[10:31] <ovidiu-florin> and keep the promotion and website stuff over there
[10:32] <ovidiu-florin> I want to add several cards
[10:32] <Riddell> ovidiu-florin: what sort of board? trello?
[10:32] <ovidiu-florin> and asign some of them to my web developer friend
[10:32] <ovidiu-florin> yes, trello
[10:32] <apachelogger> ovidiu-florin: approved
[10:33] <ovidiu-florin> do I have the rights to make it?
[10:33] <apachelogger> every organization member can make boards
[10:33] <ovidiu-florin> done
[10:33] <apachelogger> https://community.kde.org/Kubuntu/Trello101
[10:33] <ovidiu-florin> I've made it
[10:33] <apachelogger> oh, wrong url
[10:33] <apachelogger> https://community.kde.org/Kubuntu/Trello
[10:34] <apachelogger> must be visible and allow org member joining and have a couple of admins
[10:37] <apachelogger> plasma-framework-dev is incredibly inconsistent with the other package names -.-
[10:37] <ovidiu-florin> can jose be an admin?
[10:38] <ovidiu-florin> https://trello.com/b/3Fo1KXoN/kubuntu-promotion
[10:42] <BluesKaj> 'Morning folks
[10:44] <apachelogger> ovidiu-florin: everyone can be an admin for all I care ;)
[10:45] <apachelogger> the point of having more than one admin is that have no organization admins that can control all boards, so to ensure that someone can admin the board in case the creater is unavailable more than one person needs to be admin :)
[10:48] <ovidiu-florin> apachelogger: want to join?
[10:48] <apachelogger> ovidiu-florin: the people listed on the trello wiki page you can basically add everywhere and make admin
[10:49] <apachelogger> all the usual suspects
[10:51] <apachelogger> yofel: shadeslayer: Riddell: objections to a next-staging ppa?
[10:51] <apachelogger> or next-proposed for all I care ;)
[10:52] <yofel> I never got my other staging ppa's :'(
[10:52] <yofel> FWIW, approved
[10:52] <apachelogger> yofel: never made them? :P
[10:52] <Riddell> apachelogger: mm yeah
[10:53] <ovidiu-florin> thank you
[10:53] <yofel> apachelogger: back then I had no permissions, Riddell always forgot and in the end I did too
[10:53]  * Riddell begs forgiveness for forgetfulness
[10:53] <yofel> approved ;P
[11:14] <apachelogger> Riddell, shadeslayer: is kf5 uploading to archive not done yet?
[11:15] <Riddell> apachelogger: it's all done but then a rejected a bunch which need re-uploaded
[11:15] <Riddell> checked and re-uploaded
[11:15] <Riddell> I fixed all the tier 3 ones in bzr
[11:15] <Riddell> not sure if there's any tier 1 still to be reuploaded, I don't think so
[11:15] <apachelogger> ah, ok, that explains it then
[11:15]  * Riddell working on kdesudo
[11:15] <apachelogger> I only noticed some kf5s not being greyed out in the ppa ;)
[11:16] <Riddell> there's your todo list :)
[11:16] <apachelogger> still fixing that workspace mess :P
[11:21] <apachelogger> Riddell: how do we generate the meta package btw? from a seed or manually?
[11:21] <Riddell> seed
[11:21] <Riddell> bzr+ssh://bazaar.launchpad.net/~kubuntu-dev/ubuntu-seeds/kubuntu-plasma5.utopic/
[11:21] <Riddell> but I'm wondering if it was a mistake to rename it to kubuntu-plasma5
[11:21] <apachelogger> thx
[11:22] <Riddell> since all the other packages don't co-install unless we expect to put them in the ubuntu archive
[11:22]  * apachelogger notes that we should ditch CK from kde4 somehow
[11:22] <Riddell> CK?
[11:22] <apachelogger> consolekit
[11:22] <Riddell> consolekit?
[11:22] <Riddell> that thing is still around?
[11:22] <apachelogger> was pulled in for me anyway
[11:22] <apachelogger> I did some changes to kdm removing ck support
[11:22] <Riddell> I thought "kit" names had gone out of fashion along with qtmultimediakit
[11:22] <apachelogger> but I think there was something in libs also using CK
[11:23] <apachelogger> Riddell: *cough* packagekit *cough*
[11:23] <Riddell> kshutdown?
[11:23] <apachelogger> kshutdownkit, yes, what? :P
[11:23] <Riddell> something aleix is currently moaning about
[11:23] <apachelogger> I did not look into it actually
[11:23] <Riddell> that rdepends on consolekit whatever it is
[11:23] <apachelogger> woudn't kshutdown be in workspace
[11:24] <Riddell> oh user-manager ?
[11:24] <Riddell> dunno why but it depends on it
[11:24] <apachelogger> user-manager uses CK Oo
[11:24] <apachelogger> I wouldn't even know why
[11:24] <Riddell> would be worth checking if that's sane
[11:25] <apachelogger> all the stuff user-manager needs should come from accountsservice
[11:26] <Riddell> I would think so
[11:26]  * apachelogger can't actually find what uses ck_ in kdelibs
[11:26] <apachelogger> :@
[11:28] <apachelogger> libpolkit-qt-1-1
[11:28] <apachelogger> which in turn is deped upon by kauth
[11:28] <apachelogger> ubottu: find Qt5Qml
[11:29] <apachelogger> bot doesn't like me :'<
[11:32] <shadeslayer> apachelogger: already did
[11:32] <shadeslayer> or well, code merged
[11:32] <shadeslayer> apachelogger: https://code.launchpad.net/~rohangarg/ubiquity/plasma5/+merge/227341
[11:33] <shadeslayer> I is way ahead of you my friend :p
[11:34] <xnox> shadeslayer: stuck in proposed.
[11:34] <shadeslayer> doh!
[11:34] <shadeslayer> or is it d'oh!
[11:34] <shadeslayer> I forget
[11:37] <apachelogger> it's phpewwwpheew, that's the sound a jellyfish makes don't you know
[11:37] <shadeslayer> didn't realize jellyfish made noise
[11:37] <shadeslayer> ah
[11:38] <shadeslayer> maybe it's the sound they make when you squish them with your feet
[11:38] <apachelogger> :O
[11:38]  * Riddell lunches
[11:38] <apachelogger> I be hungry too
[11:46] <yofel> so, no jellyfish anymore
[11:46] <Quintasan> hurr durr
[11:46] <apachelogger> wut
[11:46] <yofel> hi Quintasan
[11:46] <apachelogger> Oo
[11:47] <Quintasan> where do I get  hold of any kmail people
[11:47] <yofel> #kontact
[11:47] <yofel> or #akonadi
[11:47] <Quintasan> >Could not create collection trash resourceId: 3
[11:47] <Quintasan> And just closes
[11:47] <apachelogger> shadeslayer: sddm-theme-breeze why is that depping sddm?
[11:48] <yofel> akonadiconsole should tell you what that is
[11:51] <apachelogger> milou rename in staging shortly
[11:53] <apachelogger> breeze-icon-theme with dep on oxygen-icon-theme also in staging shortly
[12:24] <apachelogger> yofel, shadeslayer, Riddell: http://paste.ubuntu.com/7835806/ plz revu
[12:25] <apachelogger> random note of the day: in plasma-workspace kio-extras will actually elevated to depends because the preview capabilities of the wallpaper dialog depend on it
[12:26] <yofel> that's very much... -extra
[12:26] <apachelogger> personally I don't quite get why the thumbnailers are in extra when the wallpaper previews depend on it
[12:27] <yofel> it sounds extra
[12:28] <apachelogger> oh one thing that is on my todo still
[12:29] <apachelogger> yofel, shadeslayer, Riddell: shouldn't we depend on >= 5.0
[12:29] <yofel> looks sane to me...
[12:29] <apachelogger> given some packages also existed in 4.x we might want to make sure we get the 5.x version
[12:35]  * yofel can't make up his mind
[12:47] <apachelogger> yofel, shadeslayer, Riddell: http://paste.ubuntu.com/7835943/ workspace also needs review
[13:07] <shadeslayer> apachelogger: one would imagine that just installing the theme is useless
[13:07] <apachelogger> shadeslayer: so is installing a -data package, we don't reverse dep there either though ...
[13:08] <shadeslayer> should be fixed then?
[13:08] <apachelogger> which one? the data not having a dep cicle of death or sddm technically having one? :P
[13:09] <apachelogger> shadeslayer: how do we select the sddm theme btw?
[13:09] <apachelogger> select/configure
[13:09] <shadeslayer> apachelogger: kcm, which doesn't work at the moment
[13:09] <shadeslayer> d_ed is on that
[13:09] <apachelogger> by default I mean
[13:09] <apachelogger> I install sddm... how do I get a theme?
[13:11] <shadeslayer> I don't follow,. by default you get maui
[13:11] <shadeslayer> which is a dep of sddm
[13:11] <shadeslayer> unless you do apt-get install sddm sddm-theme-foo
[13:11] <shadeslayer> in which case sddm will not work
[13:11] <apachelogger> Recommends: sddm-theme | sddm-theme-maui
[13:11] <apachelogger> shadeslayer: is that the latest? 
[13:11] <shadeslayer> yes
[13:11] <apachelogger> still not correct then
[13:12] <shadeslayer> why not?
[13:12] <apachelogger> it needs Depends: sddm-theme-maui
[13:12] <shadeslayer> no it does not,we can not install maui and just specify a config
[13:12] <apachelogger> sddm is quite simply broken if maui is not present, so it's not a recommends and it's also not interchangable with sddm-theme right now
[13:12] <shadeslayer> manually by hand
[13:12] <apachelogger> shadeslayer: yeah, which is what I said
[13:12] <apachelogger> the package relationship is broken
[13:13] <shadeslayer> and if you don't sepecify a theme, maui will be installed ootb
[13:13] <shadeslayer> so it will all work
[13:13] <shadeslayer> I disagree
[13:13] <apachelogger> there's no disagreement to be had
[13:13] <apachelogger> sudo apt-get install sddm --no-install-recommends && sudo start sddm -> black screen
[13:13] <apachelogger> that is broken by any definition of the word
[13:13] <shadeslayer> is not installing recommends even supported?
[13:14] <apachelogger> yes
[13:14] <shadeslayer> Because last I remember, mint does it, and Ubuntu said that they don't supported
[13:14] <yofel> it's the same reason why we *depend* on akonadi-backend-mysql for akonadi-server
[13:14] <shadeslayer> *support it
[13:14] <apachelogger> because the policy says <<package mustn't be broken without recommends>>
[13:14] <yofel> even if it's replacable by hand
[13:15] <shadeslayer> apachelogger: so sddm isn't broken
[13:15] <apachelogger> shadeslayer: sudo apt-get install sddm --no-install-recommends && sudo start sddm -> black screen
[13:15] <shadeslayer> you get a black screen because you don't have a theme
[13:15] <apachelogger> duh
[13:15] <yofel> that's pretty broken to me...
[13:15] <shadeslayer> it's not like it crashes
[13:15] <apachelogger> let me fix that for you
[13:15] <apachelogger> sudo apt-get install sddm-theme-breeze
[13:15] <apachelogger> sudo apt-get install sddm
[13:15] <apachelogger> sudo start sddm
[13:15] <apachelogger> black screen
[13:15] <apachelogger> I have a theme and a black screen now
[13:15] <shadeslayer> and that's a sddm bug
[13:16] <apachelogger> no
[13:16] <apachelogger> that's the packaging being wrong
[13:16] <shadeslayer> because SDDM can't be arsed to check for themes other than maui
[13:16] <apachelogger> because I *must* have maui for sddm to work
[13:16] <shadeslayer> no
[13:16] <shadeslayer> I can not have maui and have the right config, and it will work
[13:17] <yofel> you can also have akonadi with sqlite and the right config
[13:17] <shadeslayer> its a bug in the code, and not a packaging issue
[13:17] <apachelogger> yep
[13:17] <apachelogger> I can also install akonadi
[13:17] <apachelogger> and then install akonadi-sqlite
[13:17] <apachelogger> and then configure akonadi to use akonadi-sqlite
[13:17] <apachelogger> so clearly akonadi shouldn't pull in mysql
[13:18] <shadeslayer> so why does it then? why can't akonadi be fixed so that it uses a installed backend
[13:18] <yofel> shadeslayer: do you have a real hard ETA when the theme lookup issue will be fixed? As in: version or date
[13:18] <yofel> not "soon"
[13:18] <apachelogger> it doesn't really matter what the ETA is
[13:18] <apachelogger> right now the package is broken
[13:18] <shadeslayer> yofel: nope, I haven't checked with upstream about this, though I have to
[13:18] <apachelogger> shadeslayer: just because you say it is a bug doesn't make it a bug
[13:19] <shadeslayer> k I'm done, feel free to do what you think is right, I still don't think it's right
[13:19] <yofel> shadeslayer: FWIW, sure akonadi can be fixed, please go ahead and do it.
[13:19] <yofel> Nobody's done it for years though
[13:19] <apachelogger> e.g. here is an argument where the behavior of akonadi is legit: if sqlite doesn't load or the database gets corrupted (which can happen) we need a solid fallback, therefore mysql must always be available, although it will not be loaded unless absolutely necessary
[13:20] <apachelogger> either way
[13:20]  * yofel doesn't particulary care while sddm is in next, but if it lands in the archive the packaging has to match reality
[13:20] <apachelogger> as I said there is no discussion to be had
[13:20] <apachelogger> if I install sddm without recommends it is broken, that's a bug
[13:22] <apachelogger> shadeslayer: sddm has no bzr branch?
[13:26] <apachelogger> shadeslayer: nevermind
[13:26]  * apachelogger too stupid to use own tools
[13:39] <apachelogger> bzr-buildpackage-ppa now restores orign on sigint :S
[13:49] <apachelogger> breeze milou and plasma-framework moving from stage to next
[13:50] <Riddell> yay
[13:55] <Riddell> ovidiu-florin: my phone says I'm to welcome you to twitter
[13:55] <ovidiu-florin> Don't
[13:55] <ovidiu-florin> I'm not enjoing it
[13:55] <ovidiu-florin> It's for a contest
[14:14] <shadeslayer> Riddell: all uploaded
[14:22] <Riddell> shadeslayer: kf5?
[14:22] <Riddell> ovidiu-florin: if you find a use for it, let me know
[14:23] <ovidiu-florin> ok
[14:24] <apachelogger> sddm moving from stage to next
[14:31] <Riddell> yay
[14:31] <apachelogger> Riddell: still waiting on feedback for workspace, desktop and version requirements from earlier btw
[14:32] <Riddell> apachelogger: what what?
[14:32] <Riddell> I missed that, can you repeat?
[14:32] <apachelogger> [14:24] <apachelogger> yofel, shadeslayer, Riddell: http://paste.ubuntu.com/7835806/ plz revu
[14:32] <apachelogger> [14:29] <apachelogger> yofel, shadeslayer, Riddell: shouldn't we depend on >= 5.0
[14:32] <apachelogger> [14:47] <apachelogger> yofel, shadeslayer, Riddell: http://paste.ubuntu.com/7835943/ workspace also needs review
[14:33] <apachelogger> This would not have happened with Konversation.
[14:33] <yofel> 1) ack'd (with the bit of 5 knowledge I have), 2) can't make up my mind, 3) no time, laterz
[14:34] <Riddell> didn't I rename qtdeclarative5-kf5declarative ?
[14:35] <apachelogger> I dunno
[14:35] <kubotu> feed branches-next had 22 updates, showing the latest 6
[14:35] <apachelogger> quite frankly this package obeying the qml-module thing is a bit silly anyway
[14:35] <apachelogger> as it contains multiple different modules
[14:35] <Riddell> apachelogger: yes I did, that should be fixed
[14:37] <Riddell> apachelogger: plasma-desktop having versioned depends seems sensible
[14:38] <Riddell> apachelogger: workspace why plasma-widget-milou-kf5 and milou?
[14:38] <Riddell> may want to add your depends changes to changelog
[14:38] <Riddell> otherwise all good
[14:39] <apachelogger> oh
[14:39] <apachelogger> wut
[14:40] <apachelogger> god I hate bzr
[14:40] <apachelogger> so very very very very very much
[14:40] <yofel> bzr++
[14:40]  * yofel ducks
[14:40] <apachelogger> http://paste.ubuntu.com/7836508/
[14:40] <apachelogger> that's the correct one
[14:40] <apachelogger> Riddell, shadeslayer, yofel ^
[14:42] <Riddell> apachelogger: and you're doing the milou package rename too?
[14:43] <apachelogger> already done
[14:43] <apachelogger> already went through staging in fact
[14:43] <Riddell> apachelogger: then lovely
[14:44] <soee> uhm i see this packages are not required anymore: kde-style-qtcurve4 kde-style-qtcurve5 sddm-theme-maldives
[14:44] <soee> and qtcurve is  kept  back 
[14:45] <soee> also sddm-theme-maldives is not required but qill be installed :)
[14:46] <apachelogger> The following extra packages will be installed:
[14:46] <apachelogger>   sddm-theme-maui
[14:46] <apachelogger> The following NEW packages will be installed:
[14:46] <apachelogger>   sddm sddm-theme-maui
[14:47] <apachelogger> apt disagrees
[14:47] <soee> dpkg: error processing archive /var/cache/apt/archives/kde-style-qtcurve4_1.8.18+git20140721-0ubuntu1~ubuntu14.10~ppa1_amd64.deb (--unpack):
[14:48] <apachelogger> that's not really the error
[14:48] <soee> yeah
[14:49] <soee> trying to overwrite "/usr/lib/kde4/kstyle_qtcurve_config.so", which exists also in kde-style-qtcurve 1.8.14-3build1
[14:49] <apachelogger> shadeslayer: ^
[14:49] <apachelogger> shadeslayer: why the package rename btw?
[14:49] <apachelogger> should simply be higher version of kde-style-qtcurve IMO
[14:49] <soee> anyway there are qtcurce, kde-style-qtcurve4 kde-style-qtcurve5 ?
[14:50] <soee> *qtcurve
[14:50] <apachelogger> sounds about right
[14:51] <lordievader> Good afternoon.
[14:51] <soee> hi lordievader
[14:52] <lordievader> Hey soee, how are you doing?
[14:53] <soee> lordievader: great, you ?
[14:54] <lordievader> Meh, could be better.
[14:54] <soee> ;]
[14:54] <soee> brb, reboot
[14:57] <apachelogger> any neon5 users around?
[14:59] <soee> hmm http://wstaw.org/m/2014/07/22/session_error.png
[14:59] <apachelogger> eheheh
[14:59] <apachelogger> soee: paste  ... ps aux 
[14:59] <apachelogger> don't close the window
[15:00] <soee> apachelogger: http://paste.ubuntu.com/7836590/
[15:00] <apachelogger> mhh
[15:00] <apachelogger> it could be everything xD
[15:00] <apachelogger> hm
[15:01] <apachelogger> hmm
[15:01] <shadeslayer> apachelogger: FWIW I didn't make that package
[15:01] <soee> :P
[15:01] <apachelogger> soee: let me check for a way to find out what it is 
[15:02] <soee> apachelogger: maybe owncloud client that does not work with plasma5 systray ? but this error does nto show on every boot but sometimes
[15:02] <apachelogger> tricky tricky
[15:03] <apachelogger> soee: right click window decoration -> more actions -> special application settings
[15:03] <apachelogger> *applications*, not window
[15:03] <apachelogger> then go to first tab, what name does it mention there?
[15:03] <apachelogger> should be something like description "Application settings for konversation"
[15:06] <soee> shadeslayer: in the description filed ?
[15:06] <apachelogger> yep
[15:06] <soee> Ustawienia programu dla konversation == Application settings for konversation
[15:06] <apachelogger> soee:  if no name shows up ... do a ps aux paste again ... then use ctrl-alt-esc a red death head shoudl appear -> click on the window -> then do another ps aux paste
[15:06] <apachelogger> soee: ah, I meant on the window with the error ;)
[15:06] <soee> apachelogger: thers is name "Application settings for konversation"
[15:07] <soee> ahah :D
[15:07] <soee> apachelogger: got it
[15:07] <soee> "Application settings for spotify"
[15:07] <soee> :)
[15:08] <soee> ok thank you, now i know its spotify fault
[15:08] <apachelogger> soee: well, I am not terribly sure how to handle it with spotify
[15:09] <apachelogger> soee: best report a bug against ksmserver on bugs.kde.org
[15:09] <soee> spotify client isnt any stable 
[15:09] <apachelogger> but I think the answer there will be to report against spotify 
[15:09] <soee> yes probably
[15:10] <apachelogger> i.e. this wouldn't be a problem if spotify didn't complain about arguments it doesn't understand ... at the same time applications complaining about arguments they don't understand is a general problem with ksmserver trying to restore everything with a session value
[15:10] <apachelogger> alas, I don't know enough about the inner workings of session restoration, so I can't really comment all that much ;)
[15:17] <soee> the LANG=en_US does not work for me, locales problem >?
[15:18] <apachelogger> 'en_US' is not a valid locale identifier
[15:19] <soee> oh i though i used it few times and wored
[15:20] <apachelogger> you need to fix it to en_US.UTF-8
[15:21] <apachelogger> the only locales that have no encoding defined are C and POSIX because they are inherently latin1
[15:21] <soee> apachelogger: ok but i want to use it to execute command using EN
[15:22] <soee> like: #LANG=en_US sudo apt-get dist-upgrade 
[15:27] <apachelogger> LANGAUGE=en is what you want
[15:27] <apachelogger> or LANG=C
[15:27] <soee> indeed :o
[15:29] <soee> http://paste.ubuntu.com/7836735/ :)
[15:29] <apachelogger> shadeslayer: ^
[15:30] <shadeslayer> k
[15:30] <shadeslayer> noted down
[15:39] <Riddell> apachelogger: can you look at that since you're in the area? ↑ https://code.launchpad.net/~panfaust/kubuntu-packaging-next/plasma-workspace-work/+merge/227770
[15:42] <apachelogger> Riddell: already gone again. also I am leaving for today, so I'd be earliest tomorrow
[15:44] <Riddell> thanks apachelogger 
[15:45] <apachelogger> will fiddle it in with the dep changes staging I guess
[15:45] <apachelogger> anywho
[15:45]  * apachelogger out
[16:03] <shadeslayer> xnox: ping
[16:04] <shadeslayer> xnox: any ideas how to get rid of the LIBEXECDIR var here http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging-next/sddm/view/head:/debian/rules#L13
[16:05] <shadeslayer> xnox: because I thought that gnuinstalldirs sets that appropriately on ubuntu
[16:05] <shadeslayer> but apparently doesn't work when used with SDDM
[16:07] <xnox> shadeslayer: if you open a bug and assign it to me, i can look into it.
[16:07] <xnox> shadeslayer: a bit busy atm.
[16:07] <shadeslayer> sure
[16:07] <shadeslayer> I was kind of looking into it myself
[16:26] <Riddell> yay kdesudo ported to frameworks! http://people.ubuntu.com/~jr/tmp/kdesudo.png
[16:26] <Riddell> needs lots of tidying but nice that it works
[16:39] <shadeslayer> xnox: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1347018
[17:25] <shadeslayer> soee: can you add https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/next-staging to check if the kde-style-qtcurve upload fixes things for you?
[17:29] <yofel> what do we need qtcurve for again?
[17:31] <shadeslayer> default application style for Plasma 5
[17:32] <yofel> hm, it would probably help if I had that installed...
[17:33] <shadeslayer> so far my kubuntu next iso is looking pretty sweet :p
[17:33] <yofel> can you add kde-style-qtcurve5 to the p5 seed?
[17:33] <shadeslayer> yep
[17:34] <shadeslayer> done
[17:42]  * yofel reboots and watches intel pixel garbage instead of plymouth
[17:42] <yofel> how did they manage to break it this time ...
[17:49] <yofel> *sigh*
[17:50] <yofel> shadeslayer: is there some setup page that explains how one makes sddm actually work?
[17:58] <Sick_Rimmit> Hmm.. OK I broke digikam.. Builds fails with conflicting dependencies...
[17:58] <Sick_Rimmit> !paste
[18:00] <yofel> Sick_Rimmit: if you just need to look something up you can query the bot, just /msg ubottu paste
[18:00] <Sick_Rimmit> Oh ok, let me try
[18:01] <Sick_Rimmit> http://paste.ubuntu.com/7837488/
[18:02] <Sick_Rimmit> So I think I am nearly there, logic suggests the control file probably needs version dependencies updating.. 
[18:02] <yofel> ok, you'll either want to run 'builddeb -S' to just make a source package, or 'sudo apt-get build-dep digikam' if you really want to locally build the binaries
[18:02] <yofel> not sure what you wanted to do...
[18:03] <Sick_Rimmit> Ah OK, I don't understand how you figured that out..
[18:03] <yofel> ok, case 1)
[18:04] <Sick_Rimmit> alright, I'll do that, thanks yofel
[18:04] <yofel> dpkg-checkbuilddeps doesn't error out for source package builds, and your command didn't have -S in it
[18:04] <yofel> case 2) results from you not running case 1) so you'll actually need those installed then
[18:08] <Sick_Rimmit> Maybe I understand this. Working form the packaging guide, it talks about building the .deb using the command you saw in pastebin. However, for something more complex, this docs example skips building the source packages, which are required to then build the binary. If this builddeb -S completes, then I can re-run builddeb -- -us -uc to see if it will then build a compiled binary. 
[18:08] <Sick_Rimmit> Have I understood this correctly ?
[18:09] <yofel> well, if you don't use -S you need an environment that can actually build the package, and your system is missing all the build-dependencies
[18:09]  * Sick_Rimmit dives off to man builddeb
[18:10] <yofel> which means either pbuilder, or sbuild, or some other chroot
[18:10] <yofel> or you can build locally while running the dev release
[18:11] <yofel> Sick_Rimmit: bzr builddeb is pretty much the bzr interface for debuild
[18:12] <Sick_Rimmit> This is an interesting tool chain...
[18:12] <yofel> so, you're trying to build digikam
[18:13] <Sick_Rimmit> Yes.. of course I'm really trying to get good enough at packaging to be a useful part of the team
[18:13] <Sick_Rimmit> My reading got me to liking pbuilder, as it creates this pristine chroot..
[18:13] <yofel> do you have a chroot for it? I'm pretty much a very pbuilder centered person, but you can also just make a dev chroot and build stuff locally
[18:14] <Sick_Rimmit> well it struck me that pbuilder took all the hassle away, as it builds to the distro released based upon the changelog? I believe
[18:15] <yofel> usually... yes. Depends on how your .pbuilderrc is set up
[18:15] <yofel> do you have our pbuilder hooks?
[18:15] <Sick_Rimmit> I feel ultimately I will get a broader handle on the range and ability of the tool set, but I'm a handson learner, and to much RTFM, FPMO ;-)
[18:16] <Sick_Rimmit> no it's a stock trusty install, with no config just the build-essential toolk chain etc...
[18:18] <yofel> hm, our ninja wiki page got lost in the wiki move it seems
[18:18] <Sick_Rimmit> I think what makes if tough is the documentation is 1.) all over the place 2.) lets of old stuff, and I get lost real quick, in a dearth of conflicting methods and tools
[18:19] <Sick_Rimmit> but like anything if you just keep kicking it, until something starts to work, that usually gets me there
[18:19] <Sick_Rimmit> I me beligerant than intelligent :-)
[18:19] <yofel> yeah, that's true
[18:20] <yofel> ok, lets make pbuilder do something useful
[18:20] <yofel> Sick_Rimmit: bzr co  lp:~kubuntu-packagers/pbuilder/pbuilder-hooks ~/.pbuilder-hooks
[18:21] <yofel> then put this in your ~/.pbuilderrc
[18:21] <yofel> HOOKDIR="$HOME/.pbuilder-hooks"
[18:22] <yofel> I don't use stuff like pbuilder-dist, just plain pbuilder, so my .pbuilderrc is pretty long: http://paste.ubuntu.com/7837577/ (if you find some useful stuff in it)
[18:23] <yofel> you will want the pkgname_logfile stuff
[18:24] <Sick_Rimmit> Ah ha.. OK, yep saw that in the README file
[18:24] <yofel> Sick_Rimmit: if you have the hooks set up, you should be able to just make a source package for digikam, put it into pbuilder and you'll get what you need to fix from the build log
[18:25] <Sick_Rimmit> Right, I think a session with pbuilder man pages is in order.
[18:27] <yofel> there's a manpage for pbuilder and pbuilderrc, useful to read, but you should be able to start out with just the hooks and a simple pbuilder base image
[18:27] <Sick_Rimmit> yofel: Wow, you have been having fun with your Bash Kung Fu!!.
[18:28] <yofel> hehe, gave me a pbuilder setup that supports eatmydata, parallel gzip, ubuntu, debian, tanglu and icecc
[18:28] <yofel> there's a lot of junk in there too though
[18:29] <Sick_Rimmit> hmm pbuilder --build digikam_4.1.0-0ubuntu1.dsc has Crashed and Burned.. Pah!
[18:38]  * Sick_Rimmit Sort of groks pbuilder hooks..
[18:43] <yofel> Sick_Rimmit: making progress or is something trolling you? ^^
[18:44] <Sick_Rimmit> Well, I found pretty good pbuilder user manual. 
[18:44] <Sick_Rimmit> I think the trouble I am having now with digikam is that pbuilder is trying to build it in a Saucy chroot, so I'm going to fix that with create --distribution utopic
[18:44] <Sick_Rimmit> then try and build it again
[18:45] <Sick_Rimmit> http://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html
[18:45] <yofel> wow, that's long
[18:46] <yofel> IMO the series detection is pretty flakey, which is why I always build with something like 'sudo -E dist=utopic pbuilder build foo' so it never auto-guesses
[18:58] <Riddell> Sick_Rimmit: got digikam going?
[18:58] <Sick_Rimmit> Sssssh keep quite, I'm sneaking up on it
[18:59]  * yofel hears something crack and watches a huge DSLR lens falls down on Sick_Rimmit
[18:59]  * Sick_Rimmit lol
[18:59] <Riddell> !testers | 14.04.1 candidate ↑
[18:59] <yofel> :P
[19:00] <alket> :)
[19:00] <alket> what do I have to do :)
[19:01] <Riddell> alket: test the candidate for LTS update 14.04.1 http://iso.qa.ubuntu.com/qatracker/milestones/318/builds/73626/testcases
[19:01] <alket> thanks
[19:02] <Sick_Rimmit> Riddell: I've got a utopic chroot installing dependencies now, so you never know, it might work.. 
[19:04] <Sick_Rimmit> alket: Would you like me to undertake one or two of those tests with you ?
[19:05] <alket> Sick_Rimmit: yeah , much appreaciated , im lost
[19:05] <Sick_Rimmit> alket: OK, do you have some questions I can help you with ?
[19:06] <alket> yes
[19:06] <alket> where to test the iso-s ,will vbox do ? or i ahve to make a partition ?
[19:06] <Sick_Rimmit> Indeed vbox is a good place
[19:07] <Sick_Rimmit> Look at the first test for example
[19:07] <Sick_Rimmit> You would want a vbox with say Windows installed, and then mount the iso and try to install it to a dual boot setup
[19:07] <Sick_Rimmit> make sense ?
[19:08] <Sick_Rimmit> In test two you could just flash up a vbox and do a straight install 
[19:08] <alket> thanks for ideas
[19:08] <Sick_Rimmit> Test 3, make a vbox with 2 virtual disks, and then use LVM to mount them to the system as one disc, and encrypt them..
[19:09] <Sick_Rimmit> That one's a little more complex
[19:09] <alket> ok I will try
[19:09] <alket> but I have to watch that video first on how to use tracker I guess
[19:11] <soee> someone tried sddm already ?
[19:12] <yofel> soee: me, crap so far
[19:12] <soee> :P
[19:12] <yofel> i.e. fails on start without error
[19:12] <soee> there were some updates lately
[19:12] <soee> i thought maybe some fixes
[19:12] <yofel> Sick_Rimmit, alket: do test encrypted LVM without setting up disks, the installer should do that itself
[19:14] <Sick_Rimmit> yofel: Ah what I meant was create a virtual machine, but add an extra virtual HDD, so the machine looks like it has 2 discs installed. Then go for an LVM install with encryption, and it should sort that out automagically. <- Am I on same page as you yofel 
[19:14] <alket> yofel: thanks
[19:15] <yofel> oh, that would be good yeah. I was thinking single-disk
[19:18] <Sick_Rimmit> Ah ha so digikam build has exploded..
[19:18] <Sick_Rimmit> http://paste.ubuntu.com/7837857/
[19:18] <yofel> seriously...?
[19:18] <Sick_Rimmit> I think its this
[19:18] <Sick_Rimmit> CMake Warning at extra/libkface/CMakeLists.txt:78 (MESSAGE):
[19:19] <Sick_Rimmit>   OpenCV: Version is too old.
[19:19] <yofel> stupid opencv
[19:19] <yofel> yeah, it's that
[19:19] <Sick_Rimmit> Ah right... well the fact that I got that, is a good sign..
[19:19] <Riddell> Sick_Rimmit: that's in a pbuilder?
[19:20] <yofel> sid has 2.4.9, so someone will have to merge that
[19:20] <Sick_Rimmit> Ah I wonder if I made a mistake
[19:20] <yofel> you did not
[19:20] <Sick_Rimmit> sudo pbuilder --build digikam_4.1.0-0ubuntu1.dsc
[19:20] <Riddell> opencv also seems to be stuck in proposed
[19:21] <Sick_Rimmit> I was sudo.
[19:21] <yofel> our opencv is too old, all I said was that debian has the version we need
[19:21] <Sick_Rimmit> when it dropped FTBFS if left me in as Root
[19:21] <Riddell> Sick_Rimmit: the message is as it says, opencv needs to be 2.4.9, we have only 2.4.8 https://launchpad.net/ubuntu/+source/opencv
[19:21] <Riddell> debian has 2.4.9 https://packages.debian.org/search?searchon=sourcenames&keywords=opencv
[19:21] <yofel> Sick_Rimmit: that's one of the hooks so you can look into stuff on failure
[19:21] <yofel> if you want to quit just ctrl+d
[19:22] <Sick_Rimmit> Ah OK, so it looks like I can probably make a succesful build once OpenCV is updated
[19:22] <Sick_Rimmit> yofel: Ah ha got you, I see what's happened there
[19:23] <Riddell> Sick_Rimmit: I can help you merge opencv if you have a spare hour or two
[19:25] <Riddell> boy, I thought I was fanatical about KDE, this guy is nuts http://paste.kde.org/pp9ggrvee
[19:25] <Sick_Rimmit> Riddell: Are you about tomorrow ? 
[19:26] <Riddell> Sick_Rimmit: yep
[19:26] <Sick_Rimmit> Riddell: I want to review what I did to get this far, with digikam and make a few notes. Then tomorrow I will work on opencv, that way I won't confuse myself
[19:26] <yofel> why? Some people collect stamps, some tarballs :D
[19:28] <Riddell> if he's that much of a fan he should become a packager, then he'll have to put up with every tar there is
[19:32] <soee> sddm log, just tried it again http://paste.ubuntu.com/7837920/
[19:39] <soee> qtcurve showed up on the list :)
[19:43] <Sick_Rimmit> My notes from my journey to the centre of Kubuntu packaging -> http://paste.ubuntu.com/7837976/
[23:41]  * yofel wonders why people put backports into the updates ppa all the time -.-
[23:41] <yofel> *sigh*