[04:49] <jarkko> http://is11.snstatic.fi/img/978/1288646664471.jpg
[07:29] <jussi> hrm, so just read on planet kde that there will be a ported version of krunner going forward, until the replacement is ready. I dont remember what we decided, but we should stick with that as per upstream IMHO
[07:30] <jussi> "The future of KRunner, Plasma's mini-commandline was discussed. There is a replacement in the works, though at this early stage is it unclear when it is going to land. In order to allow an alternative to fully mature before it replaces a core component, the team decided to port the current version of KRunner, and adapt it for improvements in the desktop search area."
[08:28] <jacky> I was hoping for something like this
[08:28] <jacky> But I'm curious to what they'd replace it to be 
[08:28] <jacky> and if all of the prior extensions would be compatable.
[08:29] <jacky> My hopes was mainly for the searching aspect of it to be sent to a daemon of sorts and it having a QML frontend that be used/invoked anywhere
[08:29]  * jacky goes to the planet
[08:29] <jacky> gvim
[08:29] <apachelogger> Riddell: ubiquity review is in feburary
[08:30] <apachelogger> when a card is overdue it will have a red bell :)
[09:17] <shadeslayer> morning
[09:21] <soee> good morning shadeslayer
[09:27] <valorie> Riddell: I'm unsure what you were asking me?
[09:33] <apachelogger>  InstallationMedia: Fantasy32 13.10 - Release i386
[09:33] <apachelogger> we should just close all bugs that were not installed from an official flavor -.-
[09:33] <shadeslayer> *nod*
[09:35] <apachelogger> shadeslayer: oh, do we have a PPA for qt 4.8.5 yet?
[09:36] <shadeslayer> uploaded to staging
[09:36] <apachelogger> ok
[09:36] <shadeslayer> I haven't followed afterwards
[09:37] <apachelogger> shadeslayer: going to look at it when I am done with mails
[09:59] <apachelogger> Riddell: ping
[09:59] <apachelogger> :'(
[10:00] <apachelogger> yofel: ping
[10:00] <apachelogger> everyone is hiding from me :'<
[10:00] <jussi> apachelogger: awwww
[10:00]  * apachelogger hugs jussi
[10:00] <jussi> apachelogger: I began work on the activity thing :)
[10:01] <apachelogger> weeeh
[10:01] <jussi> when was the deadline again? 
[10:01] <apachelogger> shadeslayer: opinions on where to put the new qt?
[10:01] <apachelogger> jussi: feb 20
[10:01] <shadeslayer> apachelogger: beta backports 
[10:01] <shadeslayer> once it passes QA we can move to backports 
[10:01] <jussi> apachelogger: ok, excellent. 
[10:01] <apachelogger> jussi: well, before feb 20, because we have lots of quality control stuff around feb 20
[10:01] <jussi> ok
[10:01] <shadeslayer> apachelogger: maybe even do experimental -> backports
[10:02] <apachelogger> shadeslayer: yeah, I was thinking experimental for preliminary testing and then -> backports
[10:02] <jussi> apachelogger: if it isnt there already, can you add what I need to submit (which files etc) to the trello card? 
[10:02] <shadeslayer> apachelogger: yep, either one is fine IMHO
[10:03] <apachelogger> jussi: a snapshot with possible names of widgets and snippets of text you used 
[10:03] <apachelogger> jussi: I need to manually write a script that produces such an activity then
[10:03] <jussi> oh. last time you wanted some config file or something...
[10:03] <apachelogger> jussi: oh and did you poke upstream about this possibly?
[10:03] <jussi> apachelogger: I wrote to aaron today about it, yes
[10:04] <apachelogger> jussi: if he doesn't respond within the week please send one to plasma-devel@kde.org
[10:04] <apachelogger> broder audience anyway :)
[10:04] <jussi> ok
[10:04] <apachelogger> although you may do that anyway, because that's what aaron will tell you
[10:05] <apachelogger> not quite sure why we concluded that a mail should be sent to him directly, I always get annoyed when people do that to me :P
[10:05] <apachelogger> shadeslayer: throwing at experimental
[10:05] <yofel> apachelogger: pong, kinda, not really though
[10:05] <apachelogger> yofel: nevermind
[10:06] <apachelogger> not responding in time = not getting a say :P
[10:06] <apachelogger> Riddell: also unping :P
[10:06] <apachelogger> shadeslayer: mh, or maybe a separate PPA
[10:06] <apachelogger> ah well, I'll throw it at experimental, if users want a separate one that can still be arranged
[10:07] <shadeslayer> I don't think it makes much sense for a separate PPA
[10:07] <shadeslayer> No one should be running experimental long term
[10:08] <jussi> apachelogger: I was told to "talk to aaron, he is the activities god", therefore I am doing just that :)
[10:08] <shadeslayer> apachelogger: is it required to call reloadCache in the finished function?
[10:08] <shadeslayer> I mean finished means it finished successfully no?
[10:09] <shadeslayer> oh hmm
[10:09] <shadeslayer> not really
[10:09] <apachelogger> jussi: yeah, did we say that in munich? I think we said something like that
[10:09] <apachelogger> in retrospect it still seems silly tho ^^
[10:09] <jussi> yep
[10:09] <jussi> apachelogger: oh well, it is done now. lets see how we go
[10:10] <apachelogger> shadeslayer: not necessarily it's best tho
[10:10] <shadeslayer> right
[10:10] <apachelogger> that is to say I like to foward the error signal to the finished slot
[10:10] <apachelogger> because having 2 signals is shitty API
[10:10] <apachelogger> should be finished(State), enum State { Finished, Yolo, Error }, ErrorType errorType() const
[10:11] <apachelogger> so you have one function that always gets called when the backend stops doing stuff and you can call the backend for more information on possibly errors etc.
[10:11] <shadeslayer> yeah :/
[10:11] <shadeslayer> apachelogger: http://paste.kde.org/pc64cab84
[10:13] <shadeslayer> apachelogger: also, this is confusing
[10:13] <shadeslayer> does finished get called even if the transaction error'd out?
[10:14] <shadeslayer> if the transaction errors out, then both slots get called and I'm calling reloadCache twice at possibly the same time
[10:18] <apachelogger> shadeslayer: no
[10:18] <apachelogger> that's the thing
[10:18] <shadeslayer> *facepalm*
[10:18] <apachelogger> you either get an error signal
[10:18] <apachelogger> or you get a finished signal
[10:18] <apachelogger> that's why it is shitty API
[10:18] <shadeslayer> fix it fix it fix it
[10:18] <apachelogger> filed a bug, can't do anything about that at this point
[10:18] <apachelogger> would be a rather grave API change
[10:19] <apachelogger> seeing as every application is forced to pick up both signals (further evidence of the shittyness .... :P)
[10:19] <apachelogger> shadeslayer: note that you can connect to a slot without params
[10:20] <apachelogger>     connect(d->transaction, SIGNAL(errorOccurred(QApt::ErrorCode)),
[10:20] <apachelogger>             this, SLOT(transactionError()));
[10:20] <apachelogger> so since you have the same logic you can just connect the errorOccured signal to SLOT(finished()))
[10:21] <apachelogger> (because you don't evaluate the ExitStatus you don't need the param really)
[10:21] <apachelogger> </random ramblings>
[10:21] <shadeslayer> apachelogger: right, but I'm adding code that will show the user a error message widget when there's an error with the transaction
[10:21] <shadeslayer> so I do need two functions now?
[10:22] <apachelogger> 3
[10:22] <apachelogger> error, finished, cleanup
[10:22] <apachelogger> error calls cleanup, finished calls cleanup
[10:22] <shadeslayer> hmm, could rename restoreUI to cleanu
[10:22] <shadeslayer> *cleanup
[10:22] <apachelogger> yeah, that thing would reload the backend then
[10:23] <apachelogger> general idea: cleanup does everything that needs to be done on transaction end
[10:23] <shadeslayer> *nod*
[10:27] <shadeslayer> hurrat
[10:28] <shadeslayer> libqapt doesn't provide error details when you have an auth error
[10:37] <shadeslayer> apachelogger: might want to look at 1182784
[10:38] <shadeslayer> apachelogger: and does this look right to you https://projects.kde.org/projects/extragear/sysadmin/libqapt/repository/revisions/master/entry/utils/qapt-batch/qaptbatch.cpp#L212
[10:39] <shadeslayer> I mean the string says  "The following packages have not been verified by  their authors. " , and then passes the size
[10:42] <shadeslayer> and regarding http://techbase.kde.org/Development/Tutorials/Localization/i18n_Semantics#Structure_tags , do you mean ask tsdegos?
[10:43] <shadeslayer> because it won't work without i18nc as mentioned yesterday
[10:44] <apachelogger> you may be able to use the structure tags without i18n somehow, I meant that you should ask whether you should use i18n for that string in general (for the sake of localization)
[10:44] <apachelogger> becasue I am not sure whether that may be necessary
[10:48] <shadeslayer> I don't see how you can localize something like "Radeon HD XXXX"
[10:48] <shadeslayer> or "Broadcom wireless FOO"
[10:59] <apachelogger> shadeslayer: that's why you ask a specialist
[11:02] <shadeslayer> k gonna ask tsdegos
[11:02] <shadeslayer> who isn't around at the moment
[11:02] <shadeslayer> huh, he's here, but not in #kde-devel :)
[11:03] <shadeslayer> tsdgeos: poke poke
[11:05] <apachelogger> shadeslayer: he's at work work that's why he isn't in kde-devel ;)
[11:12] <lordievader> Good afternoon.
[11:19] <shadeslayer> apachelogger: http://paste.kde.org/p28371404
[11:19] <apachelogger> shadeslayer: "is hardware vendor", "is hardware model" maybe?
[11:22] <shadeslayer> k
[11:25] <shadeslayer> apachelogger: experimental PPA should have pacakges soon
[11:28] <shadeslayer> time to figure out layouting issues
[11:35] <yofel> hm
[11:36]  * yofel realized why he didn't see apachelogger's ping earlier
[11:36] <yofel> plasma isn't updating o.O
[11:36] <yofel> it's not 12:08 now...
[11:38] <apachelogger> lol
[11:38] <apachelogger> deadlock?
[11:39] <apachelogger> shadeslayer: cool
[11:40] <shadeslayer> some timer probably forgot to fire ;)
[11:44] <BluesKaj> Hiyas all
[11:50] <shadeslayer> apachelogger: so the driverOptionsVLayout QVBoxLayout is the member causing layouting issues, but I have no clue how to delete the layout so that all the child widgets get deleted
[11:51] <shadeslayer> atleast not without writing a while loop that iterates over the child widgets and deleting them one by one
[11:57] <shadeslayer> maybe it would be beneficial to migrate to a model-view system :)
[11:57] <apachelogger> shadeslayer: layout must not have a parent
[11:57] <apachelogger> not a qwidget one anyway
[11:57] <apachelogger> otherwise what happens is parent.setlayout(this)
[11:57] <apachelogger> which may be why things fall apart
[11:58] <shadeslayer> I don't follow
[11:58] <apachelogger> oh 
[11:58] <apachelogger> Oo
[11:59] <apachelogger> ah, oh
[11:59] <apachelogger> shadeslayer: you don't delete the layout
[11:59] <shadeslayer> apachelogger: I delete the entire ui
[11:59] <shadeslayer> oh
[11:59] <shadeslayer> oh
[11:59] <apachelogger> QList<QWidget *> m_driverwidgets
[11:59] <apachelogger> qDeleteAll(m_driverwidgets)
[11:59] <apachelogger> for example
[12:00] <shadeslayer> there's no call to find driverwidgets :/
[12:00] <apachelogger> shadeslayer: ^ things like that are why mode/view would be better
[12:00] <shadeslayer> I'll have to store them at the time of calling shit
[12:00] <apachelogger> shadeslayer: you create those widgets....
[12:00] <shadeslayer> apachelogger: yeah, I'm thinking of migrating to model/view now :/
[12:00] <shadeslayer> maybe tomorrow
[12:00] <apachelogger> well
[12:00] <shadeslayer> I don't have a clue how to work on that tbh
[12:00] <apachelogger> you could just do the cheapshot widget solution
[12:01] <apachelogger> QListWidgetView or what its called
[12:01] <apachelogger> see usb-creator
[12:01] <apachelogger> it's the cheap shot solution where you use an existing view without a model
[12:01] <apachelogger> not sure whether that will be enough for your layout concept though
[12:02] <apachelogger> though TBH, a less complicated layout working application would be much preferred over a well layed out one
[12:02] <shadeslayer> apachelogger: http://paste.kde.org/p8fddf42d works
[12:02] <apachelogger> that's shit
[12:02] <shadeslayer> I know
[12:02] <apachelogger> you do not ever call setupUi 
[12:02] <shadeslayer> whaaaa
[12:03] <apachelogger> just create a list of widgets to delete
[12:03] <apachelogger> and qdeleteall on that
[12:03] <shadeslayer> yeah, I'm going to port this to model/view tomorrow
[12:03] <shadeslayer> so we don't need such shitty things
[12:03] <apachelogger> shadeslayer: maybe ask for opinion in the office
[12:03] <shadeslayer> hopefully tomorrow is the day I can understand model/view
[12:04] <shadeslayer> apachelogger: ok
[12:04] <apachelogger> perhaps they have an idea for simpler thing than model/view but still better than that ^^
[12:04] <shadeslayer> true
[12:04] <shadeslayer> enough driver stuff for today
[12:04] <apachelogger> I mean, at the end of the day that is just a mushed together model/view without neatly encapsulated logic, but I already complained about latter anyway :P
[12:05] <shadeslayer> *nod*
[12:28] <Riddell> 1202 e-mails to process, I will get through them today!
[12:34] <Riddell> hi Sick_Rimmit!
[12:34] <apachelogger> Riddell: good luck with that :P
[12:45]  * Peace- got a 8 core phone
[12:48] <kubotu> ::qt-bugs:: [1198806] osgviewerQt crashes on startup @ https://bugs.launchpad.net/bugs/1198806 (by Thomas Bleher)
[13:16] <ovidiu-florin> hello world
[13:17] <ovidiu-florin> on http://www.kubuntu.org/news/trusty-alpha-2-available-testing it should say "More information on Kubuntu *Trusty* Alpha 2
[13:19] <Riddell> ovidiu-florin: do you have or want the access details to change it?
[13:20] <ovidiu-florin> Riddell: I don't have access.
[13:20] <ovidiu-florin> I'll make the change if you give me access
[13:30] <shadeslayer> apachelogger: d_ed and vHanda_ say that implementing a MVC with things like radio buttons is a PITA
[13:32] <shadeslayer> and d_ed says my solution to the problem by deleting the driver layout is fine
[13:34] <apachelogger> shadeslayer: no, make a list
[13:35] <apachelogger> you are recreating the entire UI, because you did not put the layout there in the first place
[13:35] <apachelogger> and recreating the entire UI is just wrong
[13:35] <shadeslayer> /o\
[13:36] <shadeslayer> kdepimlibs git needs akonadi git
[13:36] <apachelogger> I think that's it though
[13:36] <shadeslayer> apachelogger: hm, so keep list of radiobuttons, call qdeleteall on the list?
[13:36] <apachelogger> shadeslayer: yeah
[13:37] <apachelogger> shadeslayer: but what you want to do anyway is create a class to contain the visual prototype of an entry in your pseudo list
[13:38] <apachelogger> so you can do QWidget *ptr = MewoClass(data); m_kittehList.append(ptr); layout->addWidget(ptr);
[13:38] <apachelogger> and on refresh qDeleteAll(m_kittehList);
[13:38] <shadeslayer> hmm
[13:38] <shadeslayer> gotcha
[13:38] <shadeslayer> tomorrow
[13:38] <apachelogger> as for the deps... mtime on my clones suggest milou->baloo->kdepimlibs->akonadi
[13:39] <apachelogger> unless I started on day and finished the other day, then knewstuff would be in the list, although that doesn't make much sense I guess ^^
[13:39] <apachelogger> s/on/one
[13:39] <shadeslayer> good to know I don't have to go further than akonadi
[14:01] <shadeslayer> apachelogger: any clue if these translations http://pastebin.kde.org/pgnw8pcja can be used by plasma-widget-homerun-kicker?
[14:01] <shadeslayer> or since the file name does not have kicker, it can only be used by homerun
[14:04] <Riddell> shadeslayer: what does homerun say it uses?
[14:04] <Riddell> should specify a catalog somewhere
[14:06] <Sick_Rimmit> Riddell: Hi, sorry not ignoring you, just messing round with my machine setups
[14:06] <Riddell> fullscreen/applet/homerunlauncher.cpp:    KGlobal::locale()->insertCatalog("plasma_applet_org.kde.homerun");
[14:06] <Riddell> shadeslayer: so yes looks good
[14:07] <shadeslayer> Riddell: `yeah
[14:07] <shadeslayer> no catalog for kicker
[14:15] <Riddell> sgclark: "Multi-Arch: allowed" where did you get that from?
[14:18] <sgclark> Riddell: Umm, looked up the Arch binary in non arch error
[14:18] <sgclark> Riddell: I don't remember sorry
[14:18] <sgclark> Riddell: it fixes the error though
[14:20] <shadeslayer> Riddell: I'm really tempted to ship homerun kicker as the default kickoff :P
[14:21] <Riddell> shadeslayer: ug, why?
[14:22] <Riddell> it's like going back to windows 95 isn't it?
[14:22] <shadeslayer> I quite like it :)
[14:23] <Riddell> sgclark: where did you get the rename patches from? upstream?
[14:23] <shadeslayer> Riddell: either way, homerun-kicker in binary new soon
[14:28] <Riddell> shadeslayer: does it need a separate package?
[14:28] <shadeslayer> Riddell: IMHO yes
[14:28] <shadeslayer> because they're 2 different plasmoids
[14:28] <shadeslayer> 2 completely different things
[14:28]  * Riddell accepts
[14:29]  * shadeslayer rages at bzr
[14:31] <sgclark> Riddell: no I made those myself
[14:32] <Riddell> sgclark: you're good :)
[14:32] <Riddell> sgclark: have you sent them upstream?
[14:33] <sgclark> Riddell: no I have not, want me to?
[14:35] <Riddell> sgclark: let me look closer to check
[14:35] <sgclark> Riddell: good plan :)
[14:40] <Riddell> sgclark: looks like kf5rename  kf5renametelnetservice already have equivalents upstream but the .desktop files haven't been renamed for some reason
[14:41] <Riddell> on they install to /usr/share/applications/kde4/ anyway so not a problem
[14:41] <Riddell> oh they install to /usr/share/applications/kde4/ anyway so not a problem
[14:42] <Riddell> for renamedbus I've been keeping the diff simple and not renaming the dbus interface file in the sources but just adding a RENAME kf5_foo.xml in cmakelists
[14:42] <Riddell> also I've been using an underscore rather than a dash to show it's a namespace not part of the name
[14:45] <sgclark> Riddell: the desktop files as is would launch the kde4 version, wouldn't they?
[14:47] <Riddell> hmm, I'm not sure
[14:47] <Riddell> I assume whoever did the upstream patch thought about it a bit
[14:58] <apachelogger> shadeslayer: yes, sure, if that name is correct 
[14:59] <shadeslayer> apachelogger: so I can't build release-upgrader on precise
[14:59] <shadeslayer> it doesn't have things like ubuntu-drivers common
[14:59] <shadeslayer> or python3-update-manager
[15:02] <shadeslayer> apparently first arrives in Quantal
[15:04] <Riddell> sgclark: kf5 meeting in #kde-devel incase you're interested
[15:05] <sgclark> ok
[15:07] <apachelogger> shadeslayer: you build it on trusty
[15:08] <apachelogger> the point of the entire thing is that you download the release upgrader for trusty from trusty and it will work on precise
[15:08] <apachelogger> i.e. why it actually makes sense that this thing is pyth0rn
[15:08] <shadeslayer> so it copies libs that it requires ?
[15:08] <shadeslayer> for eg  python3-update-manager
[15:13] <apachelogger> I think the requirement is just to not have crappy dependencies
[15:19] <apachelogger>  4 files changed, 303 insertions(+), 43 deletions(-)
[15:19] <apachelogger> down from 6k or so \o/
[15:19] <Riddell> sgclark: kio uploaded!
[15:19] <Riddell> sgclark: I decided to go with only 1 -dbg package for simplicity
[15:19] <sgclark> Riddell: ok thanks :)
[15:19] <Riddell> sgclark: and rename the main package kf5-kio for simplicity
[15:20] <Riddell> sgclark: also added build-deps on acl and gssapi
[15:21] <sgclark> Riddell: how did you find that? it passed pbuilder
[15:21] <Riddell> sgclark: I don't think there's any point in manpages for those binaries, they don't do very much
[15:21] <Riddell> sgclark: look at the cmake output
[15:21] <Riddell> sgclark: they are optional
[15:21] <sgclark> Riddell: ahhh right, good idea. Also agreed on manpages
[15:22] <Riddell> sgclark: I think the dbus patch is the important one to get upstream but it should be simplified to just edit the cmakelists files, do you want to do it or shall I?
[15:23] <sgclark> Riddell: go for it :) I have a bunch more to get ready for you, I need kparts up today
[15:23] <Riddell> oh boy, maybe I won't get through this e-mail backlog after all :)
[15:23] <sgclark> lol
[15:27] <sgclark> woot I was right
[15:28] <Riddell> I never doubted you :)
[15:28] <apachelogger> ohm ohm, kcm now 90% less broken http://paste.ubuntu.com/6832572/ \o/
[15:30] <Riddell> awooga
[15:31] <Riddell> that'll please the corner of belgium which speaks german
[15:32] <shadeslayer> apachelogger: at what point is it supposed to show the release notes
[15:32] <shadeslayer> because for some reason, I just directly jump to "Preparing to upgrade"
[15:32] <apachelogger> oho
[15:33] <apachelogger> maybe the release notes are displayed by the invocing thing
[15:33] <shadeslayer> invocing thing?
[15:33] <apachelogger> update-manager-core or somesuch
[15:33] <apachelogger> I mean, something needs to download the upgrader tar and start it :P
[15:34] <apachelogger> that doesn't magically happen :P
[15:35] <shadeslayer> uhu
[15:35] <shadeslayer> *uhuh
[15:35] <shadeslayer> so your instructions are useless ;P
[15:36] <apachelogger> well I do not know
[15:36] <apachelogger> investigating stuff usually is a good idea
[15:38] <apachelogger> oh how I hate nano, I hate it so fing much
[15:40] <Riddell> better than pico
[15:42] <apachelogger> Riddell: s/better/bigger
[15:42] <apachelogger> shadeslayer: displaying is done by the fetcher
[15:43] <apachelogger> or so says grep
[15:43] <shadeslayer> right
[15:51] <apachelogger> well then
[15:51] <apachelogger> Riddell: libkubuntu and revised kcm should be good to go into archive this week
[15:51] <Riddell> aweet
[15:51] <Riddell> sweet too
[15:51] <apachelogger> still need to shuffle a whole bunch around to get into a state where the patch can be upstreamed too
[15:52] <apachelogger> also need to discuss whether we'd want a binary plugin interface for backing or scripts or whatever
[15:52] <apachelogger> though given the complexity we require it will probably have to be a plugin
[15:52] <apachelogger> plus that allows building a nicer experience inside the KCM around it anyway
[15:55] <shadeslayer> apachelogger: fwiw one can't just run the fetcher
[15:56] <shadeslayer> so I think I really need to install 13.10
[15:56] <apachelogger> you have a precise vm, no?
[15:56] <apachelogger> either way you don't need to install any specific version
[15:56] <apachelogger> you can meddle with your os-release/lsb-release file
[15:57] <apachelogger> or you can change /etc/update-manager/meta-release  to point elsewhere indicating something newer than trusty
[15:57] <apachelogger> or you can simply hardcode some stuff
[15:57] <apachelogger> but I reckon you should have a VM :P
[15:57] <shadeslayer> I have a precise VM
[15:57] <apachelogger> right then, see LTS testing instruction from deadlines board
[15:58] <shadeslayer> and what I did was install python3-distupgrade which has the KDE fetcher
[15:58] <apachelogger> or you could run kubuntu-devel-upgrade or what its called
[15:58] <shadeslayer> and it installs under the python3 namespace
[15:59] <shadeslayer> so I symlinked the old fetcher to the new one under the python3 namespace
[16:00] <shadeslayer> turns out python-kde4 isn't built with python3
[16:11] <apachelogger> shadeslayer: does not compute
[16:11] <apachelogger> precise has its own fetcher
[16:11] <shadeslayer> apachelogger: this is giving me a headache -.-
[16:12] <shadeslayer> apachelogger: yes, and I'm trying to make it use my fetcher
[16:12] <shadeslayer> which is python3
[16:12] <apachelogger> why?
[16:12] <shadeslayer> because my fetcher has the relevant code to show the html release ntoes?
[16:12] <apachelogger> why not copy the code to the old fetcher?
[16:13] <shadeslayer> then how do I know that it'll work in the new code base :S
[16:13] <apachelogger> if it works in the old, chances are it will work int he new
[16:13] <apachelogger> plus to test the new you need a trusty+1 release
[16:14] <apachelogger> testing the new code on precise gives you absolutely no quality assurance whatsoever
[16:14] <shadeslayer> not necessarily, I think it will work if I use Saucy
[16:14] <apachelogger> yeah, that's fooling-yourself-testing
[16:15] <ovidiu-florin> Calligra is broken on Kubuntu. This works on Debian, but not on Kubuntu: http://www.youtube.com/watch?v=7LOHANw_dYc
[16:16] <shadeslayer> how is the former not fooling-yourself-testing
[16:16] <apachelogger> because it's testing whether twe can throw that change at precise
[16:57] <rdieter> Riddell: ping, if you have a moment, saw your opengl comment in #Calligra, and wondered what qt/gl support you use on arm.  do you build qt with -opengl es2  (or other)?
[17:01] <shadeslayer> apachelogger: hurray, I can make python3 crash with : http://pastebin.kde.org/pd8eiw1bp on line 24
[17:04] <shadeslayer> aha nvm
[17:06]  * shadeslayer ponders about icon for upgrade
[17:16] <Riddell> rdieter: yeah it's opengles
[17:17] <rdieter> Riddell: es2 though?  or es1 ?
[17:18] <Riddell> extra_configure_opts += -arch armv6 -no-neon -opengl es2   and for arm64 -no-javascript-jit
[17:18] <Riddell> rdieter: ↑
[17:19] <rdieter> thanks
[17:20] <sgclark> kio just started building, wow that was a long wait
[17:20] <Riddell> sgclark: PPAs often take a while alas
[17:20] <sgclark> hehe np, just want to get kparts done today, quite a few depend on it
[17:21] <Riddell> sgclark: you can just self compile, you don't need to wait for the PPA to compile for you
[17:22] <sgclark> Riddell: already did that, just want to run it through pbuilder to be sure it is perfect :)
[17:23] <sgclark> it depends on kio
[17:34] <sgclark> Riddell: failed to build symbols error. Can you put your source in my ubuntu one so I can fix?
[17:55] <shadeslayer> apachelogger: :D
[17:55] <shadeslayer> apachelogger: http://i.imgur.com/DqWyfDP.png
[18:00] <genii> Sorry to bother, but a user in #k shared a folder from Dolphin and can access it from a Windows machine, etc. But he can't find where that config for that share is being stored. eg: grep share-name  /etc/sama/smb.conf  or  ~/.kde/share/config/dolphinrc  don't show it. Is there an actual place this gets saved or is it all  in RAM ?
[18:07] <shadeslayer> genii: moment
[18:07] <Riddell> sgclark: you can get it
[18:07] <Riddell> from the PPA
[18:07] <sgclark> Riddell: yeah amd64 built fine, any idea why i386 died?
[18:08] <Riddell> sgclark: probably different symbols
[18:08] <Riddell> just needs a symbol update
[18:08] <Riddell> that happens sometimes
[18:09] <sgclark> ok
[18:12] <Riddell> sgclark: I uploaded with the update
[18:13] <sgclark> ok thank you
[18:13] <Riddell> but you should be able to install amd64 now
[18:13] <Riddell> sgclark: are you running i386?
[18:13] <genii> apachelogger: The user left now and will probably post something to mailing list. If he reappears and you're around in there, the nickname they were under is berndk
[18:14] <sgclark> yeah :) kparts going through pbuilder, one of the tests takes forever >.<
[18:14] <sgclark> Riddell: no amd64
[18:23] <sgclark> Riddell: kparts ready for you
[18:24] <Riddell> ooh
[18:24] <Riddell> exciting :)
[18:47] <jarkko_> there is some ati xorg package, safe to do reboot without breaking things?
[18:48] <Riddell> dunno we only do the kde packagse
[18:49] <sgclark> Riddell: kdeclarative ready for you
[18:51]  * Riddell pays himself £50 for AWS usage for the last three months
[18:53] <Riddell> sgclark: hmm your kparts depends on a load of libraries which should be brought in by kf5-kio-dev, I'll fix up kf5-kio-dev now
[18:54] <sgclark> Riddell: yeah I thought that was odd, thanks
[18:54] <sgclark> I will fix kdeclarative, not ready yet :)
[18:56] <Riddell> sgclark: where did you get this description "Framework providing elaborate user-interface components."
[18:56] <Riddell> I'm not sure it does provide components, rather it allows for other programmes to do so
[18:57] <sgclark> Generally I search api doc, readmes etc. sometime techbase
[18:57] <sgclark> exactly where I got that one, I am not sure. 
[18:58] <Riddell> sgclark: I think best to use  Multi-Arch: same  rather than  Multi-Arch: allowed  seems "same" is definate while "allowed" is some magic detection that I'm a bit skeptical will cause breakage if something in the package changes
[18:58] <sgclark> Riddell: get reay for the lintian screaming at you then.
[18:59] <Riddell> I can take on lintian any day :)
[18:59] <sgclark> lol
[18:59] <Riddell> mv libkf5Parts5.symbols libkf5parts5.symbols   package names have lower case
[19:06] <Riddell> sgclark: kparts uploaded!
[19:08] <sgclark> thanks!
[19:34] <shadeslayer> Riddell: can you give me the output of : qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanSuspend 
[19:37] <shadeslayer> o_o
[19:37] <shadeslayer> no kde 4.12.1 for Saucy yet?
[19:39] <yofel> oh drat
[19:39] <yofel> I got not test feedback from anyone and got busy so forgot to publish it
[19:40] <shadeslayer> so it's still in ninjas?
[19:40] <yofel> yes
[19:41] <shadeslayer> ...
[19:42] <shadeslayer> yofel: how about moving to staging atleast
[19:42] <shadeslayer> so that I can send a email to Kubuntu Devel saying plz test from staging
[19:47] <apachelogger> genii: /var/lib/samba/usershare IIRC
[19:48] <apachelogger> genii: fwiw that is capsulated through samba's usershare binary, so it may well be elsewhere, no clue how to query the path
[19:48] <genii> apachelogger: Yes, he found the information elsewhere and shared it with us in the main channel :)
[19:48] <apachelogger> okeydokey
[19:49] <apachelogger> shadeslayer: http://www.bbc.co.uk/blogs/doctorwho/articles/Peter-Capaldi-Doctor-Who-Costume-Revealed- :O
[19:49] <yofel> shadeslayer: go ahead
[19:49] <genii> Strange change to Samba there
[19:49] <yofel> shadeslayer: works fine for me, but I don't release with only me testing :/
[19:49] <shadeslayer> apachelogger: yeah I know, meh, I think they're making a big deal out of it
[19:50] <apachelogger> genii: config files are hard to get right and from a security POV you don't want to allow every user to meddle with smb.conf, yet allowing users to share their own stuff at their own choosing is something much desired
[19:50] <apachelogger> so it makes sense
[19:50] <apachelogger> shadeslayer: lolwut, capaldi looks like twice as hot :P
[19:50] <apachelogger> some costume that is
[19:50] <genii> apachelogger: I would have thought it might use something like ~/.config/samba/smb.conf
[19:51] <apachelogger> shadeslayer: I still find it hard to not think of the thick of it tho
[19:51] <shadeslayer> apachelogger: looks a bit weird to me
[19:51] <shadeslayer> hhaha
[19:51] <apachelogger> OTOH a raging doctor might be cool
[19:51] <shadeslayer> apachelogger: the weird part being his pose
[19:51] <apachelogger> it's how the cool kids do it
[19:51] <shadeslayer> I see
[19:51] <shadeslayer> I'm not cool then
[19:52] <yofel> looks kinda dracula like to me :D
[19:52] <apachelogger> genii: that's harder to get right as for example ~ can be a subdirectory such as /home/foo/user etc.
[19:52] <apachelogger> also you can easily break that
[19:53] <apachelogger> becasue samba ought not be run as root, unless the samba group has read access there the share config will not work
[19:54] <genii> Hm.
[19:58] <sgclark> Riddell: that is weird kparts failed on kxmlgui but libkf5xmlgui-dev is in the control file
[20:06] <shadeslayer> yofel: oh, I thought you had copied the packages :)
[20:07] <sgclark> Riddell: kf5-kio-dev still is not pulling in the libraries
[20:19]  * shadeslayer runs kopypackages
[20:27] <shadeslayer> hah
[20:27] <shadeslayer> start new session on KTimeTracker does not work
[20:40] <Riddell> shadeslayer: what's kopying?
[20:41] <shadeslayer> Riddell: kopypackages? a script in Kubutu Dev tools that copies from one ppa/release to second ppa/release
[20:41] <shadeslayer> I like it because it's more intutive to use than copy-packages
[20:41] <genii> Heh, KDE and their obsession with starting everything with the letter K. I'm surprised they don't have their own license called Kopyright or so.
[20:42] <shadeslayer> they do, sort of :)
[20:42] <shadeslayer> though it's not called kopyright :P
[20:42] <Riddell> sgclark: version ~ppa3 of kf5-kio-dev does pull in the libraries
[20:43] <Riddell> shadeslayer: jr@wido:~>/usr/lib/x86_64-linux-gnu/qt4/bin/qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanSuspend
[20:43] <Riddell> yes
[20:43] <shadeslayer> huh ok
[20:45] <shadeslayer> Riddell: and installing pm-utils makes the suspend option appear?
[20:50] <Riddell> sgclark: uploaded kparts with xmlgui in build-deps, not sure what happened there
[20:55] <Riddell> shadeslayer: yes, I installed pm-utils and rebooted and it appears
[20:55] <Riddell> suspend is back in kickoff
[20:55]  * Riddell suspends
[20:58] <shadeslayer> how weird
[21:00]  * yofel still has to find out why the 'Hibernate' button re-appeared in kickoff
[21:00] <yofel> my system clearly cannot hibernate, but it still shows up
[21:10] <shadeslayer> :D
[21:16] <sgclark> Riddell: kdeclarative ready
[21:29] <ahoneybun> yofel: are you here?
[21:30] <yofel> yes, but sorry, I won't be able to help you much today. Working on copyright files with a headache from a cold isn't a particulary great idea
[21:30] <ahoneybun> I think I finished them tbh but I'm sure I can find someone to double check it
[21:48] <shadeslayer> yofel:  Riddell: fwiw I think we can skip copyright files for the first pass and get packages out 
[21:48] <shadeslayer> then during the testing phase, finish off copyright files
[21:48] <yofel> kf5?
[21:48] <shadeslayer> since the focus should be getting testable packages out the door
[21:48] <shadeslayer> yes
[21:49] <yofel> didn't we want to keep it in the PPA for 14.04?
[21:49] <shadeslayer> yes, but even then
[21:49] <yofel> well, fine with me
[21:49] <shadeslayer> That's just my opinion since KF5 packaging has been going on for sooooooooo long
[22:01] <sgclark> It has been dependency thing not copyright...
[22:01] <sgclark> I can only  do so much when dependency not in PPA
[22:03] <sgclark> anyway... Riddell: something happened between me/you/PPA control files, dependencies are missing, copying my control to my Ubuntu one folder
[22:04] <sgclark> For instance I have 4 ready now for pbuilder but they depend on kparts which is currently broken in PPA
[22:05] <sgclark> I am trying my best
[22:38] <ovidiu-florin> Riddell: are you around?
[22:47] <Riddell> no sorry
[22:47] <Riddell> head all wonky tonight