=== uniq [n=frode@213.184.199.55] has joined #kubuntu-devel === fromoze [n=fromoze@81.172.95.222] has joined #kubuntu-devel === seth_k [n=seth@d-ip-129-15-214-252.wireless.ou.edu] has joined #kubuntu-devel === _static [n=static@adsl-69-154-0-169.dsl.tulsok.swbell.net] has left #kubuntu-devel ["Konversation] === venda [n=sean@ndn-165-128-217.telkomadsl.co.za] has joined #kubuntu-devel === pef [n=loic@lns-vlq-39f-81-56-130-224.adsl.proxad.net] has joined #kubuntu-devel [07:50] morning [08:45] morning === hunger [n=hunger@p54A61902.dip0.t-ipconnect.de] has joined #kubuntu-devel === m-fox [n=m-fox@port-212-202-8-119.dynamic.qsc.de] has left #kubuntu-devel ["Kopete] === m-fox [n=mpasdzie@router.isea.RWTH-Aachen.DE] has joined #kubuntu-devel === tvo [n=tobi@5354EA9B.cable.casema.nl] has joined #kubuntu-devel === m-fox [n=m-fox@port-212-202-8-119.dynamic.qsc.de] has joined #kubuntu-devel === m-fox [n=m-fox@port-212-202-8-119.dynamic.qsc.de] has left #kubuntu-devel ["Kopete] === crimsun [n=crimsun@sh.nu] has joined #kubuntu-devel === m-fox [n=m-fox@port-212-202-8-119.dynamic.qsc.de] has joined #kubuntu-devel === uniq [n=frode@213.184.199.55] has joined #kubuntu-devel === uniq_ [n=frode@213.184.199.55] has joined #kubuntu-devel === uniq [n=frode@213.184.199.55] has joined #kubuntu-devel === uniq [n=frode@213.184.199.55] has joined #kubuntu-devel === Tm_T [n=travolta@85-156-4-245.elisa-mobile.fi] has joined #kubuntu-devel [06:23] hi kids [06:23] hi Tm_T [06:23] ah, mr Riddel :) [06:23] +l [06:24] I blame keyboard [06:25] any knowledge about release date? [06:25] yeah, I mean breezy ;) [06:25] https://wiki.ubuntu.com/BreezyReleaseSchedule october 13th === uniq [n=frode@213.184.199.55] has joined #kubuntu-devel [06:27] ...and with Kubuntu? =) [06:27] same [06:27] so we'll miss KDE 3.5 [06:27] oh, ok [06:28] it will be packaged as soon as possible then [06:28] ok thanks [06:28] yes it will [06:28] good to know [06:47] bah, got enough of this latencyhell, off -> === tvo [n=tobi@5354EA9B.cable.casema.nl] has joined #kubuntu-devel [07:03] yo tvo [07:03] yo Riddell [07:03] tvo: seen kio-beagle? [07:04] Riddell: no, though I recall I read about it a while ago.. [07:05] probably in kde-devel [07:05] of course you'd probably have to get beagle working first to test it out, and that isn't necessarily easy [07:05] tvo: are you planning on porting your google extention patches to kde 3.4? [07:06] no, I planned on testing it until I read it has problems on ReiserFS partitions, thats what most of my partitions are :( [07:06] that's ok, shouldn't be too easy (re: porting to kde 3.4) [07:07] *too difficult [07:07] arg [07:07] I'll test beagle on my breezy test partition, that's ext3 [07:08] good luck, I could never get it working [07:08] but maybe the ubuntu packages have improved [07:09] hehe, ok, I should try anyway [07:09] Riddell: is kat still in development? [07:09] s/kat/katapult/ [07:09] not much done on katapult for a while, I'd still like to get round to it but may not be able to before breezy [07:09] it's in berlios isn't it? [07:10] I'd definatly like to make a breezy + 1 spec for it, then maybe someone will get a bounty [07:10] yes, berlios [07:11] I should check it out and implement some of the features I myself added to the wiki, because technically they look a lot like the patches I made recently [07:11] if anyone has good projects that would make kubuntu cool and wants a bounty for them tell me so we can get a spec [07:12] will do, I'll certainly keep developing for KDE/Qt, their codebase is extremely good === tvo remembers the optional bounty ;) [07:15] Riddell: what do you know about LaptopTestingTeam ? [07:15] I got curious because my uni keeps trying to convince students to get a laptop :) === tvo ports his googlebar* patches [07:18] tvo: "No new laptops are being sent out" [07:18] :( [07:19] keep your eye open I guess, they may do it again at some point [07:25] Riddell: is it right kdeaddons 3.4.2 wasn't packaged for hoary? [07:25] it's not a problem though I grab tarballs directly from KDE [07:27] tvo: ah yes, that's waiting on kdebase which is what I'm about to look at [07:34] I'll backport the searchbar and see if that gives any problems === tvo wonders why he has a googlebar without having installed kdeaddons === tvo compiles KDE 3.4.2 with backported googlebar [08:08] tvo: you probably have konq-plugins, not the whole kdeaddons [08:09] Riddell: ah that explains it [08:46] Riddell: http://home.casema.nl/vollebregt/soc/patch/googlebar_backport_total.diff [08:46] tvo: you kick arse [08:46] it's 00-02 googlebar patches combined including a 3.5->3.4.2 backpot [08:46] seems to work here [08:46] :) [08:52] Riddell: do we want about:konqueror patch in 3.4.2 too? [08:52] tvo: ooh, yes please [08:52] that shouldn't have changed though [08:52] by looking at SVN, it seemed easier yes. [08:53] did you already test it? [08:53] (in 3.4.2 that is) [08:55] anyway, I'll test if the patch applies without warnings. If it needs a backport things are *hard* because testing kdebase it isn't as easy as kdeaddons. [08:55] ( or rather, kdebase just takes 80x more time to compile ) [08:56] did I mention that the icecream cluster here is very nice? :) [08:58] ok I patch, you compile :) [09:00] deal [09:06] as you said, it hasn't changed much. patch applies with +2 lines offset for two hunks of last file [09:11] Riddell: quickly scanned through the code, seems ok [09:11] Riddell: i'd say, compile 'n test [09:12] just discovered a minor memleak in my patch :( [09:12] want a new patch or a patch on top of this patch? [09:15] new patch [09:17] ok [09:17] btw, is that in general (rather replacement patch than patch-stack) ? [09:17] or only with bugfixes ? [09:20] whole new patch [09:24] tvo: 00-ak_searchbar_bot.diff and 00-ak_searchbar_top.diff seem to overlap [09:24] oh wait, that's deliberate [09:24] ignore me [09:31] :) [09:31] Riddell: want both top and bottom or just top? [09:32] just top, ignore me [09:36] Riddell: ok, memleak-fixed is @ http://home.casema.nl/vollebregt/soc/patch/00-ak_searchbar_top_memleak_fixed.diff [09:43] Riddell: another subject: what (for) are regression logs ? [09:45] tvo: where's that? [09:45] on packages.ubuntu.com [09:45] there's "build logs" and "regression test" for each package [09:46] I noticed "regression test" is -failed for many packages, just have no clue what it is :) [09:47] the logs look just like a build.... [09:49] the build log is the result of what happens after someone uploads the source package and the build daemons build it [09:50] regression tests I havn't seen before but it looks like random rebuilds of packages to make sure they still build [09:52] sounds plausible :) [09:53] once KDE 3.5 is out I'll check them to see if UDS_HIDDEN was properly detected [10:17] tvo: how do you mean detected? [10:18] Riddell: I modified bksys to autodetect the presence of my patch in KDE and add a -D switch in the case it's present [10:19] ooh, fancy [10:19] how does it detect it? [10:19] so as soon as kio-locate gets rebuild with 3.5 the uds_hidden feature is present [10:19] that's less fancy :) [10:20] it does a "cat $KDE_INCLUDE_DIR/kio/global.h" and checks if the string UDS_HIDDEN is therein [10:20] good solution :) [10:21] if ita is right I can make it faster using python instead of cat (bksys == python), but i'm not yet a python guru, so I could not yet figure out how :) [10:22] I shouldn't imagine it would make any noticable difference [10:24] and it's not really a time critical part of the software :) [10:26] that's why i only spent like 5 minutes trying.. [10:36] night === allee [n=ach@dialin-212-144-131-035.arcor-ip.net] has joined #kubuntu-devel