[00:00] yakuake solves that [00:00] neversfelde: did the ffe stuff go through? was it uploaded? [00:01] I always have terminals [00:01] shtylman: i havent tried to see how yakuake works with xmonad [00:01] shift+mod+return works dandily for me :) [00:01] krunner & yakuake, all I need in life [00:01] alt+f2 chrom [00:01] maco2: ffe went through and I hope it is uploaded now [00:02] neversfelde: yay [00:02] i need to learn to file a ffe [00:02] and then upload spim [00:02] I will try to get it into debian now. Well after I retur from my next vacation next week :/ [00:02] and then learn to deal with debian [00:02] and upload it there too [00:02] what's spim? [00:02] Riddell: mips emulator [00:02] lets you step through assembly [00:03] no, not a kde app [00:03] newly BSD licensed though so it gets to shift from multiverse to universe :) [00:10] yikes, vim is destroyed in lucid [00:10] ? [00:11] error detecting my scripts in .vim and .vimrc, python is broken "Sorry, the command is not available in this version: python << EOF" [00:11] that has worked for probably 5 or more years, sine I am using the same vimrc that long [00:12] works on all machines but lucid all of a sudden [00:13] Riddell: hi hi i haz release team type question [00:14] Riddell: if the only added feature is in the windows version and all changes to the linux version (but its all one tarball) are bugfixes and "looky! shiny new license!" does that need an ffe? [00:16] woo, new vim update fixes previously mayhem [00:28] maco2: bug fixes-only -> file a bug, close the bug in the changelog, upload [00:34] JontheEchidna: quite frankly I would tell them to implement an agnostic gui-packagemanagement wrapper like sensible-browser [00:34] because either way... kdi needs to depend on some sort of package install tool that is specific to KDE and of no use on an ubuntu system [00:35] so the only proper solution here is to have one wrapper for all them guis [00:36] Riddell: btw, wouldnt it be a) more sensible and b) more of a proper solution if software-properties did the cache refersh itself, instead of relying on install-package [00:36] which probably relies itself on gdebi, which then relies on python-apt [00:36] loads of abstraction :) [00:43] Riddell: is the "sleep 3" in your plasma-widget-networkmanagement procedure explicitly necessary? [01:26] crimsun: if the old instance is not terminated the service starutp will fail [01:26] I suppose jr ran into that and so he added the sleep ^^ [01:30] nixternal: You about? [01:32] DarkwingDuck: yo [01:33] nixternal: I don't have my desktop back till the very end of the month. [01:33] heh, jjesse just committed too bzr, and then he just disconnected...what a shitty connection he has [01:33] DarkwingDuck: ouch, yah, that will definitely be to late [01:33] Yeah. [01:33] you want me to take a topic froom you to help out? [01:33] I just upgraded my notebook to Lucid [01:34] I can take either games, media, or web [01:34] you can keep desktop :) [01:34] or I can 2 of the 3 listed to help you out [01:34] And I have to rework the netbook docs [01:35] jjesse: you committed to bzr and then disconnected froom irc...great connection there [01:35] what the hell would be in games and do we really need them? [01:35] DarkwingDuck: hrmm [01:35] yes [01:35] ?? [01:35] answer this: Can I run Windows games? [01:35] that's one we will need to answer...point out things like Cedega and that other one, as well as Wine maybe [01:36] .... ahh [01:36] something brief saying there are a bunch of games in the repos (ie. kde-games, gnome-games, and some other top games) [01:36] I did games before, so I could easily do it again [01:36] Okay, thanks. [01:36] web will be easy too [01:37] I will take web and games, cool? [01:37] or media and games? [01:37] Media [01:37] web will be an easy one, probably easier than media, so I can take that too [01:37] groovy [01:37] OK, media and games are mine, all mine [01:37] I'll do desktop, Netbook and Web [01:37] yeah, web should be super simple [01:37] have to take the dogs out and get a bit to eat...back in a bit [01:37] Yeah, not much has changed, [01:37] kk I'll be here. === jonathan_ is now known as jjesse [01:39] jjesse: bad connection tonite? [01:39] Riddell: It works great [01:41] the recent ubiquity fixes haven't been released yet? [01:41] DarkwingDuck: a bit [01:41] plus signing into my vpn at work disconnects me here [01:45] ahhh [02:02] nixternal: haha just commited some changes :) [02:07] akodani still is having a pissing match with my system. [02:08] maco2: Wacom drivers are working in Lucid now... [02:08] DarkwingDuck: yay [02:09] I was happy because my tablet now works [02:21] DarkwingDuck: did you see the tablet KCM on http://www.kde-apps.org/content/show.php/kcm+tablet?content=114856&PHPSESSID=15ad524778c841a97b0de5857b7b8927 [02:21] Yes, I have not tested it yet. [02:22] That's on my todo list now that my house is packed. [02:22] It's after my finishing these docs LOL [02:23] let me know, i am thinking about buying a new intuos [02:23] Ahh, I got a Referbished ThinkPad X41 [02:24] Wacom drivers work on Lucid. I have not yet gotten to the fingerprint scanner [02:26] grrr... I hate my life. I actually forgot to backup my key *sigh* [02:33] and you got rid of the old computer already? or did you format over it? [02:34] It's packed. [02:34] I'm moving cross courntry... [02:49] maco2: No, that doesn't need an FFe. [02:51] ScottK: ok thank you :) [02:51] now to figure out why pbuilder is falling over [02:51] maco2: If someone tells you different, then I hearby wave my magic wand over it and it has as much FFe as it needs. [02:52] ScottK: haha thanks [02:52] ScottK: any idea what *this* is? http://paste.ubuntu.com/391402/ [02:52] (noting that it's for lucid and lucid has debhelper 7.4 and unless math changed recently 7.4 >= 5 evaluates as "true") [02:53] The problem is in line 2 I think. [02:54] yeah thats kinda what i was figuring but i cant make heads/tails of that error message [02:54] is that "dpkg go boom"? [02:54] It is. [02:54] It would appear that it's only the victim though. [02:55] * maco2 tries to update the pbuilder again, though was just done 2 hours ago [02:55] If that doesn't work, try creating a new one: sometimes the tarballs get wedged [03:22] ARRRRRRRRRRRRRRG [03:26] * ScottK hands DarkwingDuck an "H". [03:27] Okay, how do I add Thunderbird to the KWallet so I can decrypt OpenPGP signed messages? [03:28] I would use KMail except Akonadi is being a little $@(&#( in Lucid still [03:29] and I'm about to start bashing my head against the only working computer I have at the moment [03:29] DarkwingDuck: sounds like progress [03:29] Yes It is === emma_ is now known as emma [03:30] It's all in rebuilding my system... I love new computers. [03:30] Next time I'm going to clone my HD [03:35] persia: creating a new tarball seems to have worked. thanks [03:41] Okay, got that working.. [03:42] Now, I have to see what I can do to fix Akonadi [04:04] the best Chuck yet tonight! [04:05] RAW is good [04:42] Okay, having a build issue with cmake... [04:43] apparently it's not moving it to where it should be for KDE4 [04:45] Any ideas? http://pastebin.com/74iutXyq [04:57] DarkwingDuck: sudo apt-get install kdelibs5-dev [04:58] it can't find FindKDE4Internal.cmake which is in kdelibs5-dev [05:00] ahh ty [05:04] since I have done my good deed for the year, I shall now go to bed...g'nite [05:06] nite lol [05:50] o/ [05:51] Riddell: hrm, were those instructions meant for lucid or karmic? === dpm-afk is now known as dpm [09:42] shtylman: i bet there isn't a ready to use .deb with your ubiquity changes? ( i guess i can't build them on a liveCD without internet connection) === Tonio__ is now known as Tonio_ [11:02] apachelogger: choqok - 0.9.55a-0ubuntu1~karmic1~ppa2 is in lucid in the beta backports ppa [11:06] if you are ok with it, I will change it, delete the package and reupload? [11:08] neversfelde: don't we want that in the main archive? [11:09] Riddell: it is in the main archive, that is a karmic backport, that accidently was build for lucid, I think [11:11] aah [13:01] how do i get debug packages for kde 4.4.1 on karmic? [13:03] install -dbg [13:04] dantti: when doing a distro upgrade the name and description don't seem to be picked up by kpackagekit [13:04] dantti: as far as I can tell the backend gets them correctly [13:04] dantti: how can I find out where they get lost? [13:05] Riddell: hmm let me see.. [13:06] I tried using qdbus to see if I could workout the magic to ask packagekitd directly but failed [13:07] it's a bit complicated to do that with qdbus, since you have to get a tid and then talk to another interface [13:08] which iirc will sease it's existence if not used quickly [13:08] mm, the whole tid thing always seemed excessively complex to me === asac_ is now known as asac [13:11] means I don't have an easy way to find out if the fault is in the backend or the frontend [13:11] Riddell: well you can always run packagekitd with --verbose [13:12] but using the python apt backend I must admit is a bit harder to debug [13:12] but if the signal is emmited then you will get it [13:13] Riddell: I have just looked at the kpk code and pk-qt code and it is ok [13:13] it sets the name and description of update [13:13] which pk send to it [13:14] i think if you run with --verbose you will see the distroUpgrade signal being emmited [13:22] dantti: here's the log, no obvious issues I can see although I'm not familier with its output http://people.canonical.com/~jriddell/tmp/packagekit-log [13:22] here - emitting distro-upgrade unknown, (null), (null) [13:24] ah, so it is something in the backend [13:24] yup [13:24] or the daemon [13:24] Riddell: I doubt it's on the daemon, It's more likely to be in the backend [13:32] "distro-upgrade stable melon 11.04.1 LTS The latest stable release" [13:32] that's what the backend is passing to lib/python/packagekit/backend.py distro_upgrade() [13:33] so seems to be an issue in the daemon or its python bindings [13:46] dantti, hi, if I'm not mistaken, you are kpackagekit upstream, aren't you? I've been looking at an issue with translations on bug 534915. If you have the chance to look into that and need more info, just let me know [13:46] Launchpad bug 534915 in kpackagekit "Czech translations in Ukrainian kpackagekit translation" [Undecided,Confirmed] https://launchpad.net/bugs/534915 [13:54] dpm: i get those po files from a fedora dude that has a script to get them all [13:54] I'll poke him about this issue [13:58] Riddell: today I can't help much on this issue, poke me tomorrow I'll try to help finding out what happened [14:00] dantti: thanks for your help so far, I'll e-mail my debug digging === jonathan_ is now known as jjesse [14:04] agateau: what's the relationship between application indicators and the new systray spec going to be in the future? to me it looks like they both try to solve the same problem [14:05] Sput: sure they do [14:05] Sput: actually they use the same spec :) [14:05] Sput: except it's named application indicator on the GNOME side [14:06] agateau: this means that in the future (after approval by fdo) applications using the dbus spec will support both automatically? [14:06] ok, thanks dantti === Quintasan1 is now known as Quintasan [14:06] \o [14:06] Sput: what do you mean "support both"? [14:07] Sput: application indicators and KStatusNotifierItem use the same dbus protocol [14:07] (modulo bugs) [14:07] agateau: well, currently we have support in quassel for libindicate, for status notifier (using dbus), and for the old-style trayicon (as fallback) [14:07] agateau: I'd be happy to reduce that number :) [14:08] Sput: you need to keep old-style trayicon until status notifier is more widespread (especially on the gnome side) [14:08] agateau: so if in the near future both libindicate and KStatusNotifier are using the same spec (in org.freedesktop, I assume?), would that mean that wouldn't have to have explicit libindicate support? [14:08] mmm no [14:08] libindicate != libappindicator [14:08] this is a bit messy [14:08] meh, this is confusing! [14:09] Sput: I agree :/ [14:09] ah. libappindicator is equivalent to kstatusnotifier, and libindicate is an alternative to knotify? [14:10] I think we can say this, yes [14:11] actually, not exactly [14:11] libindicate is for the message indicator applets [14:11] Sput: rather, libindicate is (according to canonical design team) a better approach to communicate human messages than using the systray [14:11] hmmm, any chance that libindicate and knotify are using the same spec (org.freedesktop.Notifications)? [14:11] no [14:11] agateau: I thought the whole idea of the new dbus specs is separating the information from the visualization... hmm [14:12] in the case of notifications, it is already separated [14:13] Sput: from the design team point of view, an application should choose either "app indicator" (aka libappindicator aka kstatusnotifieritem) or "message indicator" (aka libindicate) [14:13] but an application which deals with human to human interaction should use the message indicator [14:14] on the gnome side, they removed systray support from apps where they added message indicator support [14:14] but that was a bit too bold for the kde side IMHO :) [14:14] guess so :) [14:14] the longer term goal is to reduce the clutter in the systemtray [14:15] they think messaging apps use of the systemtray is legitimate but could be improved, hence the message indicator [14:15] other apps should either not use the systemtray or get ported to app indicator because it gives more control to the desktop [14:16] and ensure a more consistent behavior [14:17] where app indicator is the new tray spec (kstatusnotifier) [14:17] hmmm ok. Quassel now automatically uses kstatusnotifier if it's present, and falls back to the old trayicon else. and in addition, there is the libindicate stuff you implemented, which needs to be enabled explicitly [14:18] Sput: sounds good then [14:19] I'm all for removing systray applets where we have message indicator support, seems like silly duplication to me [14:24] applications will still have to implement both, because as a matter of fact, message indicator is still pretty much ubuntu-only [14:24] Sput: indeed [14:24] and tbh, I don't see that changing anytime soon [14:25] though Gentoo ships the plasmoid nowadays because I requested it to be able to test :) [14:25] yeah! [14:25] an old version though, I should probably also request a bump [14:27] we did try to get message indicator plasmoid upstream since it's far better than the hacky one shipped by KDE, but aaron thinks it should be implemented using kstatusnotifiericon, trouble is nobody except him knows how that's possible [14:28] not sure he even knows :> [14:28] mm [14:29] rdieter: do you know if anyone in fedora has looked into packaging the message indicator plasmoid? [14:29] actually it could be possible, but would need a few extensions to the existing KSNI protocol [14:30] Riddell: I don't think so, I could look into it though. [14:30] agateau: it might be an idea to have an entry on kde-apps.org for it if you don't already [14:30] Riddell: good idea [14:31] * agateau adds this to his TODO [14:44] hngh [14:44] apachelogger: ping [14:51] hngh [15:06] Riddell: when is beta freeze" [15:06] so I can get the artwork in [15:06] for the installer [15:06] Thursday [15:06] k... guess I will get to that tonight then [15:06] heh [15:07] shtylman: Note that there are *two* Beta Freezes this cycle. [15:07] yea.... its all weird [15:24] Riddell: (just got out of a meeting), so is https://launchpad.net/plasma-widget-message-indicator this it? [15:29] rdieter: that's the one [15:29] rdieter: it'll need libindicate-qt [15:30] which is turn needs libindicate [15:31] it has support upstream in kmail and quassel and there are patches for konversation and kopete ( agateau can tell you if I got any of those wrong) [15:31] Riddell: quite good, [15:32] Kopete support is not a patch, it's a plugin, hosted on launchpad [15:32] * agateau fetches the url [15:33] https://launchpad.net/kopete-message-indicator [15:34] agateau: hmm, we still have it as a load of patches to kdenetwork [15:34] Riddell: you should be able to get rid of them then [15:35] hmm, why do I have the feeling I failed to package that [15:35] :) [15:36] Riddell: pardon my ignorance, but how is this related (if at all) to the usual kde notifier? [15:37] * rdieter found some links, reading up [15:38] rdieter: it's a whole new indicator, it's one place to get notification of human to human messages rather than each app using its own systray applet [15:38] http://www.kdedevelopers.org/node/4043 has a summary [15:41] so...it replaces or complements kde/plasma default notifier? [15:42] rdieter: complements. plasma popup notifications are too distracting for chat for me, I want to be able to ignore distractions at times, also they're not persistent [15:42] ok [15:42] "Enhances:" ? === yofel_ is now known as yofel [16:18] shtylman: hmm ubquity got uploaded but I don't see anything about the language selection bug in the changelog https://edge.launchpad.net/ubuntu/+source/ubiquity [16:56] yo glatzor [16:56] glatzor, dantti: that missing distro upgrade string bug doesn't happen on karmic [16:56] but I still have to do an SRU on karmic to fix pk-upgrade-distro.sh in packagekit [16:57] hello Riddell [16:58] glatzor: I added this patch to packagekit yesterday and the karmic SRU will need to do much the same thing http://people.canonical.com/~jriddell/tmp/fix_upgrade_distro.diff [17:04] seems to be ok [17:08] * Riddell runs the distro upgrader from karmic to lucid and crosses fingers [17:10] let me know how that goes...I am thinking of a fresh install on this laptop, hoping it cures a couple of things I have noticed recently with Karmic [17:13] The upgrade worked on my laptop [17:14] DarkwingDuck: what method did you use to upgrade? [17:14] update-notifier-kde -d [17:14] DarkwingDuck: no wee problems at all? [17:15] Other then akonadi SQL issues. [17:15] my karmic is really acting up lately (Xorg is pinned at 100% of one CPU), but i don't think i'll be able to leave anytime soon -- they broke a kernel feature i need for work [17:15] amazing thing is i barely even notice the CPU usage. hooray for quad core [17:17] DarkwingDuck: do you know if we or upstream have a bug for the akonadi problem(s)? [17:17] yuriy_work: did you check if there were any likely guilty candidates among recent updates? [17:18] Riddell: I have not checked. [17:18] apachelogger: do you know if we or upstream have a bug for the akonadi problem(s)? [17:18] I upgraded last night and have not had time yet... I'm dealing with some LoCo Issues [17:21] Riddell: haven't really looked into it, but there was a kernel update that i'm *not* using [17:25] plus my time is all screwed up and the set time automatically setting won't stick [17:26] apachelogger: bug 533990 approved, asac suggested we get the code upstream, I don't know dario's policy on that [17:26] Launchpad bug 533990 in kubuntu-debug-installer "[MIR] kubuntu-debug-installer" [Undecided,New] https://launchpad.net/bugs/533990 [17:28] debfx: bug 531848 approved, kmozillahelper in main, we finally have firefox kde integration complete [17:28] Launchpad bug 531848 in kmozillahelper "kmozillahelper MIR" [Undecided,In progress] https://launchpad.net/bugs/531848 [17:30] \o/ [17:30] * asac should actually start using kubuntu now [17:30] since i am mostly free from desktop team obligations ;) [17:31] btw, when i met partners that plan to roll out ubuntu in their development department i was told that the great majority chooses kubuntu over ubuntu ;) [17:31] ooh a convert :) [17:31] just to inform you that you seem to be more attractive atm ;) [17:31] asac: that is interesting [17:31] so keep you guys motivated ;) [17:31] Riddell: yeah. they said: they show them both and most look at it and pick kubuntu ;) [17:34] ;-) [17:34] Riddell: it's only cause ublog works properly now :) [17:54] well upgrade from karmic to lucid worked well [17:55] only issue I can see is message indicator didn't get moved to the systray [17:55] * apachelogger drops in [17:55] battery did get moved though so the script is working to some extent [17:56] Riddell: nice :) [17:56] Riddell: possibly the switch is bugged [17:56] I think I use a composite condition for the indicator [17:57] Riddell: we and upstream have bugs for the akonadi problem ... there is only one (though fixing that in one particular way will result in another one) [17:57] apachelogger: got the number? [17:57] looking [17:57] Riddell: bug 448705 [17:57] Launchpad bug 448705 in akonadi "akonadi server doesn't start at login" [High,Confirmed] https://launchpad.net/bugs/448705 [17:57] upstream bug is linked [17:57] compositing seems to be turned off by default in lucid, that's the bug ScottK reported, wonder why it is [17:58] strigi seems to be turned on by default, I'm not sure that's a good idea [17:59] Riddell: further implications on our side would be that, if we need to make akonadi run that script to initialize the standard mysql databases we also need to move loads of files from mysql-server-5.1 to the core package [18:00] also I came to wonder if the way akonadi uses mysql really requires those tables to be present ... because if not I would much rather have mysql changed so that it does not look for those tables if it was started with a special config option or cmdline arg [18:00] oh, and the other implication is that we would need to enhance the apparmor profile quite a bit because that initialization script seems to require a bit more access than what is currently permitted [18:02] apachelogger: does this affect all uses or only upgrades from previous versions? [18:02] Riddell: about getting kubunt-debug-installer upstream ... the idea was to make it easy for distros to add installers, so you could set just about any app as installer (that includes any kind of script of course) [18:03] using a script bares the risk of runtime problems + makes threading more of a pita + uses more CPU time... [18:04] Riddell: all, but not really all ;) [18:04] Riddell: it is a complicate issue [18:05] primarily it affects _all_ new installations in that akondi must call that default table init script, but does not currently do that which leads to the mysqld being a crybaby and make akondi fail [18:05] BUT it actually seems that akonadi works, mysql is just all whiny [18:06] then it affects _all_ installations that were upgraded from an earlier installation that uses an akonadi dbcreated with myql 5.1 (since those also lack the necessary tables) [18:06] and finally it seems to affect installations, where the db was created with 5.0, then upgraded to 5.1, in which particular case only the time tables seem to be missing [18:07] though judging from what I read in forums it is more of a random problem, which makes it all a whole lot more awful :( [18:08] upstream seems remarkably unconcerned [18:08] yeah [18:08] also krake just keeps on telling people to run that script ;) [18:11] Riddell: anyhow, as I see it what needs to happen is find out if akonadi actually requires those tables, and if not somehow get rid of the error, or if it does, include the script into the startup process [18:11] or just use postgres ;) [18:14] steveire: as the handy upstream on the channel, have you looked at this problem at all? [18:15] Riddell: he is not into the mysql stuff he said [18:16] Riddell: I suppose vkrause is to be poked, since he is the bug assignee akonadi server stuff [18:16] I don't have specific knowledge of it at least. [18:18] JontheEchidna: I'm not convinced about bug 529488, I think only kde-l10n-sr-latin has been eaten by kde-l10n-sr, the rest just haven't been updated by upstream [18:18] Launchpad bug 529488 in kde-l10n-sr-latin "Request for removal from archive (source and binary)" [Low,Fix released] https://launchpad.net/bugs/529488 [18:18] But vkrause is in #akonadi atm if you want to raise him there. [18:19] Riddell: hmm, but the two install conflicting files... [18:19] JontheEchidna: for [18:19] JontheEchidna: for kde-l10n-sr yes, so I removed the -latin there [18:19] ah, ok [18:19] Riddell, apachelogger, Since i am not using Akonadi as I have found ways around it ATM... I don't know much about it but, if you wnat to use me as a test platform for scripts etc I'll volunteer. [18:20] Riddell: theoretically though, the translations for the locale variants have already been imported, yes? [18:20] JontheEchidna: ca-valencia I'm uploading now, it had a packaging problem in 4.4.1 [18:20] Riddell: I'll invalidate that one [18:20] JontheEchidna: yes, assuming launchpad suports those variants which I think it does [18:21] JontheEchidna: so the more general question is do we want to remove language packs that KDE doesn't ship in 4.4 [18:21] * apachelogger would think so [18:22] In my opinion, upstream is not shipping them for a reason, plus we already have the old translations imported [18:22] if they did not meet KDE's criteria, they shouldnt meet ours either [18:22] * Quintasan this is a good idea [18:22] plus more languages might go the way of sr/sr-latin and install conflicting files [18:22] Translators agree that no translation is better than borked translation [18:22] * Quintasan joined kde-l18n-pl [18:22] that's quite a few http://kubuntu.pastebin.com/fT2v7ADT [18:24] Riddell: is today your archive day? [18:24] if so, I won't bug you with stuff you'll get around to anyways ;-) [18:25] JontheEchidna: it is, requests accepted, I probably won't get through all the bugs [18:25] bug 532626, bug 532629 and bug 532712 [18:25] Launchpad bug 532626 in mailody "Request for removal from archive (binary and source)" [Wishlist,Triaged] https://launchpad.net/bugs/532626 [18:25] Launchpad bug 532629 in mailody-kde4 "Request for removal from archive (binary and source)" [Wishlist,Triaged] https://launchpad.net/bugs/532629 [18:25] for asdf in kde-l10n-af kde-l10n-as kde-l10n-be kde-l10n-be-latin kde-l10n-bn kde-l10n-bnin kde-l10n-br kde-l10n-crh kde-l10n-cy kde-l10n-fa kde-l10n-ha kde-l10n-hne kde-l10n-hsb kde-l10n-hy kde-l10n-ka kde-l10n-ku kde-l10n-mr kde-l10n-ms kde-l10n-ne kde-l10n-oc kde-l10n-or kde-l10n-rw kde-l10n-se kde-l10n-si kde-l10n-ta kde-l10n-te kde-l10n-th kde-l10n-uz kde-l10n-uz-cyrillic kde-l10n-vi kde-l10n-xh kde-l10n-zhhk; do echo ${asdf}; lp-remove-package.py -u [18:25] Launchpad bug 532712 in dbus-1-qt3 "Request for removal from the archive (binary and source)" [Wishlist,Triaged] https://launchpad.net/bugs/532712 [18:26] mailody and dbus-1-qt3 got removed from sid, and mailody-kde4 has been in alpha for 2 years [18:26] oh dear [18:26] :O [18:26] Riddell, JontheEchidna: did you take a look at kde-l10n-common? [18:27] apachelogger: I'm afraid that's still on my TODO [18:27] DarkwingDuck: good to know :) [18:27] apachelogger: I briefly read the e-mail and couldn't quite work out what it was [18:27] Riddell: it is one packaging branch that can be shared across all of kde-l10n-* [18:27] same here ^ [18:28] oh, neat [18:28] apachelogger: and some magic to make the source packages? [18:28] aye [18:28] sounds good [18:28] you do a chance once, then use an included script to build the packages from that branch [18:28] I'll do the 4.4.2 l10n packages, to iron out any problems [18:29] does it do the .desktop translation grabbing? [18:30] of course [18:30] ah, that's in debian/rules [18:30] nvm, was looking in the .sh [18:30] well, the .sh invokes the grabbing [18:30] nixternal: are you aware of bug 460225 for the docs packaging? [18:30] Launchpad bug 460225 in ubufox "Firefox v 3.5.3 (offline) Home Page Error in Kubuntu" [High,Invalid] https://launchpad.net/bugs/460225 [18:30] see bzr-buildpackage cmd [18:30] ah, kk [18:42] apachelogger: kubuntu-debug-installer worked fine when kontact crashed, good job :) [18:42] kubotu: order cookies for apachelogger [18:42] * kubotu slides a whole bunch of world's finest cookies down the bar to apachelogger. [18:42] cool [18:42] ...but not perfect just now :) [18:42] * Quintasan goes back to classes and objects magic [18:44] neversfelde: btw, what was the problem with blogilo keeping updating? [18:48] hmm, We should consider replacing skanlite with skansuite at some point [18:49] but that won't be ready any soon [18:51] apachelogger: no idea, lex reverted the change and made it conflict bilbo [18:51] ic [18:52] I never tested, if the upgrade karmic 4.3.5 => lucid works now, but it is on my todo [18:58] Riddell: Ping [19:10] Riddell: http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/changes/3896.1.3 [19:11] I guess ev didn't make a note of it in the changelog [19:22] DarkwingDuck: pong [19:22] strange happening with the plasma network widget [19:22] It took 5 minutes to accecpt my connection. [19:22] Also, has my wireless as eth1... [19:23] but still works [19:23] sebas proably the best guy to report to [19:23] kk [19:24] Riddell: Is there any functional advantage to the Plamsa widget over KNM? (e.g. works with hidden SSIDs) [19:27] ScottK: no and I don't think it works with hidden SSIDs, that's still on sebas's todo. it's more a case that it's the frontend upstream are supporting going forward [19:28]