Re: Maintainers, porters, and burden of porting

[Kurt Roeckx <kurt@roeckx.be>]

On Wed, Aug 31, 2011 at 04:30:56AM +0000, Felipe Sateler wrote:
> 
> I think some clarification needs to be done for these types of errors. I 
> sometimes get a (serious) bug reported against one of my packages because:
> 
> 1. python errored out with a glibc-detected error
> 2. gcc broke in some way (ICE, error -11, error -4)
> 3. swig failed with error -10
> 
> None of these are my package's fault. I wonder if reassigning to the 
> program erroring out is the right thing to do.

There should at least be a bug assigned to the package that
has the bug.  You can do an "affects" to indicate it affects
your package, and so it will also show up in the bugs for
your package.


Kurt