[01:35] <nixternal> DarkwingDuck: pong
[01:35] <nixternal> getting ready to eat so i might be afk for a few
[02:06] <DarkwingDuck> nixternal: can you upload any and everything you have worked on and update https://wiki.kubuntu.org/Kubuntu/Todo/Natty so I have a snapshot of where we stand as I go into 48 hours of docbook?
[03:10] <c2tarun> I was building kde4libs and I got this error http://pastebin.com/kGidy8LF, when I looked I found that on the location instead of backend there is folder name helper, file inside helper is kauth_helper_plugin.so can anyone please help :/
[03:18] <c2tarun> I am asking this question again on #ubuntu-motu if anyone found the solution please reply there. thank you
[04:21] <c2tarun> Riddell: please dont turn of that maverick ec2, I'll be back shortly. Thank you :)
[08:54] <bambee> morning
[08:54] <skfin> Good morning
[09:24] <Riddell> 4.6.2 release day today
[09:24] <jussi> :)
[09:26] <ulysses> not yesterday?
[09:46] <c2tarun> I was building kde4libs and I got this error http://pastebin.com/kGidy8LF, when I looked I found that on the location instead of backend there is folder name helper, file inside helper is kauth_helper_plugin.so can anyone please help :/
[09:47] <apparle> hey guys, I need to do some interpolation for my project, do you know any library which has interpolation functions?
[09:52] <Riddell> c2tarun: that polkit stuff does change a bit
[09:52] <Riddell> let me look at how we did it in 4.6.1
[10:06] <Riddell> c2tarun: dunno looks much the same, I'll need to compile it here to see what's up
[10:12] <c2tarun> Riddell: I adjusted few install files and its building right now, but actually I commented out the lines which were causing trouble. :/
[10:20] <c2tarun> Riddell: kde4libs built perfectly for natty, but why I am getting these errors in maverick? and what is polkit?
[10:22] <Riddell> polkit is an authentication mechanism, it is known for making incompatible releases, there may be this issue because maverick has a different version than natty
[10:49] <Riddell> c2tarun: kde4libs build fine here without problem
[10:50] <c2tarun> Riddell: on what machine? maverick?
[10:50] <Riddell> on my local chroot, yes maverick
[10:51] <c2tarun> Riddell: well either you are using super computer or ec2 is slow, because I started building it long before posting the error message and its still 64% :(
[10:54] <c2tarun> Riddell: if its build can you please upload it :/
[10:55] <Riddell> c2tarun: running  apt-cache policy libpolkit-qt-1-dev  on your ec2 machine shows me you don't have the polkit from kubuntu-ninjas installed so that's why it didn't get picked up
[10:56] <Riddell> my machine is quad core, ec2 machines are single core
[10:56] <yofel> o/
[10:57] <c2tarun> Riddell: well if its absence is creating problem then it'll be a problem on pbuilder as well, dont you think it should be included in build-depends 
[10:57] <yofel> c2tarun: what did you mean yesterday that you did what I already did?
[10:57] <Riddell> yofel: he was looking at the old version, nothing to worry about
[10:57] <yofel> ah ok
[10:57] <c2tarun> yofel: actually I saw a package with versino 4.6.1 and I thought its 4.6.2 :) I misreaad
[10:58] <yofel> heh
[10:58] <Riddell> c2tarun: yes you could say that
[10:58] <c2tarun> Riddell: ok, so if it build successfully there, are you uploading it to ppa?
[10:58] <Riddell> yes I've uploaded it
[10:59] <Riddell> also to your ec2 machine
[11:01] <c2tarun> Riddell: thanks :)
[11:01] <yofel> Riddell: is ~ppa1~maverick1 our new naming scheme?
[11:01] <Riddell> c2tarun: it's in ~jr on your ec2 machine if you want to install it and get onto kdepimlibs
[11:02] <c2tarun> Riddell: yup I am on it
[11:02]  * yofel backports meta-kde
[11:02] <Riddell> yofel: oh I got it the wrong way around didn't I?
[11:03] <yofel> Riddell: well, I was confused as you uploaded a ~ppa1~maverick1 now and bambee uploaded a ~maverick1~ppa1 2h ago
[11:03] <c2tarun> Riddell: biggest problem is accessing ktown ftp without my ssh key on that system, is there any solution for that? or I have to paste .ssh there
[11:04] <Riddell> c2tarun: you don't need ktown access, get the tars out of kubuntu-ninjas natty packages
[11:04] <c2tarun> Riddell: oh... I forgot :) thanks
[11:06] <yofel> and *who* is working on maverick kde4libs currently? since from what I get 3 people are doing the same thing and nobody put himself on the wiki page...
[11:06] <Riddell> I've done it and I'm editing the wiki page now
[11:06] <c2tarun> how can I pull any package from natty repo on maverick machine :/
[11:07] <c2tarun> without editint /etc/apt/sources.lit
[11:07] <c2tarun> without editint /etc/apt/sources.list
[11:07] <Riddell> c2tarun: by adding the deb-src line for kubuntu-ninjas natty to sources.list
[11:07] <c2tarun> ok
[11:07] <stikonas> can anybody help me with rekonq? Something absolutely crazy happens. If I run rekonq from command line then version 0.7.0 launches but if I run it from KDE menu then version 0.6.85 launches
[11:08] <stikonas> and find /usr -type f -name 'rekonq' -print   prints only /usr/bin/rekonq
[11:08] <yofel> stikonas: what does 'which rekonq' say?
[11:08] <Riddell> stikonas: I expect that's some kdeinit fun
[11:08] <stikonas>  /usr/bin/rekonq
[11:08] <yofel> hm...
[11:09] <stikonas> I can't find any other executable in the path, that is what is strange
[11:09] <stikonas> and after aptitude purge rekonq, ir doesn't launch neither from GUI nor from command line
[11:11] <jussi> anyone know if koffice/calligra does proper MSoffice format stuf yet?
[11:14] <Riddell> jussi: it has supported MS Office formats for years
[11:15] <Riddell> now this iss scary, upgraded to 4.6.2 and logged out and X stopped taking input again
[11:15] <Riddell> but this time on reboot X is ok which wasn't the case yesterday
[11:16] <stikonas> ok, thanks for that kdeinit fun, I think I will be able to find now what goes wrong
[11:16] <jussi> Riddell: really? last time I checked I couldnt save as anything but rtf, and importing wasnt supported... (unless I was "doing it wrong"TM )
[11:17] <c2tarun> Riddell: is kdelibs5-dev (>= 4:4.5.85) and kde4libs are different packages?
[11:18] <Riddell> c2tarun: kdelibs5-dev is the binary from kde4libs
[11:18] <jussi> ahh, so it seems to open them ok, but I cant seem to save as Msoffice formats.  :(
[11:18] <c2tarun> Riddell: so if kde4libs is installed it shouldn't ask for kdelibs5-dev 
[11:19] <yofel> you can't install kde4libs as that's only a source package, you can install kdelibs5-dev as it's a binary package
[11:19] <c2tarun> Riddell: oh... its not installed.
[11:21] <c2tarun> Riddell: ec2 machine is of 32 bit I guess and you uploaded binaries to it for 64-bit. They are still unavailable from the ppa, I'll will wait for sometime
[11:25] <Riddell> ah, fooey
[11:47] <steveire> Everyday at midnight Quassel dies.
[11:47] <steveire> I wonder why my blog didn't show up on planet ubuntu
[11:50] <steveire> Ah, it arrived now
[11:50] <steveire> Strange
[12:02] <c2tarun> Riddell: kde4libs build succesfully on ninja ppa, but still I am not able to install it on ec2 by apt-get install
[12:03] <Riddell> did you run apt-get update?
[12:04]  * Riddell prepares 4.6.2 for upload to natty
[12:05] <jussi> steveire: how old core are you running? I remember that issue was fixed a _long_ time ago. 
[12:05] <jussi> steveire: http://bugs.quassel.info/issues/344
[12:06] <c2tarun> Riddell: yup
[12:07] <yofel> jussi, steveire: I actually got a crash too here, I'm using git client though (only the client crashes)
[12:08] <jussi> yofel: thats weird, please get a bug onto the bug tracker. (and a nice backtrace)
[12:08] <yofel> jussi: I forgot to save the trace, was an assertion from what I saw, I'll see if it happens again
[12:08] <jussi> it should drop a backtrace into ~/.config/quassel-irc.org
[12:09] <steveire> I'm using quassel from natty
[12:09] <c2tarun> Riddell: why I am not able to install it?
[12:10] <Riddell> c2tarun: I don't know, maybe it's not published yet
[12:10] <c2tarun> Riddell: how much time will it take?
[12:11] <steveire> http://dpaste.org/gEt3/ Funny :)
[12:11] <jussi> steveire: as I said to yofel, if you can get a backtrace, please report the bug on http://bugs.quassel-irc.org/
[12:11] <yofel> jussi: oh yeah, I forgot about that ^^
[12:11] <yofel> Fatal: ASSERT: "!_ircChannel && ircChannel" in file /build/buildd/quassel-0.8~alpha+81-g393ac8b/src/client/networkmodel.cpp, line 532
[12:12] <yofel> c2tarun: they are published
[12:12] <yofel> at least the amd64 ones here
[12:12] <steveire> "!_ircChannel && ircChannel" << That's the funny part 
[12:12] <jussi> yofel: over to #quassel ;)
[12:13] <steveire> Ah, I didn't see the underscore before
[12:14] <c2tarun> yofel: how can I check whether its published or not?
[12:14] <Riddell> c2tarun: I installed it
[12:14] <c2tarun> Riddell: where on ec2?
[12:15] <yofel> c2tarun: https://launchpad.net/~kubuntu-ninjas/+archive/ppa/+packages - see that the build status is OK for kde4libs?
[12:15] <Riddell> c2tarun: yes
[12:16] <c2tarun> Riddell: how :/ still on running sudo apt-get install kde4libs I am getting error. :( can you just please explain me why I am getting this?
[12:16] <Riddell> c2tarun: kde4libs is a source package
[12:16] <Riddell> kdelibs5-dev is the package to install
[12:18] <c2tarun> well why source package name and package name to install is different?
[12:19] <yofel> c2tarun: while usually source and binary packages have the same name for small packages, a source package may build several binary packages, like here for kdelibs
[12:20] <yofel> c2tarun: in this case you can't very well name all binary packages the same, can you?
[12:20] <c2tarun> yofel: nope
[12:20] <yofel> and depending on the package, it might even make sense to not have a binary package with the same name as the source package, like in our case
[12:24] <yofel> bbl
[12:24] <c2tarun> yofel: ok, if I want to find binary name of some package? what should I do? look at the debian/control file?
[12:25] <yofel> c2tarun: apt-cache showsrc <source_package> will tell you what binary packages it built
[13:16] <c2tarun> Riddell: what is the issue with kdegraphics, you wrote missing symbols. Should I pack it for maverick?
[13:21] <Riddell> c2tarun: yes it needs packaged
[13:21] <Riddell> did you do kdepimlibs?
[13:21] <c2tarun> Riddell: yup its in ppa
[13:22] <Riddell> groovy
[13:26] <c2tarun> Riddell: i just picked kdebindings and it requires python-qt4 (>= 4.8.3) which is not in maverick but in natty. :/
[13:26] <c2tarun> should I pack the version in natty for maverick first?
[13:26] <yofel> c2tarun: we don't backport kdebindings
[13:27] <yofel> not really doable, use what's already in the ppa
[13:28] <c2tarun> yofel: I dont understand, what do you mean by we dont backport?
[13:29] <yofel> c2tarun: you would first need to backport SIP for pyqt4 and kdebindings, but SIP won't build until you fix dh_python3 in maverick. Have fun
[13:29] <c2tarun> yofel: fix dh_python3, that sounds scary..... I think I should leave this pacakge and take another one ;)
[13:30] <yofel> c2tarun: yes, you want to do that ;)
[13:30] <bambee> Riddell: our packages conflicted... this morning I have backported kde4libs into maverick and you too... (it's my fault I did not update the wiki page o_O)
[13:31] <Riddell> bambee: well as long as one of us got it in
[13:31] <yofel> both got it in actually ^^
[13:31] <yofel> ~ppa1~maverick1 was just greater than ~maverick1~ppa1 :P
[13:31] <Riddell> oh, bad me
[13:32] <bambee> :)
[13:33] <yofel> c2tarun: geh, someone of us ignored the editing warning on the wiki, can you please resolve the conflicts?
[13:34] <c2tarun> yofel: sure, but how? :/
[13:34] <yofel> nvm, took care of it
[13:35] <yofel> next time: just edit it again and merge the conflicting parts by hand
[13:45] <bambee> May be I am wrong ... kdebase has been versionned with "~ppa1" into archives (or launchpad says crap)
[13:45] <bambee> or I seriously need coffee ...
[13:45] <bambee> :)
[13:48] <Riddell> oh, bah
[14:18] <c2tarun> Riddell: I think I got the symbol issue with kdegraphics that you mentioned http://pastebin.com/1K6U4LMa :(
[14:21] <Riddell> c2tarun: pkgkde-symbolshelper batchpatch -v 4:4.6.2-0ubuntu1~maverick1~ppa1 ../*build
[14:23] <c2tarun> Riddell: what is that/
[14:23] <c2tarun> ?
[14:24] <yofel> c2tarun: http://pkg-kde.alioth.debian.org/symbolfiles.html
[14:30] <c2tarun> yofel: what exactly are symbols? that page teaches how to work with symbols
[14:33] <yofel> c2tarun: symbols are used to find the program functions the the binary files/libraries. nm -D /usr/lib/libkdecore.so.5 will give you a list of the symbols the file has for example. nm -DC will resolve them to the original c++ function names
[14:33] <yofel> s/the the/in the/
[14:33] <kubotu> yofel meant: "c2tarun: symbols are used to find the program functions in the binary files/libraries. nm -D /usr/lib/libkdecore.so.5 will give you a list of the symbols the file has for example. nm -DC will resolve them to the original c++ function names"
[14:34] <yofel> c2tarun: our symbol files are there to make sure that a library doesn't just drop functions/symbols without us noticing. As the package would need a bump of the library version then usually
[14:37] <c2tarun> yofel: sorry not getting, what do you mean by program functions? (are they simple functions?)
[14:38] <shadeslayer> Riddell: it won't, i just have to fix the url in the twitter settings online, done :)
[14:39] <steveire> Riddell: I don't get the akonadi self test dialog today, but I do still get the kwallet error.
[14:39] <Riddell> steveire: hmm, progress of sorts
[14:39] <Riddell> steveire: I thought you said that patch should fix both?
[14:39] <steveire> I did say it should, yes :)
[14:40] <steveire> There may be other synch calls that I didn't catch
[14:40] <yofel> c2tarun: take for example one of the c++ function from there:
[14:40] <yofel> OrgKdeKLauncherInterface::OrgKdeKLauncherInterface(QString const&, QString const&, QDBusConnection const&, QObject*)
[14:40] <yofel> if you compile the library, the compiler will make a computer recognizable unique string out of it, the symbol:
[14:40] <yofel> _ZN24OrgKdeKLauncherInterfaceC2ERK7QStringS2_RK15QDBusConnectionP7QObject
[14:40] <yofel> that is then used by the linker to bind a call for that function in an application to the library
[14:41] <c2tarun> yofel: ok, so this computer recongnizable unique string are symbols?
[14:42] <yofel> somewhat, yes, someone else might be able to explain that better I hope
[14:42]  * yofel is off for lunch
[14:42] <c2tarun> can anyone help me understanding what are symbols please :(
[14:42]  * c2tarun mean how do they work
[14:48] <Riddell> is a symbol goes missing it means the library has lost some functionality and we need to recompile everything that uses that library
[14:48] <Riddell> in this case the differences are due to the different gcc version so it's not an issue
[14:49] <c2tarun> Riddell: when we build a package symbols files are generated during compilation, right?  So how can anything go wrong when its compiling fine.
[14:50] <tsimpson> c2tarun: if someone changes the code between versions, the symbols change
[14:50] <tsimpson> symbols are basically names for locations in code, they are usually functions but can also be data
[14:50] <tsimpson> if an executable or library can no longer find them, then obviously it won't run
[14:51] <c2tarun> tsimpson: ok, just tell me one thing please, how symbols files are generated? (this may help me understand)
[14:52] <tsimpson> symbols are "exported" from compiled code, the exported symbols are the ones that are accessible from outside the library/program, the binary file(s) contain a table of these symbols
[14:53] <tsimpson> symbol files are basically a textual representation of that table
[14:53] <tsimpson> except symbol files can also contain which package version the symbol first appeared in, so dpkg knows what is the minimum version needed
[14:55] <Riddell> c2tarun: we make the symbols files when we first package a library following the procedure at http://pkg-kde.alioth.debian.org/symbolfiles.html
[14:56] <Riddell> c2tarun: for each new version we check if the symbols files need updated and if any of the missing symbols is a problem
[14:59] <c2tarun> Riddell: I think I am getting now, first thing symbols are for libraries and these symbols are used for packages. right? we make symbols while packaging the libraries and if there is any change in libraries then that needs updating symbols file also. am I right? :/
[14:59] <Riddell> c2tarun: yes
[15:00] <tsimpson> the symbols are created by the compiler and linker, but we create the file that contains a list of symbols
[15:00] <c2tarun> got if :) thanks everyone going to read working with symbols
[15:26] <steveire> Riddell: It's possible that the wallet bug is fixed for normal people but not for kolab accounts
[15:26] <Riddell> I'll try out a daily CD when I get a chance
[15:44] <Riddell> kde-l10n uploading to natty
[15:44]  * maco corsses fingers
[15:44] <maco> today, the bf's sister is introduced to Plasma Netbook
[15:45] <maco> UNR lucid was too buggy and annoying for her, so now she's beta testing kubuntu natty on her netbook
[15:45] <maco> (which means i still havent seen unity in action)
[15:46] <sikon> I... wasn't impressed by Unity back in Maverick, but things could have changed y now
[15:47] <Riddell> maco: at least you can blame any bugs on it being beta :)
[15:51] <Tm_T> sikon: gnome guys in my LoCo are bashing Unity ):
[15:52] <lucidfox> Eep, why was sikon? O_O
[15:52] <lucidfox> * I
[15:52] <Tm_T> lucidfox: evil personality did take over when login?
[15:52] <Tm_T> I've heard lots about unstability in Unity, cannot say else about it
[15:53] <lucidfox> I consider the GNOME stack enough of a mess these days to use exclusively Kubuntu
[15:53] <lucidfox> I was in a similar situation back around the release of KDE 4.0...
[15:56] <maco> i was going to give her unity, and then i remembered the bugginess...
[15:58] <Tm_T> lucidfox: I liked 3.50.50 (:
[16:12] <c2tarun> Riddell: can you please take a look at debdiff of kdegraphics http://pastebin.com/esAG7ShS I am uploading it to ppa.
[16:14] <Riddell> c2tarun: that's fine
[16:16] <c2tarun> Riddell: should I take kdebase for maverick?
[16:16] <Riddell> c2tarun: that needs -workspace first I think
[16:17] <c2tarun> Riddell: so workspace first!!
[16:17] <Riddell> c2tarun: I've just finished that
[16:18] <c2tarun> Riddell: thats great :) I'll wait for you to upload it :) meanwhile I'll take kdeartwork
[16:18] <Riddell> also needs -workspace, see https://wiki.kubuntu.org/Kubuntu/Ninjas/DependencyGraph
[16:19] <c2tarun> sorry I was on edit option so this link was not available
[16:20] <c2tarun> Riddell: ok :) so I'll simply wait till you upload it
[16:22] <Riddell> uploaded now but will need to wait for it to compile
[16:22] <c2tarun> Riddell: ok, meanwhile going to grab some coffee :)
[16:59] <Riddell> hello tim_ 
[16:59] <tim_> hi! 
[17:02] <tim_> Riddell: do you know if a new version of kdepim will enter kubuntu-ppa/backports? 
[17:03] <Riddell> tim_: there's no kdepim release scheduled yet
[17:03] <Riddell> ScottK: do you know what "Add udev (>= 166-0ubuntu4) to kdm Depends" is about in kdebase-workspace?
[17:04] <Quintasan> OH YEAH
[17:04] <Quintasan> sponsorship
[17:05] <tim_> What about the "HTML copy bug", will it be fixed? As far as I know it is fixed in the upstream Version?! 
[17:05] <Riddell> Quintasan: oh?
[17:05] <Riddell> tim_: steveire might be able to answer that
[17:05] <Quintasan> Riddell: I've just got mail confirming they want to sponsor my trip etc.
[17:06] <Riddell> golly
[17:06] <steveire> tim_: I don't know about the packages, but if it's fixed upstream I'm ure it will get to the ppa
[17:06] <Riddell> Quintasan: as your reward I nominate you to start a KubuntuOnericSpecs wiki page!
[17:06] <Quintasan> @_@
[17:06] <Quintasan> Riddell: Can I get to it tomorrow?
[17:06] <Riddell> Quintasan: yes
[17:07] <tim_> thanks! 
[17:08] <Quintasan> Riddell: Or wait, I will forget about it, I might as well start doing it now.  KubuntuOnericSpecs as in Ubuntu One client?
[17:09] <Riddell> Quintasan: as in a page for people to list sessions they want at UDS
[17:10] <Quintasan> Riddell: oh, Oneric sound strange to me
[17:11] <Riddell> oneiric
[17:12] <Riddell> I was missing an i
[17:12] <ulysses> OO could be Old Obi-van
[17:13] <Quintasan> That's even more confusing
[17:13] <ulysses> but it's from Star Wars!
[17:14] <Quintasan> Riddell: Can we have it like this -> https://wiki.kubuntu.org/Kubuntu/Specs/UDS-O ?
[17:15] <Quintasan> omfg
[17:15] <Quintasan> oneiric is the codename of next Ubuntu -_-'
[17:15] <maco> um...yes...
[17:16] <maco> did you think he was just putting gibberish in the example-wiki-page name?
[17:16] <Quintasan> Yeah :P
[17:17] <Riddell> Quintasan: yes
[17:24]  * c2tarun taking kdebase for maverick
[17:25] <c2tarun> Riddell: you building kdebase?
[17:25] <Riddell> c2tarun: not yet, go ahead and take it from me
[17:25] <c2tarun> Riddell: ok
[17:26] <c2tarun> Riddell: one more question, why are you rebuilding kdepim?
[17:28] <Riddell> c2tarun: the new akonadi changed library symbols so it needs a rebuild
[17:31] <bambee> Riddell: I will backport kdebindings,kdesdk and kdeutils into maverick when I back to home (I updated the wiki page)
[17:32] <Riddell> bambee: I think kdebindings won't work, needs too many other things updated 
[17:32] <bambee> ohh really ?
[17:32] <Riddell> 13:29 < yofel> c2tarun: you would first need to backport SIP for pyqt4 and kdebindings, but SIP won't build until you fix dh_python3 in maverick. Have fun
[17:32] <bambee> arrff
[17:32] <bambee> well
[17:33] <bambee> ok so just kdesdk and kdeutils
[17:36] <c2tarun> Riddell: is anyone fixing dh_python3?
[17:36] <bambee> Riddell: also I am a bit confused : maverick backports must be versioned as ~maverick1~ppa1 or ~ppa1~maverick1 ?
[17:37] <c2tarun> bambee: I think first one
[17:37] <bambee> c2tarun: me too, however some backports are ~ppa1~maverick1, that's why I am asking :)
[17:38] <c2tarun> bambee: actually Riddell told me in morning :)
[17:38] <bambee> ok
[17:38] <bambee> thanks
[17:38] <Riddell> ~maverick1~ppa1 is right, I got it wrong earlier
[17:40] <c2tarun> Riddell: is anyone working on dh_python3?
[17:57] <Riddell> c2tarun: I don't think it's worth it
[17:57] <c2tarun> ohh.... :)
[18:48] <c2tarun> bambee: you should update that page when you upload a package :( I packed kdebase which you already packed two days ago.
[18:48] <bambee> ohhh...
[18:48] <bambee> sorry xD
[18:49] <c2tarun> bambee: np :) just for no conflicts I am building kdenetwork :)
[18:49] <bambee> okay
[18:49] <c2tarun> Riddell: you were building a package which bambee uploaded :/
[18:49] <bambee> I am packaging kdesdk+kdeutils
[18:50] <c2tarun> bambee: I saw that :)
[18:50] <bambee> c2tarun, Riddell: feel free to blame me when I don't upload the page or when I do something wrong...
[18:50] <bambee> :)
[18:51] <c2tarun> bambee: its not blaming :) its just why double a work when there is plenty
[18:51] <bambee> for the love of the art... :P
[18:52]  * bambee => [ ]
[18:53] <c2tarun> :P
[18:54] <c2tarun> is this a linker error? http://paste.kde.org/9061/
[18:55] <c2tarun> gcc version on ec2 I am using is 4:4.4.4-1ubuntu2
[18:55] <bambee> c2tarun: no a compiler error
[18:55] <c2tarun> bambee: why I am getting this error?
[18:56] <c2tarun> I mean is there something missing?
[18:56] <bambee> probably a bad dependency is used (incorrect version) 
[18:57] <bambee> c2tarun: did you try with pbuilder (with a maverick basetgz)
[18:57] <bambee> ?
[18:58] <c2tarun> bambee: nope, its kind of a clean ec2.
[18:58] <c2tarun> why pbuilder?
[19:01] <c2tarun> bambee: ping
[19:02] <bambee> because with pbuilder it's built into a new and clean environnement without any pre-installed dependencies, it's easier to check errors
[19:02] <c2tarun> bambee: ok, let me try it with pbuilder, but I dont think it will do any good and I'll end up with this error :(
[19:03] <bambee> c2tarun: kdenetwork builds for natty so it's not a programming error :)
[19:03] <c2tarun> bambee: yeah you are right too
[19:03] <bambee> that's why I said that you probably missed something ;)
[19:03] <c2tarun> bambee: let me upgrade that ec2 first. may be that solve the probl
[19:05] <Riddell> c2tarun: I think the version in the PPA for natty has a wrong patch in it
[19:05] <Riddell> run   quilt pop
[19:05] <Riddell> then remove the patch in debian/patches
[19:06] <Riddell> and edit debian/patches/series
[19:06] <Riddell> and rebuild
[19:47] <c2tarun> bambee: kdesdk failed to build, https://i68471862.restricted.launchpadlibrarian.net/68471862/buildlog_ubuntu-maverick-amd64.kdesdk_4%3A4.6.2-0ubuntu1~maverick1~ppa1_FAILEDTOBUILD.txt.gz?token=a2f09ae286feb12978427de474032db6 please take a look
[19:57] <yofel> c2tarun: symbols again
[19:57] <c2tarun> yofel: yup, bambee was onto it, so I thought remind him :)
[19:58] <c2tarun> yofel: in this case also I think updating symbols will work? isnt it?
[19:59] <yofel> yep
[20:03] <bambee> c2tarun: w00t indeed
[20:03] <c2tarun> bambee: w00t??
[20:04] <bambee> s/w00t//
[20:04] <kubotu> bambee meant: "c2tarun:  indeed"
[20:04] <bambee> :)
[20:06] <Quintasan> godamn
[20:06] <Quintasan> how do I parse for \ in regexp?
[20:07] <Quintasan> I want to look up the "\"
[20:11] <yofel> \\ I would guess, depending on the syntax
[20:28] <bambee> c2tarun: should be fixed now
[20:28] <bambee> (kdesdk)
[20:28] <c2tarun> bambee: upload it :) we'll see
[20:29] <bambee> c2tarun: It has been uploaded
[20:32] <c2tarun> bambee: I dont think there is any packaging work left. ?
[20:34] <bambee> c2tarun: kde-l10n ?
[20:34] <c2tarun> bambee: ok I'll take it
[20:34] <bambee> crap... my packaged was rejected... I've to do a bumpfor that ? o_O
[20:34] <bambee> s/packaged/package/
[20:34] <kubotu> bambee meant: "crap... my package was rejected... I've to do a bumpfor that ? o_O"
[20:36] <c2tarun> bambee: where is the new tarball for kde-l10n?
[20:36] <c2tarun> its not in ktown
[20:36] <bambee> I don't know
[20:38] <c2tarun> hmm....
[20:42] <c2tarun> Riddell: ping
[20:47] <c2tarun> apachelogger_: ping
[20:47] <bambee> c2tarun: ktown => stable/4.6.2/src/kde-l10n
[20:48] <c2tarun> bambee: oh... I missed it :(
[20:48] <bambee> c2tarun: see also https://wiki.kubuntu.org/Kubuntu/Ninjas/Packaging/L10nOperatorGuide
[20:49] <c2tarun> bambee: what is so special about l10n? that there is a whole wiki page?
[20:52] <bambee> c2tarun: you really want to download 53 tarballs and package them ? it's an automatic way
[20:52] <bambee> read the wiki page
[20:52] <bambee> you will understand
[20:52] <c2tarun> 53 O_O
[20:52] <ulysses> the announcement tells there is more than 55:P somebody lies
[20:53] <bambee> :P
[20:54] <c2tarun> :P
[20:54]  * c2tarun reading wiki
[20:58] <yofel> c2tarun: I can take care of kde-l10n if you want, I know how it works (somewhat)
[20:59] <c2tarun> yofel: sure :) but I'll be very thankful if you allow me to try it once, if it failed I'll surely ping you.
[20:59] <yofel> sure, but setup a gpg agent before trying it, or you'll have to input your gpg key password a hundred times for debsign
[21:00] <yofel> (or maybe someone knows a different solution for that, that's mine)
[21:01] <c2tarun> yofel: I'll copy my .gnupg and .ssh in that ec2 and then after evrything is finished I'll delete it :)
[21:01] <yofel> well, have fun
[21:02] <c2tarun> yofel: sure :)
[21:03] <yofel> we *usually* don't upload kde-l10n to ninjas though, too much work, it goes straight to the backports ppa when we copy the packages
[21:03] <c2tarun> yofel: I'll tell you when build is successful
[21:03] <yofel> sure, the script will take quite a while to finish anyway
[21:05] <yofel> c2tarun: also, kde-l10n *is* on ktown, it's in a subfolder
[21:05] <yofel> one source per language
[21:06] <yofel> err, I should read the whole backlog, nvm...
[21:09] <c2tarun> yofel: where can I get the debian folder?
[21:10] <yofel> c2tarun: as it says on the wiki page, you want to get https://code.launchpad.net/~kubuntu-members/kubuntu-dev-tools/kde-l10n-common-maverick
[21:10] <yofel> hm, why is that still owned by -members...
[21:10] <c2tarun> yofel: I am going to pack for natty first
[21:11] <yofel> c2tarun: Riddell already uploaded that
[21:11] <yofel> you *want* to read natty-changes
[21:11] <yofel> as I said, kde-l10n doesn't go to ninjas, so don't expect it there
[21:12] <c2tarun> yofel: sorry, I checked it there, and if Riddell uploaded it well where can I see it?
[21:12] <yofel> c2tarun: https://lists.ubuntu.com/archives/natty-changes/2011-April/date.html scroll to the bottom
[21:13] <yofel> there's also an RSS feed http://feeds.ubuntu-nl.org/NattyChanges if you don't like mailing lists
[21:14] <c2tarun> yofel: and what about maverick?
[21:14] <yofel> that goes to kubuntu-ppa/backports when we release the packages
[21:15] <c2tarun> yofel: I mean he didn't packed it for maverick didn't he?
[21:16] <yofel> no, he didn't
[21:16] <yofel> https://launchpad.net/~kubuntu-ppa/+archive/backports/+packages shows the 4.6.1 packages still
[21:17] <yofel> c2tarun: are you a kubuntu-member though?
[21:17] <c2tarun> yofel: nope ;(
[21:18] <yofel> hm, well you can request a merge and I can review that when you need to commit, you can't run the script without commiting your changes first
[21:20] <c2tarun> yofel: its written there Members of Kubuntu Members can upload to this branch.
[21:20] <c2tarun> so it mean I cant
[21:20] <yofel> c2tarun: yes, but that's true for all other packaging branches too
[21:20] <yofel> so just do it like you did for the others
[21:21] <c2tarun> yofel: ok, so I got that branch and that got me the debian folder, now I have to get kde-l10n folder from ktown and then run that script in debian folder.
[21:21] <c2tarun> an I right?
[21:21] <yofel> Riddell: when are we going to start using ~kubuntu-packagers?
[21:21] <yofel> c2tarun: you first need to update the changelog and commit that
[21:22] <yofel> *then* you can run the script
[21:22] <c2tarun> ok.
[21:22] <yofel> as the script makes a fresh checkout from the branch, so all uncommitted changes are ignored
[21:26] <ScottK> Riddell: I think it was related to upstart changes, but it may be related to multi-arch.
[21:29] <c2tarun> yofel: I made changes to changelog, how to commit?
[21:30] <yofel> c2tarun: how did you commit changes for kdebase etc.
[21:30] <c2tarun> yofel: I simply uploaded them to kubuntu-ninjas ppa.
[21:30] <c2tarun> :/
[21:30] <yofel> c2tarun: er... do you remember our discussion about merge requests?
[21:31] <c2tarun> yofel: yup, I remember about adding file first by bzr add
[21:31] <c2tarun> but here I am gettin error
[21:31] <yofel> ahh, you probably don't have your bzr config on ec2 :S
[21:32] <yofel> I would make a local checkout on your PC, update that, commit, and then fetch the branch on ec2 once I merge your changes
[21:32] <c2tarun> yofel: may be, one question, do I have to make changes in changelog after moving debian folder inside kde-l10n?
[21:33] <yofel> why would you move the folder?
[21:33] <c2tarun> yofel: because I am getting this error bzr: ERROR: Not a branch: "/home/ubuntu/kde-l10n/kde-l10n/debian/changelog/".
[21:33] <yofel> you don't move the folder
[21:34] <yofel> or you would need to unpack every language, copy the folder there, edit changelog etc....
[21:34] <yofel> the script does that
[21:34] <c2tarun> yofel: ok changelog file is added by bzr add now,
[21:36] <yofel> good then push to lp
[21:39] <seaLne> steveire: have you come accros a probelm that if kontact starts before a network is available it won't ever manage to fetch imap even after network is available? you need to quit and restart it. this is 4.4 in natty. looosing network after it has started isn't a problem as it works again on reconnection
[21:40] <c2tarun> yofel: bzr: ERROR: Permission denied: "~kubuntu-members/kubuntu-dev-tools/kde-l10n-common-maverick~ppa1/": : Tarun K. Mall is not a member of Kubuntu Members :(
[21:41]  * c2tarun why I am not kubuntu member ;(
[21:41] <yofel> c2tarun: bzr push lp:~c2tarun/kubuntu-dev-tools/kde-l10n-maverick-4.6.2
[21:44] <yofel> c2tarun: did you push?
[21:44] <c2tarun> yofel: I think, I am looking for where I pushed :/
[21:44] <yofel> c2tarun: https://code.launchpad.net/~c2tarun/kubuntu-dev-tools/kde-l10n-maverick-4.6.2
[21:44] <yofel> did you get an error?
[21:45] <yofel> if it's about different rich-root ... something... push again
[21:45] <c2tarun> yofel: here is what I got http://paste.kde.org/9091/
[21:45] <c2tarun> yup
[21:45] <yofel> yeah, run the same push command again, will work this time
[21:46] <c2tarun> yofel: yup its done this time :)
[21:47] <yofel> k, propose that for merging into lp:~kubuntu-members/kubuntu-dev-tools/kde-l10n-common-maverick
[21:50] <c2tarun> yofel: I did https://code.edge.launchpad.net/~c2tarun/kubuntu-dev-tools/kde-l10n-maverick-4.6.2/+merge/56651
[21:52] <yofel> c2tarun: you did not update the svn revision
[21:52] <yofel> see step 2 on the wiki page
[21:53] <c2tarun> yofel: looking
[21:59] <c2tarun> yofel: https://code.edge.launchpad.net/~c2tarun/kubuntu-dev-tools/kde-l10n-maverick-4.6.2/+merge/56651 here please take a look
[22:02] <c2tarun> yofel: ok thanks :) what now just executing that script?
[22:02] <yofel> c2tarun: yep, should be enough
[22:03] <yofel> you run the build script as said on the wiki page, after that ignore the last step since that's for the archive
[22:03] <yofel> for the PPAs you'll need to debsign the packages and upload them to the ppa later
[22:04] <c2tarun> yofel: http://paste.kde.org/9092/
[22:04] <c2tarun> I got this error
[22:05] <yofel> .. give me a sec
[22:08] <yofel> c2tarun: try again
[22:09] <c2tarun> yofel: again same :(
[22:10] <yofel> really? Then just drop the packaging and use a fresh checkout
[22:10] <yofel> your changes are in the branch after all
[22:10] <c2tarun> hmm....
[22:16] <c2tarun> yofel: is there any other packaging work left?
[22:17] <yofel> not for 4.6.2 at least I think
[22:17] <c2tarun> so there is nothing else to do?
[22:18] <yofel> well, 4.6.2 is done, maybe Riddell knows if something else needs to be done
[22:19] <c2tarun> Riddell: ping
[22:19]  * yofel retries kdetoys
[22:20] <yofel> hm, the libqjson-dev build-dep in kdeutils has a really unlucky version choice :S
[22:21] <yofel> c2tarun: you can fix kdesdk if you want
[22:21] <yofel> esp. since bambee's gone
[22:21] <c2tarun> yofel: yup, I was looking into it, bambee is not here I guess.
[22:21] <yofel> I'll take kdeutils
[23:29] <Riddell> evening
[23:29] <Riddell> where are we at?
[23:30] <c2tarun> Riddell: are there any other packaging works?
[23:30] <Riddell> now it needs testing
[23:31] <c2tarun> Riddell: how can I do that?
[23:31] <Riddell> c2tarun: install it and run it
[23:32] <c2tarun> ok, I'll do it, anyother stuff?
[23:32] <Riddell> nope
[23:32] <c2tarun> Riddell: BTW do you know when SoC starts?
[23:33] <Riddell> no, google for soc timeline
[23:34] <c2tarun> Riddell: sorry, what do you mean?
[23:34] <Riddell> to find out I recomend you use google and search for "soc timeline"
[23:39] <yofel> Riddell: hm... a) when are we going to use ~kubuntu-packagers, b) would it make sense to subscribe ~kubuntu-bugs to the kubuntu-ppa bugs? some of us are subscribed to those, but no somewhat official team
[23:42] <c2tarun> Riddell: when can I apply for kubuntu-members?
[23:44] <Riddell> yofel: I think we'll do a mass migration during the new cycle merges
[23:45] <Riddell> c2tarun: usually two months of significant and sustained contribution is requested
[23:46] <yofel> k, sounds good
[23:46] <Riddell> yofel: bug subscriptions always confuse me, that seems sensible I think
[23:49] <yofel> Riddell: an admin needs to do that, you should have a checkbox for that on https://bugs.launchpad.net/kubuntu-ppa/+subscribe