[00:29] <valorie> hmmm, upon updates and rebooting, my weird second screen came back
[00:30] <valorie> very odd that kscreen keeps ignoring my settings, and just as weird that it thinks I have two screens on my one laptop
[00:39] <shadeslayer> ScottK: not new, someone ( possibly me ) didn't update the lib version in the 2.1 release because we needed 2.1 out ( the install file is exactly the same as 2.1 ) 
[00:43] <shadeslayer> yep, I didn't bump it in 2.1
[02:06] <manchicken> 'evening.
[02:31] <ahoneybun> hey man
[02:31] <ahoneybun> manchicken, 
[02:35] <manchicken> hiya
[02:49] <manchicken> Man, Muon is really messed up, no?
[02:49] <manchicken> Trying to do updates it screws up this environment.
[02:50] <manchicken> I suppose it's possible that this libqapt testing I've been doing may have borked something in my environment, but this just seems odd.
[03:24] <manchicken> Anybody seen JonT in a while?
[03:58] <manchicken> apachelogger: I'm thinking for the libqapt stuff, I'm probably going to refactor things a bit. I'm going to go into the SourcesListPrivate class group entries with files, and I'm going to then make the SourcesList::save() method iterate through each file and perform the save on that file individually.
[04:31] <valorie> I tried to build the new muon branch but ran into errors
[04:31] <valorie> and got no reply here
[04:32] <manchicken> What kind of errors?
[04:33] <manchicken> I wonder if the new Muon is using the new libqapt.
[04:38] <valorie> I'll have to try to make again; cloning and changing branches worked fine
[04:38] <valorie> maybe my cmake line was wrong, but I asked here and got no answer
[04:38] <valorie> I used cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=DebugFull in the build folder
[04:42] <manchicken> Well I'd need to see what your error is. Also, keep in mind that this is a global team and timezones are very much in place.
[04:42] <valorie> http://pastebin.kde.org/pr2orntvc
[04:42] <manchicken> Have you sent anything to the mailing list?
[04:42] <valorie> oh yes, I know
[04:42] <valorie> I wasn't sure that testing would still be useful
[04:42] <valorie> I did get updates to muon today
[04:43] <valorie> from apt-get
[04:43] <valorie> anyway, had stuff every night this week, so testing time has been a bit short
[04:44] <manchicken> Do you have libqoauth1 and libqoauth-dev installed? I've never built muon, but that is what I would look at with that build error
[04:44] <valorie> I think this is the weekend of the bughunt in Munich? too
[04:44] <valorie> ah, I'll try that
[04:45] <manchicken> It could be.
[04:45] <valorie> I did apt-get install build-essential muon
[04:45] <manchicken> For me, this is the weekend of geocaching in Woodbridge, VA :)
[04:45] <manchicken> Yeah, you are going to be missing a bunch of dev packages.
[04:46] <manchicken> http://techbase.kde.org/Getting_Started/Build/Distributions/Debian
[04:46] <valorie> build-essential should pull those in, correct?
[04:47] <valorie> I was missing the dev package
[04:47] <valorie> pfff
[04:47] <manchicken> No
[04:48] <manchicken> Build essential only pulls in the essentials
[04:49] <manchicken> Do a show on the package
[04:50] <valorie> like apt-cache show muon?
[04:50] <valorie> or what
[04:51] <valorie> I just pulled in libattica, libbodega, and something else
[04:51] <valorie> libqapt-dev
[04:51] <manchicken> I use aptitude
[04:52] <valorie> hmmm, I got all the bodega packages, but it isn't finding them
[04:52] <valorie> but it does find the other stuff I just pulled in
[04:52] <valorie> odd
[04:52] <valorie> anyway, those are non-essential
[04:53] <valorie> so just sudo make install?
[04:53] <valorie> or make && sudo make install
[04:53] <valorie> I never know which to use
[04:55] <manchicken> They're non-essential for building in general.
[04:55] <manchicken> I wouldn't recommend building source package and installing them along-side binary packages.
[04:56] <manchicken> Especially for things involving package management.
[04:56] <valorie> Riddell said it would just overwrite the binary package
[04:56] <manchicken> I've been doing some work on libqapt, and I'm tellin' ya, it's really easy to screw up your environment that way.
[04:56] <valorie> but that is why I was a bit leery of charging ahead with no guidance
[04:56] <valorie> i build Amarok locally
[04:56] <manchicken> What's your purpose?
[04:57] <manchicken> Are you planning on maintaining the package?
[04:57] <valorie> to test the new branch
[04:57] <valorie> oh hell no
[04:57] <valorie> I don't code
[04:57] <manchicken> I'd be very careful of doing that on your daily driver.
[04:57] <manchicken> You may want to use a virtualbox instance or run things on a test system.
[04:57] <valorie> I haven't hurt my system with the headers I've just installed
[04:58] <manchicken> The hard part about the package management stuff is that you've got so many different hands in the cookie jar that it can become difficult to determine which one broke the jar.
[04:58] <valorie> but i think I'll take your advice and not build the branch package
[04:58] <valorie> indeed
[05:02] <valorie> thanks for your advice, manchicken
=== nhandler_ is now known as nhandler
[05:15] <manchicken> Sorry, I was doing the dishes.
[05:16] <valorie> np
[05:18] <manchicken> apachelogger: I just thought of something... if I make the change I'm thinking to make, is it going to break other programs?
[05:18] <manchicken> I'm thinking it will...
[05:18] <manchicken> But I'm not sure if the new version of libqapt is going to do that anyway.
[05:18]  * manchicken speaks to apachelogger as though he were actually online...
[05:18] <valorie> manchicken: you can't make omelets without breaking eggs
[05:19] <valorie> but of course you gotta fix all those broken things!
[05:19] <manchicken> valorie: Yes, but in order to make an omelet it is important not to sit on the carton of eggs.
[05:19] <valorie> apachelogger didn't set himself away, therefore he is online
[05:19] <manchicken> apachelogger is always online.
[05:19] <manchicken> He isn't always responsive though :)
[05:19] <valorie> oh, I don't want to think of cleaning up such a mess in the real world
[05:20] <manchicken> Nor do I
[09:08] <lordievader> Good morning.
[10:14] <kubotu> ::workspace-bugs:: [1249557] kwin crashes on login @ https://bugs.launchpad.net/bugs/1249557 (by Scott Moore)
[11:43] <BluesKaj> Hiyas all
[12:16] <soee> good morning
[12:16] <lordievader> Hey soee, how are you?
[12:17] <soee> lordievader, hi im pretty good, you ?
[12:17] <lordievader> soee: I'm doing ok.
[13:18] <ovidiu-florin> is muon a KDE project?
[13:23] <debfx> it is hosted on KDE infrastructure so I guess yes
[13:36] <manchicken> Hiya
[15:53] <tester56> hi, I am gettings errors like "/org/freedesktop/UDisks2/drives/LITEONIT_LAT_128M2S_TW01KTD05508517B2925" : property "Drive" does not exist  
[15:53] <tester56> when starting applications like dolphin etc.  from konsole
[16:30] <tester56> any idea how to fix this?
[16:33] <mamarley> tester56: I get those too; I don't think it is anything to worry about unless something is actually not working.
[16:34] <tester56> i think it causes a bit of a slowdown
[16:34] <tester56> does not happen on opensuse and dolphin starts faster there :-(
[17:34] <ScottK> tester56: That's probably s udisk issue, not a KDE issue.
[17:38] <tester56> i tested the newer udisk2 in 14.04 ... same issue
[17:39] <tester56> on opensuse and the same version of kde and udisk2 i cannot reproduce the issue
[17:41] <ScottK> Hmmm.  Dunno then.
[20:30] <ScottK> Riddell (and anyone else who cares): Would you please look at what I wrote in https://blueprints.launchpad.net/ubuntu/+spec/core-1311-qt5-versions-in-ubuntu and see if you agree/have other ideas.
=== kameloso^ is now known as kameloso