[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: reassigning bugs

On Fri, Mar 25, 2005 at 09:33:22AM +1100, Matthew Palmer wrote:
> On Thu, Mar 24, 2005 at 05:54:36PM +0100, Arjan Oosting wrote:
> > I am thinking about reassigning the bug to libgtk2.0-0. Are there any
> > guidelines about how to do this? Should I include more info by sending 
> > an email to 301123@bugs.debian.org?   
> You should send a message like this to control@, Ccing
> libgtk2.0-0@packages.debian.org, so the maintainer of the recipient package
> gets it:
> ----8<----
> reassign 301123 libgtk2.0-0
> thanks
> I have spent some time hunting down this bug, and I think it's a bad
> interaction between sawfish and libgtk2.0.  I tested this by <blah> and
> <blah>, and got the following strace/backtrace output:
> <more explanation to follow>
> ---->8----
> By doing this, you're making as sure as you can that the maintainer of the
> package you're reassigning to doesn't think you're just foisting the bug off
> onto them because you don't know how to fix it yourself.
> And be prepared for a game of bug tennis if the maintainer of libgtk2.0-0
> doesn't agree with your analysis... <grin>

Hrm, three remarks though:

- Since you say bad interaction between libgtk2.0-0 and sawfish, it
  could be either of them that has the bug, you don't know it. So:

  reassign libgtk2.0-0, sawfish

  (to reassign to both, once the maintainers find out which of the two
  has a bug, they can reassign it to the correct one)

- *always* cc the bug number itself (301123@bugs.debian.org) when
  putting more than just the control commands in a message, so it shows
  up in the bug log (important)

- No need to cc $pkg@packages.debian.org, since typically the mail to
  the bug number will be processed after control@ stuff gets processed
  (and so, the message will already go to the correct maintainers). And
  even if it is not so (the order of processing gets reversed), they
  will get the control@ reply, and can look in the buglog if they missed
  the mail.


Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)

Reply to: