[00:09] <ogasawara> mrooney: I posted a note to the bug report if you can take a look.  I'll try to investigate that "noise floor calibration timeout" that you're seeing a little more.
[01:23] <mroone1> ogasawara: thanks, I can try that PPA. I also added to the description the common dmesg errors to make it easier
[02:24] <mrooney> Oh, it appears upgrading my Intrepid install to linux 27-4 removed my Hardy menu.lst entries, I am not quite sure how to boot into it now.
[02:27] <RAOF> mrooney: (a) that sounds like a bug, unless you had your menu.lst set up in such a way that it was inevitable, and (b) you can edit the grub during boot - press esc to bring up the menu, then edit the commandline to point to your Hardy root.
[02:29] <mrooney> RAOF: I edited it manually to remove old Hardy kernel entries and moved the Windows entry around
[02:29] <mrooney> I don't know if that would make it un-mergeable
[02:30] <mrooney> ogasawara: still around?
[02:31] <mrooney> I was going to install Tim's madwifi PPA but I don't see an Intrepid entry, shall I just change Hardy to Intrepid and hope it works?
[02:33] <RAOF> mrooney: As long as the hardy kernel entries were outside the "automagic kernel list" section, they should have been safe.
[02:51] <mrooney> RAOF: thanks for the tip, I copied the relevant lines from my Hardy's menu.lst over to Intrepid's and it boots fine, phew!
[04:59] <jdong> sigh, where's the "give negative karma" button?
[05:07] <RAOF> jdong: ? :)
[05:08] <jdong> RAOF: the ffmpeg AMR bug
[05:08] <jdong> bug 93849
[05:09] <jdong> both reinhard and I tried being nice. particularly frustrating because upstream seems close to a fix and the guy keeps on attaching surveys and asking how to do silly things with launchpad buttons on the side and that ends up in my inbox.
[05:09] <maco> jdong: id like one too for the reporter of bug 271891
[05:10] <jdong> maco: that's a joke, right?
[05:12] <RAOF> Hm.  That questionaire looks unhelpful.
[05:13] <jdong> RAOF: looks like the corporate version of "Nice drawing! Now I'm gonna hang it up RIGHT HERE on the fridge where EVERYONE can see it...."
[05:14] <maco> jdong: unfortunately, no, i don't think it's a joke.  just someone who doesn't know 5th grade math trying to correct a calculator.
[05:14] <jdong> maco: I'm pretty sure his correction breaks number theory :)
[05:14] <maco> jdong: yeah, me too
[05:14] <maco> i told him to ask a math teacher
[05:16] <jdong> poor kid.
[05:16] <jdong> I don't know of any calculator that interpolates things the way he expects.
[05:17] <jdong> not even the fancy user-friendly CASes like the new TI's
[05:19] <sbeattie> jdong: kcalc
[05:20] <jdong> sbeattie: really?
[05:21] <sbeattie> version 2.0.6 in hardy just did it for me, returned 950 after I entered 1000 - 5%
[05:22] <jdong> sbeattie: confirmed
[05:23] <jdong> sbeattie: but it's quirky in other ways
[05:23] <jdong> like 20%/20% just gave me 100
[05:23]  * jdong RTFMs
[05:24] <jdong> wow that's honestly, even more confusing
[05:24] <jdong> (1) If the final operator is + or - the second argument is interpreted as percentage of the first operand.
[05:24] <jdong> (2) If the final operator is * divide the result of the multiplication by 100.
[05:24] <jdong> (3) If the final operator is / give the left operand as a percentage of the right operand.
[05:24] <jdong> (4) In all other cases the % key gives identical results to the = key.
[05:24] <jdong> :-/
[05:25] <lifeless> crack!
[05:26] <jdong> yeah this sounds too smart for its own good....
[05:26] <jdong> like the python "a""b" => "ab" behavior
[05:29] <lifeless> jdong: C does that too
[05:29] <pwnguin> %'s or crazy c concatenation?
[05:30] <pwnguin> it might be a good idea if you have macros
[05:31] <jdong> lifeless: oh it does?
[05:32] <lifeless> jdong: I'm pretty sure :) "string1" "string2" is == "string1string2"
[05:32] <jdong> you're right
[05:32] <lifeless> jdong: you can see it with macros to get source lines and stuff
[05:32] <jdong> didn't know that
[05:33] <jdong> maybe that's the use for it
[05:33] <jdong> I just found it annoying for various typos
[05:33] <jdong> particularly involving constructing lists of lists and omitting a comma :)
[05:33] <maco> jdong: file a bug "KCalc breaks number theory"
[05:33] <pwnguin> isn't there already a bug?
[05:33] <maco> is it titled that?!
[05:34] <jdong> maco: lol wait for kcalc-kde4 to reinterpret what all the other operators mean too depending on how close it was to the / button.
[05:34] <pwnguin> well you brought up the bug maco, surely you can retitle it ;)
[05:34] <maco> pwnguin: the bug i brought up was his brain breaking number theory ;)
[05:35] <maco> can we have a dummy package called "user" against which to file bugs that are user error?
[05:35] <maco> it could be fun to watch the number of bugs filed against the user
[05:36] <pwnguin> there's plenty of serious work to be done ;)
[05:36] <jdong> grumble wouter stomp bugs....
[05:36] <jdong> bug 266920
[05:37] <jdong> the minimal view of transmission is informative than the first GNOME 2.14 print dialogs with one button and 1 option.
[05:37] <jdong> less*
[05:37] <pwnguin> i think tomorrow, i'll do some serious work
[05:38] <pwnguin> i'll fix the gnome system monitor applet to show I/O in the visible spectrum
[05:38] <nellery> Bug 500000 in debian is going to be reported tomorrow :D
[05:39] <pwnguin> nellery: when was the BTS started?
[05:41] <nellery> pwnguin, well the copyright at the bottom of the page has a 1994
[05:41] <pwnguin> i think debian started in 94
[05:42] <nellery> Well Ubuntu is past halfway there in 3 years?
[05:43] <pwnguin> are bugs in lp per project?
[05:44] <nellery> ah, got that mixed up
[05:44] <nellery> 216897 every reported
[05:45] <pwnguin> we should stop writing so many bugs!
[05:46] <maco> only 10% of those are still open at least...
[05:47] <maco> pwnguin: or so many duplicates
[05:48] <pwnguin> well, duplicates are hard
[05:48] <pwnguin> there's a culture of closing dupes
[05:48] <pwnguin> INVALID. THANKS FOR PLAYING
[05:50] <maco> i mean if less dups were reported
[05:50] <maco> the "are you sure you're not reporting one of these 10 bugs" thing is terrible at guessing
[05:50] <pwnguin> i agree it's not superb
[05:51] <pwnguin> ive often thought some sort of data mining challenge was in order, but I suppose there are priorities
[05:51] <maco> though i wouldn't call mozilla's "here are the 100 most frequently reported bugs that have nothing to do with your keywords" method any better
[05:51] <pwnguin> datamining and software engineering. if you can't find a few interested grad students and professors to give it a shot
[05:52] <pwnguin> the world is doomed
[05:53] <maco> haha
[05:53] <maco> hrm...i'm still a year away from a senior design project though
[05:54] <maco> and for jaunty, i'm thinking about usability issues...i hate the preferences menu. i think i'd rather stare at kmail's settings than use that menu in its default state
[05:55] <maco> i minimalize the menu then have control center enabled, but the control center is awfully cluttered as well
[05:55] <maco> but then there's ccsm....definitely more cluttered than the gnome control center
[05:56] <maco> *sigh* there's got to be something that can be done about those UIs
[05:56] <_Zeus_> i like ccsm
[06:00] <maco> _Zeus_: you must admit its UI needs a makeover
[06:01] <Burgundavia> maco: which UI?
[06:01] <wgrant> I don't think ccsm can be fixed.
[06:01] <wgrant> It just has too much to do.
[06:02] <_Zeus_> yeah
[06:02] <_Zeus_> they have thousands of settings
[06:03] <wgrant> It is terrible now, yes, but it'd be difficult to make it much better.
[06:04] <maco> Burgundavia: ccsm's
[06:04] <maco> wgrant: there was one suggestion i had for how they handle doing bindings...lets see if i can find/upload those mockups
[06:04] <Burgundavia> ah, yes
[06:04] <Burgundavia> a typical "power user" interface, which utterly fails for everybody, including power users
[06:05] <maco> ok so this was a bug i saw
[06:05] <maco> http://img184.imageshack.us/img184/471/screenshot1nx3.png
[06:05] <maco> note the ordering of the elements
[06:06] <maco> screen, keyboard, mouse....screen, mouse, keyboard....screen, mouse, keyboard
[06:06] <maco> hrm, that first one doesn't match
[06:07] <maco> and this was my suggestion for tidying up that sort of interface: http://img50.imageshack.us/img50/5648/suggestioner1.png
[06:07] <maco> its still not great, but it avoids repeating the same thing til your eyes cross
[06:07] <maco> i dont think it's necessary to have 2 ways to edit the mappings, either
[06:07] <wgrant> What about a matrix with actions as rows and screen,mouse,keyboard as columns?
[06:08] <maco> that'd work too
[06:08] <_Zeus_> https://bugs.launchpad.net/ubuntu/+source/v86d/+bug/273833/
[06:08] <_Zeus_> what should i do?
[06:09] <_Zeus_> maco: i like that better
[06:09] <_Zeus_> i was always confused by the way they did it
[06:11] <maco> if there was a way to do colored filters in X without Compiz, that'd be nice for accessibility testing as well.  then we could test for different types of colorblindness
[06:12] <wgrant> maco: Why not just use Compiz?
[06:13] <maco> wgrant: well the other reason is that the overlays themselves can be accessibility features for dyslexic people.  and compiz isn't available to everyone.
[06:14] <_Zeus_> why?
[06:14] <maco> _Zeus_: why what?
[06:14] <maco> why isn't compiz available to everyone?
[06:14] <_Zeus_> yes
[06:14] <maco> it requires certain hardware
[06:14] <_Zeus_> i thought you could run some plugins regardless?
[06:15] <maco> um, not that i'm aware of, but the filters definitely require compositing
[06:15] <_Zeus_> ah
[06:15] <maco> either that, or you use gtkfb
[06:15] <maco> which would be not-X
[06:19] <maco> creating some Compiz filters for use with that plugin to emulate different forms of colorblindness is likely a worthwhile endeavor in terms of testing for that anyway
[06:19] <maco> no idea how to create compiz color filters though
[06:20] <maco> plus the part where i dont use compiz...
[06:20] <wgrant> I thought they already existed.
[06:20]  * wgrant looks.
[06:20] <maco> there are a few included
[06:20] <maco> but i dont think they're meant to emulate types of colorblindness
[06:21] <wgrant> I see two with names rather like varieties of colourblindness.
[06:22] <maco> oo really?
[06:22] <maco> in hardy or intrepid?
[06:22] <maco> i just see sepia, negative, green, blue, and greyscale
[06:22] <maco> but i'm still on hardy
[06:24] <wgrant> Intrepid, of course.
[06:24] <wgrant> Unfortunately...
[06:24] <wgrant> X doesn't like being colourblind.
[06:24] <wgrant> It sort of freezes up and jumps off a cliff.
[06:26] <maco> lovely
[06:31] <_Zeus_> whoa, new firefox=weird license agreement!
[06:31] <wgrant> It's not particularly weird, is it?
[06:31] <wgrant> I hope I won't have to go and file another bug...
[06:32] <_Zeus_> no
[06:32] <maco> wgrant: it shows a little bar at the top saying something about firefox being free and open source software
[06:32] <_Zeus_> just one of those password-remember-type dropdowns that says read the license
[06:32] <maco> and has a little button for more info about your rights
[06:33] <wgrant> maco: Right, I complained about that wording.
[06:33] <maco> then it lists the tenants of free software
[06:33] <maco> and says it's MPL-licensed
[07:49] <dholbach> good morning
[08:23] <thekorn> morgen dholbach
[08:24] <dholbach> hi thekorn
[10:22] <Konstigt> hello guys. what is needed to include bug #262191 on https://bugs.launchpad.net/ubuntu/intrepid/+bugs?
[13:59] <davmor2> I have an issue at the moment with both hardy and intrepid.  If I run both firefox and pidgin together My system eventually runs out of memory.  There are some valgrind logs here http://www.davmor2.co.uk/firef.log ﻿http://www.davmor2.co.uk/firef-reach.log ﻿http://www.davmor2.co.uk/pidgin.log ﻿http://www.davmor2.co.uk/pidgin-reach.log the -reach logs are ones where I enabled --show-reachable=yes at seb128 request.
[14:33] <afflux> morning
[14:33] <jjesse_> morning afflux
[14:33] <greg-g> davmor2: have you reported a bug?
[14:34] <greg-g> davmor2: if you have, please attach those logs.  If you haven't, please do so and attach those logs.
[14:40] <davmor2> greg-g: yes I have and I will :)
[14:44] <greg-g> davmor2: good deal :)  I know there have been issues with pidgin before like that
[14:44] <davmor2> greg-g: bug 273587
[15:17] <salty-horse> hi. can anyone launch gnome-appearance-properties successfully?
[15:19] <ara> salty-horse: intrepid?
[15:19] <salty-horse> yes
[15:20] <ara> salty-horse: yes, i can
[15:21] <salty-horse> ara, latest version?
[15:21] <davmor2> ara: have you just done an update?
[15:21] <davmor2> salty-horse: I can't now
[15:21] <ara> salty-horse, davmor2: i am doing it now
[15:21] <salty-horse> davmor2, it crashes?
[15:22] <davmor2> yeap
[15:22] <salty-horse> I'll file a bug
[15:22] <ara> salty-horse: I just updated to latest of gnome-control-center and i can run it properly
[15:23] <davmor2> salty-horse: already known mvo and seb128 are working on it :)
[15:23] <salty-horse> ok :)
[15:25] <salty-horse> tseliot, here?
[15:25] <tseliot> salty-horse: yes
[15:25] <salty-horse> after upgrading to intrepid, I am unable to purge the defunct nvidia-glx packages -- what should I do?
[15:26] <salty-horse> that's glx-new and glx-legacy
[15:26] <salty-horse> error:
[15:26] <salty-horse> Purging configuration files for nvidia-glx-legacy ...
[15:26] <salty-horse> dpkg-divert: mismatch on package
[15:26] <salty-horse>   when removing `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx-legacy'
[15:26] <salty-horse>   found `diversion of /usr/lib/libGL.so.1 to /usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx-96'
[15:26] <salty-horse> dpkg: error processing nvidia-glx-legacy (--purge):
[15:26] <salty-horse>  subprocess post-removal script returned error exit status 2
[15:27] <salty-horse> (sorry for spam)
[15:27] <tseliot> salty-horse: did you install the driver with the NVIDIA installer too?
[15:27] <salty-horse> nope, but I have a bit of a problem with the restricted drivers manager ATM
[15:27] <salty-horse> I'm getting this error as well (pastebin)
[15:28] <salty-horse> http://pastebin.com/m67f88ff0
[15:29] <Hew> Someone has questioned me setting the importance of bug 104525 to wishlist. I still think this is the correct setting. Could someone else provide their thoughts?
[15:30] <tseliot> salty-horse: the fact that the build fail is normal: https://bugs.launchpad.net/bugs/251107
[15:31] <tseliot> i.e. a bug which depends on NVIDIA
[15:31] <salty-horse> yeah, I know that problem
[15:31] <salty-horse> (had no idea it's related to the build)
[15:31] <tseliot> as regards that diversion, the preinst of the 96 package should have removed it
[15:32] <salty-horse> I'll try reinstalling the 96 package
[15:32] <tseliot> dpkg-divert --remove --rename --package nvidia-glx-96 --divert /usr/lib/nvidia/libGL.so.1.xlibmesa /usr/lib/libGL.so.1
[15:32] <tseliot> try this command ^^
[15:32] <tseliot> with sudo
[15:32] <salty-horse> Is it something that the restricted drivers manager supposed to do?
[15:33] <tseliot> no, it's something that the .preinst of nvidia-glx-96 was supposed to do
[15:33] <tseliot> but it only added its own diversion instead of removing the old one first
[15:33] <tseliot> which is weird
[15:34] <tseliot> salty-horse: the build fails because I haven't patched the driver to get it to work with kernel 2.6.27
[15:35] <salty-horse> does the nvidia license allow you to patch it?
[15:35] <tseliot> as it would have been a waste of time since the module is not compatible with the new Xorg ABI
[15:35] <tseliot> yes, that's not the closed part
[15:36] <salty-horse> error of dpkg-divert: http://pastebin.com/m47e33e09
[15:36] <tseliot> ok
[15:36] <tseliot> sudo rm /usr/lib/libGL.so.1
[15:37] <tseliot> and try the previous command again
[15:39] <salty-horse> just a sec. reinstallation of nvidia-glx-96 printed no errors
[15:40] <salty-horse> done
[15:41] <salty-horse> I still can't purge the packages. getting the same errors.
[15:42] <greg-g> of COURSE KEXP is playing Nirvana at this time of day (7:40am their time)
[15:42] <greg-g> erm, wrong window, sorry
[15:47] <tseliot> salty-horse: can you put the output of this command in pastebin? dpkg-divert --list nvidia*
[15:48] <salty-horse> sec
[15:50] <salty-horse> http://pastebin.com/m21232229
[15:50] <salty-horse> and this is the purging error again: http://pastebin.com/m67f7e1f4
[15:54] <tseliot> salty-horse: aah, there's something wrong in the old packages then
[15:56] <tseliot> salty-horse: try this (which is safe now since all the diversions of the old package were removed): sudo rm /var/lib/dpkg/info/nvidia/nvidia-glx-legacy*
[15:56] <tseliot> sudo rm /var/lib/dpkg/info/nvidia-glx-legacy*
[15:56] <tseliot> only the 2nd command
[15:56] <tseliot> then try to remove the package again
[15:56] <salty-horse> yes, noticed :)
[15:58] <salty-horse> and -new* as well, right?
[15:59] <tseliot> salty-horse: yes, it won't hurt
[16:00] <salty-horse> ok, packages removed
[16:00] <salty-horse> is this a bug?
[16:01] <tseliot> I wouldn't know. I look into it
[16:01] <salty-horse> thanks
[16:01] <tseliot> thanks for reporting
[16:02] <salty-horse> I don't think it does any damage, but it's nice to keep the system clean after an upgrade
[16:02] <tseliot> yes, of course
[16:38] <maco> james_w: hey, i have a question about those policykit bugs
[16:38] <james_w> hey maco
[16:38] <james_w> how are you?
[16:46] <maco> james_w: alright, you
[16:46] <maco> ?
[16:46] <james_w> good thanks
[16:47] <maco> james_w: so i marked the bug i was on as a dup of the one you pointed to, but i just noticed the request for the policykit.conf, and it contains the same thing Luis said he put in to fix it
[16:48] <maco> james_w: though he did say he reinstalled before putting that in the policykit.conf, so i don't know if that makes a difference
 or similar?
[16:57] <maco> <define_admin_auth group="admin"/>
[16:57] <maco> yeah
[16:58] <james_w> that is supposed to be there, and should have been in the other report, and shouldn't matter for root as root isn't in the admin group
[16:58] <maco> but the part above that too
[16:59] <james_w> maco: if you "sudo users-admin" do you get the warning about not being able to look up session information for process blah blah
[16:59] <maco> james_w: yes
[16:59] <james_w> there should be <match user="root"><result>yes</result></match> or something above
[16:59] <maco> yes
[17:00] <james_w> maco: that's weird as you have $XDG_SESSION_COOKIE defined, and the error is that it can't find that
[17:01] <maco> should i do a sudo -s and then echo it?
[17:01] <maco> or sudo -i?
[17:01] <maco> i guess -i
[17:01] <maco> after sudo -i, it's not defined
[17:03] <maco> wow tiling window managers make it really obvious when devs haven't remembered to put in scrollbars for when windows are shrunken
[17:04] <james_w> maco: I understand the problem now, thanks
[17:04] <james_w> maco: sudo doesn't let $XDG_SESSION_COOKIE in to the environment of the child process, and so it can't use consolekit
[17:04] <maco> gotcha
[17:05] <james_w> thanks for the help
[17:05] <maco> np
[17:06] <james_w> so they are all actually duplicates of bug 210897
[17:10] <maco> james_w: wow, that's got a very descriptive title :P
[17:55] <kees> sbeattie: qa-regression-testing> your php-lp52866 testcase -- does that run on non-dapper too?
[17:55] <sbeattie> kees: yes, tested on hardy as well.
[17:58] <sbeattie> kees: the reason for the for-loop in the testcase is to try to eliminate differences in whitespace when comparing the emitted xml.
[17:59] <sbeattie> (probably should have commented that)
[17:59] <kees> sbeattie: I've queued it (though I have no idea what that means in LP)
[18:02] <sbeattie> kees: ideally, rather than doing a simple strcmp(), the emitted xml would have been parsed out and the resultant structure compared, but my attempts to do so were met with massive FAIL.
[18:08] <kees> sbeattie: heh
[21:27] <Arby> how does one unduplicate a bug?
[21:28] <Arby> bug 156044 and bug 156045 don't look like dupes to me
[21:28] <danbhfive> I think you duplicate it back to nothing
[21:28] <_Zeus_> was i right in invalidating this? https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/274085
[21:29] <Arby> danbhfive: that would be correct thanks
[21:29] <murdok> Arby: to unduplicate click mark as duplicate and then remove the bug number
[21:30] <Arby> thanks
[21:30] <murdok> you are welcome, I learnt it yesterday
[21:30] <murdok> :p
[21:30] <murdok> P
[21:35] <bdmurray> _Zeus_: why do you think it should be Invalid?
[21:36] <_Zeus_> bdmurray: do you think it shouldn't?  I think it should, because it's not supposed to show up until 8.04 anyway
[21:37] <bdmurray> _Zeus_: Yes, I think it shouldn't.  9.04, which I'm guessing is what you meant, will be tracked in LP too so the bug would get resolved later.  There is no need to invalidate it.
[21:38] <_Zeus_> bdmurray: u meant 8.10
[21:38] <_Zeus_> and it will show up in it, because it's part of GNOME 2.24
[21:38] <_Zeus_> at least from what i've heard
[21:38] <_Zeus_> *i meant
[21:39] <bdmurray> Regardless, the fact that it may or may not automatically show up does not make the bug Invalid.
[21:40] <_Zeus_> ok
[21:40] <_Zeus_> i confirmed it
[21:40] <bdmurray> Additionally, since 8.10 is past feature freeze its unlikely that a new release of Ekiga would make it in.
[21:41] <_Zeus_> i know the new version of gnome will make it in, right?
[21:44] <bdmurray> yes, I believe so
[21:45] <_Zeus_> http://library.gnome.org/misc/release-notes/2.24/
[21:47] <_Zeus_> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/274144
[21:47] <_Zeus_> why is this status high?
[21:47] <_Zeus_> i don't even think that's a bug
[21:48] <Stemp> I have a problem with bug 260918 it is a need-packaging, and it's waiting for Debian. Is there's a way to cut this dependency ?
[21:49] <bdmurray> Do you know who either of the people in that bug report are _Zeus_?
[21:49] <_Zeus_> no idea
[21:49] <bdmurray> _Zeus_: https://wiki.ubuntu.com/DeveloperResponsibilities might be helpful
[21:50] <_Zeus_> crap
[21:50] <_Zeus_> well, it's never been there before
[21:51] <danbhfive> Stemp: I think its because debian is working on it
[21:51] <_Zeus_> i never thought that was a bug
[21:52] <Stemp> I understand that danbhfive, but in fact we don't have time to wait. If libv4l is not included, that mean : no webcam applications for gspca users
[21:55] <danbhfive> Stemp: well AFAIK, it being dependent on the debian bug doesnt mean that someone else CANT do it.  But that would be duplicating work.  So, you just have to find someone with the knowhow and time to do it.  The dependency just means that someone decided to let the debian devs take care of it...
[22:00] <Stemp> So I guess It's not a bug problem. We need to report bug on every webcam apps to include libv4l handling, and libv4l is perhaps not going to be intrepid ^^
[22:01] <danbhfive> Stemp: am I correct in thinking that libv4l wraps v4l into v4l2?
[22:03] <danbhfive> nvm
[22:03] <Stemp> not only danbhfive, it also convert pixelformat for v4l2
[22:31] <kees> sbeattie: can you push to get the hardy-proposed kernel into -updates?  it's been in there a while now, and I'm not sure what's blocking it.
[22:33] <Stemp> Hi all, sorry if i'm in the wrong channel. I'd like to talk about the gspcav2 driver and about the webcams apps. There is a serious problem about the packahe libv4l not in Debian (so not in Intrepid). Is it the right place to talk about it ?
[22:34] <Stemp> sorry wrong place
[22:52] <bdmurray> sbeattie: do you have a hardy live cd environment handy?
[23:11] <sbeattie> bdmurray: sorry, was grabbing fud. What do you need?
[23:11] <bdmurray> sbeattie: I'm working on checking it myself - thanks though ;)
[23:20] <hggdh> bdmurray, ping
[23:25] <bdmurray> hggdh: pong
[23:26] <nellery> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500000
[23:27] <nellery> 500000 bugs in Debian!!
[23:27] <bdmurray> bug reports, not bugs ;)
[23:28] <greg-g> and Launchpad is over halfway there, 274182 as of right now
[23:28] <nellery> but Ubuntu is at a little under 220000
[23:34] <hggdh> bdmurray, I sent you an email with a first approach on tags for bug stati (this one specifically for 'Invalid'). Please comment
[23:41] <greg-g> oh all those bug stati ;)
[23:43] <hggdh> or statuses... but -- for me -- statuses is as bad as campuses ;-)
[23:43] <greg-g> I have been on many college campi?
[23:48] <maco> greg-g: how about campiz
[23:48] <maco> ?
[23:48] <maco> the buildings probably don't wobble though...
[23:48] <bdmurray> groan
[23:49] <maco> i like puns...
[23:58] <hggdh> maco, I propose campizes