On Wed, Aug 08, 2001 at 09:36:03AM -0700, Ian Zimmerman wrote: > > I recently filed a bug with, in my opinion, quite sufficient > documentation. At least the level of documentation was such that had > been routinely accepted with other bugs I'd filed in the past. In a > subsequent update, I even enclosed all the input files that caused the > erroneous behaviour, verbatim. Nonetheless, the maintainer closed the > bug with a dismissive and supercilious comment (on record in the BTS), > citing as reason that the input files "are not part of Debian". > > Now, the package in question is a development package, a kind of > compiler, one might say. Imagine hitting a bug in gcc, like the one > that made all Linux kernels redundantly include -fno-strength-reduce > in CFLAGS for eternity, documenting it with the C source and the > erroneus assembly output, and being told that it is not sufficient, > that you should actually debug the monster of a program that gcc is > with gdb. To me this would seem absurd, and so does the present > case. > > What do you think? Please reply to me even if you choose to copy to > the list (feel free to do that).
I think you are being too vague for anyone to give an opinion. Remember, maintainer's aren't necessarily expected to know all the ins and outs of the upstream code. If that's where the bug lies, then maybe you'll get approriate results from upstream developers (who presumably know the code base much better). -- Eric G. Miller <egm2@jps.net>
