[00:00] Right. I meant kdenetwork. [00:00] NCommander: BTW, it's Riddell's key on the upload for kdelibs in Intrepid. [00:00] ScottK, the same patch applies to both, just tweak the changelog [00:00] NCommander: You sure? [00:01] ScottK, yeah, it should apply cleanly [00:01] Didn't apply for me, but maybe I messed up. [00:01] NCommander: is it a problem? [00:01] ScottK-laptop, I can roll the debdiff myself then [00:01] Riddell, no, we just found a better fix for the problem I'm testing building [00:01] Riddell: master dirk made a better fix today in KDE svn [00:01] oh, groovy [00:01] * ScottK-laptop goes afk for a bit. [00:03] Riddell, can you upload a fix for hardy-proposed on powerpc? (its a no-changes binary rebuild to clear a segfault; I've confirmed it works right already) [00:03] NCommander: if you get it to me quick [00:03] NCommander: We don't have binary rebuilds in Ubuntu. Needs a source upload and rebuilt on all archs. [00:04] ScottK, right, I realize that. No changes binary rebuild == changelog only upload [00:04] Riddell, https://bugs.edge.launchpad.net/ubuntu/+source/gnome-python-extras/+bug/181068 [00:05] Launchpad bug 181068 in gnome-python-extras "miro.real crashed with SystemError in MozillaBrowser() on PPC" [Low,Confirmed] [00:05] THe trick is going to be finding someone on ubuntu-sru to ACK that, I don't think any of them run PowerPC [00:06] ScottK-laptop, I'm rolling the backports fix now [00:18] NCommander: uploaded, it'll sit in unapproved which usually gets reviewed by pitti on fridays [00:18] Riddell, thanks, I owe you one :-) [00:24] is anyone here running hardy ... and has a distribution list in kmail/kaddressbook that was added in gutsy (or prior release) [00:43] It is a sin to make KDE look like this: http://launchpadlibrarian.net/10104129/20071020-adept.png [00:45] Exit? Does that close the dialog or close adept manager? [00:45] seele: that's from adept2 [00:45] oh [00:45] I am going through old bug reports [00:46] hmm.. dinner or more cake? [00:57] Someone know the correct alternative of "update-manager -d" for kubuntu? [00:57] hi, btw [01:00] best ask in #kubuntu [01:03] ScottK, ping? [01:04] apachelogger, Riddell or anyone: please have a look at http://revu.ubuntuwire.com/details.py?package=kopete-cryptography for me [01:09] mornfall: is bugs.kde.org working for you yet? [01:10] I have a reproducible way to give a package the description of another package [01:10] in Adept Installer === kde_pepo is now known as kdepepo [01:15] https://bugs.edge.launchpad.net/ubuntu/+source/adept/+bug/268106/comments/6 [01:15] Launchpad bug 268106 in adept "On the Add/Remove Adept, software called "Krita" for Gimp packages" [Low,Triaged] [01:15] ^Reproduction instructions are in the comment, both of those packages should be in Debian [01:18] otherwise see http://bugs.kde.org/show_bug.cgi?id=170835 [01:18] KDE bug 170835 in general "Searching applications gives first result the description of the last expanded package" [Normal,Unconfirmed] [01:27] stdin: get-orig-source not worky [01:27] no? it worked here [01:28] http://paste.ubuntu.com/45565/ [01:28] ahh, poop [01:29] doc/ is gfdl [01:30] oh [01:30] /doc/index.docbook: GNU Free Documentation License version 1.2 [01:30] yeah [01:30] you should note that in the on debian system... as well [01:31] the GFDL license is in common-licenses [01:31] oh, yes it is :p [01:32] I am too tired to give it a full revu [01:32] the changelog entry should mention the FFe and fix the FFe bug [01:33] apachelogger: do you know a good authoritative way of getting the base kde version? I'm using kdelibs5 in the rules but that blows up [01:33] and I really don't want to have to reinvent uscan in Makefile speak [01:34] stdin: tear the original name apart [01:35] of course I have no idea how to do that in make :P [01:35] stdin: alternately you could just take a look at the other extragear apps [01:35] because I think we pretty much don't care if watch is actually useful for downloads :P [01:40] they all keep the -kde4.1.1, the lazy buggers :| [01:41] that is called productivity I guess :P [01:41] * apachelogger goes to bed [01:41] nini [01:42] I'll upload another version tomorrow, sleep sounds too good [02:38] NCommander: Back [02:39] front. [02:39] ;-) [02:40] omg [02:41] https://bugs.edge.launchpad.net/ubuntu/+source/adept [02:41] Adept is completely triaged [02:41] oh, actually a few reports still need to be forwarded upstream, grr === kde_pepo is now known as kdepepo [02:52] hello people [02:52] someone have kubuntu intrepid up? [02:53] hell emgent [02:53] hello emgent [02:53] my touchpad and usb mouse seems dead [02:55] ok found the problem :) [03:00] wb ScottK [03:00] ScottK, I have your backport :-P [03:06] K. [03:06] URL please? [03:06] ScottK, hold on [03:07] ScottK, https://edge.launchpad.net/~sonicmctails/+archive?field.name_filter=kdenetwork&field.status_filter=published [03:07] ScottK, it will probably FTBFS since the PPA doesn't have backports enabled [03:08] Oh wait, scratch that [03:08] * NCommander just posts the debdiff somewhere [03:09] Thanks. I prefer that. [03:09] ScottK-laptop, http://paste.ubuntu.com/45589/ [03:09] I didn't see the need to open a bug since I don't know what it should have for a upload [03:09] Bug wouldn't autoclose in backports anyway. [03:10] ScottK-laptop, oh, thats "wonderful" [03:10] ScottK-laptop, I'm going to attack the Incomplete queue on hardy backports relatively soon (aka, this weekend) [03:10] K. [03:11] I think I need to empty out my PPA [03:12] ScottK-laptop, care to upload the new kdelibs? [03:17] * NCommander can't get a clean debdiff [03:19] ScottK, the clean rules is pretty badly broken on kdelibs-3.5.10, its causing the .diff.gz to be bloated to 720k, and the debdiff to 500k [03:20] ScottK, its all the translations that are getting caught in the debdiff, and I have no idea how to fix this clean rule (and I'm sorta hesitant to even touch it) [03:23] ScottK, do you want me to bother changing the clean rule and possibly break it worse to try and get a clean diff, or not bother? [03:29] * NCommander checks ScottK's pulse === Czessi_ is now known as Czessi [03:31] mornfall: Triaging is also complete. Here is a list of all the bugs in the Ubuntu bugtracker that concern you as upstream: https://bugs.edge.launchpad.net/ubuntu/+source/adept/+bugs?field.searchtext=&orderby=-importance&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.status_upstream=open_upstream&field.status_upstream-empty-marker=1&field.omit_dupes.used=& [03:31] field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&search=Search [03:32] er, that's a long link and konversation broke it [03:32] apachelogger: do want battiny script [03:32] mornfall: http://tinyurl.com/5sw2hd [03:33] NCommander: I'd like the minimal fix that's gonna work. [03:33] ah the joys of fixing backport clean rules [03:34] ScottK, the debdiff still going to be huge however because it needs to decruft the previous upload [03:35] OK. [03:35] Which change are we on now? [03:35] I thought kdelibs was broken in Intrepid? [03:36] ScottK-laptop, thats the one, sorry, misremembered which version I was fixing [03:36] (this is fun :-)) [03:36] jtechidna: that's amazing. good job! [03:36] K [03:36] ScottK-laptop, I just really need to cut the diff down the size, but its going to be a huge debdiff to remove the cruft [03:36] yuriy: to tell you the truth I'm somewhat exhausted [03:37] NCommander: Do we really want to mess with it? If you say yes, I'll believe you. [03:37] ScottK-laptop, your the one who said you wanted a clean diff ;-) [03:38] Did I? [03:38] I thought I said I wanted the minimal fix that would work. [03:38] [22:33] NCommander: I'd like the minimal fix that's gonna work. [03:39] ScottK, Oh, the fix is in there, there is just a lot of cruft in the patch from the bad clean rule (it regenerated the .pos, and all that got caught up in the diff) [03:41] ScottK, https://bugs.edge.launchpad.net/ubuntu/+source/kdelibs/+bug/268817 [03:41] Launchpad bug 268817 in kdelibs "Patch to re-enable inotify on all architectures" [Undecided,New] [03:41] * ScottK-laptop looks [03:42] * NCommander hears Scott's eyes sizzle [03:43] NCommander: At a glance, the changes in messages.po don't look right. [03:45] ScottK, dah, I accidently clobbered the good diff with my work in progress one [03:45] 'doh [03:45] Oh wait [03:45] Er [03:45] No, this is what regenerated [03:45] ScottK, I have no idea its constantly regenerating these [03:48] Wahoo. Diff is less than 20,000 lines. [03:48] * NCommander sighs [03:48] The actual changes are less than 200 lines [03:49] How about you make me a special diff with just those lines and we go from there. [03:49] ScottK, yes sire :-P [03:49] IME applying 8,000 lines of .po file diff rarely ends well. [03:50] ScottK, Riddell didn't even try, he just uploaded from my PPA [03:51] I'll see what I can do [03:51] all my changes are in the debian folder, so I should be able to diff just that [03:51] Sounds good. [03:57] ScottK-laptop, check your PMs, that should be it [04:19] NCommander: Any last regrets before I upload kdenetwork? [04:20] ScottK-laptop, the worst we do is break lpia worse, and considering its an FTBFS fix, can it be any worse? [04:20] OK. [04:21] I'm to dpkg-shlibdeps, so it shouldn't be long. [04:22] * NCommander waves flags [04:22] Of course there are a lot of those ... [04:23] That took longer then the actual build itself ... [04:23] :-) [04:24] ScottK-laptop, do we have any other big KDE todos? [04:24] For KDE3, I think it's mostly a [04:25] ... a|wen finishing some investigations. [04:25] I still need to finish up on kdebindings. [04:25] urr kde4bindings [04:26] ScottK, Sounds like "fun" [04:27] I'd love to hear you figured out php-clamavlib. It's the last holdout on the libclamav5 transition. [04:28] Oh, shoot, I'm sorry, my mind slipped on that one [04:28] ScottK, I'll trade you that for uploads on my ada SRUs [04:28] ScottK-laptop, where do I grab the current source package and build logs? [04:29] NCommander: Just apt-get source php-clamavlib and throw it at your intrepid pbuilder. [04:29] intrepid? [04:29] Yes [04:29] * jtechidna goes to bed [04:30] NCommander: It won't take you long to get to the libtool fun. [04:30] How bad? [04:31] NCommander: http://paste.ubuntu.com/45614/ [04:31] ScottK, any desire for a specific patching system? [04:32] NCommander: I think the current changes are all direct in the diff.gz. I'd just go with that. [04:32] They are? [04:32] ugh [04:32] *twich* [04:32] Given that's the current path, I don't think patching and direct changes should be mixed. [04:33] If you want to go back and redo it all with dpatch, that's cool too. [04:33] No quilt please. [04:38] kdenetwork uploaded for backports. [04:57] kdelibs for Intrepid uploaded. [05:49] Riddell: I uploaded a revised kdenetwork to hardy-backports for NCommander. I pinged slangasek and asked him to accept it, but I'd appreciate it if you'd check and accept it if he didn't already. [05:49] \o/ [05:56] uhm there is a bug in kopete, seems reject some chars on password field.. and faild login with wrong password. [05:56] * emgent investigate.. [07:02] jtechidna: Thanks a lot, I'm off for a few days now, but next week I'll sort through it. The work is really appreciated, ta. [09:36] Riddell: when trying to upgrade using adept I get this: http://paste.ubuntu.com/45680/ [09:36] <\sh> apachelogger: where was the quassel bzr archive again? [09:37] <\sh> apachelogger: got it... [09:48] \o/ [09:48] I can't edit the wiki page [09:48] hooray [09:48] -.- [09:56] hm [09:57] Does anyone have arora installed? [09:57] * apachelogger would be interessted if it works there [10:30] it doesn't [10:43] ScottK-laptop: nothing in hardy-backports queues [10:47] apachelogger: hmm, interesting, it's cycling through the available views and by the time it gets to te KDE4 one it has already loaded the KDE one and the qt versions clash [10:47] I wonder why the KDE 3 one was left in there are all [10:49] Riddell: compatibility with series where python-qt4 is not installed maybe? [10:50] we've used qt4 since edgy [10:53] Riddell: dapper is still supported until 2009, isn't it? [10:53] or is only dapper -> hardy supported as upgrade path? [10:55] right, it's LTS to LTS only [10:56] ok [11:11] apachelogger: do you have the /var/log/dist-upgrade/main.log still? [11:12] Riddell: I am doing an upgrade using update-manager right now. I can get you the file in about 17 minutes. [11:14] Riddell: I got an accept shortly after I went to bed, so I guess he got it. [11:15] apachelogger: using the gtk tool? [11:16] Riddell: yes, that's the cool thing about VMs, you can easily get rid of that stuff again ;-) [13:04] hm, can/should you ignore the ignore file in bzr like you would with cvs/svn? [13:05] or is that ignored by default [13:06] bzr ingore ingore [13:06] but without the typos [13:08] Riddell: not `bzr ignore .bzrignore`? [13:11] because when i do that, it says: [13:11] Warning: the following files are version controlled and match your ignore pattern: [13:11] .bzrignore [13:11] but .bzrignore still shows up in `bzr st` [13:11] which is very unlike cvs/svn [13:13] dunno, I've not used it, you probably want to bzr add .bzrignore actually [13:39] goatsocks: the ignore stuff is an evil hack [13:39] Riddell: I invoked the DistUpgrade manually and it crashed :S [13:39] ok bzr has two kinds of ignore lists... the kind handled by `bzr ignore` and thus stored in .bzrignore within the branch are ignores you want versioned and shared with other branches... then there's the local ignore which you can specify in ~/.bazaar/ignore for a list of ignores you don't want versioned [13:40] the latter ignore file has to be hand edited [13:40] the latter is really only for global ignores [13:40] like backup files [13:40] apachelogger: backtrace? log? [13:40] apachelogger: exactly, that's the kind of ignores i'm after [13:41] apachelogger: like IDE generated crap [13:41] goatsocks: you should store them in .bzrignore if you plan on sharing the branch though [13:41] Riddell: http://paste.ubuntu.com/45769/ [13:42] Riddell: terminal seems to be broken actually [13:42] yay, cake for breakfast [13:43] apachelogger: afaict the files specified in ~/.bazaar/ignore aren't versioned hence won't be shared when sharing a branch... ? [13:43] seele: please don't say "zucchini" [13:43] goatsocks: exactly that is why you should put that stuff in .bzrignore [13:44] goatsocks: someone's got to eat it [13:44] apachelogger: but the whole problem is i don't want to share the .bzrignore file also [13:44] or get the ignores in the bzr internal ignore list on long erm [13:44] goatsocks: well, then just throw the stuff in .bazaar [13:44] seele: there is still zucchini pie left? Oo [13:45] apachelogger: i'm the only one eating it! [13:45] apachelogger: the terminal doesn't exist until the packages are all downloaded and installing [13:45] apachelogger: i think you're right though, bzr ignore handling is nasty, probably why there's a spec for overhauling it entirely [13:45] apachelogger: (to be fair, i'm home alone this week) [13:45] seele: hm, you could send some over.... ;-) [13:45] Riddell: ok [13:45] apachelogger: come visit me an i'll make you a cake! [13:46] worth a thought [13:46] maybe post-intrepid [13:47] apachelogger: where had the install got to? [13:47] Riddell: getting new packages I think [13:48] * apachelogger checks [13:49] headerHidden : bool "This property was introduced in Qt 4.4." [13:49] apachelogger: what version of python-qt4 do you have? [13:49] 4.3.3-2ubuntu4.1 [13:50] that would explain it then [13:51] apachelogger: able to try this patch? http://paste.ubuntu.com/45781/ [13:52] *trying* [13:54] Riddell: doesn't crash anymore \o/ [13:54] Riddell: I think the terminal button should be hidden unless there is something to show [13:59] apachelogger: are you upgrading or can you test a patch for that too? [13:59] * apachelogger kills the upgrade [13:59] Riddell: now I can test a patch :) [13:59] Riddell: is update-manager-kde invoked through Adept 3.0 for intrepid+1 upgrades? [14:00] apachelogger: http://paste.ubuntu.com/45784/ [14:00] jtechidna: no, through update-notifier-kde instead [14:01] Riddell: so I guess my question is, what displays the release announcement this time around? [14:03] jtechidna: update-notifier-kde will [14:03] k [14:03] thanks [14:03] Riddell: are the dependencies for update-notifier-kde fixed yet? [14:04] apachelogger: yes, in update-manager 1:0.93.10 [14:08] neato [14:08] uh, 77 updates -.- [14:08] heh so if you don't wanna bother branchers with your .bzrignore file, `echo .bzrignore > ~/.bazaar/ignore`, then do `bzr ignore foo` inside your working copy to add ignores and create .bzrignore there, then do `bzr remove --keep .bzrignore` (because `bzr ignore` automatically `bzr add`s .bzrignore!) [14:08] hm [14:09] er sorry that should be echo .bzrignore >> ~/.bazaar/ignore [14:09] ;) [14:10] seele: http://aplg.kollide.net/images/snapshot104.png what do you think about that dialog? [14:11] apachelogger: many users won't know what the "apt-file cache" is [14:11] yes [14:11] even more will not know what to click :P [14:12] I am a dev dood and have no idea what "run this action" and what "next" is going to do [14:12] Oo [14:12] it's also not very sure whether you need an internet connection to carry out the task ;) [14:13] well honestly, most users aren't going to install apt-file. But that dialog is confusing [14:13] http://aplg.kollide.net/images/snapshot105.png [14:13] I chose next [14:13] and now I am seriously confused [14:13] apachelogger: are you fixing this or are you just looking for validation? [14:13] oh [14:13] wtf, totally defeats the purpose of using a GUI updater tool [14:14] apachelogger: next probably meant, see next notification [14:14] seele: I am looking for validation [14:14] apachelogger: yes, it sucks. [14:14] i can't get past the first screen, do i click run or next? [14:14] it doesnt even use the same language [14:14] well, now that we see this is a notification browser [14:14] it says "run this command" in the message but "run this action" in the button [14:15] would run also go to next screen? [14:15] Riddell: go fix that notification thing :P [14:17] * goatsocks can now get some real work done until the next bzr wtf moment [14:18] mornfall: so, why is the sidebar widget not following the mainwindow color gradient in oxygen? [14:18] apachelogger: was 104 the first image in the wizard? [14:19] seele: the first was a popup in systray, telling me there are notifications, which left behind a light bulb, clicking on that lead to 104 [14:20] then I clicked next, which lead to 105 [14:22] what is it supposed to do? run apt-get update? [14:22] no, I think it is the thing that shows up to tell you to reboot your system [14:22] or restart firefox [14:22] ... [14:22] what? [14:23] 'post-update' notification [14:23] huh, that got lost on me. so it would show up after a kernel update and tell you to reboot? [14:23] yes [14:23] or is this the cryptic message you get everytime? [14:24] seele: http://kubuntu.org/~jriddell/update-notifier-hooks.png [14:26] ah ok.. so it's just that one that is confusing [14:26] well, I guess everytime you get more than one notification it's like that [14:27] maybe it should be ignore? [14:27] jtechidna: what should be ignored? [14:27] You could have a run action button and an ignore button, which would show the next notification, maybe? [14:27] makes loads of sense [14:28] Because, actually the light blub disappears after it walked you through the notification [14:28] At least I wouldn't expect it do that. [14:30] grr, update-notifier keeps popping up it's bubble telling me to restart [14:31] at least it's not annoying as windows where a whole freaking window comes up and steals focus [14:31] I think adept updater crashed ;| [14:31] * jtechidna reboots [14:52] seaLne: I installed the kde-devel meta package and used the dist-upgrade tool -> no problems [14:54] Riddell, or Riddelll_: terminal patch works [14:55] thanks apachelogger [14:55] Riddelll_: once oxygen-icons is installed it switches from crystal to oxygen for new current icons, looks odd IMO [14:56] hm, s/new current icons/new icon changes/g [14:56] interesting [14:56] I'll add that to a things to fix if I have spare time list [14:56] ok [14:58] Riddell: ok so I guess if there are ideas missing people should just make new ones? [15:04] uhh [15:04] that upgrade is somewhat ... weird [15:04] jcastro: according to the meeting, brainstorm isn't a requirement [15:05] ah ok [15:05] (whew) [15:05] although it might be an idea to ensure jono knows that [15:12] Riddelll_: when i talked to jono about it he said just create new ideas [15:12] seele: new kubuntu related ideas on brainstorm/ [15:13] but personally, i think that defeats the purpose of them using brainstorm in the first place. it is supposed to be a community collection of ideas. the system breaks down if people submit arbitrary ideas that the user community wont understand enough to vote on [15:13] * seele has issues with brainstorm [15:13] really, a usability category? now we're asking users to self-diagnose? [15:14] yes we are :) [15:14] why don't they tell us how to design the UI while theyre at it [15:14] my problem with brainstorm is the gnome bias [15:14] +1 JontheEchidna [15:14] * jjesse spent some time trying to find kubuntu and server brainstorm ideas for his uds application and couldn't find any [15:14] jjesse: there is a kubuntu tag [15:15] JontheEchidna: must have missed it i was using the search [15:15] tried kde and kubuntu [15:16] This idea needs to be closed: http://brainstorm.ubuntu.com/idea/11546/ [15:16] jjesse: all KDE brainstorms: http://brainstorm.ubuntu.com/search?keywords=&ordering=mostvotes&relation=99&state_new=1&state_needinfos=1&state_blueprint_approved=1&state_workinprogress=1&state_done=1&state_already_done=1&state_unapplicable=1¬hing_attached=1&bug_attached=1&spec_attached=1&thread_attached=1&attachment_operator=0&tags_operator=and&tags=&category=-1&type_idea=1&_search_submitted=true&state_deleted=0&state_not_an_ [15:16] idea=0&type_bug=0 [15:16] wow twhat a link [15:17] you couldnt' tinyurl it? :P [15:17] lol [15:17] hm [15:17] This idea needs closed too: http://brainstorm.ubuntu.com/idea/12292/ [15:17] JontheEchidna: you need a paste protection, not battiny :P [15:18] JontheEchidna: i can close them if you want me to [15:18] whith what text? [15:18] *with [15:18] uh, for the first one [15:18] Nightrose: not wortht the time [15:18] http://brainstorm.ubuntu.com/idea/11054/ katapult is no longer used [15:19] JontheEchidna: you shouldn't care about them [15:19] KDE 4.1 in Hardy has already been done [15:19] the point of rating is that pointless stuff doesn't get to the top :P [15:19] jjesse: my just upgraded vm tells a different story [15:19] and we can't doing anything about Qt's licensing, since Nokia controls that. And the current dual licensing method is Qt's whole business model [15:19] apachelogger: really katapult is still used? [15:19] * Nightrose closes them [15:20] jjesse: it certainly works [15:20] interesting [15:21] jjesse: all kubuntu-tagged ones: http://brainstorm.ubuntu.com/search?tags=kubuntu&ordering=mostvotes [15:22] has anyone gone through the registration process? [15:22] Riddell: it appears to me that all the recommends of kubuntu-desktop don't get upgraded in dist-upgrade [15:22] is there a free text area besides "about yourself" where you can talk about what you want to work on? [15:23] yes [15:23] Riddell: and adept gets removed completely which leaves the resulting intrepid without GUI package manager [15:23] * seele would rather send an email to a person that matters than fill this form out [15:23] hmmm strange [15:23] but limited to 1000 characaters [15:23] oh great [15:23] i can't edit any of the ideas you posted [15:23] +1 seele [15:23] but i can edit others [15:23] Nightrose: actually I think the first one wants KDE 4.1 moved to hardy-backports [15:24] which hasn't been done yet, so don't close it [15:24] can't [15:24] JontheEchidna: yea - i can't anyway - dunno why - i am a moderator [15:24] it's really against backports policy [15:24] could break too much [15:26] stdin: is there some lp dood I can poke about the kubuntu-bugs name? [15:30] seele: are you werking on the application right now? [15:37] jjesse: no i gave up [15:38] lol [15:38] you get a tiny box to talk about everything you do for ubuntu? [15:38] apparently that's all you need [15:38] seriously, i want an email address and i'll write up a nice letter with links to projects etc. [15:38] +1 [15:38] but i think the brainstorm links are supposed to help automate the scheduling of the disscussions [15:40] hum, i dont even know if my boss would let me go [15:41] this is a problem [15:41] i need a new job [15:41] (if i wasnt so lazy i'd just work for myself) [15:42] hmm, well I filled in the second page of the application and got sent back to the start [15:42] did it have an error message: "Too many KDE related Brainstorm topics. Please try again."? [15:42] naw, I was trying to fill in a non brainstorm URL [15:43] lol seele [15:43] i hate doing documentation for customer engagements they are so boring [15:43] it would be good if a group could fix Samba and then another group could design a UI for Samba [15:44] then we just need someone to implement it in QT and GTK [15:44] and everyone get's a new more usable samba [15:44] seele: Qt, not QT :P [15:45] apachelogger: shiftkey lag :P [15:45] isnt it Gtk also? [15:45] no [15:45] GTK+ [15:45] ah geez [15:45] the Printer config UI could use some love too [15:45] and system settings reorganized [15:46] and a new user management tool [15:46] user management is in development I think [15:46] that reminds me [15:46] <.< [15:46] we need to kill kuser [15:46] apachelogger: who is working on it? [15:46] * JontheEchidna hides [15:46] oh yeah? hehe [15:46] obvious I guess [15:46] JontheEchidna: have you seen the Redhat UI proposal? [15:47] seele: nope, just sorta trying to scrape together a working UI [15:47] IMHO we should just give kuser a make over [15:47] most useful for everyone [15:48] apachelogger: that means c++ [15:50] Riddell: if I knew c++ better than I do, I probably would prefer it over python :P [15:50] * apachelogger thinks we need a c++ workshop for next developer week [15:51] you really can't learn c++ in an hour [15:51] it takes an hour to set up the build environment [15:51] probably true [15:53] Riddell: btw, I setup a torrent tracker on kollide for the 4.1.1 CD, I guess we wouldn't be allowed to use ubuntu's tracker either [15:54] apachelogger: no I guess not [15:56] everybody hug rgreening! [15:56] * jjesse hugs rgreening [15:57] why? [15:57] hi all. looking to help out with developing KDE4 for Kubuntu. Anyone willing to be a mentor? Specifically, I'd like to start with Knetworkmanager or other similar scale app [15:57] lol [15:57] * rgreening hugs everyone back [15:57] rgreening: knetworkmanager is notoriously hard to work on [15:57] yes, knetworkmanager please [15:57] big arms [15:57] rgreening: and needs developers just for that reason [15:57] good. I'm willing to help [15:58] rgreening: it's currently broken because network-manager changed its DBus API and knetworkmanager hasn't caught up [15:58] I'm not exoerienced with deb packaging, so I'll need some tips there. However, I am proficient in C++, etc. [15:58] There is a work on a network manager plasmoid, I know [15:59] or rather, an infantile network manager plasmoid exists [15:59] ok. is there a dev currently working on Knetworkmanager [15:59] rgreening: so far knetworkmanager is essentially a suse project used by the whole of KDE, they're the only ones elite enough to know how to work on it [15:59] rgreening: haschaa is the guy, but he's on a break for the next few weeks for his thesis [15:59] rgreening: it's here http://websvn.kde.org/branches/work/knetworkmanager/ [16:00] ok. I'l make a note. Do you have an e-mail addy for him? [16:00] wow sounds like knetworkmanager is a crazy project then [16:00] rgreening: fyi, this is pretty much the state of networkmanager stuff in KDE land: http://lists.kde.org/?l=kde-devel&m=122004639403690&w=2 [16:00] yes. but it is of crucial importance [16:01] the plasmoid is the future imo [16:01] but knetworkmanager is just a few inches from "it works" [16:01] for now [16:01] rgreening: it'll be in http://websvn.kde.org/trunk/kde-common/accounts?view=log [16:02] I'll download the source and start reviewing. Does anyone have a link to the API changes that occurred? [16:03] rgreening: asac would know, he's the ubuntu network-manager dude [16:03] rgreening: you need to build --with-openvpn=no currently [16:03] ok [16:04] rgreening: the relevant bug regarding the API breakage is bug 259278 [16:04] Launchpad bug 259278 in knetworkmanager "knetworkmanager will no longer connect" [High,Confirmed] https://launchpad.net/bugs/259278 [16:04] thanks. good place to start [16:05] rgreening: specifically look for the comments about asac (alexander sack) bumping nm 0.7 without testing knetworkmanager ;) [16:05] hehe [16:06] ubuntu ain't has no QA [16:06] you know that if gnome network manager was the one that broke due to the bump they'd moan for a reversion [16:07] :P [16:07] lol [16:07] yep, which is why i'm using nm-applet atm, crapping up my otherwise nice kde4 systray [16:07] I was pretty miffed myself when it broke. I am currently using nm-applet to connect. [16:07] ditto ^^ [16:07] hm [16:07] <-- using tha prompt [16:08] the api change doesn't seem to break wired connections so I'm fine [16:08] on a side note, anyone else seeing transparency issues in the KDE systray [16:08] actually we should just break nm-applet :P [16:08] rgreening: yeah, known by KDE, should be fixed in KDE 4.2 with new systray [16:08] mine are all black background rather thna transparent. [16:08] enforcing a quick solution [16:08] rgreening: yeah that's a known issue, upstream is considering rewriting systray from scratch [16:08] ok [16:08] JontheEchidna: is that new tray already written? [16:08] just wondering if it was specific to my Intel card of a general issue [16:08] apachelogger: pretty much [16:09] JontheEchidna: pretty much means? [16:09] meaning, it hasn't replaced the current systray yet [16:09] but soon [16:09] soon might be too late for us :P [16:09] well, it is still totally 4.2 material [16:09] I'm slowly getting to like KDE4 [16:10] :) [16:10] JontheEchidna: suse backported loads of 4.1 to 4.0 [16:11] rgreening: btw, you don't have to worry about packaging, we have plenty of people who are willing to care about that ;-) [16:12] good. [16:12] :) [16:12] I come from the Gentoo world. ebuild was my friend. I just haven't gotten around to deb packaging yet [16:13] rgreening: ditto again [16:13] i'm still kinda stuck in the "if i can't compile it myself, it's crap" mentality ;) [16:14] debs sometimes are picky about the environment they're built in [16:14] well quite often actually ;) [16:14] lol [16:14] only if the environment is broken :P [16:15] apachelogger: idealist! [16:15] seriously, I never had problems due to the environment [16:15] all praise the might pbuilder! [16:15] pbuilder is nothing without hooks [16:16] exactly what pbuilder was designed to addressed... if nobody ever had build environment borkage, there'd be no need for the likes of pbuilder ;) [16:16] s/addressed/address/ [16:22] ok, fetching knetworkmanager sources now. setting build environment. any catches I should worry about? [16:25] rgreening: i've built knetworkmanager from the source deb without issue, it should be ok [16:25] what -dev libraries do I need? Says missing X libraries... [16:27] I guess I need KDE libs dev as well... any quick link to a list of what I need at a min? [16:27] try debuild, it should tell you what you need [16:27] debuild -i -us -uc -b [16:28] rgreening: apt-get build-dep knetworkmanager should get what you need [16:28] k. cool [16:29] thanks. dl now. [16:32] that seems to be working better now [16:38] successfully built knetworkmanager from svn. now need to research the API changes to D-BUS. Maybe I can find the changes in nm-applet... [16:41] ridell: you see this report on usability for Knetworkmanager... http://weblog.obso1337.org/2008/expert-review-of-knetworkmanager-07/ [16:41] I like a lot of the ideas here. [16:43] rgreening: meet seele, beloved usability guru [16:43] seele: meet rgreening our new knetworkmanager dood [16:46] hey seele [16:46] * seele waves [16:46] lol [16:46] is he coordinating with the suse peeps? [16:47] I'm actually just starting to help here... but if someone wants to point me in the right direction, I can certainly work with the SuSE folks [16:48] My goal is to work on Knetworkmanager here. Any patches should be apssed up along. [16:48] s/ap/pa/ [16:49] Given that Worelles was so important to Intrepid, Knetworkmanager needs a LOT of love [16:49] s/Worelles/Wireless/ [16:49] gee, kant spel today [16:54] Here's a question, should we opt to release nm-applet with Kubuntu if it isn't ready in time for Intrepid, given the current state of Knetworkmanager? [16:54] we should revert back to a workable network-manager [16:54] it being Knetworkmanager of course [16:56] hmm... so, opting for nm 0.6 instead of 0.7? Knetworkmanager is not real useful (the KDE4 version) as compared to the KDE 3 version, IMHO, at least not without some usability tweaks. [16:57] I'll do what I can over the next few days to see if I can figure out the current issues with the API. [17:01] the fallback should be nm-applet imo [17:01] impossible [17:01] i think that's what fedora is doing [17:01] nm-applet pulls too many stuff in [17:01] it wouldn't fit on the CD [17:02] it fits on the fedora livecd somehow ;) [17:02] we are really not going to drop anything [17:03] *shrug* i think users are just concerned with having something that actually works [17:03] yup [17:03] nm-applet is the most mature frontend [17:03] reverting to a workable network-manager works pretty much :P [17:03] I agree. If nm-applet + deps fit, then it should be the default if knetworkmanager is not suitable. [17:04] as reverting D-BUS and NM may be more problematic in the long run... [17:05] rgreening: why would it be more problematic in the long run? [17:05] other deps, future upgrades could require newer D-BUS... I'm just thinking out loud. Maybe Im wrong [17:06] It may all be a moot point if I can figure out where its broke and fix it :) [17:06] knetworkmanager gotta switch to solid at some point [17:06] and I think solid is pretty solid base to rely on :P [17:06] hmmm... [17:09] apachelogger: i think the plasmoid will make knetworkmanager obsolete, as it already uses solid [17:09] the plasmoid is not very much of any use jr said [17:09] * apachelogger is doing yoda word order again [17:10] well it doesn't work right now because the main dev has been away [17:31] How is todays daily, anyone? installable? [17:43] yay, digikam compiled (on amd64) [17:43] Riddell, ah, the fun of FTBFS fixing. [17:45] what does FTBFS mean again? [17:46] Failed To Build From Source [17:46] thankss [17:46] * NCommander always used Failure vs Failed [17:46] Riddell, know any good FTBFS to kill? [17:47] * JontheEchidna uses Fails and Failed interchangably [17:48] * NCommander has dreamed of solved FTBFS in his sleep [17:48] wow someone needs to have better dreams [17:48] Porting (K)ubuntu ;-) [17:48] Brings new meaning libtool nightmares [17:53] * apachelogger had some FTBFS [17:53] ah righto [17:53] NCommander: kdenlive doesn't build in intrepid [17:54] apachelogger, link to build log [17:54] NCommander: http://paste.ubuntu.com/45852/ [17:54] line 1796 [17:55] 1706 even [17:56] yay pretty [17:56] apachelogger, why are you packaging an SVN snapshot? [17:57] No clue why we did [17:57] probably was debian anyway :P [17:57] try packaging a new kdenlive? [17:57] NCommander: svn is KDE 4 [17:58] wait, what? [17:59] hm [17:59] maybe not [17:59] KDE 4 version is in a branch [17:59] http://kdenlive.svn.sourceforge.net/viewvc/kdenlive/trunk/kdenlive/ [17:59] trunk doesn't look very promising though :P [18:00] Riddell: is kdeglobals somehow protected from kconf_update? [18:00] apachelogger, it was updated within the last four months [18:00] NCommander: well, give it a try [18:00] apachelogger: I don't know, why? [18:00] apachelogger, you want me to package this? (I rather package a new snapshot vs. fix an old one) [18:01] Riddell: I am trying to kick the Icons group out, so that we ensure KDE 3 -> KDE 4 ends up with Oxygen [18:01] NCommander: yeah, I wouldn't really want to update kdenlive, that is an evil package ;-) [18:02] apachelogger, why? [18:02] what is kdenlive? [18:02] movie editor thing [18:02] which encludes half the floss world in it's source tarballs [18:02] *includes [18:03] * NCommander screams [18:04] doesn't seem the additional sources are there [18:04] hm [18:04] maybe they stripped them [18:05] Riddell: either there is some kind of protection or my kdeglobals is incompatible with kconf_update [18:05] I can drain stuff from any other config, just not kdeglobals [18:07] apachelogger: kdeglobals had problems in the kubuntu-default-settings profile, that's why it moved to /etc/kde4 [18:07] so it's a bit wonky [18:07] uhhh [18:07] that would explain it [18:08] Riddell: due to the text/icon position? [18:16] apachelogger, you think its worth packaging a new SVN snapshot? [18:17] well, currently it doesn't have a menu entry in anything but KDE [18:18] ew [18:30] Riddell: It looks like we are getting very close to the point where guidance-backends can go away. Is there anything we still need from kde-guidance or can I kill all of it at the same time? [18:34] guidance-power is still more useful than the plasmoid thingy imo [18:34] goatsocks: The KDE4 guidance-power-manager is in a different package now. That'll stay. [18:35] It's more (IIRC) mountconfig, serviceconfig, wineconfig, and such that I'm wondering about. [18:35] ah [18:36] what's the preferred mount util? [18:37] That's part of my question. I haven't been keeping track. [18:37] Maybe apachelogger knows? [18:39] We don't have a preferred one right now. [18:39] I suggest going wiht mountmanager though. [18:39] i'd like to know of a decent qt service config tool also [18:39] service? [18:39] * apachelogger notes to discuss mountmanager today [18:40] apachelogger: init services [18:40] there ain't such a thing [18:41] apachelogger: I think in the next week I'll be able to make guidance-displayconfig and guidance-backends go away. It'd be good to know what else in that package is obsolete and can die at the same time. [18:41] there's no qt equivalent to bum? [18:41] goatsocks: no [18:41] bummer [18:41] ScottK-laptop: I'll start an investigation [18:41] apachelogger: Thanks. [18:42] I would still like to keep guidance-displayconfig around [18:42] hm, "bummer" would make a great name for a qt port [18:42] as of now it's the only way to configure what type of monitor you have [18:42] unless X is supposed to detect such things automatically? [18:43] JontheEchidna: No. It needs to die. Increasingly the odds of it breaking your X are higher and higher. [18:43] JontheEchidna: It is. [18:43] It needs either a total rewrite or death. [18:43] death it is, then [18:47] ScottK, what must die? [18:51] mcasadevall: guidance-displayconfig [18:51] is that related to gtk-displayconfig [18:51] displayconfig-gtk uses the same backend, yes [18:51] mcasadevall: They both use guidance-backends. [18:52] mcasadevall: If you want to make your eyes bleed, grab the kde-guidance source package and look at the huge stack of hacks and patches I piled on it during Hardy to throw it over the finish line. [18:52] ok ... [18:52] Kubuntu can to devotion my someone? I live in Poland. [18:53] evening all [18:53] BartisKing: We can always use more help. [18:53] ACK IT BURNS! === mcasadevall is now known as NCommander [18:54] so what's wrong with guidance-displayconfig? [18:55] NCommander: It works great on X about 3 major versions ago. [18:55] NCommander: It totally doesn't grok xorg.conf'less configurations and still uses Xinerama, not Xrandr. [18:56] Wait, it parses xorg.conf's config file? [18:56] Yes. [18:56] * NCommander begins to twitch [18:56] * NCommander has looked at the code that parses the xorg.conf config file in xorg [18:56] My first great hack was to catch the case where it would crash if xorg.conf was missing and then invent one that was sort of right. [18:56] I'll just say it burns [18:56] wow sounds like fun [18:57] Yeah. [18:57] Xorg itself is an incredible bundle of crappy code [18:57] Or at least it was at the time of the Xfree86 -> XOrg fork [18:57] About the only good thing I can say for that cdodebase is it amazingly portable [18:57] The only good news was basically all the changes I was making were after it would have already crashed without my hacking, so the odds of me making it worse were low. [18:57] * NCommander grabs xorg's source code [18:58] ScottK, how hard do you think it would be to write a proper parser? [18:58] NCommander: tseliot apparently has done one in the x-kit package. [18:58] There are several apps that need the function. [18:58] So then *-displayconfig needs a rewrite, doesn't it? [18:59] NCommander: No, it needs to die. We have a KDE4 supplied alternative. [18:59] Gnome already got an alternative in Hardy. [18:59] so whats stopping it from dying (at least in Kubuntu) [18:59] ScottK, the GNOME alternative is a joke. [19:00] NCommander: It's what they're going with. [19:00] ScottK, I still had to use gtk-displayconfig and some manual file hacking to get things working on my old laptop [19:00] The GNOME alternative trusts that the video card doesn't lie about things like its max resolution or the monitors max resolution [19:00] NCommander: There isn't a lot of point in removing the KDE one as long as the GTK one lives. [19:01] I think you can guess my next question [19:01] Well bryce says he's about ready to kill off displayconfig-gtk. [19:02] so the problem solved itself [19:02] yay [19:02] NCommander: I think any effort you might want to put into re-writing the Guidance display stuff is better expended making the KDE4/Gnome tools better. [19:02] Yeah. [19:03] Now if we could only do that with libtool ;-) [19:03] FFe pending for moving Jockey off of guidance-backends is the last major roadblock. [19:04] very good [19:04] * NCommander looks at network manager's source === Githzerai is now known as Githzerai|NotHer [19:29] Riddell: Knetworkmanager is a fugly beast I must say. [19:33] Argh, blatant KDE unfriendliness: https://help.ubuntu.com/community/DebuggingXAutoconfiguration [19:33] "# Log out from GNOME, if you are logged in " [19:34] :( [19:35] * Arby is just returning to get back into kubuntu work after a bit of an absence [19:35] what have we got in the packaging/testing type area that needs work? [19:37] Arby: hardy to intrepid upgrade needs testing lots [19:38] Riddell: ok I can do that [19:38] * Arby builds a VM [19:38] Arby: also see celeste's blog for testing toolbars [19:38] ok [20:41] Riddell: it looks like Okular's default size got changed since I first tested the defaults, it needs to be +10px [20:41] it's enough to cut off the last button [20:43] seele: just the person [20:43] I was looking at your post on testing [20:44] yes? [20:44] seele: do you only want tests on intrepid or is testing on hardy still useful [20:44] ? [20:44] Arby: it should work in hardy if you adjust the system settings option [20:45] it will be interesting to see how many people have changed the the default size on their apps and if they are bigger or smaller [20:45] seele: it does work, I just didn't want to flood the bug report with useless information. [20:45] smaller default sizes might be a problem [20:45] Arby: no its, ok. if you tested it and the apps are ok, post a comment [20:46] seele: so you want comments for things that look fine as well as things that don't, correct? [20:46] it's an arbitrary QA bug, i did the same for kgrubeditor :) [20:46] Arby: yep [20:46] ok [20:46] * seele makes a note to clarify that for next time [20:46] seele: I did notice one interesting point [20:47] most of the apps in the 'Internet' section of the menu don't have text at all [20:47] yeah, i noticed that for konqueror but the other ones seem ok [20:47] but then other people say most of them are configured icons only [20:47] could be I don't know [20:48] I can make a complete list if that would be useful [20:48] Riddell: where is the default kde config stored? [20:48] Arby: yes it would be so i know what to check [20:48] * Arby sets to work [20:51] seele: most of it is hardcoded into the code [20:52] hum.. then i guess i ping pinotree [20:53] seele: something like default app size is often hidden away inside multiple widgets and their sizeHint === Githzerai|NotHer is now known as Githzerai [21:03] Riddell: pino says he hasnt changed it so i dont know what happened [21:03] * seele just needs 10 pixels! [21:06] as I say the width Qt choses is based on lots of factors from the widgets within the app [21:07] seele: if there's a fixed width that's needed it's not hard to set that [21:10] Riddell: hmm.. does that mean we can set optimal default sizes for all the apps and not some of the haphazard ones we have now? [21:10] The default system monitor size is stupid [21:10] Riddell, Qt widgets changed a lot from release to release [21:10] well, qt 3 -> 4 [21:11] seele: I guess so, there's various ways we could do it [21:11] Riddell: what's the best way, and what's the easiest way I could do it and send you diffs? [21:12] seele: not sure just now, I'll have to think about it [21:17] seele: if you look in your ~/.kde/share/config/okularrc there's a [MainWindow] [21:17] section [21:17] seele: presumably we need to set the height and width [21:17] I'm not too sure what the State one contains [21:18] it looks like it might need set for every resolution though which is nasty [21:20] Riddell: so we ship an rc for all the apps and they aren't autogenerated by the app? [21:20] seele: we ship an rc for any apps where we want to change default settings [21:20] that's the way i know how to change app defaults, i didnt know if there was a better way [21:20] ok, then it becomes easy [21:21] what is the rationale behind move-to and copy-to not being enabled by default in dolphin? i think it is one of the most usefull features [21:24] seaLne: where's that? [21:25] right click on a file [21:25] settings>general context [21:25] ah, I see it [21:26] hmm, I don't find that sort of menu navigation useful myself [21:26] but as with all these things feel free to presuade us [21:26] means you don't have to faff about cuting/copying files then navigating to the new place [21:27] much better than the similar send-to in windows as it isn't restricted to where [21:28] its not the sort of thing either that i think could confuse noobs as it seems to me anyway pretty intuative [21:30] oof... mountmanager is one of the nastiest UIs i've seen in a while [21:31] especially the "history" of locations in it makes it very simple to move files from say for instance a folder that a certain downloading program places them, into categorised folders [21:39] seaLne: bring it up at the meeting this evening if you'll still be awake [21:40] what time is the mtg tonight? [21:40] 7 EDT [21:43] bummer at dinenr w/ a client tonight [21:44] Riddell: sorry i'll be in bed at midnight, its not a big deal [21:51] seaLne: if you remind me i will bring it up [21:52] i find it useful as well [21:56] Riddell: first attempt at hardy -> intrepid upgrade test fails http://paste.ubuntu.com/45930 [21:56] can't launch the update-manager [21:57] this is a clean hardy install with kde4 fully up to date [21:57] default packages only [21:58] how do you want to track this, is it worth bug report? [22:48] The package for KDE4 digikam in intrepid is very very very old [22:49] so it would be good for it to be updated, if someone has time. sorry if this is the wrong channel, but it seemed logical. [22:50] hdevalence: mm, right [23:22] been mucking around with K-N-M0.7... and using D-Bus monitor to see what's happening. Not much luck so far. The code is undocumented... I hate that. lol [23:23] rgreening: yeah, it's pretty hard to get into I'm sure [23:24] For me, I doc the pseudo code and work top down. Beed doing that for 20 years. I can't stand no doc in the code [23:25] anyway... still gonna hack at knm... not giving up yet :) [23:25] maybe the dev will show up by the time I figure out the problem(s) .. lol [23:26] there are people saying the code is the only doc needed. however, this implies that code is written in an understandable way :D [23:26] whats the process to update digikam-kde4, can I help with this? [23:26] I am a noob, but seems not to bee so complicated [23:27] -e [23:27] neversfelde: I actually have it compiling away here now [23:27] neversfelde: but if you fancy looking into liblensfun that would be good, digikam says it would like to use it [23:27] but we don't have it packaged [23:27] Riddell: will try it [23:29] blizzz: even if a function appears to be self documenting, it should still be documented. Afterall, its possible what you coded is not actually what you intended. Documenting will help clear that up ahead of time if you are dilligent about it (IMO) [23:30] the trouble with knm is it's build on the equally undocumented nm [23:31] rgreening: honestly, while coding i seldom have lust to document it, eventually it is a less as possible (perhaps sometimes even less). sure it is a help, but you should name your functions and variable in a way that it is clear what they do. [23:32] on the other side [23:32] Qt e.g. is very well documented what i fully appreciate [23:32] I totally disagree. If coding for yourself...fine. But for a global community, it's rather unfriendly [23:32] :) [23:33] rgreening: yepp. probably it depends on the audience [23:33] i think the least a dev should do is give a technical overview of the whole system... the details can be left to the code itself [23:34] for sure.. though, even if I program for just me, I document as what may seem obvious to me today, might not in 5 years. [23:34] or probably 5 months [23:34] sure as well, know that problem :D [23:35] :) [23:35] it's like my handwriting^^ [23:35] * goatsocks finds stuff he forgot he coded [23:35] lol [23:35] once i even thought "what ass wrote this?" [23:35] bwhahahaha [23:36] *gg* [23:36] oh welll.. muh get back to reviewing this spaghetti [23:40] had another nice networkmanager adventure earlier when i pulled today's update of nm 0.7 [23:41] it wouldn't recognize the entry for my default ap anymore [23:41] had to remove the profile and re-add it [23:41] smells like another api change [23:42] on the bright side, it seems to connect a little faster [23:43] oh good timing on the meeting. just as I finished algebra and thought aah free for the weekend [23:45] Riddell: I think we should do the jackalope discussion last [23:47] * JontheEchidna tries to think of discussion points [23:47] apachelogger: why's that? [23:47] because it could be held indefinitely? [23:48] Riddell: because I think right now everything that is even partly intrepidish is more important than jackalope [23:48] so I finally googled liblensfun :) [23:49] vorian: ping [23:49] apachelogger: there's nothing else on the agenda [23:49] Riddell: yeah, because I can't edit it :P [23:50] yeah, it says immutable page [23:50] we need to discuss some sensible way to triage all bugs related to default applications [23:50] apachelogger: do you wanna do a report about kubuntu-bugs + the state of the bugtracker with me? [23:50] oh [23:50] lol [23:50] we need to discuss what to do about the wiki, because poor apachelogger can't use it and thus can't add agenda points [23:50] apachelogger: I'll put it on the agenda [23:50] thx [23:51] we need to discuss whether to make mountmanager part of the default applications because currently we have no mount manager in intrepid [23:51] apachelogger needs to talk a bit about upgrade testing, because we need a lot of that [23:51] adnt ehn we can talk about jackalope I think :D [23:52] s/adnt ehn/and then/g [23:54] apachelogger: done [23:54] apachelogger, is the meeting in #ubuntu-meeting? [23:55] NCommander: email Riddell sent out sez yes === Githzerai is now known as Githzerai|Away [23:55] Kubuntu meeting in #ubuntu-meeting in 5 minutes