[00:00] apachelogger: no mail yet about the complaint? [00:04] neversfelde: no, still waiting if someone else got additional input [00:04] but I should eventually push it out by next week [00:04] apachelogger: forgot to metion the many bugs about sound, seems to be a jaunty problem [00:04] probably not a kubuntu one [00:04] well, it happens when pulseaudio gets pulled in [00:04] and as I noticed that can happen in the most weird cases [00:05] like when you install a make liked build tool for java :P [00:05] yes, but purging it is not the solution everytime [00:05] bug 370520 [00:05] well, then it's probably an issue in alsa [00:05] Launchpad bug 370520 in kdepim "kio_groupwise.so should be in kdepimlibs5" [High,Triaged] https://launchpad.net/bugs/370520 [00:05] neversfelde: ^ [00:06] apachelogger: didn't you wirte a mail to me about the complaint? [00:06] neversfelde: most of the work is really just getting the fixed deployed (i.e. check with debian and prepare SRU) rather than get it done :) [00:06] neversfelde: oh... well, yes [00:06] will have a look at it [00:06] not arrived [00:06] neversfelde ... googlemail .... com [00:06] isn't it? [00:07] nope, I left google :) [00:07] well, it's a google doc... [00:07] neversfelde: about the bug: if you don't think that you have time please drop it on the devel list and find someone else to do it [00:07] mhh, probably I shoul register again [00:08] apachelogger: will do [00:08] groupwise is, as I understand, not too unfamous within corporate environments, so having it broken is kinda awful [00:08] neversfelde: http://docs.google.com/Doc?id=ajk6csn6c2vn_0c6d8rp6w [00:10] apachelogger: bookmarked and will hava a look at it tomorrow evening [00:10] okies, thx [00:11] Riddell: could you please send mail about meeting schedule + update topic + update wiki + get nixternal to fridge it? [00:11] obviously I already forgot what day and time it was :D [00:14] ah, there is a thunderstorm on my wallpaper [00:15] * neversfelde blames JontheEchidna :) [00:15] * apachelogger notes that there was a thunderstorm in his windows a few hours ago [00:15] clearly I must blame the weather though [00:16] hehe [00:17] blame the weather or blame the weatherman, never mid [01:02] hmm, I'm sure I put it in the topic [01:03] mhh [01:03] Riddell: what? :) === Riddell changed the topic of #kubuntu-devel to: You are beautiful! | https://wiki.kubuntu.org/KubuntuKarmicSpecs | Sync/Merges: https://wiki.kubuntu.org/Kubuntu/KarmicKDEMerges http://qa.ubuntuwire.com/multidistrotools/kubuntu-desktop.html | Meeting Wed 18:00 [01:17] UTC? [01:22] it's the only time zone worth considering [01:23] nixternal: please add to fridge ^^ [01:28] Would a MOTU have a look at bug 370009 [01:28] Launchpad bug 370009 in choqok "New upstream version 0.5 available" [Undecided,New] https://launchpad.net/bugs/370009 [01:28] or is it to early in release cycle? [01:31] choqok 0.5 is imo worth a backport so it would be good if it passes the line to karmic [01:35] Riddell: this Wednesday? 18:00 utc? ... I assume in this channel...? [01:40] shtylman: meetings normaly take place in #ubuntu-meeting [01:41] neversfelde: thanks [01:49] * Tonio_ packages kaffeine, konversation and latest alpha k3b [01:49] kaffeine is impressive, really [01:49] can't wait to see it back as the default kubuntu video player [01:51] Tonio_: +1 [01:51] it is a nice app [01:52] yup [01:52] neversfelde: fancy testing the deb file ? [01:52] neversfelde: ppas currently don't build anything :/ [01:53] ho and also partition manager now has a kcm module, which is pretty cool [01:53] Tonio_: I tested a svn snap some days ago [01:53] neversfelde: right ;) [01:53] I think it was from your ppa [01:53] also can't wait for konversation [01:53] * neversfelde is a quassel fan :) [01:53] I like quassel, but for some reasons it suffers lots of performances issues on my laptop :/ [01:54] mhh, no problems here [01:54] neversfelde: using compositing ? [01:54] yes [01:55] neversfelde: performances are nice, but it's going very slow when kde compositing is enabled here [01:55] NVIDIA Cards all around here, and no probs [01:56] ati with the opensource drivers here :) [01:56] which also means, at least 2 X.org segfaults a day :/ [01:56] hehe, that might be the problem [01:56] I really hope X.org will stabilize in the next month [01:56] we have several reports for ATI in kubunut-de.org forum [01:57] I can confirm there is :) [01:57] :) [01:58] hum, looks like konversation won't let me speak :) [02:02] I think I should go to bed, but several tasks left :( [02:02] Tonio__: Bug or feature? [02:04] neversfelde: wasn 't I talking about xorg crashes ? there we go :) [02:05] Tonio_: yes, there are a lot of reports like this [02:05] gnah :( [02:08] wow.... konversation + ati + compositing -> crash [02:08] * Tonio_ loves opensources drivers [02:08] I remember when the xorg team was complaining... [02:08] "want good opensource drivers, please Mr ati and nvidia, release the specs and we'll do them" [02:08] what a joke..... === Quintasan_ is now known as Quintasan [08:36] Hiho [08:37] * Quintasan is back from trip [08:38] :o [09:56] can someone take a look at the upstream bug of bug 301698 the problem could not be reproduced with qt 4.5.0 r961909 [09:56] Error: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/301698/+text) [10:00] eagles0513875: see ... what do you want to know in this case? [10:00] for instance since it probably needs testing who to assing it to [10:01] yourself? [10:02] how woudl i go about testing this bug though [10:02] this case is extremly difficult because upstream did not even request data, but just noted that it seems unreproducible in trunk [10:03] gotcha thing is i have never gotten an error like that when posting to launchpad [10:03] eagles0513875: apply all patches from qt-copy (in kde svn) to our qt package and rebuild the package, then try if the bug still appears [10:03] * eagles0513875 needs to figure out packaging and pbuilder [10:03] well [10:04] another option is to check the patch names to try find those which might have fixed this issue [10:04] or read through the patches themselfs [10:04] ok [10:04] as said, difficult to do anything on that bug [10:05] should i ask jon bout how to proceed i know its not nice to lump it on someone else but for right now i think its above me level [10:05] you can [10:05] * apachelogger wants to note that his trunk build still exposes that bug though [10:06] ahhhh ok [10:06] that build is > 1 week old, but I doubt the issue was fixed in the meantime [10:06] i feel bad lumping this on him im still a novice i admit as well that i dont have much time to bug fix i can report bugs upstream but that is about it for now till after 19th of may [10:08] another question not realted to this bug but devel in general im packaging an updated snapshot of kvirc 4.0 would it make it into the kubuntu-experimental ppa or stay just in my personal ppa [10:12] technically it should go into karmic and then jaunty-backport [10:12] s [10:13] so anythign that gets updated goes into the next release then pushed back to the previous release [10:13] well, the backport only happens if the package qualifies for backport [10:14] what would make something get pushed to jaunty as an update [10:14] like a KDE beta will probably not qualify for backport as it actually degrades what is in jaunty by default [10:14] for instance an updated kvirc snapshot wouldnt that not hurt anything its just an upgrade to latest version of kvirc which is in jaunty [10:15] eagles0513875: well, update != update ... there are stable release updates (minor changes with considerable great impact ... e.g. fixing a crash) ... there are security updates.... and there are backports (which are mostly new versions) [10:15] like amarok 2.1.0 will qualify for backports, but not for SRU nor security [10:15] ahhhhh ok that clears up alot of stuff [10:16] backports repos is like the bleeding edge stuff [10:16] well, kinda [10:16] would pbuilder work for installing it on the local machine then building the package [10:17] eagles0513875: svn snapshot is a different story though, an svn snapshot only would qualify when jaunty included a svn snaphot and when there is no stable release available [10:17] thing is i dunno what was done for jaunty in regards to kvirc 4.0 [10:17] or when the new snapshot provides considerable improvements over the stable release [10:17] eagles0513875: what would you need to know? [10:18] was kvirc for jaunty built from svn [10:19] take a look at the version number in jaunty [10:19] also, there was no kvirc 4 release yet, so... [10:20] gotcha [10:20] and that is a way outdated version in the repos [10:20] its 3039 and they are on 3190 [10:21] another question what would cause an svn version of a program to make a release like kvirc for instance [10:22] can't follow [10:22] what cause kvirc which is still in svn what got it to be allowed into jaunty [10:23] a horribly broken KDE 3 version I suppose [10:24] you should ask the uploader though [10:24] ok [10:24] it's just common sense surly ? [10:24] the best available package is taken === k4v is now known as m4v [10:25] even if its missing alot of features [10:25] for instance themed backgrounds dont work in the version in the repo [10:25] if it's the best available - it doesn't matter what's in t [10:25] eagles0513875: does it work on any other versions ? [10:25] on the 3.4.2 it does [10:26] which is stable [10:26] what is the version in the repo ? [10:26] svn 3039 and they are on svn 3190 [10:26] http://websvn.kde.org/trunk/?rev=3039&view=rev | svn://anonsvn.kde.org/home/kde/trunk -r 3039 | Matthias: small fixes for Bernd's fixes :-) And --- as additional gimmick --- no more kwm border. So you need either Alt-F3 o... [10:26] http://websvn.kde.org/trunk/?rev=3190&view=rev | svn://anonsvn.kde.org/home/kde/trunk -r 3190 | Martin K.: automatically created webpage [10:27] eagles0513875: has the feature your talking about been removed or is it a bug [10:27] it's unusual for a feature to be removed in later versions [10:28] i think it hasnt been implemented in the version that is currently in the repo [10:28] i havent installed the latest snapshot [10:28] is the svn repo a new branch or just an update to the existing? [10:28] i dont understand what you mean [10:29] i got the code from the svn of kvirc [10:29] is the branch your talking about in the svn repo a brand new branch, or is it building on the existing code base ? [10:29] building on the existing code i think not sure [10:30] so how can it not have been implmented if it's on the same branch ? [10:30] i see where you are coming from so then its most likely a bug [10:30] I don't know as I don't use it, [10:31] ill have to compile the latest svn code and see if the issue still exists [10:32] how are you compiling it, are you using the same options as the existing deb package ? [10:32] i dunno how it was compiled [10:32] or are you just typing make && make install ? [10:32] no it seems to use cmake so ill be using cmake [10:32] i tried with make and make install but there is no make file to go with [10:33] ok - but you need to make sure you use the same options as the existing deb package or it's a pointless test that will give miss-leading results [10:33] how can i determine what was used [10:33] strip the deb [10:33] ok [10:33] eagles0513875: see how cmake got invoked in the build log :P [10:34] apachelogger: after stripping it [10:34] ikonia: the svn version doesn't have said feature because it gets rewriten for KDE 4 [10:34] which usually comes down to gets rewrittencompletely [10:34] apachelogger: which is why I was asking if it was a difference branch or not [10:34] i didnt know :( [10:35] to be honest it looks the same as 3.4.2 [10:35] looks has nothing to do with it [10:35] ikonia: amarok 2 is not a different branch and yet has barely any relation to amarok 1's code ;-) [10:35] hence why I was asking about the code base [10:35] gotcha [10:35] apachelogger: may not be a different branch in the repo - but it's a fresh branch of code [10:35] although I don't know amarok at all really [10:35] nope [10:35] got based upon amarok 1 [10:36] how can it be based on amarok 1 yet be a re-write ? [10:36] hahah just found the cmaake flags [10:36] dont have to strip the deb its under the about kvirc [10:36] ikonia: that is what happens when you port, refactor and enhance at the same time :D [10:37] ok - so it is a seperate branch - it's a new base [10:37] it became a new base [10:37] however, how would you tell it is [10:37] features can also get lost because of the porting alone [10:37] thats a good point if it's not noted [10:37] when there is a non-trivial problem preventing the feature's portation for example [10:38] which in the case of kvirc the theme feature got lost [10:38] eagles0513875: do you know it's got lost as you just said it looked like a bug ? [10:38] I don't know - which is why I'm asking [10:38] * apachelogger would bet on unfinished porting in this case [10:38] i wont know until i try the updated svn version [10:39] in the about kvirc this is showing this was built on march 7th which is almost 2 months old [10:40] two months old isn't old [10:40] depending on how active the dev team is alot could change [10:40] !best [10:40] Usually, there is no single "best" application to perform a given task. It's up to you to choose, depending on your preferences, features you require, and other factors. Do NOT take polls in the channel. If you insist on getting people's opinions, ask BestBot in #ubuntu-bots. [10:41] or rather [10:41] mornign to you too jussi01 [10:41] !wfm [10:41] Common Sense: Just because you can, does not mean you should (and especially recommend to others). Think before you do. "Works for me" does not mean it is ok. The latest version of everything is not always useful if you aim for stability. Please see http://geekosophical.net/random/worksforme/ [10:41] hm [10:41] that clearly doesn't fit SVN 90% of the time [10:41] * jussi01 waves in apachelogger's direction [10:42] yo jussi01 [10:43] * eagles0513875 goes and sits in corner and ponders packaging an updated kvirc version to replace the one thats in repos [10:45] do you think its a bad idea to have an updated version of kvirc since its still in svn and also in jaunty [10:46] http://brainstorm.ubuntu.com/idea/19358/ [10:47] * eagles0513875 waits for konqueror to crash [10:48] that got my vote i think it would be kool to have the unique login scree like we do splash screen for kubuntu [10:51] maybe I should file an idea "people should stop complaining about kubuntu artwork, but do something about it" [10:51] I was just about to say there are tons on kde-look, ubuntu-fy one and submit it [10:53] well, they would need to fit in [10:53] just having a splash doesn't cut the chese [10:53] of course not, [10:53] along with that we'd need a kdm theme and probably a wallpaper [10:53] FFFFUUUU [10:53] ? [10:53] Quintasan: you package minion? [10:54] apachelogger: what? [10:54] are you a packaging minion? [10:54] * eagles0513875 wants to eventually become a package minion [10:54] apachelogger: looks like :D === thunderstruck is now known as gnomefreak [10:54] Quintasan: anything up on revu to revu? [10:54] i think gnomefreak is as well lol he was packaging seamonkey when he came on lol [10:54] currently I'm trying to package new minirok but debuild complains about symbolic links [10:55] dunno how to deal with it [10:55] eagles0513875: i finished Seamonkey nightly yesterday [10:55] Quintasan: show build log [10:55] ahhh my bad [10:56] apachelogger: ok I need a second because I cleared source :P [10:56] oi vei! [10:58] koffice has a broken dependency and when installing that dependency first it wants to uninstall my whole kde desktop :( [10:59] apachelogger: http://pastebin.com/f66e17ca6 [10:59] eagles0513875: You are running jaunty? [10:59] ah [11:00] Quintasan: you seem to have generated binary blop in your source tree [11:00] that is preventing dpkg-source from creating the diff and makes it wanna die [11:00] Quintasan: ya i am but stripped it down to kde-base install and building it up that way and when i did this same thing on intrepid the same issue [11:00] apachelogger: duuno, I did "git clone" [11:01] eagles0513875: Wouldn't it be easier to start with Ubuntu Server and install KDE packages? [11:01] ah my fault [11:01] Quintasan: dpkg-source: error: new version is symlink to minirok [11:01] dpkg-source: error: old version is directory [11:02] Quintasan: not a big problem on kubuntu purge kde* [11:02] that means minirok-2.0/src is a directory with $content in the tarball [11:02] but in your source tree it is a symlink to the directory minirok [11:02] thing is koffice is really annoying me i cannot install it due to kformula dependency issue and when i try to install kformula it wants to uninstall kde [11:02] apachelogger: hmm, I tared and gzipped the git tree I downloaded [11:02] so either the tarball is all messed up or you poluted your source tree :P [11:03] Quintasan: well, try to do it again [11:03] and make sure you get rid of the .git dir before taring it up [11:03] hm ok [11:04] any idea as to why when installing the missing dependency of koffice which is kformula it wants to remove anythign kde that is installed [11:04] eagles0513875: #kubuntu [11:04] for support [11:04] ok [11:05] eagles0513875: use aptitiude, it shows available solutions for dependencies problems [11:05] Quintasan: normally i use apt-get build-dep koffice [11:05] i think there is a bug in the koffice package [11:06] * a|wen notes that if aptitude offers less than 180 options, you haven't messed your system up bad enough [11:06] lol [11:07] morning a|wen [11:07] ill have to take a look at the koffice source code [11:07] Hi a|wen [11:07] and hi [11:07] the sad thing was, that none of the 180 options was what i wanted :/ [11:09] apachelogger: looks like taring didn't preserve symlinks [11:09] I wonder how should I do it [11:10] Quintasan: im not a package master but have you tried pbuilder [11:10] it buidls the package using the .dsc file [11:10] eagles0513875: I'm using pbuilder [11:10] ahh my bad [11:11] * Quintasan wonders how to create karmic pbuilder env [11:11] Quintasan: make a jaunty one and dist-upgrade [11:11] and re-creat a fresh one, when we get a debootstrab that supports karmic [11:12] a|wen: lol, looks like the best solution is easiest one, thanks :P [11:12] Quintasan: he :) wish it was always so :P [11:14] * a|wen loves his modified pbuilder-dist making all those things easy [11:15] ARGH [11:16] * Quintasan cloned minirok tree for 30th time [11:18] YEAH [11:18] I just discovered --preserve option for tar [11:22] .... [11:22] Quintasan: TBH, there shouldn't be in the source to begin with [11:23] you might wanna poke $upstream in the eye [11:23] apachelogger: nvm this [11:23] apachelogger: It woked [11:23] still, go complain [11:23] apachelogger: but python-kde4-dev has wrong permissons on pykdeuic.py (no +x) and I can't do "make ui" [11:24] again? [11:24] and if I don't make it then configuration dialogs don't work [11:24] * apachelogger fixed that stuff like 300 times by now [11:24] apachelogger: It was just downloaded and installed by pbuilder :/ [11:24] maybe we should start a suite of QA tests for bindings [11:24] that package is regressing like no other [11:25] ok so I will leave minrok until this get's fixed [11:25] minirok* [11:28] Quintasan: meanwhile you can annoy upstream with not creating symlinks though :D [11:28] apachelogger: sure I will, such things give me headace :< [11:32] woah gcc 4.4 [11:34] hmmmm [11:34] JontheEchidna: ping? [11:34] vorian: ping [11:34] no one heere [11:35] Quintasan: would you happen to know whether we are using pkg-kde-tools yet? [11:35] apachelogger: nope :( [11:35] :S [11:36] apachelogger: only in synced packages [11:36] a|wen: why not in the others? [11:36] that would mean that we have to keep kde4.mk from cdbs and the one in pkg-kde in sync [11:37] apachelogger: because it places the docs in a dir where they are not found [11:37] Riddell is linking isn't he? [11:37] anyway, I'll just cdbs for now [11:37] but pkg-kde is the longterm target [11:37] a|wen: + we can change that pretty easily :P [11:38] apachelogger: yeah .. but that would lead to half the synced packages FTBFS'ing on us [11:39] apachelogger: but Riddell will probably do some link-magic in kdelibs ... and the long-term target is to use pkg-kde-tools (and alligning our doc-paths) [11:40] well, debian can't align until they dropped kdebase3 [11:40] and that will propably take a while i suppose [11:41] well if we get the symlink-magic in place, then we should be good [11:41] Quintasan: http://revu.ubuntuwire.com/p/plasma-widget-klicker [11:41] can you pleas tell me why that changelog lists 3 entries? [11:42] dunno, I think it was dropped, let me check [11:42] a|wen: it all seems rather weird anyway [11:43] neversfelde: bug #364926 [11:43] Launchpad bug 364926 in ubuntu "[needs-packaging] FotoWall" [Wishlist,In progress] https://launchpad.net/bugs/364926 [11:44] apachelogger: looks like it's not going to be developed anymore, could you remove it please? [11:44] Quintasan: only revu admins can [11:45] you might catch one in #ubuntuwire [11:57] NCommander: Would you please rescore the kile and alarm-clock srus in Jaunty. [12:05] Quintasan: http://revu.ubuntuwire.com/p/plasma-widget-pgame [12:06] Quintasan: http://revu.ubuntuwire.com/p/plasma-widget-gxmailnotify [12:17] * apachelogger notes that apps using qmake usually are the ones with the worst tarball === olujicz_ is now known as olujicz [12:46] apachelogger: I am using pkg-kde-tools [12:46] a|wen: link magic? [12:55] Riddell: well, we should start a full migration [12:56] apachelogger: yep, the merges should migrate it [12:57] Riddell: well, I was thinking about not adding new packages with cdbs' kde4.mk [12:57] then over time we can move the others to use pkg-kde-tools [12:59] yes, there shouldn't be a reason to use kde4.mk now [13:35] Riddell: I was thinking about replacing k3b and kaffeine by their respective kde4 version in karmic [13:36] Riddell: do you think we should do this right now ? [13:36] * Tonio_ even thinks we should install kaffeine as default video player [13:37] * eagles0513875 thinks we need to find something better the pulse audio to use. i have more problems then its worth. i cant use my hd sound card drivers :( [13:38] do we have qt 4.5.1 and qt-creator 1.1 in some ppa? [13:38] hi Tonio_ [13:38] Lure: ey ! [13:38] * Lure wants to try qt-creator after all the positive blog posts [13:39] Tonio_: how are you? [13:39] Lure: appart from my eyes, I'm doing well :) [13:39] Tonio_: +1 on getting k3b and kaffeine asap in karmic [13:39] Lure: I'm having an eye surgery this summer, little problem on that point :/ [13:40] Tonio_: ups, that does not sound that good [13:40] Tonio_: do you plan to come to akademy? [13:40] * Lure is considering... [13:40] Lure: my company on't pay since I'm leaving my job [13:40] hehe [13:40] Lure: I probably won't [13:40] Tonio_, Riddell: http://aplg.kollide.net/images/osiris/snapshot036.png [13:40] partitionmanager beta2 [13:40] oh, got something better? [13:40] with kcm [13:40] hrrhrr [13:41] apachelogger: packaged on my ppa fyi [13:41] Tonio_: lul, I just updated for karmic :P [13:41] apachelogger: ah ;) [13:41] Tonio_: i think they will regret loosing you [13:41] apachelogger: I'm not that in what pkg-kde-tool is doing... do we have to stop using kde4.mk ? [13:42] you really should create a bug report when you update something and don't upload to $archive right away :P [13:42] Tonio_: that is a good question indeed [13:42] Riddell: do we have to? [13:42] eagles0513875: bah... everyone can be replaced [13:42] Tonio_: but the next guy might not be as good as you then they will regret it [13:42] apachelogger: what are the benefits in using pkg-kde-tools ? [13:43] there are none [13:43] eagles0513875: the only big problem is that I'm the only one to know everything about the french parliament [13:43] well, no important ones at least [13:43] eagles0513875: I did their distribution mostly alone.... and they'll have to provide support [13:43] Tonio_: then they will be begging to get you back [13:43] for one we don't need to update all of cdbs to get our kde stuff sorted [13:43] second all the kde related build stuff is in one package [13:43] that's about it [13:43] qtCreator is an very good program IMHO [13:44] eagles0513875: they won't :) cause they know once I've decided something, there's no way I can get back [13:44] Tonio_: sent you pm to not take channel ot [13:47] Tonio_, apachelogger: pkg-kde-tools is the debian version of kde4.mk, since we don't want to alter from debian for no reason we should use pkg-kde-tools [13:47] okies [13:48] kde4.mk only exists because debian weren't getting round to adding a separate cdbs file, now they have we should use it, it's effectively identicle anyway [13:48] Tonio_: I've not looked at kaffeine but if we're certain they'll be stable for karmic we should upgrade to the kde 4 versions [13:49] Riddell: it's mostly finished right now [13:50] * apachelogger updates partitionmanager with pkg-kde [13:50] Riddell: target is kde 4.3 [13:51] * eagles0513875 should get back ot upstreaming bugs but will have to do that when im fedup of revising [13:54] Tonio_: go for it then [13:54] Riddell: kk === hunger_ is now known as hunger === eYv_ww`p is now known as LjL [14:43] * Riddell spots http://www.kubuntu-de.org/english/interview-with-kubuntu-developer-jonathan-thomas [14:44] O_O [14:44] damn that puts me to shame [14:44] im 22 this month and i dotn know how to do jack squat cept upstream bug reporting lol [14:48] Riddell: thanks for pointing that out im learning bout alot of kool stuff in jaunty [14:49] Riddell: we should blog, fridge, UWN, NYT ... [14:52] apachelogger: your mentioned in the interview that jon gave [14:52] uh [14:52] *reads* [14:52] near the bottom bout what a ninja is [14:52] he mentions you in there [14:53] hm [14:53] * apachelogger thinks that his bug triage work is much more valuable than streamlining the release packaging [14:53] lol [14:53] then again who wants to know about how I triaged 500 bugs a day by forwarding everything to jonny :P [14:54] hahahahahaha [14:54] he puts me to shame [14:55] * eagles0513875 will be back later to upstream more bugs after a nap and getting fedup of revising [15:13]