[00:18]  * apachelogger blinks at Riddell
[00:32] <Riddell> shadeslayer: that's cos 4.12 is first
[00:32]  * Riddell bats eyelids at apachelogger 
[00:33] <apachelogger> I thought .12 aint gonna make alpha1?
[00:33] <shadeslayer> think again *presses red button of doom*
[00:33] <apachelogger> ohhohohohohohho
[00:33] <apachelogger> problem
[00:34] <apachelogger> rekonq bookmarksies don't get imported into fireringdingding it seems
[00:34] <shadeslayer> Nooooooooooooooooooooooooo
[00:36] <apachelogger> not sure how to make that happen
[00:37] <ahoneybun_> ping valorie
[00:38] <apachelogger> 'Ubuntu 13.10 should be upgraded to LTS status'
[00:38] <apachelogger> lawl
[02:50] <valorie> hi ahoneybun_
[02:52] <valorie> jussi: I've heard a person on #kubuntu asking where our merch is on the website
[02:53] <valorie> so perhaps whip up a link on the main page this time?
[02:53] <valorie> Riddell: got my cards!
[02:53] <valorie> \o/
[02:53] <valorie> thank you
[03:06] <ahoneybun> valorie: ping
[03:07] <valorie> o/
[03:07] <valorie> I said hello earlier, but you must have pinged out
[03:08] <valorie> you sounded pretty happy last night!
[03:08] <ahoneybun> Yea away and did not mark away
[03:08] <ahoneybun> But of course
[03:08] <ahoneybun> You got us a space on user base
[03:08] <valorie> once we got a few pages the way we want them, I'll write to the translators
[03:09] <valorie> so once you take off the "under construction" thingie
[03:09] <valorie> then the tools auto-mark it ready for translation
[03:09] <ahoneybun> I got the welcome main and basic pages over
[03:09] <ahoneybun> Also made a card on trello
[03:09] <valorie> awesome
[03:10] <ahoneybun> Userbase.KDE.org/kubuntu
[03:11] <ahoneybun> Yep
[03:11] <ahoneybun> Amazing this mediawiki
[03:11] <valorie> when I click the basic link, I get to https://wiki.kubuntu.org/Kubuntu/KubuntuDocs/Basic
[03:12] <valorie> it really is awesome, yes
[03:12] <ahoneybun> Got to fix then links
[03:12] <valorie> Welcome too
[03:12] <ahoneybun> Yea
[03:13] <valorie> ok, as long as you know
[03:13] <ahoneybun> Yea
[03:13] <ahoneybun> Thanks
[03:13] <ahoneybun> But amazing work valorie 
[03:13] <ahoneybun> Getting us a spot
[03:14] <valorie> that was fun
[03:14] <valorie> getting us connected feels great
[03:14] <ahoneybun> Yea we are all a whole
[03:15] <valorie> I agree
[03:15] <ahoneybun> Brb
[03:15] <valorie> and it's good for everyone here to get used to working directly with KDE
[03:18] <ahoneybun> Media wiki is much more powerful
[03:19] <ahoneybun> But not too much of a stretch for new comers
[04:03] <ahoneybun_> mediawiki and moinmoin share somethings in common
[04:13] <valorie> sure, both wikis, but beyond that?
[04:25] <ahoneybun_> valorie: beyond?
[04:26] <valorie> sec
[04:31] <manchicken> apachelogger: JonT came and saved the day on that apt-pkg deprecation warning.
[04:31] <ahoneybun_> g2g 
[04:32] <manchicken> I've gotten that out and I now have no warnings in libqapt with my changes.
[04:43] <frank1> who knows how to get  wifi working  for hp f4500?
[04:44] <valorie> frank1: sorry, support is in #kubuntu
[04:45] <valorie> manchicken: awesome
[04:45] <valorie> so have you submitted it to reviewboard yet?
[04:47] <manchicken> Still running through tests.
[04:48] <manchicken> I'm wondering if anybody's going to have time to help test it.
[04:48] <valorie> you are being very thorough
[04:53] <manchicken> Yeah, I submitted many of my changes before to apachelogger just to find out that I completely failed to see something. Just learning from my mistakes :)
[04:53] <manchicken> C++ is my weakest language, and I'm not going to get better by making the same mistakes again and again :)
[05:04] <valorie> heh
[05:37] <manchicken> krazy2 has found a bunch of stuff in libqapt.
[05:37] <manchicken> Most of it was there when I got there, I'm trying to decide whether or not I need to fix the issues since they're legacy.
[05:41] <manchicken> I got the QPointers bit in for modal dialogs opened via exec(), that seemed like an important one.
[06:35] <wifistinks> hello???
[08:26] <lordievader> Good morning.
[08:30] <prem_> hi
[08:30] <lordievader> Hey prem_ 
[08:30] <prem_> how much ram is reqd. to install kubuntu
[08:30] <prem_> 64 biy
[08:31] <prem_> 64 bit
[08:31] <lordievader> prem_: User support is in #kubuntu.
[08:31] <prem_> oh..
[08:32] <lordievader> prem_: This tells me 1GB is recommended: http://en.wikipedia.org/wiki/Kubuntu#System_requirements
[08:33] <prem_> thanks but i was looking for 64 bit distribution because for ubuntu 64 bit requires minimum of 2gb ram
[08:36] <lordievader> prem_: Sounds reasonable. The bare minimum is probably somewhere around there, 1~2Gb of ram. But please join #kubuntu for support, I'm in there too ;)
[09:25] <waliarubal> can anyone tell me advantages over standard ubuntu?
[09:26] <waliarubal> anyone?
[09:26] <waliarubal> I am pretty bored from Ubuntu now and need a change in distro.
[09:27] <waliarubal> no one can answer my question? :(
[09:27] <tsimpson> KDE SC, that's an advantage in itself
[09:29] <waliarubal> tahnks simpson. can u please tell me something about KDE SC and its advantages? please
[09:29] <tsimpson> is a different UI and is generally more configurable than most other desktop environments
[09:30] <tsimpson> it looks nice too
[09:30] <lordievader> For me the biggest advantage is that I can find things. Unity seems to hide a lot of things.
[09:30] <waliarubal> sounds good, actually I have a dual monitor coniguration and I am also a gamer.
[09:31] <waliarubal> Yes, unity hides a lot... twisted part by canonical. :(
[09:31] <waliarubal> I generally game, program and watch movies. that's what I do. earlier I used to be windows user, but now I use Linux because of freedom.
[09:32] <waliarubal> I guess KDE has looks like windows also?
[09:33] <tsimpson> it can look like whatever you want, but its default look is not dissimilar to how windows looked before they went all metro
[09:34] <waliarubal> sounds good, maybe I shall switch to it.
[09:34] <waliarubal> Thanks a lot simpsons and dievader.
[09:35] <waliarubal> can you guys help me with a problem too? actually I have Canon LBP3000 printer and I can't make it work under linux. It worked perfect under windows.
[09:36] <waliarubal> Canon support is worst.. they haven't answered any questions. maybe you geeks can help.???
[09:37] <waliarubal> anyone of you GEEKS.... help???
[09:37] <lordievader> waliarubal: Kubuntu support is in #kubuntu. Canon isn't know for their Linux support I'm afraid.
[09:38] <waliarubal> sounds bad... but I just can't throw away my piece of hardware. any help will be appreciated.
[09:38] <waliarubal> Maybe I will setup KUbuntu today, in that also I will need printer installation.
[09:38] <lordievader> waliarubal: Join #kubuntu ;)
[09:39] <waliarubal> Ya, I will install K ubuntu today.
[09:40] <waliarubal> so now I expect help from u guys on my printer installation. :)
[09:41] <lordievader> waliarubal: Like I said, join the channel #kubuntu for support. This is not a support channel.
[09:42] <waliarubal> Thanks vader. much appreciated.
[09:42] <waliarubal> bby, thanks all for ur time. :D
[09:56] <apachelogger> yofel: piiiiiing
[09:57] <apachelogger> yofel: kf5 is now split... so I started wondering ... why exactly does each neon branch have the full debian/ shebang
[09:58] <apachelogger> oh wait, launchpad can't do tempalte processing
[09:58]  * apachelogger rolls eyes
[09:59] <apachelogger> yofel: different question ... what do you think about moving the 3000 new repositories to builder and use *one* template debian/ to create them
[10:00] <yofel> what do you mean? In neon4, we had a 'dummy-ubuntu' branch that we took for each package and simply regex replaced the new package names to have a new packaging branch
[10:00] <yofel> neon5 had that too IIRC
[10:00] <apachelogger> right but you still had 3000 branches with packging
[10:00] <apachelogger> what I am proposing is something like kde-l10n-common
[10:01] <yofel> that needs non-launchpad pre-processing which we couldn't do back then
[10:01] <apachelogger> one branch that is regex-subbed at build time to the actual package
[10:01] <apachelogger> yofel: yeah, so what do you think about doin git now xD
[10:01] <apachelogger> because to me maintaining 30000 former kdelibs packages/branches/projects seems like a major hassle
[10:04] <yofel> just so I understand this right, you essentially want to deprecate the branches *and* the recipes?
[10:05] <apachelogger> I want to deprecate launchpad really :P
[10:05] <yofel> well, sure, we can do this all by ourselves, if you go and provide the infrastructure
[10:05] <apachelogger> already there :P
[10:06] <apachelogger> it's just very much hand crafted towards neon
[10:06] <apachelogger> which ain't a bad thing, just saying ;)
[10:07] <yofel> well, I don't really care what builds the packages and how they get to the PPA really, as long as there's a way to edit it and run it manually
[10:08] <apachelogger> right
[10:08] <apachelogger> there has been talk of a general purpose build infrastructure btw
[10:49] <yofel> anyone else getting http://paste.kde.org/p32313f5e when trying to open a mail print preview in kmail?
[10:55] <Riddell> jose: how's the feature tour?
[11:31] <apachelogger> yofel: http://paste.ubuntu.com/6593706/
[11:41] <Peace-> Riddell: btw do you know how to start a nested session of plasma-desktop ?  this doesn't work :S  Xephyr :1 -screen 1280x800 & sleep 3 && export DISPLAY=:1 && plasma-desktop
[11:41] <Peace-> with plasma-netbook instead works
[12:13] <BluesKaj> 'Morning all
[14:24] <Riddell> !testers | alpha 1 candidates need testing
[14:25] <shadeslayer> will have a look
[14:26] <BluesKaj> Riddell, alpha 1 is out today ? thought tomorrow was the release day.
[14:26] <soee> :O
[14:26] <soee> i shall test it later at home after gym
[14:42] <shadeslayer> Riddell: might be useful to have muon on the CD btw
[14:42] <shadeslayer> unless muon-updater works, in which case, it's fine
[14:43] <shadeslayer> Riddell: link to CD's missing :)
[14:46] <BluesKaj> no alpha images available in https://wiki.kubuntu.org/TrustyTahr/Alpha1/Kubuntu
[14:46] <soee>  smartboyhw is on the testers list but isnt he inactive since unknown date?
[14:46] <soee> *till
[14:46] <soee> as he studing hard ? :)
[14:47] <shadeslayer> http://iso.qa.ubuntu.com/qatracker/milestones/309/builds/59389/downloads
[14:47] <shadeslayer> http://iso.qa.ubuntu.com/modules/qatracker/misc/cdrom.png
[14:47] <shadeslayer> http://iso.qa.ubuntu.com/qatracker/milestones/309/builds/59391/downloads
[14:50] <Riddell> BluesKaj: needs testing
[14:51] <Riddell> shadeslayer: do you think muon-updater isn't working?
[14:51] <shadeslayer> It wasn't working on Netrunner Saucy
[14:51] <shadeslayer> and it had muon from Ubuntu archives
[14:51] <Riddell> didn't we fix the problems with muon?
[14:51] <Riddell> we did a load of post-release fixes
[14:51] <shadeslayer> plz check if muon-updater works in Trusty
[14:52] <shadeslayer> I can't because I've screwed up my muon install somehow
[15:00] <BluesKaj> muon-updater works here shadeslayer, Riddell, says trusty system is up to date
[15:00] <shadeslayer> okay then
[15:00] <shadeslayer> idk why, but it didn't work on a derivative
[15:00]  * shadeslayer needs to SRU
[15:01] <Riddell> yeah we had that bug at release
[15:01] <Riddell> but (I hope) we fixed it as an SRU
[15:01] <BluesKaj> shadeslayer, netrunner doesn't use all the same repos as kubuntu , it restricts a few , but i can't recall which ones
[15:02] <shadeslayer> BluesKaj: it was a bug in muon
[15:02] <shadeslayer> which Aleix fixed
[15:06] <BluesKaj> shadeslayer, does the first url you posted above contain the alpha-1 image ?
[15:06] <shadeslayer> BluesKaj: yes
[15:06] <BluesKaj> shadeslayer, ok thanks
[15:08]  * BluesKaj wonders how different it is than yesterday's daily build
[15:24] <ahoneybun> valorie: ping
[15:25] <shadeslayer> ScottK: Riddell muon in saucy-proposed
[15:25] <shadeslayer> bug 1261812
[15:56] <shadeslayer> Riddell: installer keeps throwing up errors
[15:56] <shadeslayer> and crashed
[16:12] <Riddell> shadeslayer: err
[16:12] <Riddell> what sort of errors?
[16:15] <apachelogger> hm
[16:16] <apachelogger> xnox: I think your cmake upload broke something
[16:16] <apachelogger> xnox: https://launchpadlibrarian.net/160121636/buildlog_ubuntu-trusty-i386.project-neon5-dbusmenu-qt_0.0%2Bbzr20131218%2Br255%2Bneon20~ubuntu14.04.1_FAILEDTOBUILD.txt.gz
[16:17] <apachelogger> happens with every package apparently
[16:17] <apachelogger> kdelibs for example https://launchpadlibrarian.net/159748514/buildlog_ubuntu-trusty-amd64.project-neon5-kdelibs_0.0%2Bgit20131214%2Br97583~de0aa0b%2Bneon12~ubuntu14.04.1_FAILEDTOBUILD.txt.gz
[16:17] <xnox> apachelogger: possible.
[16:18] <xnox> apachelogger: can you point me to the actual source/build-record instead of the logs?
[16:18] <xnox> apachelogger: there is no way to go from the build-log back to the actual build-record.
[16:18] <xnox> apachelogger: can  you open about against cmake with links to source-package builds and assign it to me?
[16:19] <apachelogger> can do
[16:19] <apachelogger> https://code.launchpad.net/~neon/+archive/kf5/+build/5362429
[16:19] <apachelogger> also happens regardless of architecture
[16:20] <xnox> apachelogger: do you also have a link to a previously working build for comparison what's "good" ? such that I don't hunt red-herrings
[16:20] <apachelogger> xnox: https://code.launchpad.net/~neon/+archive/kf5/+build/5323961
[16:21] <apachelogger> oh wait, that';s saucy
[16:21] <apachelogger> xnox: https://code.launchpad.net/~neon/+archive/kf5/+build/5323959
[16:21] <apachelogger> this one is trusty ^^
[16:22] <Riddell> running archive-upload script for 4.12.0 to trusty
[16:22] <xnox> apachelogger: could it be just new cmake upstream release regression though? i'll try with my patches reversed.
[16:23] <apachelogger> xnox: possible but unlikely, agateau has the same version (built from source) and cannot reproduce the issue
[16:23] <xnox> ack.
[16:24] <apachelogger> bug 1262273
[16:24] <apachelogger> agateau: ^ in case you want to subscribe as well
[16:25] <xnox> apachelogger: does project neon builds it's own qt5?
[16:25] <xnox> apachelogger: and is it multiarched like the stock qt5 in ubuntu?
[16:26] <manchicken> apachelogger: Should I fix all of the krazy2 findings in libqapt, you think?
[16:26] <xnox> apachelogger: cause in my tool chain I set an explicit path to qt5::moc
[16:26] <agateau> apachelogger: does the cmake package has any patch?
[16:26] <xnox> apachelogger: is proejct-neon-qt5 multiarched?
[16:27] <xnox> apachelogger: if it isn't you are really ought to build project-neon-cmake, as cmake package in the distribution has been tailor specifically to the qt5 package as shipped in ubuntu.
[16:28] <apachelogger> hm
[16:28] <xnox> apachelogger: i think there are variables that you can export to make it act more like stock "cmake", i've made sure there is a fallback, but it's rather "opt-out" kind of thing as by default i enabled cross-compilation without modifying all sources.
[16:28] <apachelogger> that's a bug
[16:28]  * apachelogger puts on his kde developer hat
[16:28] <xnox> apachelogger: what is the full path to "moc" in qt5? as in not the qtchooser one.
[16:28]  * xnox adjusts my kubuntu-developer badge
[16:29] <apachelogger> when working on kde libraries I often want to have my own qt build, this is not working properly on ubuntu :P
[16:29] <apachelogger> xnox: /opt/project-neon5/bin/moc
[16:30] <apachelogger> http://paste.ubuntu.com/6595065/
[16:30]  * xnox points out, that the correct interface, is to explicitely set QT5::moc in that case, in your toolchain file used for custom/prefix installed system libraries, as advised by CMake.
[16:31] <xnox> apachelogger: you are pointing to the last resort path. in cmake there is Qt5::moc already set to a different location.
[16:31] <apachelogger> Oo
[16:31] <xnox> (as in the code path before that paste)
[16:31] <apachelogger> why?
[16:31]  * apachelogger fails to compute this just now xD
[16:32] <xnox> apachelogger: because the one generated at qt5 package build-time is always wrong for the cross-compile case on Debian OS.
[16:32] <apachelogger> I think the solution is to fix the qt5 cmake config, not hardcode stuff into cmake?
[16:32] <xnox> apachelogger: thus, it's adjusted to the right one. Which is also, a wild guess, if you don't happen to use stock-cmake with stock-qt5. Both of them are failing to guess it at all times.
[16:33] <xnox> i can guard my changes better, but your are exploiting implementation details of cmake here.
[16:33] <xnox> and it's sad to see that project-neon is diverging so much.
[16:34] <apachelogger> it's exploiting the fact that cmake is not supposed to hardcode stuff :P
[16:34] <apachelogger> as for neon diverging ... ultimately (in my dreams) I'd like to have it running on actual production packaging
[16:35] <xnox> apachelogger: wrong. in CMake one should use a Toolchain file for any non-standard locations. Actual modules are, last fallback, not the first look up.
[16:35] <apachelogger> so you have a rolling packaging so to speak and at release time you simply branch the latest version and have your ready to go release packaging
[16:35] <xnox> apachelogger: if toolchain file sets all variables, none of the Find* foo modules are loaded, nor executed.
[16:35] <xnox> apachelogger: please start using multiarch qt5 packaging then.
[16:36] <apachelogger> I'll put it on my todo
[16:36] <xnox> cause at the moment one can co-install qt5:i386 and qt5:amd64 which doesn't look possible with project-neon at all.
[16:37] <xnox> apachelogger: when you'll do that, you will find your automoc broken, fyi ;-)
[16:40] <xnox> apachelogger: what's your pkg-config? what's your location of .pc files? this should be passed to CMake via Toolchain file!
[16:42] <apachelogger> export PKG_CONFIG_PATH := $(NEONDIR)/lib/pkgconfig:$(NEONDIR)/lib/$(DEB_HOST_MULTIARCH)/pkgconfig:$(PKG_CONFIG_PATH)
[16:42] <apachelogger> xnox: build foo is here http://bazaar.launchpad.net/~neon/project-neon5/project-neon5-runtime/view/head:/opt/project-neon5/share/pkg-project-neon5/0/default-settings.mk
[16:43] <xnox> apachelogger: cmake_defaults and all the LD_LIBRARY_PATH, PKG_CONFIG_PATH, QT_PLUGIN_PATH, QML2_IMPORT_PATH, are ought to live in a Toolchain file which is passed to CMake by default.
[16:44] <xnox> apachelogger: anything else is fragile, and is free to be changed by CMake both upstream and distribution.
[16:44] <xnox> apachelogger: a Toolchain file is the only contract-based interface to guarantee correct and expected compilation in CMake.
[16:45] <apachelogger> xnox: you should probably raise that at kde-buildsystem@kde.org because that is the actuall way they expect things to be done
[16:47] <xnox> apachelogger: Anybody who uses CMake and does reproducible builds is using Toolchain files (to e.g. enforce compiler versions / editions / pick this or that) it's pretty standard.
[16:47] <xnox> apachelogger: it's not my problem at all, that project-neon builds chooses to have non-deterministic builds.
[16:47] <apachelogger> ok
[16:48] <xnox> apachelogger: CMake upstream, and Qt upstream, and KDE upstream all support deterministic builds, for a given environment.
[16:48] <xnox> apachelogger: the one who picks the environment must provide a matching toolchain file to make it deterministic.
[16:51] <xnox> apachelogger: i took special care to honor and not break any existing users of toolchain files =/
[16:51] <xnox> apachelogger: this is very low priority, as it doesn't actually affect any packages build for the distribution, by the distribution provided sources.
[16:53] <xnox> apachelogger: don't get me wrong, it's "incompatability" between the two and all 4 parties can claim it's a bug in the other three. (parties being: upstreams qt, cmake, kde, ubuntu)
[16:53] <xnox> that's what toolchain files are for, to assert ones expectations.
[16:58] <lordievader> ahoneybun_: Ping
[16:59] <shadeslayer> Riddell: couldn't find errors in syslog
[16:59] <shadeslayer> so I restarted and it works now
[17:00] <Riddell> shadeslayer: what works?
[17:00] <shadeslayer> the installer
[17:00] <Riddell> shadeslayer: you started a fresh install and it completed without complaining?
[17:04] <shadeslayer> well, it's at 93% 
[17:06] <Riddell> kdeframeworks is split!
[17:06] <Riddell> now where do we have qt5 5.2 packages so I can try and build something?
[17:12] <shadeslayer> Riddell: kwalletd doesn't run here on the live cd
[17:15] <apachelogger> that's intentional I think
[17:15] <apachelogger> we casper that away
[17:15] <apachelogger> manchicken: judgement call, technically yes tho
[17:16] <apachelogger> sometimes excluding a check may be more appropriate though
[17:16] <shadeslayer> apachelogger: causes issues when trying to add a ktp account
[17:16] <apachelogger> http://techbase.kde.org/Development/Tutorials/Code_Checking#In-Code_directives
[17:16] <shadeslayer> why do we casper it away
[17:16] <apachelogger> shadeslayer: I do not know
[17:16] <apachelogger> mem consumption and stuff
[17:16] <apachelogger> and you'd get a popup to create a wallet in the past
[17:16] <shadeslayer> what is this, the 90's
[17:16] <apachelogger> tho it's le unnecessary
[17:17] <apachelogger> shadeslayer: yes, apparently people still bother with 1gib ram :P
[17:17] <apachelogger> or so my inbox says
[17:17] <shadeslayer> xD
[17:17] <shadeslayer> Since afiestas is writing us PAM integration, it won't be necessary at some point I think
[17:31] <shadeslayer> oh what fun : http://i.imgur.com/AznluXM.png
[17:32] <apachelogger> stop having fun and get some work done :@
[17:32] <apachelogger> that looks excitingly broken
[17:32] <shadeslayer> I think the video driver is broken
[17:32] <shadeslayer> not KDE's fault ( it's using nouveau )
[17:33] <shadeslayer> seeing such artifacts all over the place
[17:40] <Riddell> woo, karchive from kf5 is looking good
[17:47] <manchicken_> I think I'm going to ignore the pre-existing d-pointer issues in a couple of the classes, but I'll update the explicit constructors.
[17:48] <manchicken_> The d-pointer stuff seems like it'll be a much larger risk in the change.
[17:48] <apachelogger> mind the binary compatibility
[17:50] <manchicken_> Isn't explicit just a compile-time check?
[17:50] <shadeslayer> manchicken_: y u no post patches to RB
[17:50] <manchicken_> shadeslayer: Still cleaning up
[17:50] <shadeslayer> okay
[17:50] <manchicken_> And what I've ended up doing here is much bigger than just a single patch.
[17:51] <manchicken_> sourceslist.cpp got a lot of work done on it.
[17:51]  * Riddell high fives manchicken_ 
[17:51] <manchicken_> :)
[17:52] <manchicken_> I kinda took the approach that the maintainer needed to step away from this library, he had conceded there were some issues, so I just kinda took over a little bit.
[17:54] <manchicken_> There may already be binary compatibility issues, which is why I've been trying to get someone who maintains a package depending on this library to jump in and help me verify that I haven't broken their world (or if I have, where).
[17:55] <shadeslayer> Riddell: full install looks good
[17:55] <Riddell> manchicken_: just look at the symbol files?
[17:57] <manchicken_> I guess I could do that, just compare the current version with the existing one.
[17:57] <vet> hi there
[17:57] <manchicken_> That said, most of the dependencies (muon included) seem like they should be updated to take advantage of the new functionality in this version, namely tracking separate sources.list files.
[17:59] <manchicken_> But I suppose that's probably a future task given all of the things likely going on in muon.
[18:00] <Riddell> hi vet 
[18:00] <vet> having some wifi issues on Kubuntu. After rebooting the wifi doesn't connect as it appears with no key on the configuration menu. 
[18:00] <Riddell> vet: user support in #kubuntu (I'm afraid I don't know a quick answer)
[18:01] <vet> thank you very much Riddell ;)
[18:02] <vet> first time I install kubuntu and I am way lost... :S
[18:03] <shadeslayer> apachelogger: do you have a regex handy for that upstart version parsing?
[18:04] <apachelogger> lol, no?
[18:04] <apachelogger> I don't even know what the string looks like
[18:04] <apachelogger> because dat code was shit :P
[18:05] <apachelogger> split.strip.chop.setsize.join.yourmom.yolo.morestringoperations.meow.bad.kitteh.toInt()
[18:07] <shadeslayer> :|
[18:12] <manchicken_> I don't think that I broke binary compatibility compared to the stable version of libqapt running right now... but it's in no way binary compatible with the unreleased 2.1 version JonT was working on before.
[18:23] <manchicken_> apol is my new favorite person.
[18:23] <xnox> apachelogger: i'm deeply upset and pissed off about your email message, which puts my conversation with you here, out of context, in the spotlight, with widely exaggerated claims.
[18:23]  * vHanda should switch off alerts for spotlight
[18:23] <xnox> apachelogger: none of my cmake changes are complete, and are only known to not regress native compilation against system libraries for a wide subset of packages (~20% of the archive) whilst at the same time enabling as less intrusively as possible a really cool feature.
[18:24] <xnox> apachelogger: you on the other hand, give me what, an irc conversation and a bug report and no time to review, respond, code, prototype and fix a bug in an unstable distribution code-named trusty, which is yet to do any milestone release.
[18:25] <xnox> apachelogger: yet, implying that it's the final state and final implementation of 14.04 LTS.
[18:25] <xnox> apachelogger: i will respond to that email, but on my own time, not by your schedule.
[18:26] <xnox> apachelogger: i'm off to volleyball now, and will return to computers tomorrow GMT time.
[18:27] <xnox> apachelogger: do note, that no toolchain changes are validated until full archive rebuild, which has not happened for trusty yet.
[18:27] <xnox> apachelogger: as kubuntu/ubuntu developer, i would have expected you to know better.
[18:27] <apachelogger> xnox: upsetting was not intended, sorry for that
[18:27] <xnox> apachelogger: appologies are accepted. i'll calm down and respond in calm manner.
[18:27] <apachelogger> see you tomorrow and have fun at volleyball
[18:28] <xnox> apachelogger: but i'm already getting personal messages and attacks from unknown to me people about this.
[18:28] <xnox> apachelogger: see ya =)
[18:52] <apachelogger> !find xmllint
[18:58] <shadeslayer> manchicken: fwiw I talked to Aleix today and he says that there is a file search API in libqapt
[18:58]  * shadeslayer will have another look 
[18:58] <shadeslayer> apachelogger: updated
[18:59] <manchicken> shadeslayer: I wonder if it is just using the libapt-pkg interfaces consumed by libqapt.
[18:59] <manchicken> I looked through the code and didn't see anything that looked like that, but I could be wrong. It's not a huge codebase, but it's not tiny either.
[19:03] <shadeslayer> *nod*
[19:03] <shadeslayer> apachelogger: see RB
[19:03] <apachelogger> unicorns
[19:03] <apachelogger> so much betterz
[21:22] <ahoneybun> ping valorie
[21:22] <Riddell> why don't you come on over valorie?
[21:23]  * Riddell votes for Tm_T for Ubuntu IRC Council
[21:23] <ahoneybun> hey Riddell
[21:31] <ahoneybun> Riddell: is it ok if I fix the link on http://www.kubuntu.org/community/contribute linking to https://wiki.kubuntu.org/Kubuntu/Documentation ?
[21:51] <Riddell> apachelogger: of course
[22:04] <Quintasan> shadeslayer: KTp 0.7.0 in PPA for saucy
[22:04] <Quintasan> thoughts?
[22:11] <Quintasan> shadeslayer: wait, we do have it
[22:11] <Quintasan> I'm dumb and can't filter by release
[22:15] <Riddell> Quintasan: does ktp need synced in trusty?
[22:16] <Quintasan> Nope
[22:16] <Quintasan> It's 0.7.0 in trusty alright
[22:16] <Quintasan> and we have 0.7.0 in ppa for saucy
[22:16] <Quintasan> I just couldn't find it since I filtered by the wrong release.
[22:20] <Riddell> ah but it would be synced with debian
[22:47] <ahoneybun> Riddell: I did not see a answer if you did
[22:50] <Riddell> ahoneybun: of course
[22:51] <Riddell> sorry bad tab competion
[22:51] <ahoneybun> ok cool
[22:52] <ahoneybun> I'll work on it when I get home I'm porting more docs over
[22:52] <ahoneybun> the software page is the last one I think
[22:59] <xnox> Riddell: was the alpha1 block lifted? or are all of those kde packages are for the alpha1 images?
[23:02]  * Riddell publishes http://www.kubuntu.org/news/kde-sc-4.12
[23:03] <Riddell> xnox: I'm hoping they'll be caught by the block
[23:04] <xnox> Riddell: =/ did you check that. i think most of it will. anyway not helping alpha1, cause now for all of these packages you have no option to upload bugfix & respin with it. you'll have to go with 4.12 or release-note bugs =( so i'm a bit surprised you traded "respins option" for upload 4.12 now, instead tomorrow / friday.
[23:05] <xnox> Riddell: on the other hand if kubuntu alpha1 images are all dandy good =) then all is good.
[23:05] <xnox> Riddell: it's just doesn't look co-ordinated to me.
[23:07] <Riddell> xnox: I had to get those .orig in the archive so we can get the packages into backports PPA without taking up many GB of disk space and have them released promptly
[23:08] <Riddell> xnox: but I'm not sure I see a problem, if we do need to upload a package we can just delete the one in -proposed and upload the bugfix instead
[23:08] <Riddell> I guess there will be a dependency chain for some of them on the relevant library
[23:11]  * Riddell snoozes
[23:23] <xnox> Riddell: yeah, you could cowboy it. just ugly =)