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

Re: forwarding bugs to other packages

>>>>> "Wouter" == Wouter Verhelst <wouter@grep.be> writes:

    Wouter> On Mon, Oct 18, 2004 at 10:19:18AM +0200, Gergely Nagy wrote:
    >> > I could just close the bug against my package, but this means other
    >> > people will encounter the same problem and report the bug against my
    >> > package again (as it isn't always obvious that it isn't the fault of
    >> > my package).
    >> How about merging those bugs with the bug reported against the correct
    >> package?

    Wouter> That's not possible. You can only merge bugs if /all/
    Wouter> properties (tags, severity, package reported against, ...)
    Wouter> are the same.

Why is this? I can open one bug against multiple packages, so I think
it should be possible to merge two or more bugs against different

Still, I can think of times when merging isn't
appropriate. e.g. consider:

bug report 1 package A: Program A segfaults.
bug report 2 package B: libb segfaults.

In which case, the 2 bug reports may highlight different aspects of
the same bug; while they are the same bug they are not the same. Bug 1
would list the details of the bug from the users perspective trying to
run A, but bug 2 is more likely to have extensive debugging
information proving the library is at fault.

Also, if I encountered a problem with A segfaulting, I would notice
the first title, but I might miss the second title (unless I knew A
was linked against libb).

When bug report 2 is closed, the maintainer of A may want to double
check to make sure that the bug really is fixed in A (maybe bug 2
wasn't the real cause after all), before 1 gets closed.
Brian May <bam@debian.org>

Reply to: