[01:51] <aj041191> hello goodmorning
[01:52] <aj041191> can i ask a question about customizing kde? or is there a channel for it?
[01:52] <aj041191> im new to kde things x.x
[02:10] <shadeslayer> aj041191: sure 
[02:11] <shadeslayer> you can have a look at Kubuntu-default-settings which contains modifications
[02:12] <aj041191> shadeslayer: where is that located?. i need to install it?. i think i dont understand youre  answer =)
[02:12] <shadeslayer> or if you have questions about something you want to configure for yourself, #kde and #kubuntu 
[02:13] <aj041191> thanks2, #Kubuntu seems no one is answering, they are talking aliens :)
[02:13] <shadeslayer> aj041191: what exactly do you want to customize ?
[02:13] <aj041191> http://kde-users.deviantart.com/gallery/37232101#/d5kn7gf
[02:13] <aj041191> i know now how to make that like global menu
[02:13] <aj041191> but im hearing about this be::shell and bespin
[02:13] <aj041191> now i install bespin but what to do with it.
[02:14] <shadeslayer> ok, user support questions in #kubuntu or #kde
[02:15] <shadeslayer> And I woukdnt know, barely do any customizing :)
[02:16] <aj041191> haha. thanks anway, i just like a good desktop =)
[02:16] <aj041191> gnome is easy to customize x.x
[02:18] <shadeslayer> that sounds like a oxymoron, but I don't want to get into that discussion :P
[02:22] <aj041191> why? xD ok ill google that hehe
[11:59]  * apachelogger wonders what a beshell is
[12:01] <apachelogger> "BE::Shell is a simple desktop shell on KDE technology (namely KIO and Solid) for the rest of us."
[12:01]  * apachelogger bets 50 euros that it uses qgraphicsfail :P
[12:03] <yofel_> do we have a plasma applet that uses konsole? I can't find one
[12:03] <apachelogger> there is a python one that is a terminal emulator
[12:03] <apachelogger> dunno about a konsole kpart
[12:03] <yofel> oh, the widget downloader doesn't crash anymore in 4.9.3 \o/
[12:04] <yofel> Plasmacon is a terminal emulator based on KDE Konsole technology (uses libkonsolepart). - that looks kinda nice
[12:04] <apachelogger> oh lol
[12:04] <apachelogger> beshell does appear to use qwidgets
[12:04] <yofel> heh
[12:05]  * apachelogger fears for his sanity
[12:08] <apachelogger> I wanted nothing more than to finish kubuntu-settings and now I am reading codez I did not know about 10 minutes ago -.-
[12:10] <tsimpson> looks like (yet) another "I want a Mac, but don't have a gazillian monies" thing
[12:11] <apachelogger> yeah
[12:11] <apachelogger> well
[12:11] <apachelogger> no
[12:11] <apachelogger> while it is from the bespin/whateverspinoff dude this thing actually is semi-sane
[12:11] <apachelogger> i.e. there is nothing wrong with using qwidgets
[12:15] <tsimpson> I mean more aesthetically
[12:15] <apachelogger> there is no such thing
[12:15] <tsimpson> and yes, qwidgets are much nicer than the insanity of graphics-whatever
[12:16] <apachelogger> be::shell relies on the user to come up with a config and css
[12:16] <tsimpson> from the screenshots posted
[12:16] <tsimpson> I presume you can make it pink ;)
[12:19] <apachelogger> tsimpson: http://wstaw.org/m/2012/11/18/plasma-desktopYM5541.png
[12:19] <apachelogger> that's what it actually looks like
[12:20] <apachelogger> not the authors fault that users make shit always look like osx for some reason :P
[12:20] <tsimpson> I was mostly going off http://sourceforge.net/p/be-shell/discussion/showroom/thread/b7f99467/
[12:21] <apachelogger> as I said, it's just how that particular invidual chose to theme the shell ;)
[12:22] <tsimpson> I have to say, there's a part of me that would be quite happy with nothing but a context menu on the desktop
[12:23] <apachelogger> use fluxbos
[12:23] <apachelogger> fluxbox
[12:23] <apachelogger> also a word of advise: do not try beshell
[12:23] <apachelogger> my plasma found out that I am seeing something else
[12:24] <apachelogger> now I have 4 panels
[12:24] <apachelogger> ontop of each other
[12:24] <apachelogger> and there is the crash
[12:24]  * apachelogger sighs
[12:25] <tsimpson> I did use fluxbox a while back, but then I start to miss launchers. I'm one of those people who can't make up their minds
[12:25] <tsimpson> or rather it changes based on my mood
[12:25]  * apachelogger likes to use konsole
[12:27] <tsimpson> I do take yakuake to whatever DE I'm using
[12:27] <tsimpson> it's the first thing I install
[12:29] <apachelogger_> I could live with ttys alone if there were sensible audio players :P
[12:37] <apachelogger_> debfx, Riddell, shadeslayer, Quintasan: if you don't reply to the 'kubuntu-settings restructuring' thread I'll go ahead and break it
[12:46] <apachelogger> https://code.launchpad.net/~kubuntu-packagers/kubuntu-settings/kubuntu-settings
[12:47] <apachelogger> ready for upload except for possible dep changes etc.
[14:49] <BluesKaj> Hey all
[19:43] <Quintasan> apachelogger: looking
[19:43] <Quintasan> or lemme know if you broke it already
[19:55] <Quintasan> agateau: ping
[19:56] <Quintasan> apachelogger: ping
[19:57] <apachelogger> yes?
[19:58] <Quintasan> apachelogger: http://paste.kde.org/609992
[19:58] <Quintasan> Is this even remotely dep-5 compatible
[19:58]  * Quintasan wonder is he actually has to care about dep-5 compatibility
[19:58] <apachelogger> who would know what with there not being a sensible parser and all that :P
[19:59] <Quintasan> Wait.
[19:59] <Quintasan> So you mean there is no dep-5 parser at this point in time?
[19:59] <apachelogger> have not seen one
[19:59] <apachelogger> it's spec compliant though
[20:00] <Quintasan> apachelogger: so it's good according to the specs?
[20:00] <Quintasan> Good.
[20:00] <yofel> hm, lintian has some limited dep-5 parsing support
[20:00] <yofel> looks fine though
[20:00]  * Quintasan wonders why introduce dep-5 if you have no parsing for it
[20:01] <Quintasan> It's like, useless now
[20:02] <Quintasan> yofel,apachelogger: symbols are needed only for libs that export public fuctions, right?
[20:02]  * Quintasan has no idea how to determine whether library does that or not
[20:03] <apachelogger> every library does that
[20:03] <yofel> uhm, if it doesn't have anything public you won't have any public symbols either...
[20:03] <apachelogger> there are only public interfaces
[20:04]  * yofel is in weekend-leathargy mode and has his brain on powersave
[20:04] <Quintasan> SO
[20:04] <Quintasan> how the hell do I know that about homerun?
[20:04] <yofel> does it ship headers?
[20:04] <yofel> if there are no headers, nothing will link against the lib and you don't need a symbol file
[20:04] <Quintasan> some
[20:04] <Quintasan> usr/include/homerun/abstractsource.h
[20:04] <Quintasan> usr/include/homerun/homerun_export.h
[20:04] <Quintasan> usr/include/homerun/pathmodel.h
[20:04] <Quintasan> usr/include/homerun/sourceconfigurationwidget.h
[20:04] <apachelogger> that there is a much saner policy ... every library that has header files associated with it needs to have a symbols file ;)
[20:05] <yofel> homerun_export.h -> you can't get anymore public than that
[20:05] <apachelogger> yofel: that is technically a false statement
[20:05] <yofel> well, I meant nothing not from the same package...
[20:05] <Quintasan> AFAIR pdebuild should yield something about missing symbols file but I didn't get that
[20:05] <apachelogger> e.g. qt has api that is not in an installed header but comprises interfaces that an application having the headers will be able to link against
[20:06] <apachelogger> that what qtcreator does
[20:06] <yofel> ... fun
[20:06] <Quintasan> yofel: Your definiton of "fun" is definitely weird
[20:06] <Quintasan> :P
[20:06] <yofel> well, I know I'm weird. I like things that don't work :P
[20:07] <Quintasan> I like things that work after you kick them
[20:09] <Quintasan> yofel, apachelogger: should I use pkgkde-gensymbols magic or just use dpkg-gensymbols?
[20:10] <yofel> if it's c++ use pkgkde
[20:11] <Quintasan> yay for homerun
[20:36] <Quintasan> apachelogger, yofel: dget -xu http://people.ubuntu.com/~quintasan/uploads/homerun_0.1.0-0ubuntu1.dsc
[20:36] <Quintasan> I need review
[20:45] <yofel> Quintasan: can you please add a comment to override_dh_auto_test so whoever looks at the package in a year from now still knows why they're disabled?
[20:46] <yofel> and maybe put the libs into the libs section
[20:46] <yofel> looks fine otherwise
[20:48] <Quintasan> yofel: Like adding Section: libs to the binary packages or put the whole source package into libs?
[20:49] <yofel> the former (the libs should be in libs, the plasma widget in kde, not sure about the source)
[20:55] <shadeslayer> Quintasan: don't forget to send me a merge request for the homerun daily packages 
[20:56] <Quintasan> sure
[20:56] <Quintasan> will upload somewhere to LP
[21:08] <Quintasan> shadeslayer: uhh, I can't branch https://code.launchpad.net/~blue-shell/homerun/packaging for some reason, want me to bzr init my packaging, upload it to my lp space and request a merge?
[21:09] <shadeslayer> bzr branch lp:~blue-shell/homerun/packaging doesn't work ?
[21:10] <shadeslayer> odd ...
[21:11] <Quintasan> ssh_exchange_identification: Connection closed by remote host
[21:11] <Quintasan> ConnectionReset reading response for 'BzrDir.open_2.1', retrying
[21:11] <Quintasan> ssh_exchange_identification: Connection closed by remote host
[21:11] <Quintasan> bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist. 
[21:11] <shadeslayer> whaaa ... 
[21:12] <shadeslayer> Quintasan: nevermind then, will check your package later then 
[21:12] <Quintasan> yofel: I fixed the things you mentioned, uploading to raring
[21:13] <yofel> \o/
[21:13] <Quintasan> better testbuild once again
[21:17] <Quintasan> yofel, shadeslayer: uploaded to raring-proposed, the bug #1078889 should get closed automagically soon
[21:17] <yofel> why -proposed?
[21:17] <shadeslayer> kool
[21:18] <Quintasan> yofel: That's how raring works
[21:18] <yofel> but you didn't really put that into the changelog, right?
[21:18] <Quintasan> First it goes to proposed then is copied to raring AFAIR
[21:18] <Quintasan> ofc I did not :P
[21:18] <yofel> ok, then I just misunderstood ;)
[21:22] <yofel> (note that the bug is only closed when it's published in RELEASE)