[00:10] okay, bed time now! good night! [01:49] There will be a short interruption to bazaar.launchpad.net and the ubuntu wiki to deploy a fix for the performance problems. [03:10] pochu: a (fairly) good way of keeping up with current metacity bugs is the Metacity blog [03:10] pochu: it isn't just a log of fixes and things; we try to make it a good read [03:15] marnanel: nice, *subscribes* [03:16] marnanel: perhaps it could be syndicated in Planet GNOME... [03:16] ? [03:35] Playing with bug triage, I'm looking at LP#58162... Hardy has incorporated an upstream fix. What status should the bug be set to? [03:35] Fix released, if the fixed package is in the hardy archives. [03:36] And as a random off-the-street user, I can set that status? [03:37] Yes. [03:38] RAOF: really, you don't even have to join BugSquad? [03:38] empirically, ROAF speaks the truth :-) [03:39] mrooney: Indeed. Anyone can mark a bug as fixed. [03:41] ubuntu-bugsquad isn't archived at gmane? [03:55] pochu: no, they won't do that; Planet GNOME is only for humans. It is at http://planet.gnome.org/news though, and one day there'll be a planet at http://news.gnome.org [03:56] believe me, I'd *like* it to be on Planet GNOME: it'd get a lot more readers :) [04:05] who assigns bugs? [04:06] bugs, or bug tickets? ;-) [04:06] bug tickets [04:09] lets say you're triaging a bug and you have everything you need. It's been confirmed, it's not a dupe, all the proper attachments are part of the ticket. What happens after that. Does the person triaging the bug assign it to someone that maintains the package it affects? [04:09] or does someone from that team just pick it up when they have the chance to take a look at it? [04:10] The latter, generally. We don't really have the Debian system of maintainers. [04:10] ok [04:10] People will generally assign bugs _to themselves_ when they start to work on it. [04:11] RAOF: would that be analogous to (unused, AFAICT) "bts claim" under Debian? [04:12] I have no idea. That's the first time I've heard of such a thing :) [04:16] triaging is kind of fun. at least it's something to do [04:29] Is bughelper(1) supposed to do anything other than just sit there when I run it without arguments? [04:30] (Or does it, without arguments, list *EVERY* bug?) === Seveaz is now known as Seveas [07:17] I'm trying to understand how to report and manipulate bugs on Ubuntu without having to use the launchpad web UI (which I find extremely painful). I have discovered apport-cli. [07:17] I tried to run "apport-cli -p gnome-system-tools", but this exits immediately without an error status or, apparently, doing anything useful. [07:18] twb: Sorry, but I'm pretty sure that's going to spawn a firefox process on you. [07:18] Oh. [07:18] The mail interface remains? :/ [07:19] I was expecting something called -cli to have a command line or curses interface. [07:19] It seems to do something if I include -f [07:20] Unfortunately, that something is to fire up a web browser. [07:20] Namely w3m, which I believe cannot log into launchpad, because launchpad does naughty things with cookies. [08:02] If I am triaging a bug https://bugs.launchpad.net/ubuntu/+source/totem/+bug/209541 but I suspect that the problem isn't with the totem application but with gstreamer how do I go about running that down if I can't replicate the bug because mine works perfectly? [08:02] Launchpad bug 209541 in totem "totem pauses for about 10 seconds before playing a movie in hardy" [Undecided,Incomplete] [08:26] Hi all, I'm new to the BugSquad, but would like to help with triaging. So far, I've tried triaging a few bugs today. Right now, I'm looking at bug 209532 and wondering what to do with it. My thoughts are to assign it to the at-spi package and try to confirm it. Is this the right way to do it? [08:26] Launchpad bug 209532 in ubuntu "Accessibility keyboard settings get lost" [Undecided,New] https://launchpad.net/bugs/209532 === \sh_away is now known as \sh [08:27] no [08:27] he says it's been reported before. find the other reports mark as dupe. move on [08:28] ok, will do. Thakns [08:28] *thanks [08:31] twb, you can write a python script using python-launchpad-bugs to report bugs without using a webbrowser, [08:31] https://wiki.ubuntu.com/BugHelper/Dev/python-launchpad-bugs/Bug [08:41] thekorn_: that's my intention [08:41] thekorn_: I went off on a tangent when I saw apport === doko_ is now known as doko === asac_ is now known as asac [09:41] hi [09:41] can someone look if he/her has the same problem: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/209578 [09:41] Launchpad bug 209578 in gdebi "gdebi-kde crashes with an memory allocation error" [Undecided,New] [09:44] warren_: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/153943 ? [09:44] Launchpad bug 153943 in gdebi "Gdebi-kde uses massive amounts of memory!" [Undecided,Confirmed] [09:45] no [09:46] Is ubotu clever enough to post a link if you just say something like this? [09:46] LP 153943 [09:46] Launchpad bug 153943 in gdebi "Gdebi-kde uses massive amounts of memory!" [Undecided,Confirmed] https://launchpad.net/bugs/153943 [09:46] Cool. [09:49] warren_: why isn't that the one? [09:49] do you have loads of RAM? [09:49] no [09:49] the program can't allocate mem and nothing happens at all [09:49] it even doesn't start installing [09:50] the other bugs seems to install the package but uses too much memory [09:53] ah, ok. [09:54] quite important bug IMHO [10:30] james_w: that's a known bug with gdebi, I've asked someone to fix it [10:31] Riddell: ah, thanks [10:34] * ogra_cmpc has similar probs on the classmate, it loads the full package db files into ram, if you only have main/restricted enabled it should work with a lot smaller footprint [10:35] (classmate has 256M and no swap) [10:36] i dont know how thats fixable though ... you would need to load the file compressed into ram and uncompress on the fly or so,m but i suspect that would make everything slow [10:40] gdebi looks interesting, but does it have a non-GUI version? [10:57] twb: wget and dpkg -i? [10:58] actually, I don't think covers it all. [11:00] james_w: the point of gdebi, AIUI, is that you already have a .deb that you wgot, but you want it to resolv the debs automagically [11:00] Instead of running dpkg -i, waiting for it to fail because of missing deps, then apt-get installing those missing deps [11:01] (ICBW, I'm just going by the package description.) [11:01] ah yeah, sorry [11:01] I was getting it a bit confused with apturl [11:02] No problem. [11:14] gdebi is the non gui version [11:14] gdebi-gtk or -kde are the gui variants of that [11:14] ogra_cmpc: then why does gdebi depend on glade? [11:15] Oh, the names are a little different on Debian: gdebi = gdebi-gtk and gdebi-core = gdebi [11:15] because it ships gdebigtk by default [11:16] *gdebi-gtk [11:16] i guess Riddell would like to see the same split :) [11:17] Just sync from sid :P [11:17] * twb ducks [11:28] twb, given that the change was likely uploaded to debian to do exactly that i think that might happen :) [12:22] marnanel: well, I hope it's written by humans ;) [12:26] seb128: hi, I realise it's a universe package, but would you have any objection to the following upload for hardy? [12:26] https://bugs.launchpad.net/ubuntu/+source/nautilus-python/+bug/44704 [12:26] Launchpad bug 44704 in nautilus-python "Expects to find libpython2.4.so, should look for libpython2.4.so.1" [Low,Confirmed] [12:27] it's a completely broken package at the moment, so we should have something. I'm just wondering if the proposed patch is the wrong solution. [12:55] Hey [12:58] james_w: will do it, ideally the sponsor teams should be subscribed on such bugs though [12:58] hello Iulian [12:59] james_w, your python-nautilus patch works for me, it's now nautilus-bzr.py spitting some tracebacks [12:59] Hi seb128 [12:59] hello Iulian, seb128 [12:59] seb128: thanks, I just wanted to know if you had any objections, I'll subscribe the sponsors now. [12:59] hey thekorn [13:00] thekorn: yes, it seems very out of date from looking at the tracebacks. [13:00] james_w: thanks [13:06] pochu: part of it is actually written by a script; it has a human editor, though (me) [13:06] Hi thekorn, pedro_ [13:06] hello Iulian [13:58] james_w: still around? [13:59] james_w: any reason nautilus-python still has a python directory under the old nautilus directory? [14:01] in the source package? [14:02] ah, I see, I've no idea [14:02] it's listed in debian/dirs [14:03] - Create an empty /usr/lib/nautilus/extensions-1.0/python directory for [14:03] plugins to be installed into. [14:03] [debian/dirs] [14:04] Loic Minier Wed, 1 Mar 2006 20:36:33 [14:04] I don't see when it moved to the new nautilus-extensions though, do you know when this would have been? [14:05] james_w: nautilus 2.21 changed the abi version [14:06] james_w: maybe you could fix that too before I sponsor the change? ;-) [14:06] - Make it work with nautilus 2.22 [14:06] so I think it was just missed in that update [14:06] right [14:07] it's not technically required, most users install those in their user directory usually [14:08] sure, give me 5 minutes to test [14:12] hello [14:12] seb128: done, thanks [14:12] thank you for doing the changes ;-) [14:13] no problem [14:13] I'm working on the users-apple fix right now [14:13] what is that? [14:13] -applet sorry [14:13] ah [14:13] https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/198172 [14:13] Launchpad bug 198172 in gnome-system-tools "[users-admin] Changing anything about the root account sets and invalid home directory" [High,Triaged] [14:46] james_w: not sure if it would have make sense to update the dir version rather than drop it? [14:48] seb128: ah, ok. I thought that the python/ dir was obsolete now, I'll update it [14:48] james_w: no, that's just the versioning which changed, ok [14:56] pedro_: if you triage bug #209587 be careful it has login informations [14:56] Bug 209587 on http://launchpad.net/bugs/209587 is private [14:57] seb128: ok [15:28] morning [15:44] hi [15:45] can someone have a look at this bug https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/209578 [15:45] quite annoying bug [15:45] also very annoying for persons who are now to linux; please fix it :D [15:57] Boo [16:06] jcastro: the other day we were discussing having a way for upstreams to have superpowers for their downstream packages in launchpad. marnanel was interested in doing this, is there an expected timeframe for this feature? [16:06] Has it been proposed and agreed upon? [16:07] james_w: I will talk to bdmurray about it in our call in about an hour, I will let you know asap [16:09] jcastro: great, thanks [16:12] jcastro: we have a call? [16:14] bdmurray: every monday. :D [16:14] jcastro: ;) [16:14] Hi everyone. I have committed a patch to fix #201330. It is attached to a comment I left. How do I make it go through to be released ? shall I "Nominate for release" ? [16:15] bug 201330 [16:15] Launchpad bug 201330 in compiz "Need to whitelist multiple ATI cards, or remove blacklisting" [Medium,Fix committed] https://launchpad.net/bugs/201330 [16:15] exactly [16:16] check the last 2 comments [16:16] andrea_c7a: no, you need to find a sponsor [16:17] andrea_c7a: putting your patch in a .tar.gz isn't great, as it makes it more work to review [16:18] umm, and which one is yours? [16:18] I'm changing the status of the bug back to Triaged as the fix has not been commited to the package's source tree. [16:18] the preferred way to present these is either as a plain patch file, or a debdiff, which is still a patch, but slightly more [16:18] the tar.gz is the debian/patches directory. compiz uses the quilt system. I thought the debian/patches was all you need to define a patch [16:18] https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff [16:19] andrea_c7a: yes, that's fine, it's just not the preferred way to do this. [16:20] also, you should use "dch" from the devscripts package to update the changelog [16:20] and don't include the changelog change in the quilt diff, as that will not work [16:22] andrea_c7a: thanks for writing the patch though. [16:22] I don't know the usual workflow for the compiz package, but if you upload a new patch that fixes the above we can ask what the next step would be [16:24] ok I will try to generate a debdiff and send it again then [16:27] once I generated the debdiff it says to "send it to the relevant person" but I can't see who the maintainer of the compiz package is [16:28] would that be MOTU-Media ? [16:32] andrea_c7a: it's ubuntu-main-sponsors, just subscribe them to the bug using "subscribe someone else". Don't forget to attach the debdiff to the bug! [16:32] andrea_c7a: you could ping amaranth or mvo [16:32] okay, I'll be quiet :) [16:33] (yeah, bzr is running again!) [16:33] ok I'll do that. Thanks very much for your help! [16:35] andrea_c7a: what bugnumber is that? [16:35] mvo: bug 201330 [16:35] Launchpad bug 201330 in compiz "Need to whitelist multiple ATI cards, or remove blacklisting" [Medium,Triaged] https://launchpad.net/bugs/201330 [16:37] yep [16:38] mvo: my patch is in the last comment of the bug === warren_ is now known as WarrenD [16:45] hi secretlondon [16:46] hi james_w === WarrenD is now known as WarrenDUM [16:51] someone know 'mbh' ? [16:58] WarrenDUM: where from? [16:59] thanks seb128 [16:59] james_w: you are welcome [16:59] WarrenDUM: Last Seen: 9 weeks 3 days (22h 9m 21s) ago [16:59] seb128: what's the difference between mime-support and shared-mime-info? [16:59] pochu: ?? [17:00] WarrenDUM: /msg NickServ info mbh [17:00] ok [17:00] someone knows if he wrote gdebi-kde? [17:01] james_w: mime-support is the old mimesystem, I'm wondering if that's not a debian invention, shared-mime-info is the freedesktop specification implementation [17:01] WarrenDUM: mhb, yes [17:01] WarrenDUM: what's the problem? [17:01] james_w: the modern desktops, etc use the freedesktop datas, mime-support is still used by debian tools, mutt, and likely lot of other non desktopish things [17:01] well there's still a huge bug in gdebi-kde [17:01] in hardy and gutsy, it can't install any package [17:02] seb128: ah, ok thanks. I'm looking at bug 201291. I've grabbed shared-mime-info and it seems to have the changes already, so it's no problem it seems. [17:02] Launchpad bug 201291 in mime-support "Add ogv (video) and oga (audio) as recognized extension for Ogg Theora and Ogg Vorbis, respectively" [High,In progress] https://launchpad.net/bugs/201291 [17:02] Cannot allocate memory error, but isn't the bug where too much memory is used [17:02] WarrenDUM: works for me, is that the out of memory issue? [17:02] well it is a mem issue but not the same [17:02] WarrenDUM: right, I have someone working on that [17:02] really? [17:02] on what problem? [17:03] on the embedded konsole widget doing silly things with memory [17:03] but it should install? [17:03] it doesn't install at all [17:03] others are able to install but it simply uses too much memory [17:04] my problem is that it doesn't do anything [17:04] it should install if it doesn't randomly get memory problems [17:04] but i made a bug report [17:05] james_w: do you have an example? and what mimetype is displayed in nautilus? [17:05] is it possible that it doesn't crash in an english environmentn but crashes in a franch environment? [17:05] bug: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/209578 [17:05] Launchpad bug 209578 in gdebi "gdebi-kde crashes with an memory allocation error" [Undecided,New] [17:06] seb128: I don't have an example I'm afraid, but the .xml has all of the entries for audio/ogg etc., which is what needs adding there. [17:07] Riddell : aren't you the kde packager? [17:07] james_w: right, what I means is that it works correctly for me, this bug doesn't seem to be rightly milestoned, it's a low importance issue and has no concrete example [17:08] WarrenDUM: I work on Kubuntu [17:08] ok [17:08] but is my bug related to the other bug? [17:08] seb128: ah, ok. I guess it just affects things that are still using mime-support. [17:08] WarrenDUM: yes [17:08] ok [17:09] seb128: or does it affect KDE as well, they've not transitioned to shared-mime-info correct? [17:09] so this bug report wasn't needed? === \sh is now known as \sh_away [17:09] Riddell: hi, does KDE use shared-mime-info or mime-support or something else? [17:10] james_w: I think all modern desktop used shared-mime-info but I'm not sure [17:10] PS: i don't like the new qtcurve theme ^_^ [17:10] polyester was nicer :p [17:10] james_w: KDE 4 does, KDE 3 not [17:11] Riddell: ok, thanks, it's still worth updating mime-support. [17:13] Riddell: will qtcurve be the default theme for the final release? [17:14] WarrenDUM: yes [17:14] ow ok :( [17:16] ubotwo? :/ === elmargol_ is now known as elmargol [17:53] james_w, Hey, I talked with you about https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/200064 and have gotten some others aware of this report. Would you be considered officially looking at this bug or how does that work? [17:54] Launchpad bug 200064 in network-manager "the iwl3945 driver will not connect to my open, 802.11 b, linksys AP" [Undecided,New] [17:54] Pres-Gas: hi [17:54] I'm not looking at it no, I'm subscribed, but I don't really know enough to tackle it. [17:55] Ahhh, okay, that is what I thought, but wanted to trebble check, james_w [17:55] * Pres-Gas is wondering who's door I should be knocking on [17:56] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/190968 [17:56] Launchpad bug 190968 in linux "[hardy] [regression] iwl3945 doesn't associate on kernel 2.6.24-7" [Medium,Triaged] [17:56] Maybe I am not googleing right, but I am not seeing many issues like this... [17:56] can you verify if that is the same? [17:56] * Pres-Gas is looking now [17:56] Pres-Gas: is your AP SSID hidden? [17:57] ESSID sorry [17:58] LOL, no [17:59] ...and I did a fresh install in that I parted the drive...so Hardy is not carrying legacy files [17:59] Yeah, I may jump in on this one, though since it is triaged [18:07] the hidden ssid is well known and being worked on, so if yours was that would explain it. [18:13] james_w, I wish it was....plus I have other strange AP issues and am afraid it is throwing things off [18:13] The thing I DO know is that my AP works okay in 7.10 [18:19] well, it could well be a driver issue then, due to the change to iwl [18:21] That is what I am thinking, but that does not help without facts (log entries, etc.) [18:24] ubuntu-ca [18:24] oops [18:24] :P [18:24] There is supposed to be an update to the iwl drivers shortly [18:29] bdmurray, where did you hear that? [18:29] That would be wonderful, though [18:29] Looked like the iwl drivers themselves are newer than in Ubu [18:29] Pres-Gas: in bug 200509 [18:29] Launchpad bug 200509 in linux-backports-modules-2.6.24 "iwl4965: Microcode SW error detected. Restarting 0x2000000" [Medium,Fix committed] https://launchpad.net/bugs/200509 [18:30] and bug 185470 [18:30] Launchpad bug 185470 in linux "iwl3945 not functioning : microcode error" [Unknown,In progress] https://launchpad.net/bugs/185470 [18:31] bdmurray, not quite the issue I am having, but here is to hoping that it stumbles onto my issue and fixes it as well. [18:58] james_w: What is the best way to link a bzr branch to a bug? I found the url structure odd [18:58] s/found/find/ [19:00] bdmurray: dunno, I've never done it, let me have a look [19:00] You can't use the full url like https://code.launchpad.net/~brian-murray/unattended-upgrades/brian-fixes [19:00] Instead you have to remove everything before ~ [19:00] You'e using "add branch" from the bug? [19:00] ah, ok [19:01] so, a branch name has 3 parts, ~owner/project/branch-name [19:01] so you need to give all three to identify it [19:01] it's probably worth filing a bug asking for a full URL to be allowed in there [19:02] at least a code.lp.net/~owner/project/branch one. [19:02] Okay, it seems like people would try to use a full url there but I wasn't sure if it was just me. [19:02] heh, I read that branch as "brain-fixes" [19:02] yeah, especially as that's how you do upstream bug links [19:03] I right clicked on a branch at https://code.launchpad.net/unattended-upgrades/+branches to paste in it. [19:04] james_w: Do you know if that would be a malone bug? [19:04] I think it's probably malone [19:04] though I don't know [19:04] they'll at least know where to send it if it isn't [19:04] there is that ;) [19:09] james_w: does bug 113218 look the same as what I am talking about to you? [19:09] Launchpad bug 113218 in launchpad-bazaar "fields for entering a branch should just let you paste a url" [High,Confirmed] https://launchpad.net/bugs/113218 [19:11] yeah, but that's a wider issue [19:11] that's asking for http://wherever/some/branch to be accepted [19:11] you're just asking to be able to use the full code.lp.net URL rather than just the full branch name [19:11] okay, I'll submit another one then [19:11] which should be easier for them [19:15] james_w: I've submitted bug 209834 if you are curious [19:15] bdmurray and james_w, how long does it take for commits (that backports package) to get to the main apt servers? [19:15] What is the turn aroud time [19:17] Pres-Gas: don't know [19:17] where's the commit you are talking about? [19:18] bdmurray: There is supposed to be an update to the iwl drivers shortly [19:19] Pres-Gas: you could watch https://launchpad.net/ubuntu/+source/linux-backports-modules-2.6.24/ for a new version as it would show up in Launchpad first [19:20] By the way, you two are very helpful and userfriendly. Thanks a ton! [19:22] Pres-Gas: uploads appear to happen on average every one to two weeks [19:22] the commit was done three days ago and the last upload was more than two weeks ago [19:22] so I doubt it will be too long [19:23] I'd imagine this week so maybe I shouldn't have said shortly === \sh_away is now known as \sh [19:27] Shortly in a relative sort of way [19:55] * DOOM_NX helloooo === \sh is now known as \sh_away === \sh_away is now known as \sh [20:04] jwendell: regarding your Liferea bug, asac meant -0ubuntu3, not ubuntu4. please update the bug report once you update to ubuntu3 :) [20:05] pochu: jwendell: as i wrote in the bug ... that fix will not be effective until next xulrunner is available [20:05] you cannot really verify it right now === \sh is now known as \sh_away [20:06] hmm, right [20:06] asac: I'm curious, what will the next xulrunner upload change? [20:06] pochu: jwendell: to test you can setup a link libsqlite3.so -> libsqlite3.so.0 [20:06] ah [20:06] thats all what xulrunner does to help this fix [20:06] pochu: the link is the other way around [20:06] so: ln -s libsqlite3.so libsqlite3.so.0 [20:06] :) [20:06] do you have an ETA for that upload? :) [20:07] pochu: upstream is about to release beta5 [20:08] we will upload latest by then [20:08] next few days [20:08] good, thanks [20:09] I read beta5 will be the last beta, is that true? [20:09] lets hope [20:10] I guess the download dialog won't change this late... [20:11] nobody knows. i will not push for anything that might slow down the release process at last [20:12] heh, understandable :) [20:12] but IMHO the current one is much worse than FF2's one [20:13] does someone else experience this bug? https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/209578 === \sh_away is now known as \sh [20:43] can so have a look at Bug 206921 [20:44] bug 206921 [20:45] ah, it's not here [20:45] the bot? [20:46] yep [20:47] annoying [20:47] That is a nice bot to have. [20:47] not in -announce either [20:48] ubotu died [20:48] wont be back till at least tomorrow [20:48] ah ok [20:48] I thought Seveas was rewriting it [20:48] what happened? [20:48] server upgraded to hardy, won't come up after reboot [20:48] upgrade to hardy and the server died... [20:48] I guess I have to file some bugs :) [20:49] We can offer a temporary replacement bot if you wish. [20:51] it'll be back tomorrow around 10:00 CEST [20:51] the world won't die without him [20:51] sure [20:51] thanks for fixing it :) [20:54] sroecker: mine uses org.freedesktop.PowerManagement.Backlight [20:54] your's uses org.freedesktop.Hal.Device.LaptopPanel [20:54] james_w, does yours work in latest hardy? [20:55] yep [20:55] sroecker: reading more I see you understand the problem a little better [20:55] mine's not a macbook [20:56] james_w, ah ok, need a macbook to confirm this [20:57] sroecker: can you strace it to find out why mmap fails please? [21:00] james_w, I don't know, hal calls it somehow [21:01] strace -f hald [21:02] It's doing an mmap directly on to the video card memory, which obviously has the potential to go wrong [21:02] ah [21:06] sroecker: http://gitweb.freedesktop.org/?p=hal.git;a=blob;h=99c390518fb383485af5e22a501c19c2275f649f;hb=3eac1d8399a7e7d1eb76873c10a29e0fea94ad6c;f=hald/linux/addons/addon-macbook-backlight.c [21:06] that's the code if you understand any of it [21:10] * DOOM_NX Eimai edw eimai edw, na sou lew alh8eies, na omorfainw tis nuxtes giati apla S'AGAPW. [21:19] <\sh> guys, the archive of the ubuntu-bugs ML is updated the last time in 2007? [21:31] \sh: the web interface you mean? the listmasters asked about it and nobody was using the webinterface to read the thousand of bugs the list gets every week [21:32] you can still get the mbox for it though I think [21:32] <\sh> seb128: ah ... I didn't know... [21:32] do you really think there is a need to have a webinterface for that? [21:32] all the bugs are in the bug tracker anyway [21:33] I know where to get the mbox if somebody is interested [21:34] <\sh> seb128: google search is faster then to search in LP sometimes [21:35] <\sh> seb128: I was just wondering .) === \sh is now known as \sh_away [21:35] I think there are some other sites that index the bugs mailing list. [21:37] Like http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/ [21:45] hmm [21:45] light is pretty damn fast :-) [22:01] https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/209924 === blueyed_ is now known as blueyed [22:25] * DOOM_NX Mou ekane afierwsh kopela to S'EXW ERWTEUTEI. etsi gia na skasoun kapoies. [22:38] hey tawmas [22:39] hey ascarel [22:56] hi greg_g [22:56] hi greg-g [23:01] hey greg-g [23:13] hiya secretlondon bdmurray [23:14] bdmurray: do you want people in bugcontrol to give a +1/-1 for applicants (via a private email of course)? [23:18] hi bdmurray [23:19] bughelper question, i think. how did you go about putting together the bug day page? [23:19] for tomorrow [23:24] yuriy: it's quite a mess really [23:26] yuriy: However this one should work for you http://pastebin.osuosl.org/6614 [23:26] Mmm, those bugs should work [23:28] What I mean is that list of bugs was created using the same logic I used for the GNOME bugs [23:35] bdmurray: ah, neat! thanks! [23:35] no problem