On Wed, May 09, 2007 at 11:01:36PM +0100, Neil Williams wrote:
> I can't see how this can be deemed "important" - perhaps the automated
> tool should be less paranoid. I built, tested and run gpe-timesheet ON
> amd64 and have done for the entire time it was waiting in NEW.
> 
> There is no way that the automated message can claim that this "problem" :
> "will cause
> your package to segfault on architectures where the size of a pointer
> is greater than the size of an integer, such as ia64 and amd64."

The scanner is automated, I manually write the messages and formulate
the patches.

> That simply is not true.

Are you sure? Have you executed a code path that makes use of the
pointer returned by this function? If you do, it should segfault
because your pointer has been truncated. If not, I'd be interested in
examining the problem further since this would be the first known
instance.

> It's a minor problem and a minor bug. If a real user can demonstrate a
> problem then that would be different but this automated tool is out of
> line.

If its a codepath that is never going to be taken then sure, its minor
- feel free to downgrade. But in the majority of instances these bugs
are likely to cause segfaults and therefore deserve at least an
important severity (which isn't even release critical, mind you).

I simply don't think its worth the effort of reviewing every potential
codepath to see how likely it is that a user will hit it because
there's no question that these issues are bugs and in most cases will
cause software to crash - and they are typically very simple to
fix. And $deity forbid we fix an issue *before* a user hits it!

In the ~2 years and ~200 bugs, you're the first maintainer to respond
rudely (and extremely rudely) about it. I certainly don't see what's
so offensive about someone spending time examining your package for
potential problems and even providing you with a patch! I hope you're
just having a bad day and not simply a fulltime jerk.

-- 
dann frazier



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to