[00:26] <bsmartt`> ok great! I have been approved to join the bugsquad team on launchpad.  What is the next step I need to take to get assigned a mentor? Just wait? I've completed all the requirements that I found online.
[00:34] <bsmartt`> one question I already have is I've noticed from a number of bug reports I've looked at often triagers ask the reportee if they've confirmed this bug is reproducable with the nightly build, as a dev will I need to be doing nightly builds? If so, is a vm good enough?
[00:42] <charlie-tca> bsmartt`: no, you are not required to do nightly builds as a bugsquad member.
[00:43] <charlie-tca> bugsquad attempts to get the bug report ready, so that when the developer gets it, he/she does not have to try to get enough information to work it. It should already be there for them.
[00:44] <charlie-tca> As a dev, you would be the one getting the report after bugsquad finishes with it, normally
[00:44]  * charlie-tca is not a developer, and doesn't really know what they do.
[00:47] <bsmartt`> ok.  thanks for clarifying
[00:47] <charlie-tca> Since bugs are normally fixed in the latest development release first, asking if the bug is still present in the development release verifies if the bug is still there.
[00:49] <bsmartt`> right, I figured that to be the case.  So then it would be quite handy as a triager to have the latest dev release to try to reproduce the bug for them if they can not?
[00:49] <charlie-tca> Many times the bug will be fixed/not present in the development release, so the developers can look at a diff and find how to fix it easily
[00:50] <charlie-tca> or decide that it will not be fixed in stable releases.
[00:50] <bsmartt`> i see
[00:51] <charlie-tca> Yes, many of us do use VBox to check the bugs in the latest development release, if the reporter is unable and we have the time.
[00:56] <mandarg> charlie-tca: Is there a place where you can get pre-compiled vbox images of the daily builds so you don't have to install them repeatedly in virtualBox?
[02:13] <hggdh> no, and this would actually not make much of a sense. We need to test *installation* and usage, not only usage
[02:15] <maxpolk> Should I add a comment to the end of a perfect match bug, that it applies to an all new DistroRelease?  Or open a new bug against the different DistroRelease where I'm seeing it as well?
[02:18] <maxpolk> I think maybe I should follow the advice "If you have further information about an already reported bug, add this information to the existing report, rather than opening a new one", even though it didn't match distro release
[02:20] <charlie-tca> maxpolk: normally, adding information to the existing bug report is great! If it is a bug against the kernel (linux), opening a new report is preferred.
[02:21] <charlie-tca> If the existing report is closed as fixed, adding information to it outside the release it was fixed in often complicates the issues and a new report is better.
[02:21] <maxpolk> new unassigned
[02:21] <maxpolk> thanks!
[02:21] <charlie-tca> Thanks for asking.
[02:23] <charlie-tca> hggdh: I am in complete complete agreement with that.
[02:23] <charlie-tca> and now, I will say goodnight to all :)
[02:23] <hggdh> g'night chalcedny
[02:24] <hggdh> darn, he was faster than me. Sorry for the wrong ping ^
[08:14] <njin> Hello guys, why if I run gdb (with or without sudo) to track aptd it return /usr/sbin/apyd not in executable format, i've tried with file or exec-file but nothing change. what i get wrong?
[08:14] <njin> *S apyd/aptd
[14:59] <Abhijit> hi
[15:00] <Abhijit> one user in #ubuntu wants to submit bug against newest kernel in natty narwhal. what is its package name?
[15:00] <Abhijit> vish, ping
[15:02] <nigelb> Abhijit: Usually, kernel bugs go to linux package.
[15:02] <Abhijit> nigelb, i mean the actual package name to be typed after ubuntu-bug
[15:03] <nigelb> That's what I meant. But I may be wrong.
[15:03] <Abhijit> np. i think they found another similar bug.
[16:50] <hggdh> yes, bugs against the kernel go to the 'linux' package