[00:18] <emgent> heya
[00:22] <bdmurray> howdy
[04:34] <mrooney> hmmm, why are aptitude and apt-get so different for installing python-epydoc
[04:34] <mrooney> apt-get will install it juuust fine
[04:34] <mrooney> but aptitude wants to pull in 230 megs of deps for a total of ~500MB unpacked
[04:34] <mrooney> is that some sort of bug
[04:34] <crimsun_> no.  aptitude installs Recommends by default, too.
[04:35] <mrooney> oh, well is it a bug against epydoc that it recommends so much? that seems off
[04:35] <mrooney> but, maybe not!
[04:36] <crimsun_> no, it's not a bug in either aptitude or epydoc.
[04:36] <mrooney> crimsun_: okay, fair enough
[04:36] <mrooney> I'll just use apt-get for it
[04:37] <mrooney> thanks!
[04:37] <RAOF> mrooney: You can turn off the recommends-by-default logic on a case-by-case basis; I think it's --without-recommends.
[04:38] <mrooney> RAOF: thanks, that is good to know, I will probably do that
[04:38] <mrooney> I have never seen such a large set of recommends
[05:15] <bimberi> Installing devscripts on sid wants to bring in all sorts of things - citadel-common, x11-common, subversion, dillo, mysql-common to name a few.
[06:46] <bliZZardz> \/join #ubuntu-in
[06:46] <bliZZardz> err...sorry for that
[15:30] <bliZZardz> when a bug is a duplicate, then what should be it's status ?
[15:33] <bliZZardz> got it - thanks!
[15:44] <bliZZardz> if there is a known issue in upstream, then how should the bug be changed? should the status of the bug be changed to 'Confirmed'?
[15:46] <pedro_> bliZZardz: it should be Triaged, but if you don't have the permissions to set it, Confirmed is ok
[15:49] <bliZZardz> pedro_ : kindly have a look at Bug #241808, and let me know whether my response was right.
[15:54] <pedro_> bliZZardz: that's ok, also it doesn't seems to be an openoffice.org issue so you might want to reject that task
[15:54] <pedro_> hi Iulian
[15:55] <Iulian> Hello pedro
[18:14] <Ienorand> Anybody in here got some spare time to look at new attachments for bug #219584? /give instructions for further "research"...
[18:46] <persia> I'll be doing a class on interpreting apport retraces in about 17 hours, and wondered if anyone had a favorite apport bug with a good stacktrace to nominate for investigation during the session?
[18:59] <bdmurray> persia: bug 136371 maybe?
[19:01] <persia> bdmurray: That could work.  I tend to like longer traces (10 or more calls) as they are easier to explain.  Do you have an interest in that bug  specifically?
[19:02] <bdmurray> persia: not really just rss-glx seems to be a mess
[19:02] <bdmurray> a mess of apport crashes that is
[19:03] <persia> bdmurray: Makes sense.  I'll look about and see if I can find a more complex crash, hopefully in hardy.
[19:03] <persia> On the other hand, I'm guessing most of the problem is with GL issues, which are a little special :(
[19:03] <bdmurray> that particular one has some more recent duplicates
[19:04] <persia> 9!  Wow.  Now I understand why it's interesting :)
[19:04] <bdmurray> persia: will you be covering a python crash at all too?
[19:06] <persia> bdmurray: There's usually only time for one, and I have more experience with C than with python.  Do you have a good python candidate?  I'd be willing to do a python, as I've had a few of the same students at previous sessions, and they may like variety.
[19:06] <persia> (said differently: I'll do a python one if I can figure it out before class :) )
[19:07] <bdmurray> heh
[19:09] <bdmurray> displayconfig-gtk has a fair number of crash reports but I believe the application is deprecated so that might not be best
[19:14] <persia> Not only that, but it likely breaks because of issues with which video drivers support what operations.
[20:37] <bdmurray> pedro_: ping
[20:41] <pedro_> bdmurray: hi
[20:41] <bdmurray> Did you already have a hug day planned for tomorrow?
[20:41] <pedro_> bdmurray: nothing for tomorrow, I'm more looking to next week
[20:42] <bdmurray> pedro_: okay, great
[22:05] <LimCore> hello
[22:05] <LimCore> is this a good place to discuss general ubuntu "wish" idea?
[22:08] <danbhfive> LimCore: maybe brainstorm.ubuntu.com
[22:08] <LimCore> yeas I know it, ok
[22:09] <LimCore> but is it brainstorm really usefull? Most ideas get a lot of votes... and what then?
[22:09] <danbhfive> I dunno, I've posted several ideas in several places, and none have gotten any attention from anyone important
[22:10] <bdmurray> Developers have started responding to ideas on brainstorm
[22:10]  * LimCore is a developer too \o/
[22:11] <LimCore> If I'm awesome C++ devel, can I get $$$ for developing for ubuntu?
[22:11] <LimCore> any sponsorhip etc?
[22:11] <LimCore> *spelling