[00:23] <afiestas__> https://bugs.launchpad.net/ubuntu/+bug/702706
[00:23] <afiestas__> but apt-cache search gstreamer | grep -i qt returns 0 :p
[00:23] <afiestas__> (well a telepathy stuff which is not QtGst)
[00:33] <JontheEchidna> It's in new queue at the moment: https://launchpad.net/ubuntu/natty/+queue
[00:34] <afiestas__> oh :p
[00:38] <JontheEchidna> QtGstreamer is infinitely nicer to use than raw GStreamer
[00:53] <DarkwingDuck> Whoot my VB works again.
[00:53] <DarkwingDuck> rather VM
[02:31] <JontheEchidna> wtf, I have a video paused in dragon player and I keep getting these vlc popups
[02:32] <JontheEchidna> of random pictures
[02:32] <JontheEchidna> like a grilled cheese sandwhich and a bottle of milk
[02:36] <nigelb> lol
[02:43] <JontheEchidna> ok, they're pictures on my hdd
[03:26] <afiestas__> JontheEchidna: ping
[03:27] <JontheEchidna> afiestas__: pong
[03:28] <afiestas__> JontheEchidna: with all this "noise" about "App Stores" I'm wondering what is the current status of muon/packagekit/KPackageKit etc
[03:28] <afiestas__> does muon work (or could work) with packagekit?
[03:28] <afiestas__> do you have any plans to join forces with KPackageKit ?
[03:28] <JontheEchidna> nope
[03:31] <JontheEchidna> I personally believe that PackageKit is flawed and that a least common denominator solution can't compare to a fully-integrated solution
[03:32] <jjesse> hrmm the installer is stopping for me under the daily
[03:34] <afiestas__> JontheEchidna: oks
[03:34] <JontheEchidna> the gross inadequancy of PK back a year ago was what drove me to start the whole Muon thing. I didn't expect PK to at least become somewhat adequate, but I still believe that the tight apt integration Muon has can deliver a better experience
[03:40] <jjesse> hrmm ok don't know if anyone is around but after putting in my username and password ubiquity stops and sends me back to the desktop on today's daily
[03:49] <DarkwingDuck> jjesse: I found a god daily
[03:50] <DarkwingDuck> god/good
[03:50] <jjesse> hrmm i haven't :(
[03:50] <jjesse> but now it is time for bed
[03:50] <DarkwingDuck> jjesse: I'll upload it and email it to you
[03:50] <jjesse> ok
[03:51] <DarkwingDuck> jjesse: http://cdimage.ubuntu.com/kubuntu/daily-live/20110131.2/
[03:51] <DarkwingDuck> the i386 ISO is good for install
[07:54] <apachelogger> JontheEchidna: you are incredibly hot
[07:54] <apachelogger> or maybe 114 degrees f are not that hot, though then the red-ness indicator on the plasmoid is wrongish
[07:55] <ulysses> UDS in Corinthia Grand Hotel Royal, Budapest, 9-13 May 2011
[08:23] <apachelogger> JontheEchidna: you are not around by any chance?
[08:23] <apachelogger> ulysses: uhhh
[08:23] <apachelogger> ehhh
[08:23] <apachelogger> ahhhh
[08:23] <apachelogger> Nightrose: there, I cannot attend linuxtag either
[08:23] <apachelogger> -.-
[08:23] <ulysses> whut?
[08:23] <apachelogger> scary
[08:23] <apachelogger> ulysses: that is the same week linuxtag in berlin is :D
[08:23] <ulysses> oh
[08:23]  * apachelogger withdraws his 3 papers
[08:36] <jussi> Hrm, How do I install/use the git/svn plugins in 4.6? 
[08:42] <apachelogger> jussi: you install kdesdk-dolphin-plugins and actiavte them in the dolphinzzz
[08:43] <jussi> kdesdk-dolphin-plugins is already the newest version
[08:44] <jussi> oh...found it! :D
[08:46] <apachelogger> ulysses: do you happen to know where one can apply for sponsorship yet?
[08:46]  * apachelogger has ever so great plans
[08:46] <ulysses> apachelogger: no, I just know this page: https://launchpad.net/sprints/uds-o
[08:48] <apachelogger> ok
[08:48] <apachelogger> that is the stranges t thing evar
[08:49] <apachelogger> http://aplg.kollide.net/images/avatar/snapshot144.png
[08:49] <apachelogger> that is the funniest thing evar
[08:50] <ulysses> four people of the attendees are hungarian now:>
[08:50] <apachelogger> that is not the funny bit :P
[08:51]  * apachelogger recons there are hungarians in hungary
[08:51]  * apachelogger joins the fun
[09:45] <valorie> http://summit.ubuntu.com/uds-o/sponsorship/
[09:45] <valorie> page is definitely up
[09:45] <valorie> whether or not they want us to use it
[09:48] <apachelogger> when it is up you gotta use it ^^
[09:51] <valorie> would be funny if the first 10 applicants were all KOO buntu
[09:52] <valorie> can't decide if I should apply or not
[09:52] <valorie> would be soooo fun though
[09:52] <apachelogger> do it
[09:55] <ulysses> hm, I should change the name in the form, but I can't
[09:56] <nigelb> I wonder if valorie ever sleeps :O
[10:00] <valorie> in maybe a half hour I will 
[10:00] <nigelb> heh
[10:00] <valorie> but night is when I can get some work done
[10:00] <valorie> no interruptions
[10:00] <nigelb> I agree with that
[10:00] <nigelb> same here
[10:02] <valorie> otoh, I have my music on random, and just got Britney: Baby One More Time
[10:02] <valorie> lol
[10:02] <valorie> one of the most common earworms evar
[10:05] <ulysses> what does „Would you be willing to participate as member of the crew?” mean?
[10:07] <valorie> ulysses: one day during uds, you run around replacing the signs for the various sessions
[10:08] <valorie> it's fun, and you get a shirt
[10:08] <ulysses> oh, then I answer yes
[10:08] <valorie> you do it with a partner
[10:08] <valorie> you do have to leave sessions a few minutes early, which can suck a bit
[10:08] <valorie> but you and your partner work it out
[10:09] <valorie> I partnered with Vish
[10:09] <ulysses> I could be the first at the bar for a beer then:P
[10:09] <valorie> well, this is during the day
[10:09] <valorie> hopefully that's *after*
[10:09] <valorie> lol
[10:16] <valorie> ok, nothing ventured, nothing gained -- applied
[10:17] <ulysses> what have to I write as further information? Shall I write that I'm a student, so I can't go without support, or something better?
[10:18] <nigelb> wait, sponsorship is open?
[10:18] <nigelb> did someone actually announce UDS?
[10:18] <ulysses> http://summit.ubuntu.com/
[10:18] <nigelb> generally jorge or jono blogs about it first
[10:19] <valorie> ulysses: last time I just applied more on a dare than anything else
[10:19] <valorie> and was accepted late
[10:19] <nigelb> hehe
[10:19] <nigelb> I don't want to remember last time :/
[10:19] <valorie> are you coming this time, nigelb?
[10:19] <valorie> WE MISSED YOU
[10:19] <nigelb> valorie: I don't know.  Far too many variables this time around.
[10:20] <valorie> lots of variables for me too, but I figured -- why not ask
[10:20] <valorie> I can always say no
[10:41] <valorie> true to my word, off to bed....
[10:46] <c2tarun> yofel: hi, I am here. I was going through ur page, so there are three ways in which i can contribute into kubuntu dev?
[10:52]  * apachelogger would think there are more
[10:53] <yofel> c2tarun: welcome, those aren't the only ways, and packaging and being a ninja go hand in hand
[10:53] <c2tarun> yofel: thanks :) what are the other ways?
[10:53] <yofel> apachelogger: meet c2tarun, found him in #kubuntu desperately wanting to become a ninja ;)
[10:53] <c2tarun> hi apachelogger :)
[10:54] <apachelogger> http://listverse.files.wordpress.com/2009/04/ninja.jpg-tm.jpg
[10:54] <apachelogger> I can see why
[10:54] <apachelogger> c2tarun: ahoy ahoy
[10:54] <yofel> hehe
[10:54] <c2tarun> what happend? :/
[10:55] <c2tarun> not exactly coz of that pic :) but ya somehow it sounds cool :P
[10:55] <apachelogger> http://4.bp.blogspot.com/_tNRAa-BYU7M/Ru7zpQTKSYI/AAAAAAAAADw/nz9gMP7T3zU/s1600/ninja_tux.jpg
[10:55] <apachelogger> that one is more like
[10:56] <c2tarun> hmm.... :/
[10:56] <apachelogger> Quintasan: c2tarun shall be your first padawan
[10:58] <c2tarun> sure :) just tell me what is a padawan?
[10:58] <c2tarun> apart from aprentice
[10:58] <tsimpson> just that
[10:58] <c2tarun> ok :) 
[10:58] <apachelogger> the stage before becoming minion, which is the stage before becoming developer of somesort
[10:59] <apachelogger> one becomes a ninja somewhere between minion and developer
[11:00] <c2tarun> how can i start?
[11:01] <apachelogger> c2tarun: that is for Quintasan to decide, but I suppose you could just read a bit through the packaging guide https://wiki.ubuntu.com/PackagingGuide/Complete until he arrives
[11:03] <c2tarun> apachelogger: I already read this page. few months back, on this page all is written use of some tools for packaging, I don't actually understood any concept of packaging :( (I am not blaming anyone, I am just saying)
[11:04] <apachelogger> c2tarun: http://en.wikipedia.org/wiki/Deb_(file_format) http://en.wikipedia.org/wiki/Dpkg
[11:05] <c2tarun> apachelogger: ok, this page is good :) i'll read it. by the way is there really anything known as padawan in kubuntu-devel?
[11:06] <apachelogger> no, george lucas would probably sue us ^^
[11:06] <apachelogger> officially there is contributor and developer
[11:07] <c2tarun> what do contributors do?
[11:07] <yofel> c2tarun: there's also http://www.debian.org/doc/debian-policy/ which you should know and keep as a reference (yo don't need to understand everything at once) - and also http://www.debian.org/doc/maint-guide/ as another introduction guide
[11:07] <apachelogger> c2tarun: regular patch contribution etc. etc.
[11:07] <apachelogger> contributors do generally not have upload rights but developers do
[11:08] <apachelogger> which is really the only difference
[11:08] <c2tarun> apachelogger: one more thing, while reading i got this term a lot Patching, Can u please explain me a bit?
[11:09] <apachelogger> c2tarun: http://en.wikipedia.org/wiki/Patch_(computing)
[11:09] <apachelogger> also the appropriate linux app: http://en.wikipedia.org/wiki/Patch_(Unix)
[11:09] <apachelogger> c2tarun: basically a patch is just a text file representing the difference between one file and another
[11:09] <apachelogger> (or a bunch of files for that matter)
[11:10] <c2tarun> like a .diff file?
[11:10] <apachelogger> yes
[11:11] <apachelogger> patch is just the more general term
[11:11] <apachelogger> as a patch can also be a binary executable that manipulates another binary executable
[11:11] <apachelogger> http://paste.ubuntu.com/560894/
[11:11] <apachelogger> say that is a diff and a patch
[11:11] <apachelogger> it is a diff because,. well, because it is one ;)
[11:11] <apachelogger> and a patch because it fixes something
[11:12] <c2tarun> ok. 
[11:12] <apachelogger> though generally those two words are used as synonyms
[11:12] <c2tarun> so after reading the documentations, where can i start?
[11:12] <apachelogger> c2tarun: find something that annoys you and do something about it ;)
[11:13] <apachelogger> c2tarun: or look for cool new software that might need packaging
[11:13] <apachelogger> kde-apps.org or qt-apps.org are generally good places to look for that sort of thing
[11:13] <c2tarun> apachelogger: ya where can i look for those softwares that might need packaging?
[11:15] <c2tarun> apachelogger: sorry to ask this, but where in kde-apps.org?
[11:17] <apachelogger> everywhere
[11:17] <apachelogger> mian page mainly
[11:17] <apachelogger> c2tarun: bangarang has a new version out
[11:17] <apachelogger> I do not think we have that yet
[11:18] <apachelogger> !info bangarang natty
[11:18] <apachelogger> http://kde-apps.org/content/show.php/Bangarang?content=113305
[11:18] <apachelogger> there, 2.0 is new and we have 1.0.1
[11:18] <apachelogger> you could update that bugger
[11:19] <c2tarun> sorry, but what do u mean by we have?
[11:21] <c2tarun> apachelogger: ^^
[11:21] <apachelogger> c2tarun: the ubuntu archive
[11:21] <apachelogger> contains version 1.0.1 of bangarang
[11:22] <c2tarun> apachelogger: I think u told that only developers can access the archive. And exactly how to do that?
[11:22] <c2tarun> apachelogger: I just checked we don't have 2.0 there
[11:28] <apachelogger> c2tarun: you update the package, create a debdiff, then either report a bug report and subscribe sponsors or find someone in here to sponsor the upload
[11:28] <apachelogger> !sponsoring
[11:28] <apachelogger> hm
[11:28] <apachelogger> !sponsor
[11:28] <apachelogger> ubottu: you are useless my friend
[11:29] <apachelogger> !sponsorship
[11:29] <apachelogger> ah
[11:29] <apachelogger> !!
[11:29] <apachelogger> ubottu: silly beast
[11:29] <apachelogger> yes you are
[11:30] <apachelogger> hm
[11:30] <c2tarun> apachelogger: hehehe... anyway leave the bot :)
[11:30] <apachelogger> ok, current sponsorship information is absolutely worthless to beginners
[11:30] <apachelogger> awesome
[11:30] <apachelogger> c2tarun: just poke Quintasan_ once you have a debdiff
[11:30] <apachelogger> he will guide you
[11:31] <c2tarun> I'll read the packaging again :) and i'll try to create a debdiff for 2.0
[11:31] <c2tarun> sure i'll come back with debdiff.
[11:35] <apachelogger> cool
[11:48] <jussi> apachelogger: leave my poor little girl bot alone!
[11:49] <jussi> !search sponsor
[11:49] <jussi> apachelogger: what shoudl that factoid say? 
[11:59] <apachelogger> jussi: https://wiki.ubuntu.com/SponsorshipProcess
[12:00] <apachelogger> but since that page is utterly useless...
[12:01] <jussi> apachelogger: write me 1 line that you want it to say...
[12:01] <apachelogger> jussi: If you know what distributed development is: https://wiki.ubuntu.com/SponsorshipProcess
[12:02] <jussi> apachelogger: how about: If you have made a package and would like to get it uploaded to the official Ubuntu repository, see https://wiki.ubuntu.com/SponsorshipProcess
[12:03] <apachelogger> jussi: that is not what the page is bout
[12:04] <apachelogger> https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue
[12:04] <apachelogger> that might actually be more useful
[12:53] <Riddell> Quintasan_: E: libqtglib-2.0-0: symbols-file-contains-current-version-with-debian-revision on symbol _ZNK5QGlib5Value3getI7QStringEET_Pb@Base and 7 others
[13:20] <c2tarun> for packaging which is best, pbuilder, chroot or installing a distro using virtual box?
[13:24] <shadeslayer> c2tarun: pbuilder
[13:25] <c2tarun> shadeslayer: thanks :)
[13:25] <shadeslayer> c2tarun: i mean pbuilder works out the best for me
[13:26] <shadeslayer> and then there's !best
[13:26] <c2tarun> shadeslayer: can u please tell me the diff b/w pbuilder and chroot?
[13:27] <shadeslayer> c2tarun: a pbuilder is a clean chroot
[13:27] <c2tarun> shadeslayer: sorry not getting, any operational difference.
[13:27] <shadeslayer> if you create a chroot .. you might dirty it ( installing build deps etc )
[13:27] <shadeslayer> whereas the pbuilder is always ( mostly ) clean
[13:28] <shadeslayer> c2tarun: use a pbuilder ... its the best packaging tool 
[13:28] <c2tarun> shadeslayer: but I have a problem, I dont have very fast internet connection so as to download dependencies each and every time. but I have 30GB or partition in which kubuntu is installed.
[13:29] <c2tarun> of partition*
[13:29] <shadeslayer> c2tarun: the build deps are cached
[13:30] <c2tarun> shadeslayer: that's good :)
[13:30] <c2tarun> i'll go for pbuilder then. Thanks 
[13:31] <apachelogger> surely shadeslayer has worse intarwebs connection
[13:31] <shadeslayer> probably :S
[13:32] <apachelogger> also he has net neutrality even though I still do not know what it is
[13:32] <shadeslayer> ask kubotu .. he knows all
[13:32] <c2tarun> apachelogger: :D not worse than mine, my download speed is max 50kbps :)
[13:32] <shadeslayer> c2tarun: worse
[13:32] <apachelogger> see
[13:32] <apachelogger> :D :D :D
[13:32] <apachelogger> net neutrality has its price it would appear
[13:32] <c2tarun> shadeslayer: even slower than mine?
[13:32] <apachelogger> shadeslayer: did you write a blog post yet?
[13:32] <shadeslayer> yep
[13:33] <shadeslayer> apachelogger: too busy fixoring LP + rekonq for you
[13:33] <apachelogger> oh, I do not care
[13:33] <apachelogger> I do not use either of those products anymore
[13:33] <apachelogger> chromium and bugzilla work very well I must say
[13:34] <shadeslayer> s/you/anyone who cares
[13:34] <shadeslayer> apparently kwebkitpart works ... i commented out stuff that was causing issues, yet it does not work -.-
[13:35]  * Riddell cares
[13:35] <shadeslayer> see :P
[13:36] <shadeslayer> http://paste.kde.org/3885 << is supposed to work
[13:36] <shadeslayer> yet it doesnt
[13:47] <apachelogger> shadeslayer: why would that be worky?
[13:47] <shadeslayer> apachelogger: because kdewebkit is now fixored
[13:47] <shadeslayer> has all those operations
[13:48] <shadeslayer> and i think its the CustomOperations stuff that caused issues
[13:48] <apachelogger> oh, did I mention that this code was most silly :P
[13:48] <shadeslayer> apachelogger: it was there because kdewebkit did not support those operations ( see the comments )
[13:48] <apachelogger> yes, still the code is silly
[13:48] <shadeslayer> well now its gone
[13:48] <apachelogger> anyhow
[13:49] <apachelogger> shadeslayer: why does it not work?
[13:49] <shadeslayer> apachelogger: no idea
[13:49] <shadeslayer> nigelb: ^^ :P
[13:49] <apachelogger> how does the notworkingness presents itself?
[13:49] <shadeslayer> you know what to say :P
[13:49] <shadeslayer> apachelogger: go to any bug in lp ... comment on bug ... shows up [object Object] instead of comment
[13:50] <shadeslayer> same thing with konqueror works
[13:50] <apachelogger> because konqueror is supreme
[13:50] <shadeslayer> konqueror + kwebkitpart that is
[13:50] <apachelogger> shadeslayer: surely you are just using a wrong kdeinit lib again :P
[13:50] <shadeslayer> nope
[13:50] <apachelogger> then the issue is not fixed?
[13:51] <shadeslayer> apachelogger: in kdewebkit?
[13:52] <shadeslayer> its fixed in kdewebkit since it works with konqueror + webkitpart from git
[13:52] <shadeslayer> verified it myself
[13:52] <apachelogger> that is flawed reasoning
[13:52] <apachelogger> maybe the webkit part also works around it
[13:53] <shadeslayer> hmm .. dont think so ... lemme check
[13:53] <shadeslayer> https://projects.kde.org/projects/extragear/base/kwebkitpart/repository/revisions/master/entry/src/networkaccessmanager.cpp
[13:54] <shadeslayer> doesnt look like it
[13:54] <apachelogger> maybe rekonq is just broken...
[13:54] <apachelogger> or maybe kwebkitpart messes with things elsewhere
[13:54] <apachelogger> #define QL1S(x) QLatin1String(x)
[13:54] <apachelogger> uh lovely
[13:55] <shadeslayer> hehehe
[13:55]  * apachelogger feels like doing some java now
[13:55] <shadeslayer> ROFL : https://projects.kde.org/projects/extragear/base/kwebkitpart/repository/revisions/master/entry/src/networkaccessmanager.cpp
[13:55] <shadeslayer> er
[13:55] <shadeslayer> shadeslayer@saphira /media/Data/rekonq/build ±master⚡ » sudo make java
[13:55] <shadeslayer> look what you made me do
[13:58] <apachelogger> why do you make with sudo
[13:58] <apachelogger> !!!
[13:58] <claydoh> Riddell: sorry I'm a day late, but yes I can do the announcement if you still need it
[13:58] <apachelogger> you are mad, a mad hatter you are!!!
[13:58] <shadeslayer> because i dont have rekonq installed from packages
[13:59] <shadeslayer> and i use rekonq from git
[13:59] <apachelogger> also I should be messing with likelihoods and stuff
[13:59] <apachelogger> shadeslayer: one installs to ones home
[13:59] <shadeslayer> apachelogger: http://paste.kde.org/3889/ << kio_http logs
[13:59] <apachelogger> except for phonon that will just refuse to be installed to $home :D :D:D
[13:59] <Riddell> claydoh: you're still two days early :)
[14:00] <claydoh> Riddell: sweet
[14:00] <shadeslayer> i cleared them logs before i commented
[14:01]  * claydoh is still eagerly awaiting his ebay purchase: a dualcore dell laptop that isn't quite so ancient, can't wait to install Kubuntu on that one :)
[14:02] <apachelogger> shadeslayer: from restomp?
[14:02] <shadeslayer> apachelogger: whut?
[14:02] <claydoh> apachelogger:  ^^ maybe that is something I can blog about :)
[14:02] <apachelogger> claydoh: what if kubuntu does not work on it?
[14:02] <apachelogger> claydoh: you could also blog about how cool kde is ;)
[14:02] <claydoh> apachelogger: it should
[14:02] <claydoh> it is :)(
[14:03] <shadeslayer> Dell + Kubuntu works out pretty well
[14:03] <apachelogger> shadeslayer: is that log from restomp or from konquerr0r?
[14:03] <shadeslayer> its from rekonq
[14:03] <shadeslayer> via kdebugdialog
[14:03] <apachelogger> now where is the error there?
[14:03] <claydoh> shadeslayer: part of the reason I chose it
[14:03] <apachelogger> I do not see no error
[14:03] <shadeslayer> i dont see any error too
[14:03] <apachelogger> I blame it on rekum
[14:03] <shadeslayer> thats the problem -.-
[14:03] <apachelogger> kio does it all just as it should
[14:04] <c2tarun> need help in setting pbuilder environment :(
[14:04] <apachelogger> shadeslayer: maybe it is distrubed by the first sending that sorta went kaput
[14:05] <apachelogger> kio_http(24502)/kio_http_debug HTTPProtocol::sendQuery: Connection broken! ( "bugs.staging.launchpad.net" )   -- intended to write 958 bytes but wrote -1 .
[14:05] <apachelogger> !pbuilder
[14:05] <apachelogger> c2tarun: ^
[14:05] <shadeslayer> maybe something wrong here : http://paste.kde.org/3891
[14:06] <c2tarun> apachelogger: I was reading the same page, I have a question, like in chroot we have to login by chroot command and then our system locks into chroot env. is there anything like that in pbuilder?
[14:06] <apachelogger> shadeslayer: gdb will tell
[14:06] <apachelogger> c2tarun: pbuilder login
[14:07] <apachelogger> c2tarun: why would you want to login though?
[14:07] <shadeslayer> hmm
[14:07] <c2tarun> apachelogger: don't know, I thought that like in chroot we have to login, in this also we must. 
[14:07] <shadeslayer> c2tarun: nope
[14:08]  * apachelogger throws some hypotheses at shadeslayer
[14:08] <shadeslayer> use pdebuild!
[14:08] <apachelogger> take that H_0 and feed it to rekonqw
[14:08] <apachelogger> muhahaha
[14:08] <shadeslayer> :P
[14:08] <apachelogger> c2tarun: sudo pbuilder build some_new_packages.dsc
[14:09] <apachelogger> that will autobuild the source package of that .dsc and spew it somewhere
[14:09] <apachelogger> though I cant recall where it spews by default
[14:09] <apachelogger> probably somewhere in /var/cache/pbuilder
[14:09] <shadeslayer> /var/cache/pbuilder/result
[14:09] <c2tarun> apachelogger:  ok thanks :)
[14:09] <apachelogger> righto
[14:09]  * shadeslayer reads gdb man page
[14:10] <apachelogger> shadeslayer: the efficient developer makes it spew into .local/share/Trash/files btw :P
[14:10] <shadeslayer> hahaha :P
[14:10] <shadeslayer> the most efficient developer makes it spew into /tmp
[14:11] <apachelogger> nah
[14:11] <apachelogger> bad idea
[14:11] <shadeslayer> whai?
[14:11] <apachelogger> then your system goes crashy crashy and all is gone
[14:11] <shadeslayer> ah see ... i have my /tmp set to erase after 2 reboots
[14:11] <apachelogger> also maybe you are building software under NDA, then you should not have it outside your precious home at all :P
[14:11] <apachelogger> shadeslayer: I have my /tmp to point to /dev/null :P
[14:12] <shadeslayer> lol :P
[14:12] <c2tarun> apachelogger: 'sudo pbuilder create' will create a chroot. but of which version? 
[14:13] <apachelogger> maverick by default
[14:13] <apachelogger> --distribution natty will make it natty
[14:13] <apachelogger> or you create a .pbuilderrc in your home
[14:13] <apachelogger> and write DIST=natty in there
[14:13] <apachelogger> oh
[14:13] <apachelogger> and . /etc/pbuilderrc or something like that
[14:14] <apachelogger> oh
[14:14] <shadeslayer> or read the wiki page
[14:14] <apachelogger> actually it is
[14:14] <apachelogger> DISTRIBUTION=natty
[14:14] <c2tarun> apachelogger: thanks :)
[14:14] <shadeslayer> apachelogger: you actually have the full thing in there? "DISTRIBUTION"
[14:14] <shadeslayer> i just use DIST=
[14:14] <apachelogger> shadeslayer: you know, I believe Quintasan_ is a bad master to c2tarun
[14:15] <shadeslayer> oic
[14:15] <apachelogger> shadeslayer: I have a full blown pbuilderrc from back in the days
[14:15] <apachelogger> !!!
[14:15] <apachelogger> like when ScottK still was young and stuff :P
[14:15] <shadeslayer> ahahahaha
[14:15] <apachelogger> and since it is so old it is filled up with precious pirate booty, most terrific
[14:16] <apachelogger> the pbuilderrc that is, not ScottK
[14:16] <shadeslayer> apachelogger: hmm ... i cant seem to work out setting a break point in rekonq/src/networkaccessmanager.cpp:createRequest
[14:16] <apachelogger> PBUILDERSATISFYDEPENDSCMD="/usr/lib/pbuilder/pbuilder-satisfydepends-gdebi"
[14:16] <apachelogger> I am not even sure what it does
[14:16] <apachelogger> surely something buggy
[14:16] <apachelogger> otherwise I would remember
[14:16] <shadeslayer> (gdb) break networkaccessmanager:createRequest No source file named networkaccessmanager.  Make breakpoint pending on future shared library load? (y or [n])
[14:16] <apachelogger> well
[14:16] <apachelogger> as it says
[14:16] <Riddell> waa, kdebindings doesn't compile on arm if I remove the qreal_double stuff, it just fails further on :(
[14:16] <apachelogger> there is no such source file :P
[14:17] <shadeslayer> apachelogger: same thing with networkaccessmanager.cpp
[14:17] <apachelogger> you can also define the break by class btw
[14:17]  * apachelogger finds that more comfortable
[14:17] <ari-tczew> Riddell: did you see choqok request?
[14:17] <apachelogger> also it then can autocomplete for you
[14:17] <apachelogger> (if the appropriate symbols are loaded)
[14:18] <shadeslayer> the symbols are loaded afaik
[14:18] <apachelogger> then just tip it
[14:18] <apachelogger> erm
[14:18] <shadeslayer> Reading symbols from /usr/local/bin/rekonq...done.
[14:18] <apachelogger> tab it
[14:18] <apachelogger> ^^
[14:18] <apachelogger> :D:D:D:D
[14:18] <Riddell> ari-tczew: no, where?
[14:18] <apachelogger> emit giggle(GiggleShaldon);
[14:18] <ari-tczew> Riddell: bug 710981
[14:18] <shadeslayer> all i get is a bunch of weird looking vars like __CTOR_END__
[14:19] <apachelogger> then the symbols are not loaded
[14:19] <apachelogger> or you are not good at tabbing
[14:19] <apachelogger> you type
[14:19] <apachelogger> NetworkAccessManager::tab tab tab tab tab type something tab tab tab type something more tab tab tab enter
[14:19] <apachelogger> unless you are in a namespace
[14:19] <apachelogger> then of course you need to prefix the namespace and stuff
[14:21] <shadeslayer> apachelogger: i just did : gdb rekonq -> (gdb) break NetworkAccessManager::<tab> ... nothing
[14:21] <apachelogger> that is because the symbols are not loaded :P
[14:22] <apachelogger> run rekonq without bp once
[14:22] <apachelogger> then ctrl^c
[14:22] <apachelogger> and then you can set the bp for sure
[14:22] <apachelogger> unless you built without debug symbols ;) ;)
[14:23]  * apachelogger hands shadeslayer some more hypotheses
[14:23] <shadeslayer> omg symbohls!!!
[14:23] <apachelogger> oh
[14:23] <apachelogger> by ze way
[14:23] <Riddell> ari-tczew: what were the troubles with packaging upstream?
[14:24] <shadeslayer> hmm?
[14:24] <ari-tczew> Riddell: with old format debuild creates *0ubuntu.tar.gz - source + /debian/ in one.
[14:24] <apachelogger> about my java exercise thingy we had a final presentation and I am not sure why but it ended in me bashing my group's tutor for proposing to introduce everywhere and in the ear of the customer and stuff
[14:24] <apachelogger> the java fanbois obsession with interfaces is rather scary
[14:24] <shadeslayer> hahah
[14:24] <shadeslayer> apachelogger: also i found out why i make leaky programs
[14:24] <shadeslayer> it comes from my teachers
[14:25] <Riddell> ari-tczew: oh that's because it's a .bz2 and source format 1 doesn't do those
[14:25] <shadeslayer> they go " Oh! no need to delete that pointer, the OS will take care of it itself "
[14:25] <apachelogger> whut? :O
[14:25] <apachelogger> whut??????
[14:25] <shadeslayer> i spent 30 mins arguing that she should delete the pointer
[14:25] <apachelogger> whut??????????????????????????????????????????
[14:25] <ari-tczew> Riddell: I'd like to not recreate upstream tarball. Hope you understand my point.
[14:25] <shadeslayer> apachelogger: that too in Jahvah
[14:25] <apachelogger> in java you do not delete ptrs in java
[14:26] <Riddell> ari-tczew: yes that's fine, uploaded, thanks
[14:26] <shadeslayer> O_O
[14:26] <apachelogger> in java you do not delete no nothing
[14:26] <apachelogger> in java you have a garbage collector
[14:26] <shadeslayer> ah
[14:26] <apachelogger> so you pray to good that the garbage collector has a smart algorithm
[14:26] <apachelogger> of course it does not
[14:26] <apachelogger> but that is not the point
[14:26] <apachelogger> ...
[14:26] <ari-tczew> Riddell: many thanks ;-)
[14:26] <c2tarun> in the manual of pbuilder, it is written to install debian-archive-keyring but didn't explain why. I tried to google the term but failed to find material of what an debian-archive-keyring is?
[14:27] <apachelogger> ignore
[14:27] <Riddell> neversfelde: ping update needed on bug 706409
[14:27] <shadeslayer> apachelogger: how do you remove breakpoints?
[14:27] <apachelogger> c2tarun: it is a package that contains the gpg keys with which the official debian archive packages are signed
[14:27] <apachelogger> it is needed so that authenticy of the packages can be ensured
[14:27] <apachelogger> our pbuilder does that automagically for the ubuntu archive keys
[14:28] <apachelogger> shadeslayer: questions you ask...
[14:28] <apachelogger> del I think
[14:28] <apachelogger> me hasnt done gdb debugging in years
[14:28] <apachelogger> well
[14:28] <apachelogger> months maybe
[14:28] <c2tarun> thanks 
[14:31] <Quintasan> >implying old stuff is always good
[14:31] <Quintasan> apachelogger: ^
[14:31] <Quintasan> Referring to your "magical" pbuilderrc
[14:32] <Quintasan> shadeslayer: >they go " Oh! no need to delete that pointer, the OS will take care of it itself "
[14:32] <Quintasan> Are you serious?
[14:33] <Quintasan> This is soo....sooo... soomething it's not even funny :O
[14:34] <apachelogger> Quintasan: say hi to your padawn you unfriendly troll :P
[14:35] <Quintasan> If you are referring to c2tarun then we must first ask him if he want to join our ranks
[14:35] <apachelogger> in my C course you got -50% on points if you memleaked ;)
[14:35] <Quintasan> c2tarun: Anyways, hello there :)
[14:35] <c2tarun> hi I am here.
[14:35] <c2tarun> Quintasan: hello :)
[14:35]  * apachelogger personally would have gone for -90 but oh well
[14:36] <Quintasan> apachelogger: That's a good course
[14:36] <Quintasan> When I read what shadeslayer said I just held my head with both hands
[14:36] <Quintasan> "WTF" is not even halfway there in describing the dismay :O
[14:37] <shadeslayer> Quintasan: yeah .. dont ask
[14:38] <Quintasan> c2tarun: https://wiki.ubuntu.com/PbuilderHowto
[14:38] <apachelogger> in fact, never ask shadeslayer anything, you will only get rekonq diffs thrown at you...
[14:38] <shadeslayer> right now im wondering why even overload all this networkaccess crap
[14:38] <c2tarun> in packaging manual, there is an example of packaging from scratch. In that example they told to install some packages (I guess I have to install them into chroot) how to install them in chroot?
[14:38] <shadeslayer> apachelogger: right
[14:38] <apachelogger> shadeslayer: I wondered that all along
[14:39] <apachelogger> but if one were to voice all the wonderings about rekonq one would be voicing all day long
[14:39] <apachelogger> poor use of time that is
[14:39]  * shadeslayer looks at what it would take to remove those subclasses
[14:39] <Quintasan> c2tarun: Change base.tgz Location contains the pbuilder config which apachelogger deems strange black, bad magic which you apparently shouldnt use but I use it and nothing has exploded yet
[14:39] <shadeslayer> bwahahaha
[14:39] <apachelogger> whut
[14:40] <apachelogger> where did I say one should not use it?
[14:40] <Quintasan> apachelogger: at least two times you said it
[14:40] <shadeslayer> apachelogger: rekonq overloads all that crap to use kio cache
[14:40] <apachelogger> Quintasan gets a beatin' at uds
[14:40] <apachelogger> !
[14:40] <Quintasan> pfff
[14:40]  * Quintasan will go back trough the logs
[14:40] <apachelogger> shadeslayer: does kio not cache?
[14:40] <c2tarun> Quintasan: what is the relation in b/w changing location and those packages mentioned ? :/
[14:41] <Quintasan> c2tarun: this config is just for managing pbuilder chroots
[14:41] <Quintasan> c2tarun: if you want to install something in a chroot, I assume you are using pbuilder
[14:41] <shadeslayer> apachelogger: https://projects.kde.org/projects/extragear/network/rekonq/repository/revisions/master/entry/src/networkaccessmanager.cpp#L66
[14:41] <Quintasan> c2tarun: sudo pbuilder --login --save-after-login
[14:41] <c2tarun> Quintasan: actually I am creating pbuilder, it will take some time
[14:42] <Quintasan> c2tarun: you are creating a natty one?
[14:42] <c2tarun> Quintasan: nope maverick.
[14:42] <shadeslayer> lines 57-64 ... i have no idea what they do
[14:42] <Quintasan> okay, you will also need it at some point
[14:42] <apachelogger> they do make love to the protocolmanager
[14:43] <apachelogger> Quintasan: he does not want to install anything into the chroot at this point ;)
[14:43] <Quintasan> well, that's kinda expected without having a one :P
[14:43] <apachelogger> beware of the intention behind a question, for the question can deceive you
[14:44]  * apachelogger also hands Quintasan some hypotheses and is now all out of them \\o/
[14:44] <Quintasan> c2tarun: what makes you think you want install something there?
[14:44] <Quintasan> >hypotheses
[14:45] <Quintasan> Why would I want your hypotheses apachelogger? :O
[14:45] <shadeslayer> Quintasan: because he has too many of them
[14:45] <c2tarun> Quintasan: I used chroot env earlier and in that we have to install each and every package we want to use there.
[14:45] <Quintasan> c2tarun: no need to do this in a pbuilder
[14:46] <c2tarun> Quintasan: so i just guessed. and its also written in the manual's tutorial
[14:46] <Quintasan> c2tarun: you add the dependencies to the debian/control file of a package which should be pulled and they will be installed during the build process and then they will get removed
[14:47] <c2tarun> Quintasan: OK thats cool, is there any manual of packaging using pbuilder. wiki manual is using something called CDBS or chroot.
[14:48] <Quintasan> I'm not sure what are you reading c2tarun :)
[14:48] <c2tarun> Quintasan: https://wiki.ubuntu.com/PackagingGuide/Complete
[14:49] <Quintasan> c2tarun: You want to make a new package?
[14:50] <c2tarun> Quintasan: actually I am new to it. apachelogger told me that there is new version of bangarang out but kubuntu archive dont have it. so I was trying to make it from its source code.
[14:51] <Quintasan> Always, always search Debian and Ubuntu latest release for packages
[14:51] <Quintasan> c2tarun: Actually, natty has a package imported directly from Debian, but the version is old: 1.0.1-1
[14:52] <Quintasan> c2tarun: Do you have the source tar-ball?
[14:52] <c2tarun> ya i downloaded it from kde-apps.org
[14:52] <c2tarun> Quintasan: ^
[14:52] <Quintasan> Awesome, so, instead of doubling the workload and creating the packaging from scratch we can just use existing one.
[14:53] <c2tarun> Quintasan: ok, how
[14:54] <Quintasan> c2tarun: open up a command line and go to where you have the source
[14:54] <Quintasan> make sure it's a separate directory cause we will grab some files
[14:54] <Quintasan> c2tarun: what you want to do is to pull latest Ubuntu source package available
[14:54] <c2tarun> Quintasan: ok I m inside a directory which only has tarball
[14:54] <Quintasan> c2tarun: pull-lp-source bangarang
[14:55] <shadeslayer> if that gives a error hit Quintasan
[14:55] <Quintasan> That command will download the latest source of bangarang available on Launchpad
[14:55] <Quintasan> shadeslayer: I just downloaded it
[14:55] <shadeslayer> if it doesn't give me a cookie
[14:55] <shadeslayer> Quintasan: maybe he doesnt have the devscripts? :>
[14:56] <Quintasan> shadeslayer: the guide tells to install them :)
[14:56] <c2tarun> ya its doing something, actually pbuilder create is also working simultaneously so it'll take some time
[14:56] <shadeslayer> ah your following the guide
[14:56] <shadeslayer> now where's my kookie?
[14:56] <c2tarun> Quintasan: meanwhile can u please explain me what does pulling means?
[14:56] <Quintasan> You don't get any cookies
[14:57] <Quintasan> c2tarun: it's just downloading source files from launchpad
[14:57] <shadeslayer> apachelogger stole all our kookies
[14:57] <c2tarun> Quintasan: ya its done. :)
[14:57] <Quintasan> c2tarun: download-lp-sources would be longer probably :P
[14:57] <Quintasan> c2tarun: http://i.imgur.com/ITEzF.png
[14:58] <Quintasan> That's what you should have in your sources dir
[14:59] <c2tarun> Quintasan: ya i have it
[14:59] <Quintasan> c2tarun: Now, I usually rename the tarball first of all because I usually forget to do this later :P So 'mv bangarang-2.0.tar.gz bangarang_2.0.orig.tar.gz'
[15:00] <Quintasan> That's the naming policy, there should be a "_" between the package name and the version and .orig. before rest of the extension marking it as an ORIGInal tarball
[15:00] <Quintasan> Naming policy in a big shortcut :P
[15:00] <c2tarun> that was i just about to ask :)
[15:01] <Quintasan> so, now we unpack the new sources with 'tar zxvf bangarang_2.0.orig.tar.gz'
[15:01] <apachelogger> Quintasan: I don't want them, so clearly I needed to get rid of them
[15:01] <Quintasan> You get a 'bangarang-bangarang' directory so rename it to 'bangarang-2.0'
[15:01] <Quintasan> apachelogger: Can I get rid of them too?
[15:02] <apachelogger> sure, just not in my direction
[15:02]  * Quintasan passes them on to shadeslayer
[15:02] <apachelogger> Quintasan: you might want to inspect them first
[15:02] <Quintasan> There you go
[15:02] <c2tarun> ok
[15:02] <apachelogger> you never know if you give away a good H
[15:02] <c2tarun> Quintasan: ya done
[15:03] <Quintasan> awesome, then we will reuse the packaging by
[15:03] <Quintasan> cp -rf bangarang-1.0.1/debian bangarang-2.0/
[15:03] <Quintasan> That copied the debian/ directory from the old package to the new one
[15:04] <Quintasan> c2tarun: I assume you read through the guide and know which files do what?
[15:04] <c2tarun> ya i know :)
[15:05] <c2tarun> Quintasan: copied
[15:05] <Quintasan> It has a watch file. Apparently you can update packages using some uscan magic but I tried it once and it made a mess
[15:06] <c2tarun> Quintasan: can u please explain me what is a watch file. I never understood actually
[15:06] <Quintasan> It scans upstream files for a newer release of the package
[15:06] <Quintasan> so it's a verison check of some sort
[15:07] <c2tarun> Quintasan: which mean we can check the current version in archive?
[15:07] <Quintasan> c2tarun: nope, the watch file scans UPSTREAM files, upstream as in the developer that made the application
[15:08] <Quintasan> I can tell you I used it once and it all it did was some mess but I think it works because some people use it.
[15:08] <c2tarun> Quintasan: ok, so we can check the latest version available for the application?
[15:08] <Quintasan> c2tarun: Yes
[15:08] <Quintasan> But we will do it the other way since not all packages have "watch" files available
[15:09] <c2tarun> Quintasan: ok, one more question, if we want to check the current version in archive how can we do that?
[15:09] <apachelogger> Quintasan: I think the bigger gain in watch files is really tracking the up-to-dateness rather than actually conducting the package update
[15:10] <Quintasan> c2tarun: okay, if you want to know latest package version available in YOUR distribution archive by apt-cache show <package name>
[15:10] <Quintasan> c2tarun: http://paste.ubuntu.com/560990
[15:10] <Quintasan> This is what I get with apt-cache show bangarang on natty, it will show nothing if there is no such pacakge
[15:11]  * apachelogger notes that apt-cache policy yields less spew
[15:11] <Quintasan> c2tarun: if you want to know what is the latest package version in latest development release you will  have to ask launchpad or debian package list
[15:11] <Riddell> debfx: I added some comments to https://wiki.kubuntu.org/Kubuntu/ReducingDiskFootprint
[15:11] <c2tarun> Quintasan: ok, got it
[15:12] <Quintasan> c2tarun: now, something I usually do is cd bangarang-2.0/debian 
[15:12] <c2tarun> Quintasan: now what after copying the debian folder/
[15:12] <c2tarun> ?
[15:12] <c2tarun> Quintasan: i m already in there :)
[15:12] <Quintasan> do a dir and look through all files there so I know what the hell I'm working with
[15:13] <Quintasan> Usually I look at debian/{control,rules,compat} and *.install files
[15:13] <c2tarun> Quintasan: ok, i have many files, with control, changelog and one watch file.
[15:13] <apachelogger> ls > dir
[15:13] <apachelogger> ls has the coloring by default :D :D :D
[15:13] <shadeslayer> yep
[15:14]  * Quintasan has alias dir = "ls --color-auto" or something like this
[15:14] <c2tarun> ok, let me post the o/p
[15:14] <apachelogger> Quintasan: what pointlessness is that?
[15:14] <apachelogger> dir != ls
[15:14] <apachelogger> scary scary
[15:14] <Quintasan> apachelogger: Don't give a damn, I usually use ls to display stuff in a directory
[15:14] <Quintasan> or ls -al sometimes
[15:14] <c2tarun> here is what i got: http://paste.ubuntu.com/560991/
[15:14] <shadeslayer> apachelogger: sigh ... breaking on  (gdb)  break NetworkAccessManager::createRequest(QNetworkAccessManager::Operation, QNetworkRequest const&, QIODevice*) doesnt do shit
[15:15] <apachelogger> Quintasan: you speak funny gnu
[15:15] <apachelogger> everyone else does ls -la :P
[15:15] <shadeslayer> i commeneted on a bug, and execution didnt stop
[15:15] <Quintasan> omfg apachelogger go help shadeslayer instead of disturbing me :P
[15:15] <shadeslayer> lawl
[15:15] <apachelogger> shadeslayer: clearly something is the broken then, right? :P
[15:15] <Quintasan> c2tarun: that's pretty much what you should have there
[15:15] <shadeslayer> apachelogger: clearly gdb is broken  :P
[15:16] <apachelogger> or you dont know how to use it
[15:16] <shadeslayer> same thing as gdb being broken
[15:16] <Quintasan> c2tarun: well, the case here is to look around and make sure you understand the files inside in case you run into some problems
[15:16] <Quintasan> c2tarun: you don't have to do this everytime you upgrade a package
[15:16] <apachelogger> shadeslayer: iGree
[15:17] <c2tarun> Quintasan: ok, i don't know about some files here.
[15:17] <Quintasan> c2tarun: "cd .." so we land into bangarang-2.0
[15:17] <Quintasan> c2tarun: go ahead and ask, if I don't know something we can always pester apachelogger
[15:17] <apachelogger> emit yawn(YawnHippo);
[15:17] <c2tarun> like bangarang.1, menu, *nepomukwriter.1
[15:17] <apachelogger> I shall not be pestered
[15:17] <c2tarun> *=bangarang
[15:17] <apachelogger> I have exam in t-2h or so
[15:18] <Quintasan> bangarang.1 and *nepomukwriter.1 are MANual pages
[15:18] <shadeslayer> which means i can pester you for 2 hours
[15:18] <Quintasan> c2tarun: I hoped you used man before, right? :P
[15:18] <c2tarun> Quintasan: ya :)
[15:18] <shadeslayer> also
[15:18] <c2tarun> what about menu?
[15:18] <Quintasan> c2tarun: and bangarang.manpages tells the build system what files are to be installed as manual pages
[15:18] <shadeslayer> Quintasan: be ready to write man pages at UDS if apachelogger decides to come
[15:18] <Quintasan> shadeslayer: You will do that
[15:18] <Quintasan> :P
[15:19] <shadeslayer> Quintasan: i had my share of man page writing
[15:19] <Quintasan> c2tarun: now, this menu stuff is new to me
[15:19] <shadeslayer> id rather stick to C++
[15:19] <Quintasan> apachelogger: wtf is this menu?
[15:19] <Quintasan> apachelogger: http://paste.kde.org/3896
[15:19] <apachelogger> :O
[15:19] <apachelogger> and we made you kubuntu dev? :O
[15:19] <apachelogger> holy smokes
[15:20] <shadeslayer> lmao
[15:20] <apachelogger> http://www.debian.org/doc/packaging-manuals/menu.html/
[15:20]  * apachelogger takes a note to ask more questions about files in debian/
[15:21] <Quintasan> oh, that's stuff for generating menus in DEs? @_@
[15:21] <c2tarun> Quintasan: got it :)
[15:21] <Quintasan> now, there is a debian/source/format files
[15:21] <Quintasan> file*
[15:22] <c2tarun> yup
[15:22] <apachelogger> Quintasan: in window managers actually
[15:22] <Quintasan> It tells which source format are we using in this package
[15:22] <apachelogger> predates the desktop file magic by a bazillion years
[15:22] <apachelogger> as old as debian is itself
[15:22] <Quintasan> apachelogger: who still uses this stuff when KDE is around? :P
[15:22] <c2tarun> Quintasan: ok
[15:22] <apachelogger> back in the days one only had crappy window managers
[15:22] <apachelogger> Quintasan: debian
[15:23] <shadeslayer> such as fwm :P
[15:23] <Quintasan> c2tarun: now go back to the source (bangarang-2.0) dir
[15:23] <Quintasan> and do "dch -i"
[15:23]  * apachelogger starts writing a header for himself
[15:24] <c2tarun> Quintasan: I think we didn't made any changes to source code. Than why are we updating changelog?
[15:24] <Quintasan> c2tarun: That's not the changelog for source code :)
[15:24] <Quintasan> c2tarun: It's changelog of packaging
[15:24] <c2tarun> Quintasan: oh :)
[15:25] <Quintasan> c2tarun: Now what we want to do is to change the version form 1.0.1-1ubuntu1 to 2.0-0ubuntu1
[15:25] <c2tarun> Quintasan: what should i write there?
[15:25] <Quintasan> The line should look like this "bangarang (2.0-0ubuntu1) natty; urgency=low"
[15:26] <c2tarun> ok, and anything with maverick and urgency?
[15:26] <Quintasan> c2tarun: maverick should be natty
[15:27] <c2tarun> Quintasan: ^
[15:27] <Quintasan> You don't usually change urgency unless new version fixes something critial
[15:28] <c2tarun> Quintasan: ok, anything i should write here?
[15:28] <apachelogger> shadeslayer, Quintasan: http://paste.ubuntu.com/560998/ what do ye say?
[15:28] <shadeslayer> *click*
[15:28] <shadeslayer> ahahahahaha
[15:28] <Quintasan> apachelogger: you forgot pretendToBeWorking()
[15:29] <apachelogger> oh
[15:29] <apachelogger> true
[15:29] <Quintasan> c2tarun: Well
[15:29] <Quintasan> c2tarun: It usually mentions what you changed in the packaging
[15:29] <Quintasan> c2tarun: Since we are updating it I would add "New upstream release" for now
[15:30] <c2tarun> Quintasan: ok :)
[15:30] <Quintasan> If something pops out that makes you need to change something in the packaging we can add it at a later point
[15:30] <Quintasan> c2tarun: Save the changes and exit
[15:30] <c2tarun> Quintasan: ok, done.
[15:30] <c2tarun> Quintasan: done
[15:30] <Quintasan> do "debuild -S"
[15:31] <Quintasan> c2tarun: it should ask for passphrase for you gpg key, it signs the package and the *.dsc and *.changes file
[15:31] <Quintasan> hmm
[15:31] <c2tarun> Quintasan: I think I got an error.
[15:31] <Quintasan> it will probably fail at patching
[15:32] <Quintasan> damn it
[15:32] <Quintasan> :S
[15:32] <Quintasan> shadeslayer: I sense some DSO stuff jumping at me
[15:32] <c2tarun> wait let me show it to u
[15:32] <shadeslayer> apachelogger: http://paste.kde.org/3898/
[15:32] <c2tarun> Quintasan: http://paste.ubuntu.com/560999/
[15:33] <apachelogger> shadeslayer: do you think the void ** are a bit unsafe?
[15:33] <apachelogger> could happen that someone tries to feed me java or something
[15:33] <shadeslayer> apachelogger: yeah ... i was thinking that :P
[15:33]  * apachelogger better forward decls paritcular classes
[15:33] <Quintasan> oh
[15:33] <Quintasan> c2tarun: You have to install pkg-kde-tools
[15:33] <apachelogger> shadeslayer: your korundum is broken
[15:34] <c2tarun> Quintasan: oh... manual was for ubuntu
[15:34] <shadeslayer> apachelogger: blame upstream
[15:34] <shadeslayer> its from git
[15:34] <shadeslayer> so a fix is appreciated
[15:34] <apachelogger> I have no time
[15:34] <Quintasan> c2tarun: now, it will fail at patching
[15:34] <apachelogger> I am working
[15:34] <shadeslayer> After this operation, 55.5MB disk space will be freed. << Neon freeing disk space :O
[15:34] <c2tarun> Quintasan: why so?
[15:34] <shadeslayer> thats a first
[15:35] <apachelogger> hm
[15:35] <Quintasan> c2tarun: because this particular patch was applied upstream
[15:35] <apachelogger> then clearly something broke
[15:35] <Quintasan> c2tarun: When a patch fails to apply you need to check whether it was applied upstream or it needs some line adjusting
[15:35] <Quintasan> kubuntu_01_linker_fix.diff <--- this patch went upstream
[15:36] <c2tarun> Quintasan: chk this http://paste.ubuntu.com/561000/
[15:36] <apachelogger> shadeslayer: http://paste.ubuntu.com/561001/ better?
[15:36] <Quintasan> c2tarun: so you can do "rm debian/patches/kubuntu_01_linker_fix.diff"
[15:36] <Quintasan> c2tarun: look at line 28, it says which patch it was applying
[15:36] <c2tarun> Quintasan: can u please explain me what happened after my debuil -S
[15:36] <shadeslayer> apachelogger: lol //    void study();
[15:37] <apachelogger> ^^
[15:37] <Quintasan> c2tarun: it failed applying the patch
[15:37] <Quintasan> c2tarun: less vim debian/patches/kubuntu_01_linker_fix.diff
[15:37] <Quintasan> urgh
[15:37] <Quintasan> -vim there
[15:37] <shadeslayer> apachelogger: best not to put it there, you might be tempted to uncomment it later on
[15:37] <apachelogger> well
[15:37] <apachelogger> it is not implemented
[15:37]  * shadeslayer goes to #kde-devel with his broken kroundum
[15:38] <Quintasan> c2tarun: and then look at the files which it patches and you will see the lines are already there
[15:38] <apachelogger> shadeslayer: kde-ruby might be tter
[15:38] <shadeslayer> hmm
[15:38] <apachelogger> oh
[15:38] <apachelogger> look what I did
[15:38] <Quintasan> c2tarun: so the patch is useless now
[15:38] <apachelogger> scary scary
[15:38] <c2tarun> Quintasan: PM!
[15:38] <shadeslayer> apachelogger: #kde-ruby is filled with markey
[15:39] <shadeslayer> i dont feel safe  now
[15:39] <apachelogger> lolz
[15:39] <apachelogger> oh
[15:39] <apachelogger> I could tweak that a bit
[15:39] <shadeslayer> tweak what 
[15:39] <apachelogger> be{2} tter
[15:39] <shadeslayer> your class?
[15:39] <apachelogger> no
[15:39] <shadeslayer> korundum?
[15:39] <apachelogger> shadeslayer: kde-ruby might be{2} tter
[15:40] <apachelogger> now lets see, how do we fix them whitespace problem
[15:40] <shadeslayer> heh
[15:40] <apachelogger> ah
[15:40] <apachelogger> maybe
[15:40] <apachelogger> or no
[15:40] <apachelogger> hm
[15:41] <shadeslayer> ah oh ... ...
[15:41] <shadeslayer> i could just start the recipe, all the deps are satisfied
[15:41] <shadeslayer> not my fault that korundum is broken
[15:42] <apachelogger> ah regex is crap
[15:42] <apachelogger> oh
[15:42] <apachelogger> maybe not
[15:42] <apachelogger> (be |be){2}tter
[15:43] <apachelogger> then again that also matches bebetter whch is no goody
[15:43] <apachelogger> hm
[15:43] <apachelogger> oh
[15:44] <apachelogger> meh meh meh
[15:44] <apachelogger> I give up
[15:46] <shadeslayer> Internal Server Error
[15:46] <shadeslayer> what are you running? Winduh's?
[15:46] <afiestas> I'm getting a loooooooot of crashes with the next bt: http://paste.kde.org/3900/
[15:47] <afiestas> kdevelop crash (because of kdevmanpage.so) amarok crash, crystal plasmoid (compiled by myself) crash
[15:47] <shadeslayer> thats webkit being sucky
[15:47] <afiestas> I can see that :p
[15:47] <afiestas> rekonq crashing too
[15:48] <shadeslayer> now to fix some webkit bugs
[15:48] <afiestas> no thanks... 
[15:48] <afiestas> :p
[15:49] <shadeslayer> afiestas: i was talking about myself :P
[15:49] <afiestas> aah : xd
[15:49] <apachelogger> you are very selfish
[15:58] <shadeslayer> this stuff needs in-depth study during the weekend -.-
[15:59] <shadeslayer> what to do then ... 
[15:59] <shadeslayer> apachelogger: i need #work
[15:59] <shadeslayer> something easy
[15:59] <shadeslayer> well ... i could finish reading the design guidelines
[16:09] <Quintasan> apachelogger, shadeslayer: I have to go to my English lessons soon and then I also have homework to do, c2tarun should have a debdiff ready soon so please review
[16:09] <shadeslayer> will do
[16:09] <shadeslayer> im on for another hour
[16:09] <Quintasan> shadeslayer: about the time it finishes downloading and building on his PC
[16:09] <shadeslayer> then i sleep .. i haz a java lab tomorrow :S
[16:10] <shadeslayer> hehehe
[16:10] <Quintasan> I'm in a hurry so see you later
[16:10] <shadeslayer> ill come online via my phone
[16:10] <shadeslayer> cya
[16:12] <shadeslayer> c2tarun: you have a interesting IP btw
[16:12] <c2tarun> guys I have my debdiff ready.
[16:12] <shadeslayer> 1.23.171.154
[16:12] <c2tarun> IP??
[16:12] <shadeslayer> oooh
[16:12] <shadeslayer> c2tarun: show 
[16:12] <c2tarun> oh :)
[16:12] <shadeslayer> pastebinit somewhere :)
[16:12] <c2tarun> ok wait
[16:13] <c2tarun> shadeslayer: i think that file is too big to be pasted, anyother way?
[16:14] <shadeslayer> c2tarun: can you take a diff of the debian folders?
[16:14] <c2tarun> wait let me try
[16:16] <c2tarun> http://paste.ubuntu.com/561019/
[16:16] <c2tarun> shadeslayer: ^
[16:16] <shadeslayer> looking
[16:17] <shadeslayer> c2tarun: try diff -u 
[16:17] <shadeslayer> wait no
[16:17] <c2tarun> shadeslayer: ya
[16:17] <shadeslayer> boi .. its been long since i used diff
[16:18] <c2tarun> hmmm..... I myself used it once. :(
[16:18] <shadeslayer> ah
[16:18] <shadeslayer> c2tarun: diff -Nru
[16:19] <shadeslayer> between the 2 debian folders
[16:20] <c2tarun> shadeslayer: http://paste.ubuntu.com/561021/
[16:21] <shadeslayer> c2tarun: give a explanation as to why you removed the patches in the changelog
[16:22] <Quintasan> derp
[16:22] <c2tarun> coz debuild -S failed on patching process.
[16:22] <shadeslayer> looks good otherwise
[16:23] <shadeslayer> c2tarun: nope .. they were probably applied upstream
[16:23] <Quintasan> c2tarun: They were applied upstream
[16:23] <c2tarun> ya somewhat after that :S
[16:23] <Quintasan> c2tarun: Ther reason then failed to apply during the debuild -S stage is that they were applied upstream
[16:24] <Quintasan> but well
[16:24] <Quintasan> not bad
[16:24] <c2tarun> actually very sorry Quintasan but I'll read patching once by myself, u tried a lot but i understood a little :(
[16:24] <Quintasan> I started not even knowing what on earth was diff anyways
[16:24] <c2tarun> :)
[16:25] <Quintasan> c2tarun: It's just that I've grown too acustomed to technical wording and I don't know how to explain it in simple language
[16:25] <Quintasan> :S
[16:26] <c2tarun> Quintasan: no prob :) can u please refer me to any link on patching.
[16:26] <Quintasan> shadeslayer: care finding some guide on quilt? I think we had one on Wiki
[16:26] <c2tarun> Quintasan: I just looked at  ur name :P u gave an interview in fullcircle??
[16:26] <shadeslayer> looking
[16:27] <Quintasan> Full Circle Magazine?
[16:27] <c2tarun> Quintasan: yup
[16:27] <shadeslayer> https://wiki.kubuntu.org/Kubuntu/Ninjas/QuiltMagic
[16:27] <Quintasan> c2tarun: Can't say I did that, you sure I was there? :O
[16:27] <shadeslayer> there ya go ^^
[16:27] <c2tarun> ya may be b/w issue 41-45
[16:28] <c2tarun> issue 44 i just saw
[16:28] <Quintasan> LOL
[16:28] <Quintasan> No, seriously
[16:29] <Quintasan> I'm there :O
[16:29] <c2tarun> cool :)
[16:29] <Quintasan> Thanks for telling me
[16:30] <shadeslayer> whut
[16:30] <shadeslayer> WHUT
[16:30] <shadeslayer> Quintasan: your famous?
[16:30]  * Quintasan and his awesome hat
[16:30] <c2tarun> ya and hat too :)
[16:30] <Quintasan> Too bad I broke the hat while skateboarding
[16:37] <shadeslayer> so rekonq now has a UA string changer
[16:37] <shadeslayer> rejoice
[16:37] <Quintasan> yay for broken X stack
[16:37] <shadeslayer> Riddell: ^^
[16:38] <yofel> grr... evdev crashes on suspend here
[16:38]  * yofel goes updating
[16:43] <shadeslayer> http://i.imgur.com/7tXFv.png
[16:43] <shadeslayer> :D
[16:44] <yofel> you sure like useless features..
[16:44] <shadeslayer> yofel: not useless actually
[16:44] <shadeslayer> for eg. the new yahoo only works with chrome/FF
[16:44] <yofel> well yeah, but how often do you actually need that...
[16:44] <yofel> oh ok
[16:44] <shadeslayer> well .. if you use yahoo ... alot? :P
[16:45] <yofel> yeah, which I don't :P
[16:45] <shadeslayer> right .. but we had this discussion at uds ... rekonq wont open yahoo mail
[16:47] <Riddell> if I remember what the Chrome chap told us, it needs the user agent changed (or was that hotmail)?
[16:49] <shadeslayer> yep
[16:49] <shadeslayer> all it needs is a user agent change
[16:49] <shadeslayer> i think i made it change the user agent and it worked
[16:50] <shadeslayer> now i cant remember my yahoo pass
[17:08] <debfx> Riddell: I've replied to your comments
[17:08] <debfx> apachelogger: what's the status of dvd playback in natty?
[17:08] <debfx> dragonplayer + gstreamer backend doesn't work at all?
[17:10] <debfx> Riddell: imho libgeoip should suggest geoip-database and packages which really need geoip can recommend/depend on the database
[17:11] <Riddell> tricky part is then we have to work out what packages really need geoip
[17:12] <debfx> yes and it's something that needs to be done in Debian
[17:15] <Riddell> debfx: why do you say that?
[17:33] <debfx> Riddell: because we would have to review all new packages that use libgeoip
[17:34] <shadeslayer> apachelogger: http://searchengineland.com/google-bing-is-cheating-copying-our-search-results-62914 < *snigger*
[17:35] <maemologger> Any nus for me?
[17:37] <ari-tczew> does somebody working on ktorrent?
[17:42] <shadeslayer> lol
[17:42] <shadeslayer> maemologger: look at #rekonq from your main account
[17:42] <shadeslayer> commit floods ftw
[17:42] <maemologger> No quassel
[17:43] <maemologger> You do work
[17:43] <shadeslayer> hmm?
[17:43] <maemologger> Actually, can someone paste me my header?
[17:44] <yofel> what header?
[17:44] <maemologger> Mine
[17:44] <shadeslayer> maemologger: http://paste.ubuntu.com/561001/
[17:44] <shadeslayer> yofel: apachelogger.h :P
[17:44] <maemologger> Cheers
[17:44] <yofel> LOL
[17:46] <maemologger> Stuff is missing
[17:46] <maemologger> Brainstorm plz
[17:47] <shadeslayer> what happens if apachelogger.h gets into rekonq and stl
[17:47] <shadeslayer> i cannot imagine
[17:48] <maemologger> No template means no stl
[17:51] <maemologger> Also there is a bug
[17:51] <maemologger> Instance is a ptr and a var
[18:03] <shadeslayer> maemologger: patch : http://git.reviewboard.kde.org/r/100456/diff/#index_header
[18:07] <maemologger> Wtf
[18:08] <shadeslayer> maemologger: :P
[18:08] <maemologger> Is it pron?
[18:09] <shadeslayer> maemologger: its a 176KB patch
[18:10] <maemologger> It happens
[18:10] <maemologger> Reviewboard is not suited for that
[18:10] <maemologger> Imho
[18:10] <shadeslayer> yep
[18:10] <shadeslayer> gitorious++
[18:11] <maemologger> I think overlord of reviews aseigo agrees
[18:11] <shadeslayer> gitorious has a awesome merge system
[18:11] <shadeslayer> maemologger: i hear its going to get better soon
[18:44] <jjesse> umm what's up with the bzr commit notificiations today?
[18:44] <maco> jjesse: what?
[18:46] <jjesse> in my gmail i got a bunch of bzr commit messages from lp in regars to kubuntu stuff
[18:46] <yofel> probably you're subscribed to the branches on launchpad?
[18:47] <jjesse> maybe wonde rhow
[18:48] <Riddell> jjesse: I just approved the backlog of stuff blocked on that list
[18:48] <Riddell> ignore it
[18:49] <Riddell> I set a filter so it shouldn't happen in future
[19:06]  * Riddell wonders what to do with bug 709416
[19:07] <Riddell> it's from a customer of canonical so I feel I should do something but if he's moved to another e-mail client I don't think there's much I can do
[19:14] <Quintasan> Riddell: tell him to backup
[19:14] <Quintasan> I just can't imagine how they want us to keep consistency with such a big leap in software stack :O
[19:17] <Riddell> mm, it's not a supported upgrade indeed
[19:26] <maco> Riddell: do you think they went through 10.04 or mashed the sources.list?
[19:27] <maco> though when i think about it...i dont think my contacts survives 9.10 -> 10.04. i had to tell kaddressbook "listen dear, you made this vcf before, dont you remember? please just keep using it, its right over here"
[19:28] <Riddell> maco: no idea
[19:29] <Tm_T> right, akonadi-switch doesn't bring the old contacts along
[19:31] <DarkwingDuck> ahhhh, good old Akonadi
[20:35] <sheytan> Quintasan ping
[20:36] <sheytan> Quintasan http://img20.imageshack.us/img20/8500/pn128.png
[21:23] <debfx> Riddell: you haven't actually demoted gvfs to suggests in gstreamer
[21:24] <debfx> http://launchpadlibrarian.net/63229777/gst-plugins-base0.10_0.10.32-1_0.10.32-1ubuntu1.diff.gz
[21:28] <Riddell> oh it has silly control.in evilness
[21:43] <Riddell> well needs to wait for alpha 2 now
[21:49] <Riddell> natty-desktop-powerpc.iso         01-Feb-2011 20:13  698M
[21:49] <Riddell> ScottK: success ^^
[23:38] <ScottK> Riddell: Looks like I guessed just about right.
[23:38] <ScottK> Tm_T: ^^^ Can you test?