[00:01] <apachelogger>     // FIXME: This code seems to be nonfunctional - it needs to be fixed somewhere (is it Qt BUG?)
[00:01] <apachelogger>     QDBusConnection::systemBus().connect(service, path, interface, name,
[00:01] <apachelogger>                                          q, SLOT(dbusFilter(const QDBusMessage &)));
[00:05] <apachelogger> Oo
[00:05]  * apachelogger sighs
[00:06]  * apachelogger cries
[00:08] <BarkingFish> morning guys :)  Just a quick check - is it ok for me to add untrusted ppa's into kubuntu while I'm beta testing?  The last thing I want to do is break stuff or wind up losing my install.
[00:11] <apachelogger> ppas are always a risk
[00:14] <BarkingFish> yeah, that's what I thought.  I'm looking to try hexchat as an irc client, since its url to browser capability isn't broken, like xchat's - but we don't have hexchat prepackaged.
[00:14] <BarkingFish> hexchat.org has it as a ppa though
[00:16] <apachelogger> BarkingFish: use konversatin
[00:16] <apachelogger> konversation
[00:16] <apachelogger> it has the best ever written url parser
[00:16] <BarkingFish> does konversation support sasl authentication?
[00:17] <BarkingFish> until april, I have to connect to IRC using Tor/Sasl, so whatever client I use needs to be able to handle sasl or i'm stuck
[00:17] <apachelogger> konversation can do all and everything
[00:18] <apachelogger> http://userbase.kde.org/Konversation/Configuring_SASL_authentication
[00:18] <apachelogger> they even have nice documentation
[00:18] <BarkingFish> right, that's definitely worth looking at then.  
[00:18] <BarkingFish> If it beats the hell out of xchat or quassel, I am sold :)
[01:44] <kubotu> ::qt-bugs:: [1131166] package libqt4-xmlpatterns 4:4.8.3+dfsg-0ubuntu3.1 failed to install/upgrade: cannot copy ... @ https://bugs.launchpad.net/bugs/1131166 (by kmkale)
[06:53] <soee> any idea why notifications or panel have no shadows ?
[09:11] <agateau> ScottK: apachelogger: just commented on bug 1092910
[09:12] <agateau> ScottK: the MI plasma does not have any maintainer right now, unfortunately
[10:14] <kubotu> ::workspace-bugs:: [1131647] Python version mismatches causes "Could not create script engine" errors @ https://bugs.launchpad.net/bugs/1131647 (by Cole Mickens)
[10:15] <Riddell> yay webkit compiled on arm
[10:15] <yofel_> c++ headers are missing though
[10:15] <shadeslayer> huzzah
[10:16] <yofel_>  /build/buildd/calligra-2.6.1/stage/part/ui/KPrHtmlExportDialog.h:26:29: fatal error: QtWebKit/QWebPage: No such file or directory
[10:16] <Riddell> yofel_: still?
[10:16] <yofel_> http://paste.kde.org/678212
[10:17] <yofel_> that's 2.3-0ubuntu2
[10:18] <Riddell> yofel: you mean it's missing QWebPage vs qwebpage.h?
[10:19] <yofel> yes
[10:20] <yofel> it's missing those capitalized c++-style headers
[10:21] <Riddell> yeah, let me try again
[11:43] <Quintasan> Hi 
[13:17] <yofel> JontheEchidna: when muon-updater needs to install/remove packages, is it intentional that the packages to be installed are listed above those that are to be removed?
[13:18] <yofel> maybe I'm just making our users look stupid, but maybe switching that would make people more aware of what's happening
[14:07] <BluesKaj> Hiya all
[14:07] <smartboyhw> Hello
[14:11] <mikhas> Riddell, perhaps you should tell them it's Kubuntu, not QUbuntu: http://bazaar.launchpad.net/~phablet-team/qtubuntu/trunk/view/head:/src/platforms/ubuntulegacy/window.cc
[14:23] <smartboyhw> Bah Riddell can you fix powerpc for qtwebkit-source? It's killing the calligra build (i386) for one day already and I don't want it to fail until 2.6.2 gets released:P
[14:27]  * smartboyhw is really wondering why is packaging an application like calligra so difficult:P
[14:38] <yofel> smartboyhw: the calligra failure has nothing to do with powerpc
[14:38] <smartboyhw> yofel, than what?
[14:38] <yofel> the -dev package is still missing files
[14:38] <smartboyhw> yofel, missing what files?
[14:38]  * smartboyhw opens the buildlog
[14:38] <yofel>  /build/buildd/calligra-2.6.1/stage/part/ui/KPrHtmlExportDialog.h:26:29: fatal error: QtWebKit/QWebPage: No such file or directory
[14:38] <smartboyhw> yofel, anyway to fix?
[14:39] <yofel> yeah, fix qtwebkit-source. Riddell was looking at it though I think
[14:39]  * smartboyhw waits for eternity
[14:39] <smartboyhw> Riddell, shadeslayer apachelogger yofel what devices do you want to port to Ubuntu Touch?
[14:40] <yofel> what's ubuntu touch? (the only touch device I have is a nexus 7)
[14:40] <smartboyhw> yofel, well Ubuntu for phones + tablets
[14:40] <smartboyhw> yofel, and it works for Nexus 7 now:P
[14:41] <yofel> ah, well, we do want to have a plasma-active image at least for the nexus7
[14:41] <yofel> unity on the nexus7 didn't really work out in quantal here ^^
[14:41] <smartboyhw> yofel, of course:P 
[14:41] <smartboyhw> yofel, try Ubuntu Touch yo see if it works
[15:30] <Riddell> smartboyhw: about?
[15:30] <smartboyhw> Riddell, about?
[15:30] <smartboyhw> !?
[15:31] <Riddell> smartboyhw: "are you about?"
[15:31] <smartboyhw> Riddell, yep
[15:31] <Riddell> smartboyhw: I have a qtwebkit build with the headers fixed
[15:31] <Riddell> http://starsky.19inch.net/~jr/tmp/libqtwebkit-dev_2.3-0ubuntu2_amd64.deb
[15:31]  * smartboyhw finds that simplified version extremely weird
[15:31] <smartboyhw> Riddell, great
[15:31] <Riddell> http://starsky.19inch.net/~jr/tmp/libqtwebkit4_2.3-0ubuntu2_amd64.deb
[15:31] <Riddell> smartboyhw: but rekonq still doesn't compile
[15:32] <smartboyhw> Riddell, rekonq!?
[15:32] <Riddell> smartboyhw: first thing I thought of that used qtwebkit
[15:32] <smartboyhw> Riddell, oh
[15:34] <Riddell> smartboyhw: want to see if I'm missing anything?
[15:34] <Riddell> I'm installing those packages
[15:34] <smartboyhw> Riddell, OK
[15:34] <Riddell> then dpkg --install the old libqtwebkit-dev
[15:34] <Riddell> rekonq cmake works fine
[15:35] <Riddell> and replacing each part of libqtwebkit-dev with the new files from libqtwebkit-dev_2.3
[15:35] <Riddell> but I can't track it down
[15:35] <Riddell> smartboyhw: want to try something similar to see if you have any luck?
[15:35] <smartboyhw> Riddell, problem: I am about to sleep soon
[15:36] <Riddell> ach it's the weekend :)
[15:37] <smartboyhw> Riddell, not that problem
[15:37] <smartboyhw> It's 11:37 PM here:P
[15:45] <Riddell> smartboyhw: hoorah, I got it
[15:45] <smartboyhw> Riddell, good
[15:45] <smartboyhw> Riddell, how about powerpc?
[15:45] <smartboyhw> We don't care about it
[15:46] <smartboyhw> But it's good to have it build too
[15:46] <Riddell> don't know, don't really care
[15:46] <smartboyhw> Riddell, LOL
[15:47] <Riddell> there's ment to be a powerpc team for people who want to care about powerpc
[15:47] <smartboyhw> Riddell, I saw in one of your blueprints you want powerpc builds
[15:47] <smartboyhw> LOL
[15:47] <Riddell> you can try trcking them down
[15:47] <Riddell> not I, I've been for dropping them since my mac died
[15:47] <Riddell> others take the view of "if they work and get tested we might as well release them"
[15:48]  * smartboyhw doesn't care about powerpc either
[15:56]  * Riddell just had a random phone call from someone who sounds like a hillbilly american wanting to know if he should use kubuntu
[15:56] <Riddell> I said yes
[15:57] <smartboyhw> Riddell, :)
[15:57] <Riddell> he said companies in the US were so greedy
[15:58] <Riddell> maybe he was a socialist hillbilly
[16:00] <smartboyhw> Riddell, LOL
[16:20] <BluesKaj> Riddell, did he speak with colloquialisms or decent English with a hillbilly accent? ...sometimes the accent fools ppl .
[16:24] <Riddell> BluesKaj: just the accent I think
[16:25] <BluesKaj> Riddell, right ..he .knows enough to look for advice in the right place :)
[16:27] <Riddell> well, to look for my phone number to call me, not quite the right place :)
[16:37] <BluesKaj> Riddell, inconvenient for you but not for him , he got the right answer :)
[16:39] <yofel> grrrrrrrr
[16:39] <yofel> Riddell: can you re-upload qtwebkit please? i386 failed without log and launchpad crashes when I try to retry it
[16:41] <Riddell> yofel: ug
[16:41] <Riddell> yofel: yeah go ahead
[16:42] <Riddell> yofel: oh wait
[16:42] <Riddell> I see my problem
[16:42] <Riddell> another stupid mistake
[16:43] <yofel> ah, *now* the log is there
[16:43] <Riddell> I'll upload a fix, sigh
[17:09] <BluesKaj> BBl
[17:27] <murthy> hello everyone
[17:34] <murthy> http://paste.kde.org/678524/ This is the debian/rules for libdlna. From viewing this can you determine the source format and debhelper version ? 
[17:34] <yofel> no, source format is 1.0 unless debian/source/format says otherwise, debhelper compat level is set in debian/compat
[17:36] <murthy> yofel: If i want to convert the source format from 1.0 to 3.0 what should i do?
[17:36] <yofel> 3.0 quilt I guess?
[17:36] <yofel> mkdir debian/source/; echo "3.0 (quilt)" > debian/source/format
[17:37] <murthy> yofel: done that
[17:37] <murthy> yofel: i removed the cdbs from builddeps and also put debhelper >=7 in control
[17:38] <yofel> then make sure the compat level is actually 7, remove all cdbs references from rules and make sure your package still works
[17:38] <yofel> dh7 packaging actually needs debhelper >= 7.0.51 or so, not sure about the exact version
[17:38] <yofel> lintian will tell you ^^
[17:39] <agateau> Riddell: new Ubiquity review for you!
[17:40] <murthy> yofel: i removed everything from the rules files except the default first line and put this "%:  dh $@"
[17:40] <murthy> yofel:  i am getting errors 
[17:40] <murthy> yofel: during the build process, it reports about an unknown option for the auto configure
[17:40] <yofel> I would assume so, you'll have to pretty much rewrite rules
[17:41] <murthy> yofel: its something like x86_64_linux_gnu
[17:41] <murthy> yofel: its something like "--build=x86_64_linux_gnu"
[17:42] <yofel> dunno
[17:42] <yofel> (at least not without context)
[17:42] <murthy> yofel: i will give you the link
[17:43] <murthy> yofel: https://bugs.launchpad.net/ubuntu/+source/libdlna/+bug/1129977
[17:43] <murthy> yofel: read the last comment
[17:43] <yofel> ok, but you could still use cdbs with source format 3
[17:44] <murthy> yofel: in that case i have to remove only this line ? "include /usr/share/cdbs/1/rules/simple-patchsys.mk"
[17:45] <murthy> yofel: from here http://paste.kde.org/678524/
[17:45] <yofel> that and add a series file so quilt uses the patches
[17:45] <murthy> yofel: thats is done already
[17:45] <yofel> should work then
[17:45] <murthy> yofel: so the control file should contain the cdbs deps right?
[17:46] <yofel> right
[17:46] <murthy> yofel: also what about the debhelper version requirement?
[17:46] <yofel> hm.....
[17:46] <yofel> 7 will work, that much I can say
[17:47] <yofel> what's compat set to now?
[17:47] <murthy> yofel: the previous default was debhelper (>= 5)
[17:47] <murthy> yofel: 5
[17:47] <yofel> read the debhelper manpage, that shows the changes in the versions
[17:47] <murthy> yofel: ok
[17:50] <murthy> brb
[17:54] <apachelogger> Oo
[18:40] <murthy> yofel:  libdlna successfully build. http://paste.kde.org/678590/ . I have to go thought the log one more to confirm it. this is the new rules file http://paste.kde.org/678596/ 
[18:42] <murthy> yofel: so is the new debian/rules ok?
[18:43] <yofel> looking
[18:43] <yofel> you should be able to drop DEB_CONFIGURE_PREFIXS too
[18:43] <yofel> "./configure" should be "dh_auto_configure --"
[18:45] <murthy> yofel: but the source contains a .configure
[18:45] <yofel> you still don't call that directly
[18:45] <yofel> dh_auto_configure will do that
[18:46] <yofel> all you need here is pass some options to it
[18:46] <murthy> yofel: i need dh_auto_configure not to use the --build option how can i do that
[18:47] <yofel> murthy: what's the problem with it?
[18:47] <yofel> murthy: if it's actually breaking something you can call .configure
[18:47] <murthy> yofel: its reports --build="x86-64_linux_gnu" as an unknown option
[18:48] <yofel> ah, probably non-standard configure script
[18:48] <murthy> yofel: ya
[18:48] <yofel> then call configure the normal way, just make sure that dh_auto_clean really removes all build flies
[18:48] <yofel> *files
[18:49] <yofel> hm
[18:49] <murthy> yofel: how can i do that?
[18:50] <yofel> calling make distclean in dh_clean it seems? 
[18:50] <murthy> yofel: i mean how can i check if auto_clean removes all the build files?
[18:50] <yofel> if I understand "DEB_MAKE_CLEAN_TARGET    := distclean" right
[18:50] <murthy> yofel: ya
[18:50] <murthy> yofel: should i override dh_clean?
[18:51] <yofel> can someone familiar with cdbs answer that? ^
[18:51] <murthy> apachelogger: ^
[18:52] <yofel> murthy: but a different question: *why* are you using a dh7 rules file?
[18:52] <murthy> yofel: to upgrade when ever possible
[18:53] <yofel> it's not like cdbs will vanish anytime soon
[18:53] <murthy> yofel: it was once a mandate which was dropped, if i am not wrong
[18:53] <yofel> sure, but what *breaks* by sticking to cdbs?
[18:53] <murthy> yofel: nothing, but i like to take this forward
[18:54] <murthy> yofel: why not try to update?
[18:54]  * yofel leaves this to someone else then
[18:54] <murthy> yofel: anything wrong>
[18:54] <yofel> murthy: I wouldn't do it since I'm not familiar with cdbs to be confident that I won't introduce bugs in the process
[18:54] <murthy> yofel: ok
[18:55] <yofel> but someone of the folks that have been around longer than me should be able to help you
[18:56] <murthy> yofel: i have the legend for help the apachelogger
[18:56] <murthy> apachelogger: help?
[18:57] <murthy> yofel: are you laughing?
[18:58] <yofel> no, why?
[18:59] <murthy> yofel: I doubt that apachelogger will , after i got him piss off the other day
[18:59] <murthy> yofel: I doubt that apachelogger will *help , after i got him piss off the other day
[19:00] <yofel> this is apachelogger we're talking about, he'll forgive you eventually
[19:00] <murthy> yofel: that would be very nice
[19:01] <apachelogger> my quassel is all orange
[19:01] <apachelogger> why is my quassel all orange?
[19:01] <apachelogger> what's with all the orange
[19:02] <murthy> apachelogger: hi
[19:02] <apachelogger> helos
[19:02] <murthy> apachelogger: how are you today?
[19:03] <murthy> apachelogger: yofel has some doubts :)
[19:03] <apachelogger> I  bought me some guinness today \o/
[19:03] <apachelogger> <- happy lion
[19:03] <murthy> apachelogger: nice
[19:04] <murthy> apachelogger: I am like a ginne myself, except i try programming
[19:04] <apachelogger> so what's with the highlights?
[19:05] <murthy> yofel: ^
[19:06]  * apachelogger informs yofel that http://paste.kde.org/678596/ is not using cdbs :P
[19:06] <murthy> apachelogger: https://bugs.launchpad.net/ubuntu/+source/libdlna/+bug/1129977   
[19:06] <murthy> apachelogger: I am asked to convert to 3.0
[19:07] <apachelogger> jolly pointless
[19:07] <murthy> apachelogger: and also i like to update it to 7+
[19:07] <apachelogger> yeah well
[19:07] <apachelogger> dpkg-buildpackage -us -uc && dpkg-buildpackage -S 
[19:08] <apachelogger> if it fails or creates a patch that was not intended your clean target is not complete
[19:08] <yofel> apachelogger: http://paste.kde.org/678596/ is his port of http://paste.kde.org/678524/
[19:08] <apachelogger> if not then the rules look fine
[19:08] <apachelogger> yofel: dh7 probably calls distclean anyway
[19:08] <yofel> oh, right, one can do that...
[19:08] <apachelogger> e.g. autotools stuff often requires distclean
[19:09] <yofel> yeah
[19:10] <murthy> apachelogger: when using the default dh_auto_configure , i get an error message about an unknow option --build="x86_64_linux_gnu" how can i disable that option
[19:11] <apachelogger> you simply don't call dh_auto_configure?
[19:11] <yofel> use ./configure as you did at first 
[19:11] <murthy> yofel: ok
[19:11] <apachelogger> also you should probably send a mail to upstream
[19:11] <apachelogger> if --build is not recognized they either broke something or their autogen is like ancient
[19:12] <murthy> apachelogger: ok
[19:13] <murthy> apachelogger: so for now the new debian/rules that i created is ok?
[19:13] <murthy> apachelogger: here is the build log http://paste.kde.org/678590/
[19:14] <apachelogger> if the clean target is complete
[19:15] <murthy> apachelogger: i have to check that
[19:17] <murthy> apachelogger: how can i check if the clean target is complete?
[19:17] <murthy> apachelogger: dpkg-buildpackage -us -uc && dpkg-buildpackage -S ?
[19:18] <apachelogger> yes
[19:19] <murthy> apachelogger: building with builder doesn't do that?
[19:19] <murthy> apachelogger: building with pbuilder doesn't do that?
[19:20] <apachelogger> no
[19:20] <murthy> apachelogger: ok i will try that now
[19:25] <murthy> apachelogger: http://paste.kde.org/678668/ there are no patches in debian/patches 
[19:27] <murthy> apachelogger: so is the clean target complete?
[19:34] <yofel> murthy: I don't see the patches mentioned *anywhere* though, can you "export DH_VERBOSE=1" and run it again please?
[19:34] <murthy> yofel: ok
[19:36] <murthy> yofel: http://paste.kde.org/678680/
[19:37] <murthy> yofel: there is no series file in /debian/patches 
[19:37] <yofel> murthy: different question: are there any patches left?
[19:38] <yofel> murthy: and you said earlier that you created a series file
[19:38] <murthy> yofel: all the patches were applied upstream and so i removed them
[19:39] <murthy> yofel: previously since it was using simple patch there was no series file
[19:39] <yofel> ah ok, then it's fine
[19:39] <murthy> yofel: so the clean target is complete?
[19:39] <yofel> yeah, but I got confused as you said that you created a series file but there were no patches
[19:40] <yofel> murthy: looks like you're fine with the defaults
[19:40] <murthy> yofel: ??
[19:40] <apachelogger> yofel: http://media.moddb.com/images/downloads/1/34/33809/patches.png there you go
[19:41] <apachelogger> where's the shady slayer when you need him -.-
[19:41] <apachelogger> shadeslayer: P-I-N-G
[19:41] <yofel> apachelogger: stamp that on launchpad :P
[19:41] <yofel> murthy: dh_clean already does everything you need to do, so you don't need to do anything
[19:41] <apachelogger> luuuunchpats
[19:42] <murthy> yofel: nice
[19:42] <apachelogger> oho
[19:42] <apachelogger> launchpatch
[19:42] <apachelogger> trolololo
[19:42]  * apachelogger  goes back to building qt5
[19:42] <murthy> yofel: one last doubt about debian/rules
[19:43] <murthy> yofel: is it ok if i use "./configure $(DEB_CONFIGURE_NORMAL_ARGS) $(DEB_CONFIGURE_PREFIXS)" instead of "[ -f config.mak ] || ./configure $(DEB_CONFIGURE_NORMAL_ARGS) $(DEB_CONFIGURE_PREFIXS)"
[19:44] <yofel> depends on what config.mak is supposed to be
[19:44] <yofel> if you can imply that it's there, yes
[19:47] <murthy> yofel: since the previous debian/rules http://paste.kde.org/678524/     used this     can i use the same in the new one?
[19:49] <yofel> should work
[19:50] <yofel> I wonder why config.mak would even be there though
[19:52] <murthy> yofel: because of this ? line 65 in here http://paste.kde.org/678680/
[19:52] <murthy> yofel: also line 364
[19:53] <yofel> yeah, that's what I mean - the file should never be there. But maybe it was in some older version.
[19:53] <yofel> just use the same command and it'll work
[19:54] <yofel> murthy: do you have a config.mak after your dpkg-buildpackage -S run?
[19:54] <yofel> (I assume not)
[19:55] <murthy> yofel: no, no such file present
[19:57] <murthy> yofel: should i put something like this to reflect the dh change "switch to dh > "?
[19:57] <murthy> yofel: in the changelog
[19:58] <murthy> yofel: "switch to dh > 7 "
[19:58] <yofel> yes, but a bit more verbose
[19:59] <murthy> yofel: "switch to debhelper version grater than 7" ? 
[19:59] <JontheEchidna> yofel: no reason in particular, that's just how they happened to be listed. It does make sense to put removals first though
[20:01] <yofel> murthy: you can use that as a general changelog item, but then please document the individual changes you did
[20:01] <yofel> i.e. changing compat level, build-dep, rules changing, dropping cdbs, ...
[20:02] <murthy> yofel: http://paste.kde.org/678716/
[20:02] <murthy> yofel: thats the changelog now, i will update it now
[20:03] <murthy> will be back after dinner
[20:03] <yofel> JontheEchidna: want a bug report?
[20:04] <JontheEchidna> yofel: it'd be for the best, yeah
[20:04] <yofel> k
[20:04] <JontheEchidna> I'd probably forget otherwise ;-)
[20:04] <yofel> ^^
[20:52]  * yofel retries calligra again
[20:52] <Quintasan_> Now
[20:53] <Quintasan_> that I'm trying to install Kubuntu on my laptop
[20:53] <Quintasan_> I wonder how does one use LVM when not using the entire disk, is it even possible?
[20:53] <yofel> Quintasan: more like: why would you want to do that?
[20:54] <yofel> you usually create partitions *inside* LVM
[20:54] <Quintasan> yofel: Thanks for letting me know about downtime, I have been wondering if it wouldn't be too hard on my iMX53 to run a core
[20:54] <Quintasan> yofel: Oh, well, that's true
[20:54] <Quintasan> the main problem is
[20:54] <Quintasan> Can I install windows then?
[20:54] <yofel> haven't tried it on my raspi. I can tell you that an old Pentium1 166MHz was too slow for quassel ^^ (just barely though)
[20:55] <yofel> hm, good question
[20:55] <yofel> after my last issues with grub2 and windows I never install linux and windows onto the same HDD
[20:56] <Quintasan> wow
[20:56] <Quintasan> Kubuntu discovered the system recovery partition from Lenovo and marked it as Windows 7 installation
[20:59] <Quintasan> hmm I wonder if I can get rid of that
[21:00] <yofel> do that after you order an installation media from lenovo
[21:00] <yofel> unless you can get a windows license key from Uni
[21:00] <Quintasan> I have a win key sticker under my battery
[21:01] <Quintasan> it has a cd key on it
[21:01] <yofel> yeah, but you'll need the CD for it (I think)
[21:01] <yofel> which you don't have
[21:01] <Quintasan> hmm
[21:02] <yofel> I personally have linux on a different HDD and put my windows HDD into my thinkpad baydrive HDD adapter when I need it - that ofc. requires a spare HDD
[21:03] <Quintasan> yofel: Any idea how can I order such a disk? I don't see anything like that on lenovo.com
[21:03] <yofel> Quintasan: the recovery partition should only be like 2% of the whole disk though
[21:03] <Quintasan> oh well
[21:04] <Quintasan> I could try renaming the grub entry before I install windows 7
[21:05] <yofel> there is http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-4M7HWZ
[21:05] <yofel> but I don't know more than that
[21:08] <Quintasan> hmmm
[21:08] <Quintasan> yeah
[21:08] <Quintasan> you can order one
[21:08] <Quintasan> and I would rather do that
[21:08] <Quintasan> I wonder what the CD you create at the boot does then
[21:16]  * Quintasan tries upgrading KDE
[21:17] <shadeslayer> apachelogger: P-O-N-G
[21:21] <yofel> shadeslayer: how's the trip so far?
[21:23] <murthy> yofel: the author of the libdlna has aked to send bug reports to his mail id. He hasn't mentioned any bug management system. http://libdlna.geexbox.org/ . So what to do? 
[21:23] <yofel> send him a mail?
[21:24] <murthy> yofel: http://paste.kde.org/678776/
[21:24] <murthy> yofel: ^ the changelog for libdlna
[21:25] <murthy> yofel: does the MOTO team maintain upstream bugs?
[21:29] <yofel> murthy: line 10-11 belong to the part below, and "Switch to Debhelper version greater than 7", should be something like "Switch to dh7 style buildsystem" or so
[21:29] <murthy> yofel: ok
[21:30] <yofel> s/dh > 7 incompatable/dh_auto_configure incompatible
[21:30] <yofel> dh_auto_configure existed before 7
[21:30] <Quintasan> it did?
[21:30] <yofel> I thought it did
[21:30] <Quintasan> I think the whole auto stuff was introduced in dh7
[21:30] <yofel> oh
[21:30] <Quintasan> but I may be wrong
[21:30] <yofel> good point
[21:31] <kubotu> ::qt-bugs:: [1131926] package libqt4-qt3support 4:4.8.1-0ubuntu4.3 failed to install/upgrade: libqt4-qt3support:... @ https://bugs.launchpad.net/bugs/1131926 (by Håvard Korsvoll)
[21:31] <yofel> it would be still incompatible with dh_auto_configure though
[21:31] <Quintasan> but generally  yeah, say we switched to dh7 build system
[21:32] <murthy> yofel: so i should mention"Override dh_auto_configure with custom command to workaround dh_auto_configure incompatable upstream configure script." ?
[21:33] <yofel> yeah, that's fine
[21:33] <murthy> yofel: isn't cdbs part of patch system so shouldn't be mention under the format change section?
[21:34] <yofel> cdbs is *not* a patch system, simple-patchsys which is part of cdbs is a patch system
[21:34] <murthy> yofel: ok
[21:34] <Riddell> evening
[21:34] <yofel> cdbs stands for "Common Debian Build System"
[21:36] <yofel> murthy: I think you can remove "    -Create debian/source/format with value "3.0 (quilt)"" - switching to 3.0 (quilt) implies that
[21:36] <murthy> yofel: thats what i thought
[21:38] <murthy> yofel: i read about cdbs for sometime yesterday as part the homework you assigned to me :)
[21:41] <Riddell> cdbs is complex as anything
[21:41] <Riddell> I'm not sorry to see it go out of fashion
[21:42] <murthy> ya
[21:42] <murthy> yofel: http://paste.kde.org/678788/
[21:42] <murthy> Riddell: also i like quilt very much
[21:42] <murthy> Riddell: 3.0
[21:44] <murthy> Riddell: i will try to upgrade the packages to dh7, format 3.0 and to the latest standards 
[21:45] <yofel> murthy: one thing about style, you should write it like this: http://paste.kde.org/678212
[21:45] <yofel> erm http://paste.kde.org/678794
[21:48] <murthy> yofel: i saw some package changelogs for examples and i found most containing the one i am using, so i followed it. I will change it now. But i feel grouping by the major change would be more helpfull
[21:49] <yofel> uh, it's still grouped by major change (*), but grouping changes by file is also common
[21:49] <murthy> yofel: i am on it
[21:49] <yofel> or rather you don't write the file you change on every line if you have more then one change in a file
[21:53] <Quintasan> murthy: Usually when you do changes in .install files you don't really want to mention every single change, I usually write "Refreshed install files"
[21:53] <murthy> yofel: done http://paste.kde.org/678800/
[21:53] <Quintasan> that was an example of course
[21:53] <murthy> Quintasan: ok
[21:54] <yofel> hm... ship it
[21:54] <Quintasan> :DDDD
[21:56] <murthy> yofel: nice
[21:57] <yofel> murthy: from what i've seen now at least, would need to test build to verify that everything's right. The logs look ok though so I'll leave that to the sponsor
[21:57] <Quintasan> LOL
[21:57] <Quintasan> yofel: there is a small rectrangular button right below the display
[21:57] <Quintasan> I have no idea what it is suppoed to do
[21:57] <Quintasan> the manual says
[21:58] <Quintasan> it's BLACK BUTTON
[21:58] <Quintasan> BRILLIANT
[21:58] <yofel> what o.O?
[21:58] <Quintasan> nothing else
[21:58] <Quintasan> number 7 - black button
[21:58] <Quintasan> xD
[21:58] <murthy> i will do a test build now
[22:00] <Quintasan> yofel: well
[22:00] <Quintasan> apparently it is supposed to boot the system into recovery
[22:00] <Quintasan> so it's useless in windows
[22:00] <Quintasan> but I can bind it to something in Linux :DDD
[22:00] <yofel> why do you need a *button* for that o.O
[22:01] <yofel> the thinkvantage button was meant for stuff like hat
[22:01] <yofel> *that
[22:01] <Quintasan> i think that is the thinkvantage button
[22:01] <Quintasan> but it's not blue
[22:01] <Quintasan> and on windows it did noting
[22:02] <yofel> does it send key events? the thinkvantage button doesn't according to xev
[22:03] <yofel> hm... which reminds me that I don't use those folder switching buttons for anything
[22:03] <Quintasan> it does
[22:04] <Quintasan> XF61Launch1
[22:04] <Quintasan> bleh
[22:04] <Quintasan> XF86Launch1
[22:04] <yofel> heh
[22:04] <Quintasan> BUT
[22:04] <Quintasan> the microphone mute button doesn't work
[22:04] <yofel> yeah
[22:05] <murthy> yofel: test build log http://paste.kde.org/678806/
[22:05] <Quintasan> yofel: do you know if it's possible to turn off the touchpad with a command of sorts?
[22:05] <Quintasan> I would bind that thinkvantage button to this
[22:06] <yofel> synclient TouchpadOff=1
[22:07] <Quintasan> synclient TouchpadOn would turn this on, right ?
[22:07] <yofel> no, =0 will
[22:07]  * Quintasan writes a shell script to enable/disable
[22:09] <yofel> eeeeeerk
[22:09] <yofel> I tried to install 4.10 in a fresh precise VM, failed due to an overwrite error from kmahjongg
[22:09]  * yofel goes fixing
[22:12] <yofel> murthy: looks fine
[22:13] <murthy> yofel: ok, prepared the debdiff, going to attach it and subscribe to the sponsors team
[22:14] <yofel> grrrr
[22:14] <yofel> shadeslayer does not backport fixes
[22:15] <Quintasan> >shadeslayer
[22:15] <Quintasan> >fixing
[22:15] <Quintasan> pick one :P
[22:15] <Quintasan> he is our general leader when it comes to breaking stuff
[22:15] <Quintasan> :P
[22:15] <yofel> >qa :P
[22:15] <yofel> the qa page look fits pretty well actually :D
[22:19] <Quintasan> why the heck the script doesnt get invoked
[22:19] <Quintasan> wtf
[22:24] <Quintasan>   ffffff
[22:25] <yofel> https://launchpad.net/ubuntu/+source/calligra/1:2.6.1-0ubuntu5/+build/4317151 \o/
[22:25] <Riddell> awooga
[22:26]  * yofel goes trying what do-release-upgrade does when you try to upgrade 12.04+4.10  to 12.10
[22:40] <Quintasan> Riddell: How do we handle restricted extras?
[22:40] <Quintasan> There is a problem with flash now I believe
[22:41] <Quintasan> if you enable the partner repo there is adobe-flashplugin
[22:41] <Quintasan> and adobe-flash-properities-kde
[22:41] <Quintasan> the latter package is particulary intertesting for us I presume and even after I install that, restricted extras installer keeps bugging me
[22:42] <Quintasan> the bad thing is that the flash player kcm is under lost and found
[22:43] <yofel> no, the bad thing is that our extension installer patches don't to alternate deps. if you have adobe-flashplugin installed rekonq will constantly tell you to install flashplugin-installer
[22:44] <apachelogger> pf
[22:44] <apachelogger> put it on some todo for 14.04
[22:46] <apachelogger> as a matter of fact
[22:46] <apachelogger> we should rethink the entire wanna-install-stuff solution we have in place
[22:46] <apachelogger> perhaps come up with something more integrated
[22:47] <apachelogger> e.g. rekonq triggering a workspace notification is somewhat strange as installing flash is in fact a highly contextual feature
[22:47] <yofel> well, true
[22:48] <yofel> rekonq has that password storage dialogue - maybe put it in the same place
[22:48] <apachelogger> needs investigation
[22:48] <apachelogger> i.e. why I dont want to discuss it now but put a task somewhere to look into at uds or something
[22:49] <yofel> true
[22:49] <Quintasan> apachelogger: Could you write that down or you want me to do that?
[22:50]  * Quintasan notes he is not the best person to take care of that
[22:51] <Riddell> Quintasan: cor what does adobe-flash-properities-kde do?
[22:52] <apachelogger> Quintasan: mail -devel when in doubt
[22:52] <apachelogger> Riddell: kcm to configure flash
[22:52] <Riddell> what needs configuring?
[22:53] <Quintasan> what logger said
[22:53] <yofel> http://paste.kde.org/678794
[22:53] <yofel> erm
[22:53] <yofel> http://people.ubuntu.com/~yofel/pics/flash_properties.png
[22:53] <Quintasan> yeah
[22:53] <yofel> today's paste fail day
[22:53] <Quintasan> was to describe that
[22:53] <apachelogger> yofel: at least it wasnt prn :P
[22:53] <yofel> ^^
[22:54] <Riddell> oh that's very nice of it actually
[22:54] <murthy> yofel: thats because i was spamming you will all those pastes
[22:54] <Riddell> flash cookies are a sneaky way to spy on people
[22:55] <Quintasan> That's why I actually bothered to install that
[22:55] <Quintasan> and it turns out restricted installer still bugged me about missing flash
[22:56] <yofel> I wonder if it would make sense to request that adobe-flashplugin provies flashplugin-installer
[22:57] <yofel> *provides
[22:57] <murthy> yofel: isn't adobe had already dropped support ?
[22:57] <yofel> it already has "Provides: flashplugin-nonfree"
[22:57] <yofel> murthy: not for the current one
[23:03] <yofel> hm. so. upgrading 12.04+kde4.10 to quantal ends up being 12.10+kde4.10(from 12.04) - which so far works fine...
[23:05] <Quintasan> well yeah
[23:06] <yofel> except that digikam crashes - but that's the lcms issue I should be debugging
[23:06] <Quintasan> upgrade to kde 4.10 on 12.10 works fine as well