[00:00] _Groo_: I've not looked at kdebindings yet since it didn't compile with beta 1, hopefully it'll compile with beta 2 we'll just have to see [00:00] Sime: do you know if kdebindings is compiling now? [00:00] <_Groo_> Riddell: well like i said youll have backport pqt4, qscintilla2 and sip from current snapshots [00:02] <_Groo_> Riddell: i didnt tryed to compile with latest kdelibs from svn but with beta1 it borks . [00:02] mm, fun fun [00:02] <_Groo_> it has problems with both soprano and akonadi [00:04] <_Groo_> even disabling both doesnt do the trick... i even tryed last week kdebindings svn, still no can do... but im using libs from beta1 so i hope its fixed upstream.. but new pyqt and qscintilla are mandatory [00:05] <_Groo_> Riddell: one good news is that i did extensive testing with qt raster enabled by default, and im happy to report that it looks pretty good [00:06] <_Groo_> and thats with qt 4.5.1, 4.5.2 should be even more stable [00:06] raster is interesting but I'd really like to know the opinion of Qt developers before considering changing it in our packages [00:06] i was just reading something in #koffice about kword crashing because kubuntu had raster by default [00:07] <_Groo_> Riddell: agreed, but since its a compile option and can be deactivated at runtime (per app), it might be nice to create a specific ppa or branch for it.. its just the same qt anyway [00:07] <_Groo_> m4v: not true, im using raster and koffice works like a charm [00:07] <_Groo_> m4v: and kubuntu DOESNT ship raster by default [00:08] <_Groo_> m4v: raster isnt evil anyway, its even a more clean susbsystem then native.. what occurs is that some apps needed workarounds that are exposed with raster [00:09] <_Groo_> m4v: bespin had a such workaround that was crashing plasma-overlay on exit (nothing major) (like in screensaver locking), i reported and helped bespin guys, and its now fixed in bespin svn... [00:10] <_Groo_> m4v: so if you use raster and some app MIGHT crash try changing the decorator to oxygen or bespin. skulpture works fine also [00:11] don't worry, I'm not a dev just you don't actually have to explain me, i was just quoting "17:51 I guess that kubuntu ships a Qt that uses the raster paint engine per default. which makes kword crash" [00:11] i'll paste that in #koffice [00:11] <_Groo_> Riddell: what i would sugest (less work path) would be to create a qt-raster packages that would be mutually exclusive with qt native (like ffmpeg restricted). easy to do and the user would be able to use whatever he wants or works best for him [00:12] <_Groo_> m4v: aparently he doesnt even know that if he used kword -graphisystem native he would be back to native behaviour... [00:13] <_Groo_> m4v: and would have the same crash since kubuntu DOESNT compile raster as default [00:13] ThomasZ works for Qt so he likely has a fair idea of how it works [00:14] <_Groo_> Riddell: i respect that, but then he SHOULD know that kubuntu doesnt.. [00:14] <_Groo_> unfortunatelly kubuntu is getting a bad rep for not being a good kde distro.. which is absolutely not true [00:15] <_Groo_> Riddell: but sometimes you guys screw up big time :D like the idea to ship network plasma manager by default in jaunty... the damn thing is far from being finished.. [00:15] _Groo_: we didn't have many options for network mangement [00:16] <_Groo_> i bitched over and over on this channel about that would blow up in our faces [00:16] <_Groo_> Riddell: shipped nm-applet instead.. thats what fedora guys did for 11 [00:16] we're a kde distro, nm-applet isn't kde [00:16] <_Groo_> unfortunatelly the plasma one is amazing but its in early stages of development.. maybe it will it gold in 4.4 [00:17] _Groo_: whats the problem with an apt-get install network-manager-gnome ? [00:17] neversfelde: hard to do without a network connection :) [00:17] <_Groo_> neversfelde: hum... here we go again.. ok... [00:17] <_Groo_> Riddell: exactly... [00:17] or with using knetworkmanager or even wicd? [00:17] mhh, I never had a problem with a cable and the network-manager [00:18] <_Groo_> neversfelde: that was my point all along, i know nm-applet its a gnome app and need some heavy libs but unfortunatelly kde world is in transition.. and we DONT have a finished networkmanager app still [00:18] is there really a user, that can't install nm-applet via a calbe connection? [00:19] <_Groo_> neversfelde: a lot unfortunatelly, all the bitching with latest kubuntu (reviews etc) are precisely because of not being able to use wifi with plasma [00:19] apt-get install carrier-pigeon [00:19] old school data delivery [00:19] <_Groo_> neversfelde: and we cant presume that the average joe even knows the name or how to install those packages [00:20] <_Groo_> neversfelde: and how could he if he cant use wifi anyway? its a dead end. [00:20] neversfelde: me. my e1000e got fried by intel drivers when that bug was around [00:20] mhh, put the cable in and enjoy the net, if you are not at home, wait till you are there [00:20] <_Groo_> Riddell: you too ? :D [00:20] ryanakca: ping [00:20] <_Groo_> neversfelde: i respect you, but you are being stubborn :P [00:20] hehe [00:20] _Groo_: I only discovered it months later when I was testing network manager with cabled connections :) [00:21] <_Groo_> Riddell: unfortunatelly i find out right away :P [00:21] I read about the CD beeing oversized 70 MB, so this is a discussion without any future isn't it? [00:21] rgreening: pong [00:21] <_Groo_> neversfelde: ripp of openoffice.. [00:21] hey, did you see kobby beta3 is out [00:21] I read about wict 1.6 beta as a curses frontend [00:21] s/wict/wicd [00:21] rgreening: I saw it was tagged, but uscan wasn't showing anything [00:22] author blogged about it [00:22] rgreening: Lovely, uscan spotted it, I'll update my packages [00:22] :) [00:22] <_Groo_> neversfelde: or leave out some packages that arent that used in the first place.. its a live cd.. ppl need network more then they need word processing.. [00:22] whee... maybe less crashy [00:22] _Groo_: I think that there should be no Kubuntu without an office suite? [00:23] <_Groo_> neversfelde: and we can now ship koffice 2.0 anyway ;) [00:23] can we? [00:23] If there isn't an office suite installed on the live CD, how will Joe Average know that Kubuntu comes with an office suite? [00:23] I tested it over months and it is good, but not for the average user [00:23] <_Groo_> ryanakca: python script? click here to install FREE openoffice? [00:23] you can't print from kword for example [00:24] <_Groo_> neversfelde: yesi know, i was saying.. better then none [00:24] <_Groo_> neversfelde: sure you can.. [00:24] koffice <> ready for me :) [00:24] no, an office suite seems to be much mor important than nm-applet [00:24] _Groo_: Weren't you just advocating that you shouldn't ship something that's half done? [00:24] lol.. hahah ryanakca [00:24] zing [00:24] rgreening: are you able to Export as PDF in kword or even do a print? [00:25] <_Groo_> ryanakca: im advocating that shipping a broken wifi manager pisses ppl more then not shipping openoffice because of lack of space [00:25] neversfelde: I sadi koffice <> (not equal) to ready [00:25] <> != etc [00:25] Im a ooo user [00:25] I much prefer it [00:26] _Groo_: for me the plasmoid work perfectly fine wireless and wired [00:26] * ryanakca uses LaTeX and much prefers it... but it isn't something you really want to teach your grandmum how to use... [00:26] what about that wicd ncurses, should be samll and not gtk. We could wirtite a good doc how to use it and there would be an alternative [00:26] latex == teh evil [00:26] <_Groo_> rgreening: are you using wpa or wpa2 by any chance? [00:26] nope, wep (weak I know) [00:27] imo much better than killing the office suite or using the gnome frontend [00:27] iirc, wasn't knetworkmanager available (and possibly in the cd)? [00:27] it is [00:27] <_Groo_> rgreening: here wep doesnt work with plasma, only wpa and wpa2.. its a known bug its even in the source TODO.. like i said the plasma is very nice but its a running target for now [00:27] neversfelde: Shouldn't be too hard to port an ncurses frontend to qt4? And yeah, what happened to knetworkmanager? [00:28] but no one understands, that there is a knetworkamanger AND a plasma-widget-networkmanager [00:28] _Groo_: wep doesn't work for you? what version are you running. I have be successful with wep for a long time [00:28] <_Groo_> neversfelde: yes true, but the plasma one is activated by default [00:28] So, if knetworkmanager is there, why would we also bother with nm-applet? [00:28] <_Groo_> rgreening: latest from svn [00:29] I do support to new users every day and it is not a sollution for them do use knetworkmanager or nm-applet [00:29] <_Groo_> rgreening: never did, with the one shipped with jaunty and with latest code [00:29] svn == don't complain ;) [00:29] they do not know the difference or even how to start ist [00:29] * Riddell snoozes [00:29] <_Groo_> rgreening: come on, you know svn is more updated and stable then what was shipped ;) [00:29] rgreening: Any ideas as for http://ryanak.ca/~ryan/ryan-kobby_1.0b3-1-i386-20090602-1925 ... libqinfinity gets pulled and installed, but CMake doesn't seem to be able to find it.... [00:29] Night Riddell [00:30] * rgreening thinks _Groo_is looking to help develope, patch, bugfix the next build... [00:30] <_Groo_> i gotta go also.. [00:30] <_Groo_> rgreening: yes i do [00:30] ryanakca: I read about it in the faq http://wiki.github.com/greghaynes/kobby/faq [00:30] <_Groo_> rgreening: im doing it one way or the other for the last two builds :P but i normally keep myself in the shadows.. waiting, plotting... [00:31] neversfelde: Hmm... looks like a good place to look, thanks :) [00:31] like a grew [00:31] * rgreening has played zork [00:31] * _Groo_ is a ex-WoW addict [00:31] meh, nuttin beat a text based game [00:31] * neversfelde plays freeciv, only one time a year :D [00:31] * _Groo_ misses is raids [00:32] :g n [00:32] :open door [00:32] do you think we coukd update wicd to 1.6 beta ? [00:32] s/coukd/could [00:33] neversfelde: is it in main or universe [00:33] <_Groo_> neversfelde: let me see. wicd which is gtk = good.. nm-applet = bad? [00:33] I never tested that curses frontend, but I know several users, that are very happy with it [00:34] rgreening: there is a ncurses and gtk frontend afaik, we could ship the first one for emergency [00:34] rgreening: Gotta love MUDs, eh? [00:34] if it works [00:34] muds were da bomb [00:35] Personally I'm very happy with the plasma nm in jaunty [00:35] yes, works perfectly here, too [00:35] * _Groo_ will start killing kitties [00:35] I agree, works for me [00:36] <_Groo_> aaaaarghhh [00:36] but there are a lot of people, who can't use ist [00:36] I think Its cause I use Intel based systems :) [00:36] please no gtk+ :P [00:36] neversfelde: CMAKE_INSTALL_PREFIX = /usr ... should be correct, no? [00:36] atheros here [00:37] <_Groo_> i have atheros also, but the problem isnt always your card but the router.. that works fine with nm-applet but has issues with plasma [00:37] ryanakca: sorry, no idea, I only read the FAQ for starting the server^^ [00:39] <_Groo_> well gotta go.. i know the current netwrkmanager plasma thing is a hot topic, lets see till karmic is out if the kde guys have time to bang out the bugs [00:40] <_Groo_> but remember that fedora guys where able to release kde 4 with bell and whistles AND nm-applet :P [00:40] <_Groo_> ow btw, where can i send rekonq 0.1 package? [00:41] _Groo_: afaik has Tonio_uploaded it,yet [00:42] <_Groo_> this review shows exactly what i said about frustration with network [00:42] <_Groo_> http://www.itnewstoday.com/?p=293 [00:42] _Groo_: Debian [00:42] <_Groo_> neversfelde: ok ppl, seeya all later [00:43] <_Groo_> ryanakca: i was thinking about some queue upload? no one ever botehered to explain to me a proper upload sequence [00:44] <_Groo_> well see ya ppl :) [00:44] Could someone take a look at kobby & libqinfinity please, http://packages.ryanak.ca/apt/pool/main/ has the source and binary (i386) packages [00:46] someone likes to bet with my about the daisy plasma widget version :D [00:46] ist is 0.0.4.14 [00:46] I think that there will be 0.0.4.26 [00:46] anyone holds it :D [00:46] s/ist/it [02:52] * ScottK waves. [03:23] yo [03:23] * ScottK isn't going to play that game again tonight. [03:23] ha [03:24] oy [03:24] oy vey! [03:25] is that a different game? [03:26] dunno [03:31] are you interested in playing the sponsorship game? [03:33] if so, its an easy one [03:33] http://machine-crusade.net/skulpture/ [04:14] vorian: I'll have a look. [04:16] vorian: debian/copyright could stand an update. [04:18] The package isn't distributable as described by debian/copyright, but fortunately it's wrong (at least for the new version) [04:38] vorian: When you get that fixed, let me know. [07:16] Riddell: PyKDE4 should be in good working order for beta 2. \o/ === hunger_t is now known as hunger [08:55] Sime: awooga === sabdfl1 is now known as sabdfl [09:43] Are there 4.3 packages for Jaunty? [09:44] sebas: yes, I'm about to copy them across [09:44] Riddell: ah nice [09:44] oh, 4.3 [09:44] I've got my new machine and want 4.3 on it [09:44] assumed you were asking about 4.2.4 for the release [09:44] we have 4.3 beta 1 as well [09:45] No, I'm looking for the beta [09:45] * sebas went for edgy in this setup [09:45] ext4 from the start, 4.3 ... [09:45] Where can I find the 4.3 beta ones? [09:46] sebas: https://edge.launchpad.net/~kubuntu-ppa/+archive/experimental [09:46] thank you! [09:46] they never left experimental because of upgrading problems but those should be all fixed now [09:46] let me know if you still have any problems though [09:47] sure [09:57] sebas: don't forget that beta2 is going tagging today so it should be coming out soon [09:59] Tm_T: sure, I'm usually the one releasing it :) [09:59] aye [10:50] Riddell: you know about this? http://www.kubuntu.org/news/kde-4.2.4 [10:50] (the article is missing) [10:51] hmm, now there's some [10:52] yes, I did write it [10:52] roger [10:52] was just wondering [11:22] Tm_T: any problems? [11:31] Riddell: no not anymoer [11:31] more [11:43] sebas: hmmmmm, how will we do with Jaunty and KDE bugfix releases, are these coming to main repositories or not? [11:43] hi [11:44] printer config is broken on karmic or is that just me ? [11:44] http://pastebin.ca/1446049 [11:45] not just you [11:48] kk [11:48] it worked 10 days ago since I was able to install my printer using it [12:05] Riddell: kopete-facebook stil ftbfs for me... that's why it's not uploaded yet... [12:06] Riddell: /usr/bin/ld: cannot find -lkopete_videodevice <-- have seen that problem ? [12:10] Tonio_: sigh, my kdenetwork upload to fix that doesn't seem to have arrived [12:10] let me try again [12:11] kk [12:11] * Tonio_ works on k-d-s [12:17] 4.2.4 Upgrade wants to remove kdeartwork, kdebase-workspace-bin, kdeplasma-addons, kscreensaver and kscreensaver-xsavers [12:18] I do not want to remove kdeplasma-addons :) [12:46] neversfelde: those are not build yet? [12:56] Tm_T: what do you mean? [12:56] Which KDE version for example? [12:56] sebas: 4.2.4 for example [12:57] will it only be in ppa ? [12:57] We've never put those bugfix updates in main AFAIK [12:57] Maybe it can go into backports [12:57] sebas: backports sounds good to me [12:58] but ppa only is bit, well, not helpful for everyday users [13:08] 4.2.4 packages are a bit broken, but non broken ones are compiling === Quintasan_ is now known as Quintasan [13:29] any ninja around? [13:29] apachelogger: yo [13:30] Riddell: please try copying kobby and libqinfinity from my ppa to the experimental ppa [13:30] https://edge.launchpad.net/~apachelogger/+archive/ppa/+copy-packages [13:30] lp errors here [13:32] builds are *long* to perform.... [13:32] https://edge.launchpad.net/ubuntu/+source/mlt/0.4.2-1ubuntu1/+build/1056358 [13:32] still not in the archives though... [13:32] apachelogger: AssertionError: Found more than one build candidate: [1057731, 1057486]. It possibly means we have a serious problem in out DB model, further investigation is required. [13:33] apachelogger: you broke soyuz [13:33] indeed I did [13:33] though I think it is just not treating the problem properly [13:33] the packages were in experimental [13:33] however I wanted them built against stock jaunty ... so I copied to my PPA for rebuild, deleted in experimental and now it should be going back to experimental [13:34] I assume it doesn't like that case very much [13:34] * apachelogger uploads version bump [13:34] ouch, what was that again? I have users complaining about 4.2.4 doing weird stuff? [13:35] users should not use any ppa in a productive environment :D [13:36] developers should do what is most important about packaging :P [13:37] neversfelde: and devs should not make release announcements without the usual warnings and if not sure there are no problems with the PPAs... [13:38] devs should not make release anouncements at all :P [13:38] :D [13:38] the marketing dudes should [13:38] well, there is a release announcement still visible in the left on the website, see June... [13:39] so if this PPA is full of bugs that should not be there [13:39] which, from a social POV, would probably make devs deploy higher quality to begin with [13:39] since the marketing dudes get beaten up if the quality sucks [13:40] so in theory the devs would not want to have the friendly marketing dudes bleed out of their noses, so they will try to get higher quality [13:40] of course we aint got not marketing... so [13:40] so we can happliy bet you up? [13:40] * Mamarok larts apachelogger [13:40] * apachelogger aint got nothing to do with anything [13:40] using PPA are at your own risk ... only ever expect the quality in the archives to be of high quality. [13:41] rgreening: well, then don't advertise it on the website as a bugfix release... [13:41] PPA are a testing ground by their nature of existance [13:41] like that is true [13:41] 4.2.4 is a bugfix rrelease for 4.2.3 from KDE... [13:41] don't advertise it at all untill you are sur it's not killing your cat and the baby [13:41] rgreening: read the release text for 4.2.3 then :) [13:41] doesn't mean its ready yet as its in a PPA for testing [13:42] meh.. I never put out release notices.... shoot the ones that do :) [13:42] then do not advertise it or change the text with lots of warnings and bliking lights: for *testers* only [13:42] no [13:42] PPA == test [13:42] shoot the one that publishes the packages :P [13:42] period [13:42] rgreening: that is not true either [13:43] apachelogger: for the most general cases (dont argue semantics) [13:43] rgreening: we lost that card a long time ago by contunially using ppa's for releases [13:43] :) [13:43] (not saying it's a bad thing but...) [13:43] lol [13:43] rgreening: for the most general cases some loony uploads packages to his personal ppa [13:43] but since we are the source distributor... [13:43] anyway, we really should change the texts on the website, it's disastrous to advertise "bugfix releases that ar not in the backports anyway [13:43] we can't expect users to know the difference between a broken and a good ppa [13:43] and really [13:44] who posted the release [13:44] looking at the issues that appeared in karmic... it makes me doubt if anyone here really cares about quality [13:44] so, could somebody please take that text down? it's still there in June... [13:44] I mean, you say PPA is for testing, but it seems the archives are just for testing as well [13:44] like, throw out that merge or update and see what people whine about and then go fix it [13:44] karmic == test [13:45] :) [13:45] karmic == development [13:45] rgreening: ... [13:45] development != testing [13:45] yeah... [13:45] both [13:45] not in terms of file conflicts and whatnot [13:46] true [13:46] so please, somebody take that text down or give me write access, I'm not going to spend weeks on reparing stuff in #kubuntu with people who took this for a "bugfix" release [13:46] like when we render ourselfs unable to testbuild stuff etc. [13:46] Mamarok: Riddell has to do that [13:46] Mamarok: bug Riddell, not the channel. He's the only one with current access. [13:46] Hobbsee: not true [13:46] Riddell: see above, the text is still there... [13:46] * Hobbsee ^5 Nightrose [13:47] at least 2 other ninjas do [13:47] Hobbsee: ;-) [13:47] apachelogger: oh? someone else got ssh access in? [13:47] anyway, if I was sabdfl I would have forced you all to attend a QA training at UDS [13:47] Hobbsee: it's drupal nowadays :P [13:47] apachelogger: :) [13:47] apachelogger: hm, so it is. [13:47] apachelogger: don't throw stones :) [13:47] apachelogger: who are the other two? [13:48] me and vorian I think [13:48] also ryanakca got access [13:48] whenever I try to log in I get 403'd :( [13:48] as for QA, there is a conflicxts report thats run. I've asked the QA team to help us out with that.. [13:48] I used to be able to login [13:48] apachelogger: so, yeah, we took some initiative at UDS to try and fix our QA. [13:49] apachelogger: then please take that text down... [13:49] or you will be tied to a chair with eyes forced open and do support in #kubuntu [13:49] JontheEchidna: true [13:49] so, what's up with the 4.2.4 packages? /me is out of the loop [13:49] then poke Riddell [13:50] rgreening: so, why can every individual developer just not ensure that his package ain't got no problems? [13:56] the packages themselves are fine, it's copying them to the other PPA when they were compiled in a PPA with qt 4.5.1 which breaks it [13:56] * Riddell unticks published story [13:57] where were the built? Oo [13:58] kubuntu-experimental, probably [13:58] morning [13:58] Riddell: thx :) [13:59] I think we need a staging PPA for the kubuntu-ppa updates/backports [14:00] JontheEchidna: ninjas [14:00] * JontheEchidna seems to recall this happening last time, minus the borkage [14:01] we pushed to experimental accidentally [14:01] :S [14:02] we should prob have not copied between PPA's... [14:02] mayb e thats the lesson here. [14:02] copying is the only way to have the published in a sensible time [14:02] if the packages had been uploaded to ninjas then copied over to kubuntu-ppa/updates then everything would have been fine [14:03] else we need a -stable (4.2.[234..]) and -unstable (4.3 betas) for staging [14:03] or something... [14:05] the problem here is that experimental was being used for non-experimental things and as a result KDE 4.2.4 got built against the Qt 4.5.1 that was in there [14:05] then copied to a location that didn't have Qt 4.5.1 [14:05] or at least this is how i see it at 9 in the morning [14:05] * rgreening goes back to usb-creator hacking... [14:06] rgreening: why would we be staging a stable and unstable in the same series at the same time? [14:06] apachelogger: forget what I said.... [14:06] ok [14:06] JontheEchidna: but we can't copy from ninjas, that's the pain [14:06] Riddell: why not? Oo [14:06] apachelogger: goodness knows. some internal soyuz thingy [14:07] [08:59:07] I think we need a staging PPA for the kubuntu-ppa updates/backports [14:07] The following source cannot be copied: kdebase-runtime 4:4.2.4-0ubuntu1~jaunty1~ppa2 in jaunty (Cannot copy private source into public archives.) [14:07] that is ewww [14:07] akonadi-resource-googledata on revu guys ! [14:07] just raze the staging ppa each time you're done with it and everything's good [14:08] JontheEchidna: aye, get staging and request size bump [14:08] and while you are at it: beat someone up for that mess [14:08] really, people will be using a public staging and break their system [14:08] just like they use my public staging and break their system :P [14:09] staging seems the way forward [14:09] Tonio_: is that package name debian approved? [14:09] Riddell: well, in the long run that private vs. public issue should be resolved [14:09] staging twice is a waste of resource [14:10] Tonio_: The changelog does not close a bug from Launchpad. New packages should have a needs-packaging bug and the upload close it using the syntax "(LP: #nnnn)". [14:10] apachelogger: who's the authority for that ? [14:10] https://edge.launchpad.net/~kubuntu-ppa/+archive/staging [14:11] Tonio_: that=? [14:11] approving a package name [14:11] JontheEchidna: size bump [14:11] Tonio_: debian-qt-kde team [14:13] https://answers.launchpad.net/soyuz/+question/73122 [14:14] thanks JontheEchidna [14:14] apachelogger: should I ask for the package name, really ? [14:15] well, if the naming pattern is ok [14:15] akondi-resource-... [14:15] sounds good to me, debian might have a different POV though ;-) [14:15] apachelogger: debian is used to change it's mood on that point :) [14:15] apachelogger: ok... I'll ask... [14:16] apachelogger: still revuable I think :) [14:18] sure [14:19] lex79: hi, is your konversation branch ready for merging? [14:20] ok [14:20] that ctrl shortkey shit in konqueror made me loose my input again [14:20] someone please deactivate it for karmic [14:20] apachelogger: which one ? [14:20] apachelogger: I'm on kds right now [14:21] press ctrl [14:21] kubotu: search konqueror ctrl shortcut config [14:21] apachelogger: and ? nothing happens... [14:21] Results for konqueror ctrl shortcut config: 1. 'Re: KDE 4.1 rc1 issues' - MARC: http://lists.kde.org/?l=kde-devel&m=121227176710104&w=2 | 3. KDE 4.1 rc1 issues: http://lists-archives.org/kde-devel/16738-kde-4-1-rc1-issues.html | 4. CodeIdol - Thinking about Fedora Linux - Using Fedora On Your ...: http://codeidol.com/unix/fedora/Using-Fedora-on-Your-Desktop/Customizing-KDE/ [14:21] ah ! [14:21] apachelogger: hum I like this option [14:21] poor google [14:21] very usefull for usability [14:21] lex79: btw, we are keeping the debhelper folder around to decrease the diff from debian [14:21] Tonio_: on sites with less then 300 links maybe [14:22] if we disable it people might not know this option exist, no ? [14:22] lex79: we just aren't using it ;-) [14:22] which is rather uncommon these days [14:22] everything has to be an option and what not [14:22] apachelogger: right [14:22] apachelogger: fixing this [14:22] kthx [14:23] apachelogger: just in case, do you know where the option hides ? [14:23] lex79: same with the debian patches [14:23] Tonio_: no, ask google [14:23] I am not even sure that thing is GUI visible [14:23] KDE refused to have it in the GUI AFAIK [14:24] for some wired reason though [14:24] that's what I think... [14:24] will check [14:24] I have to find out the option's name first.... and the file it is in [14:25] apachelogger: kwriteconfig --file khtmlrc --group "Access Keys" --key Enabled --type bool false [14:26] fyi [14:27] apachelogger: done in k-d-s bzr pushed [14:27] Tonio_: akonadi resource reviewed [14:29] apachelogger: new packages do need a launchpad bug outside of the freeze context ? [14:30] yes [14:30] for documentation purpose [14:30] and to avoid work duplication [14:31] * Tonio_ is sick with the growing and growing bureaucracy in ubuntu... [14:32] hello. I'm trying to help someone who mistakenly sent feedback@launchpad.net a concern about kubuntu. This is what they said: Attention the last packages of kde4 (4.2.4) in [14:32] http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu/pool/main/ [14:32] are generated with qt-library 4.5.1 from [14:32] http://ppa.launchpad.net/kubuntu-ppa/experimental/ubuntu/ [14:32] could be a problem for who don't have experimental repository [14:32] Would you all like me to add this to https://bugs.edge.launchpad.net/~kubuntu-bugs? [14:32] or is there another reply I should send this person? [14:33] gary_poster: tell him we're working on it and it should be fixed shortly [14:33] Riddell: many thanks, will do. [14:34] gary_poster: and to look for the announcement on kubuntu.org when it is fixed [14:34] Riddell: ack, thanks [14:35] Riddell: fyi...arora would not work in gmail for me when trying to attach a file [14:37] brilliant, what do I do now with all the 4.2.3-users who are stuck in the Upgrade process? [14:39] Mamarok: tell them to hold tight, updates coming shortly [14:39] * Mamarok hates it to waste her time on doing damage limitation...*sigh* [14:40] Riddell: got a timeframe? [14:40] couple of hours? [14:40] sorry, is my bad [14:40] * apachelogger is wondering why markey is questioning his package version scheme :P [14:41] did you read me mail? [14:41] ok, will put taht in topic till tomorrow then in #kubuntu :) [14:41] I explained it [14:41] it's pretty confusing for users (and devs) [14:42] "hey, I have 2.0.90, where can I get beta1"? [14:42] because your scheme is all messed up [14:42] "duh, that is beta1" [14:42] 80 should be beta1 [14:42] 90 rc1 [14:42] 70 alpha1 [14:42] the closer you are to 100 the more stable is the thingy [14:43] are things stable enough to try kde 4.3 in whatever beta form it is at now? [14:43] markey: or just go 71, 81, 91 [14:43] that way you are not even off by one [14:49] hrm netsplit === smarter_ is now known as smarter [17:21] JontheEchidna: where are the packages for amarok 2.1 jaunty? [17:21] 17:00 < Riddell> it's in https://edge.launchpad.net/~kubuntu-ppa/+archive/backports [17:21] testing welcome [17:21] Riddell: adding that ppa now ;) [17:22] Riddell: much else in there? [17:23] and updated. Ill let you know if theres any issues [17:39] will there be a backport of qt 4.5.1 to 9.04? [17:44] canen_: there's one in the experimental PPA [17:45] https://edge.launchpad.net/~kubuntu-ppa/+archive/experimental [17:45] Mamarok: 4.2.4 is all built now except kdesdk === mcasadevall is now known as NCommander [17:58] anyone on jaunty able to test 4.2.4? [17:58] * tsimpson is on jaunty [17:59] Riddell: i am on jaunty [18:00] it is pretty much stock [18:00] no ppas added [18:07] jjesse: please add https://edge.launchpad.net/~kubuntu-ppa/+archive/ppa and test [18:07] will do [18:09] thats for 4.2.4 right? [18:11]