[00:12] ScottK: smarter [00:12] JontheEchidna: Thanks. [00:13] it looks like we had a package conflict that is already fixed in beta2, so I'm not going to sweat it. [00:17] Is somebody updating kdeplasma-addons for beta2? [00:18] I'm looking at what needs to get rebuilt to get rid of libplasma2 and that's one of htem. [00:21] JontheEchidna: plasmoid-quickaccess needs rebuilding. [00:21] probably won't build due to api changes [00:22] OK, will you look after updating/removing/etc? [00:23] I am wondering how long we should wait for an upstream release for KDE 4.2 before we remove it [00:24] maybe I could look in to updating it for the new api myself, but I'm not too confident in my C++ abilities [00:25] but yes, I will at least look in to it :) [00:30] OK. [00:31] Any ideas about if we still need compiz-kde? [00:31] My thought is that it ought to go away. [00:36] you would have to convince debian to not package it or for upstream to remove it [00:38] or at least the ubuntu compiz doods [00:38] since I don't believe the debian people would care since they aren't going to be updating to KDE 4.2 for a long while [00:39] Well, at least now sip is doing the right thing on bindings [00:48] JontheEchidna, on kde4bindings, are we disabling nepomuk's binding? [00:49] to tell you the truth I don't know what the hell we're doing with bindings anymore [00:50] I wrote some code to fix nepomuk on ARM, but I'm not sure if its still necessary or desirable [00:50] And the binding is miserably broken (WHY THE HECK DO WE HAVE A BINDING AROUND A VARIENT CLASS IN PyKDE?!) [00:50] * NCommander inhales [00:50] I don't have a huge issue killing the nepomuk binding ATM since we have it dead in kde4libs [00:51] if we disabled neopmuk bindings it was because of ftbfs [00:51] Well, bindings has half a brain [00:51] if it can't find nepomuk, it disables the binding [00:51] a huge, monolithic, half-brained turd [00:52] So far nepomuk is the only thing I've actually had break with my experimental changesets [00:52] (and given the comments Sime left in nepomuk.sip, its not just me who's having issues) [00:53] I wish we could just kill the mono/cli bindings dead [00:53] We did [00:53] Didn't we? [00:53] kde4lib's build process is SO slow ;.; [00:53] I believe the packaging is still there, just diabled [00:53] *disabled [00:54] ah [00:54] I think I can call PyKDE4 fixed [00:54] so the package is a partially-commented mess [00:54] But I still haven't done a full test build [00:54] * NCommander simply doesn't have the processor power [00:54] and backporting it brings in a whole other batch of headaches [00:56] so far so good on pykde4 [00:57] NCommander: Nepomuk is turned off (last I checked) but because it was broken, not out of any desire not to have it. [00:58] so maybe my ARM problems aren't anything I need to worry about [00:58] Not directly for Nepomuk right now. [00:58] * NCommander pulls the bazaar branches [01:07] The mono stuff isn't disabled. [01:07] whoever disabled nepomuk didn't do the best job ever: [01:07] [ 97%] Built target nepomuk-rcgen [01:10] Urgh. [01:10] I killed it off at one piont, but whoever did beta2 may have restored it. [01:12] Its actually building in full [01:12] -_-; [01:12] yay :-P [01:12] It's however properly dead in bindings [01:14] When I did it I just hard coded all the Cmake flags involving finding Nepomuk to off. [01:14] I left that patch in when I submitted bindings (iirc) [01:14] Last I checked (beta 1) properly doing the Nepomuk stuff would have required a circular build-dep. [01:14] OK. [01:14] It's dead in bindings [01:14] libs is building it [01:14] Ah. [01:17] bah [01:17] * NCommander still has to hack on kde4bindings [01:20] * NCommander swears [01:20] THis is going to require some "fun" cmake hacking [01:40] 4.1.85 libplasma + 4.1.80 plekd plasma [01:41] I should have er [01:41] um, even I don't know what's up with my keyboard === rmblr is now known as Ramblurr [02:02] NCommander: Lemme know when you're ready to fire for effect with your armel patches. [02:03] I have to rework some cmake macros to make it all work [02:03] and I'm still not fully sure its going to build [02:03] But I have managed to build an older pyqt4 [02:03] er [02:03] pykde4 [02:03] so we're very close to getting this to work [02:03] OK. [02:11] can someone check something for me please? [02:11] it seems amarok 2 still has a ruby dependency [02:11] that shouldn't be needed anymore === emma_ is now known as emma [02:32] Ok, so far so good [02:35] Well, I'm learning to port from KDE3 to 4.... this is certainly tedious looking up and modding the class changes... [02:37] lol [02:37] rgreening, when you get some free time, usb-imagewriter awaits :-) [02:39] yus [03:20] nixternal: did you ever get a chance to upload skulpture to the archives? i'm not seeing it in jaunty :) [03:21] vorian: waiting for it to clear new in debian and then will sync [03:21] ah, excellento [03:21] going to update it once it gets out of new in debian first though [03:28] * ScottK wonders where smarter hid the svn snapshot for kde4-style-bespin that has packaging sitting in bzr. [03:28] Making libplasma2 go away is something else people can work on. [03:42] porting this kdelibs flash installer patch from kde3 to 4 is proving challenging [03:56] ok, what binary has libXcomposite.so [03:57] * ScottK is mashing the seeds about a bit so we have some hope of an installable desktop for the Alpha. [03:57] :o [03:57] stop mashing me! [03:58] libxcomposite1 [03:58] http://packages.ubuntu.com/jaunty/libxcomposite-dev [03:58] libxcomposite1-dev maybe [03:58] ya [03:58] werd [03:58] vorian: I said seeds, not hayseeds. [03:58] got me there :) [04:00] they really must be spicing kdeplasma addons up a bit [04:01] I'm going to kill kde4bindings [04:01] Or my slow build hardware [04:01] Not sure which yet [04:03] NCommander: How far is the kde4bindings armel build that's going on right now going to get? [04:04] It's going to die at about 90% [04:04] Lovely. [04:04] You can tell why my patience has been running short running through these FTBFS [04:04] :-) [04:05] I'm pretty sure my python-qt4 patch is good [04:05] and I'm 90% sure on the kde4libs one [04:05] Its a multitude of errors [04:05] NCommander: How sure are you they won't hurt anything else even if they don't help? [04:05] 99% sure [04:06] Essentially the issue is triplefold [04:06] python-qt4 didn't properly pass qreal_double feature flags [04:06] kde4libs ignored said flags [04:06] :-) [04:06] and kde4bindings just went WTF on it :-) [04:06] Double fuckup and it's a win. [04:06] BTW, the reason the feature flag didn't work because it had a blotched configure test [04:06] What a miserably pile of failures [04:07] :-) [04:07] /usr/bin/sip -t ALL -t WS_X11 -t Qt_4_4_1 -x VendorID -x PyQt_NoPrintRangeBug -g -x\ VendorID\ -t\ WS_X11\ -x\ PyQt_NoPrintRangeBug\ -x\ PyQt_qreal_double\ -t\ Qt_4_4_1 [04:07] I'm concerned about all the escapes that crept in [04:08] New kubuntu-meta uploaded. That knocks out a couple of problem packages for the Alpha. [04:08] Unseed the problem child, rebuild meta, upload meta - No problems left for Kubuntu Desktop. [04:10] ScottK, anyway, we're in soft freeze [04:10] cjwatson will descend upon you in case of breakage [04:10] (of said freeze) [04:12] Right, well I'm doing stuff that fixes problems for the Alpha. [04:12] soft freeze...pffft [04:12] You're right though, your stuff ought to wait until Thursday. [04:12] Saturday [04:12] Alpha 2 goes on Friday [04:12] * ScottK thought it was Thursday. [04:12] Hrm [04:13] ubuntu-announce message said Thursday. [04:13] Of course it may end up Friday, or Saturday ... [04:14] It's amazing, we've had two alpha releases [04:14] and no new features [04:14] -_-; [04:14] go figure [04:16] that's usually how it is at the beginning [04:16] I think Edgy was the only release where the first few releases were getting crazy amounts of new features [04:16] dapper was fairly sane, but long [04:16] * NCommander blinks [04:16] what was before dapper? I already forgot [04:16] who resigned from MOTU SRU? [04:16] NCommander: not necessarily no new features - 2.6.28-rc3 fixes a boatload of acpi regressions [04:17] nixternal, breezy [04:17] I have been around here to long....maybe it is time to take a hiatus [04:17] nixternal: dude, whatever [04:18] haven't been around as long as you though, so I guess I have more work to do yet :p [04:18] I think someone resigned from motu-sru and it flew under the radar [04:18] *rader [04:18] NCommander: Dktrkranz [04:18] When did that happen O_o; [04:18] A couple of weeks ago. [04:18] and it didn't fly under that radar because I got an email about it iirc [04:18] nixternal: Didn't you do a hiatus during Intrepid? [04:19] shush [04:19] not really, as I was still doing distro development :) [04:19] and upstream development [04:19] * NCommander wonders who will fill the void [04:19] and still fixing my MOTU bugs [04:23] NCommander: are you volunteering? [04:23] The thought crossed my mind, but I think I probably have enough on my plate as is [04:23] crimsun: I think he is [04:23] SRU == boring!!! [04:24] then again, so did REVU Coordinator [04:24] On the plus side, having a backporter and an SRU together is handy because in cases where the same fix can be applied to both jaunty and intrepid [04:24] Then you can simply upload to jaunty, and tell an archive admin to backport and copy into proposed [04:27] I think rich is volunteering for motu-sru! [04:28] nope [04:29] * NCommander looks who he knows on sru [04:29] right now I am working on our plans from UDS for the MC and looking to help the TB [04:29] NCommander: I'd say go for it. I've done both, just requires due-diligence (as do most things). [04:29] nixternal for TB! [04:29] NOOOOOOOOOOOOOOOOOOO [04:29] helping mdz and them get things straight [04:29] * NCommander smashs Riddell with a golden brick wrapped around a lemon [04:30] they already have a list of people to fill the TB spots [04:30] dude, rich for tb? awesome! i could ask him all my infrastructure questions then! [04:30] * nixternal quits [04:30] all hail nixternal!!!! [04:30] * NCommander bows down [04:30] so why doesn't resume work on laptop x, rich?! [04:30] NAVY [04:30] Riddell: Since you're on vacation I just uploaded kubuntu-meta to clear out some cruft and give us a shot at an installable CD for the Alpha this week. [04:30] Never [04:30] Again [04:30] Volunteer [04:30] Yourself [04:30] crimsun: sign my key! [04:30] * vorian runs [04:31] nixternal: And yet you're on the MC. [04:31] he doesn't sign keys [04:31] thanks ScottK [04:31] nixternal: i've noticed [04:31] :P [04:31] plasma-addons are gonna be hawt! [04:31] I am sure I signed his from OLF [04:31] me too [04:31] vorian: i apply an aging trust policy; i don't sign keys right away. [04:31] nice [04:31] crimsun: fair enough [04:31] crimsun: I think I have aged quite well :p [04:31] I look hawt for 34 :p [04:32] :o [04:32] hahahahahahaha [04:32] OK, I am sure I am going to work from home yet again tomorrow [04:32] [04:32] NOOOOOOOOOO [04:32] hahahahahahah, I have been a dancing fool at the past few conferences [04:32] it is time for me to step down [04:32] nixternal: it's a darn good thing i didn't make it to uds ... we had our 5th kiddo sunday night [04:32] actually jono and jcastro are bad influences [04:33] vorian: wow, congrats!!! [04:33] nod. i can confirm that bug [04:33] haha [04:33] \o/ [04:33] vorian: word, 'grats [04:33] danke [04:33] 5th? you going for a football team or what? [04:33] yep [04:33] I have one, so she could be the coach! [04:33] basketball will have to do for now [04:34] the more I look at rPath, the more I become afraid, but I have to do something for work, and they just threw in this new feature called "OS Rollback Support" [04:34] I only know of 1 OS that does it, and does it well [04:34] foresight? [04:35] OK, 2...rPath and Foresight [04:35] conary is niceish [04:35] Conary packaging is niceish [04:35] very much so, i haven't tried the new stuff yet though... [05:04] tb? [05:04] Tech Board. [05:04] ah [05:06] seele: are you going to the nova girlgeek dinner tomorrow night? [05:07] crimsun: no.. i'm still recovering from all the excitement from last week :) [05:07] is it coed? are you going? [05:07] seele: yes, and yes [05:08] nixternal: I told you you should have moved. [05:08] crimsun: cool [05:08] ScottK: he said he's going to be visiting sometime soon [05:08] although i agree. we should make DC a Kubuntu hub :) [05:09] Yeah, he threatened not to tell me when he was coming because I was teasing him. [05:09] hehe [05:09] * seele yawns [05:10] ugh.. should get some sleep. l8r all [05:11] g'nite [05:11] guess I should...haven't debated on if I will work from home tomorrow or not [05:11] depends on how big the snowman looks in the morning [05:13] Irssi uptime: 41d 14h 11m 14s [05:14] on that note, it is time for sleep [05:14] g'nite [05:40] * NCommander files KDE bugs [05:42] JontheEchidna: plasmoid-quickaccess seems to be just about the last thing wanting libplasma2. I kicked it off the CD for the Alpha. We can add it back after you get it ported to libplasma3. [05:45] apachelogger, https://bugs.kde.org/show_bug.cgi?id=177965 - mind seeing if you can get someone to take a look at this? [05:45] ScottK == teh awesome [05:45] KDE bug 177965 in KDE4 (cmake) "FindPyQT4 provides no method of accessing SIP configuration options" [Normal,Unconfirmed] [05:45] I'm not going to use it in my fix for KDE on ARM, but its necessary when Sime wants to build a proper fix [06:03] Riddell: Once the binary promotions I've asked slangasek or pitti to do are done, I think we'll be in good shape for the Alpha. Everything else is uploaded, seed shuffled, etc. [06:05] Anyone here a cmake guru? [06:13] ScottK, ping [06:13] NCommander: Pong. Not me. [06:13] o_o? [06:13] * ScottK is not a Cmake guru [06:13] No, I solved it in a really hacky fashion [06:13] upstream can dehackify it if they want [06:13] ScottK, is it too late to get the last uploads of python-qt4/kde4libs/kde4bindings to fix it on ARM? [06:13] (I hope) [06:14] ScottK: beta 2 all uploaded? [06:14] Riddell: I think so. [06:14] * ScottK wasn't counting. [06:14] Riddell: I've been looking an the Jaunty problems page and component mismatches. [06:15] ScottK: excellent [06:15] Riddell: Is getting armel working with KDE a release goal worthy of uploading during the freeze? [06:15] Riddell: You can do binary promotions, right? [06:16] * ScottK shoves the list at Riddell [06:16] python-plasma libkdcraw7 libkdcraw7-dev libkexiv2-7 libkexiv2-7-dev all need promoting. [06:17] NCommander: If Riddell says it's a release goal, I'll upload them tomorrow. [06:18] Its all in bazaar [06:18] If he doesnt' say it's not a release goal, I may anyway. [06:18] and on its way to my PPA for a final rebuild test or two [06:18] NCommander: Which packages again? kde4linbs, python-qt4, and kde4bindings? [06:19] python-qt4, kdelibs, and kde4bindings [06:19] I versioned bindings correctly so it will dep-wait until the previous two are properly built [06:19] NCommander: kde4libs, right? [06:20] no, kde4libs and python-qt4 can go in either other [06:20] kde4bindings requires both of those to be updated [06:20] The dependencies are correct so it all works :-) [06:20] Right, but you said kdelibs, not kde4libs. Just making sure. [06:21] oh, sorry [06:25] ScottK: all promoted [06:25] Riddell: Thanks. [06:26] ScottK, I'm uploading my PPA if you don't wish to test build [06:29] NCommander: Link me at some point. I'm going to be here soonish. [06:29] ScottK, https://bugs.edge.launchpad.net/ubuntu/+source/python-qt4/+bug/308814 [06:29] Launchpad bug 308814 in python-qt4 "Patches for kde4bindings to build it on ARM" [High,In progress] [06:29] I know the python-qt4 is perfect, if your not going to upload for alpha 2, then I'm going to rebuld kde4libs all the way through on ARM (which will take about two days) [06:30] Riddell: Comments on uploading the armel fixes for Alpha 2 or wait until after the freeze? [07:09] <_Groo_> hey/2 all [07:09] <_Groo_> anyone alive? [07:10] <_Groo_> im working on kipi-plugins 0.2 and digikam 0.10 for intrepid/jaunty [07:10] <_Groo_> also i finished koffice2-kde4 beta4 and kvirc 4.00 [08:09] <_Groo_> hi/2 all.. [08:09] <_Groo_> anyone alive yet? [08:10] no, everyone's dead. [08:10] they were earlier though, before you came in the first time. go figure [08:11] <_Groo_> Hobbsee: hehehe [08:12] <_Groo_> ok, i now finished kipi-plugins 0.2.0 for kde4, compiling digikam 0.10 for kde4 , fixed kvirc and koffice2-kde4 beta 4... where can i dump all my work? (dont say trash pls) :P [08:14] <_Groo_> Hobbsee: are you there> [08:16] _Groo_: perhaps revu or a ppa [08:18] (no) [08:21] <_Groo_> crimsun: my idea was for you guys to review it so we could add it for intrepid + jaunty [08:21] <_Groo_> maybe in kubuntu-experimetal ppa [08:43] <_Groo_> digikam-kde4 0.10 beta6 is complete + kipi-plugins 0.2.0 beta 5 :) [08:44] <_Groo_> gwenview also inherited the kipi plugins out of the box :D [09:11] what is the main lib now for kde? used to be libmt3 IIRC? [09:15] Anyone know when KDE 4.2 Beta 2 is going to be packaged? [09:16] Yes and yes [09:16] "When it gets done?" :D [09:16] lol you got it [09:17] Do you happen to know how to get the tempature monitor in the new KDE 4.2 "System Monitor" widget working? [09:17] I've no idea really, I know they are working hard :) [09:17] the beta 2 release date was pushed back a day (to today) [09:17] I've running Neon right now, and it's really stable. [09:17] Oh? It's on the KDE release announcement... [09:17] I haven't tried the temperature monitor yet I'm afraid [09:18] I can't figure out how to get it working :( [09:18] And that (for me) is one of the most exiciting features :) [09:18] Where's the release announcement? [09:18] I could have swarn I saw it... [09:18] *shrugs* [09:18] It's not on the KDE homepage yet [09:18] Oh well, the Neon build is as close as it's going to get to Beta 2 right now ^_^; [09:19] Though they've started to edit the beta 1 release page [09:19] (http://www.kde.org/announcements/announce-4.2-beta2.php) [09:19] So I'm sure they'll publish it on the home page later today [09:19] Yeah, that's what I read. [09:19] Someone must have posted to the edited article >_> [09:19] Yea :) [09:20] Im still amazed at how stable it is [09:20] Heck, they might as well release THIS as 4.2; since there's going to be no new features lol [09:21] DOH [09:21] Plasma just crashed, lol [09:22] rofl [09:22] I want to help develop Kubuntu, but.. I have zero experience at packaging, programming, (anything really) [09:22] I know a decent amount about Linux in general though [09:26] was libqt3-mt updated for kde4? or is there a different lib in its place? [09:34] can i report bugs about 4.2? [09:34] or should i report them to the kde.org bugzilla or smth? [10:11] Hi [10:11] I'm a c++ developer [10:11] I would like to help you [10:13] I have previous experience with qt [10:15] Is there any task for me? [10:24] almost certainly, we just need to find the right one :) [10:24] Riddell: apachelogger what have we got for a willing c++ coder ^^ ? [10:25] <_Groo_> nicolab80: did you read http://www.kde.org/getinvolved/ ? [10:25] <_Groo_> Arby: btw ive completed to port kipi-plugins 0.2.0 and digikam 0.10 [10:25] <_Groo_> Arby: also fixed kvirc and koffice2 beta4 [10:29] <_Groo_> no one gives a damn for my work oO [10:33] _Groo_: sorry I'm at work [10:33] got called away [10:34] <_Groo_> Arby: :P :) [10:34] _Groo_: you need somebody to review your work and then upload [10:34] and I can't do that [10:35] <_Groo_> Arby: yeah, im waiting for apachelogger to show up... compiling in the ppa meanwhile [10:35] _Groo_: yep, he's your man :) [10:36] mornings (European time) are always quiet in here for some reason [10:36] <_Groo_> Arby: im in latin america but yeah... ppl are all sleepy :D [10:36] <_Groo_> Arby: where are you from? [10:36] _Groo_: UK [10:37] <_Groo_> Arby: im portuguese, but living currently in brasil [10:37] <_Groo_> Arby: my brother is in london [10:37] cool, the more the merrier [10:37] having non-English speakers is always handy to :) [10:38] right, better stop slacking and get back to work [10:38] _Groo_: stick around, your work is more than welcome :) [10:38] * Arby -> $dayjob [10:39] <_Groo_> Arby: :) [10:50] _Groo_: I read [10:51] is it better to work with kubuntu or kde? [10:53] <_Groo_> nicolab80: kubuntu is a distro.. kde is the real thing (TM)... [10:53] <_Groo_> nicolab80: you can work with both [10:53] <_Groo_> nicolab80: open source is about choosing and beeing happy :) [10:54] :) [10:54] <_Groo_> nicolab80: but kde also needs good qt devels.. [10:54] <_Groo_> i mean always [10:55] I'm looking for little task to start [10:55] <_Groo_> choose a mentor in kde and they'll guide you along [10:56] ok! Thank you! [10:56] <_Groo_> nicolab80: you welcome [12:29] changing channels in irssi in konsole 4.1.85 takes like half a second :o [12:35] ScottK: that rsibreak thing got nothing todo with neon at all [12:35] Sime: pretty pretty please take a look at https://bugs.kde.org/show_bug.cgi?id=177965 [12:35] KDE bug 177965 in KDE4 (cmake) "FindPyQT4 provides no method of accessing SIP configuration options" [Normal,Unconfirmed] [12:41] apachelogger: sebr said the amarok 2 package still seems to have a ruby dep - can you check that please? [12:42] possible [12:42] Nightrose: I am not going to rebuild them because of that though [12:42] *nod* [12:42] for the next release though [12:43] something to keep in mind [12:43] or something to fix and commit right away :P [12:43] :P [12:43] even better [12:44] Riddell: upstream fixed the moon [12:44] committed for rc1 [12:44] * apachelogger also drops the workspace dep as well [12:47] wth [12:47] "I think 1024x768 is probably the most widely used size of screen on laptops." [12:47] does our prophet live on the moon?... to connect to what JontheEchidna said :P [12:51] Nightrose: committed [12:51] * Nightrose hands apachelogger a cookie [12:51] thx :) [12:51] JontheEchidna: you didn't bump build deps in kdeartwork [12:52] * apachelogger eats cookie [13:01] <_Groo_> apachelogger: eyah apachelogger [13:02] <_Groo_> apachelogger: have a few goodies for you today :) [13:02] that doesn't sound good [13:02] <_Groo_> apachelogger: kipi-plugins 0.2.0 for kde4 (intrepid backport) and digikam 0.10.0 f for kde4 (same thing).. both are jaunty compatible [13:02] <_Groo_> also i fixed the kvirc package [13:03] <_Groo_> kipi and digikam are available from my ppa [13:03] digikam can't build against 4.1 [13:03] thus kipi is a no-go as well [13:03] <_Groo_> i can send you the diffs if you want.. tested it a lot... gewnview inherited kipi-plguins just fine also [13:03] <_Groo_> apachelogger: ist for kde 4.2... ence the build for kubuntu-experiemtnal [13:04] <_Groo_> apachelogger: the idea is to include them for jaunty and kde 4.2 beta 2 [13:04] so what does this have to do with intrepid-backports? [13:08] <_Groo_> apachelogger: no, i explained it wrongly.. i meant i built in in intrepid using the kubuntu-experimetnal ppa dep... so it can be included in the next kde 4.2 beta 2 AND jaunty [13:09] hm [13:10] _Groo_: https://wiki.ubuntu.com/SponsorshipProcess [13:10] besides, someone is working on digikam I think [13:11] ^^working on it for jaunty anyways [13:11] <_Groo_> apachelogger: i already did it... [13:11] http://revu.ubuntuwire.com/details.py?package=digikam-kde4 [13:12] <_Groo_> ok [13:12] <_Groo_> how about kipi? [13:12] <_Groo_> kipi should be treated as a new package in jaunty? [13:12] no kipi before digikam kde3 is kicked out [13:12] <_Groo_> since is a kde4 version [13:12] _Groo_: depends on how you packaged it [13:12] but usually not [13:12] JontheEchidna: why digikam-kde4 btw? [13:12] if you happen to know [13:12] <_Groo_> i packaged it as kipi-plugin-kde4 with kipi conflict for kde3 verison [13:13] apachelogger: no clue [13:13] _Groo_: no need, AFAIK gwenview and digikam use it [13:13] so the kde3 version would either have to be removed or supersed [13:13] I would prefer the latter [13:13] <_Groo_> digikam-kde4 so it wont ve confused and to be easier to conflict with digikam for kde3 [13:13] there is no need for the KDE 3 version anymore [13:13] <_Groo_> exactly [13:14] I find this all very confusing [13:14] <_Groo_> but it still lives in intrepid.. so i created it with the kde4 added, anyway it appears to be the standard for new packages anyway for kde4.. amarok-kde4, krvirc-kde4, etc [13:14] it is not [13:15] there is no amarok-kde4 in jaunty because it will be added as amarok once mysql 5.1 is available [13:15] <_Groo_> intrepid still has digikam and kipi (kde3) version, who dont have any more deps.. since gwenview (which is kde4) isnt using kipi... [13:16] <_Groo_> so to be able to maintain digikam and kipi (if you choose to use kde3) and still be able to use kde4 versions safely, i named them kipi kde4 and digikam kde4 which conflicts with the kde3 versions just to be safe [13:16] hm [13:16] I think I get the thinking problem here [13:17] _Groo_: you should be thinking about jaunty [13:17] and in jaunty digikam as well as kipi ought to replace their KDE 3 counterparts [13:17] <_Groo_> its a matter of renaming the damn thing anyway :O i couldnt care less what name you devs give the damn thing.. im just rtying to help and create the packages with all deps and stuff correctly.. the name is the least impopirtant opart [13:18] <_Groo_> yes, but i made this first packages specifically for kde 4.2 beta 2!!!! to be used with kde-experimental since beta2 is around the corner.. and this same packages can be used for jaunty, just need to be renamed [13:18] * apachelogger cuts the jaunty part [13:19] * _Groo_ gonna start to kill some kitties [13:19] <_Groo_> small ones... cute ones [13:19] _Groo_: I don't agree on the -kde4 suffix for kipi [13:20] it forces us to introduce appropriate repalces in jaunty [13:20] can live with digikam-kde4 [13:20] anyway [13:20] <_Groo_> apachelogger: so what you sugest for kde-experimental? [13:20] _Groo_: go talk to JontheEchidna, he's working on b2, he can upload your stuff to experimental along with it [13:21] * JontheEchidna waves [13:21] <_Groo_> hi JontheEchidna [13:21] * JontheEchidna has been reading [13:21] that said [13:21]