[MERGE] use apport to get richer detail in bug reports.

Aaron Bentley aaron.bentley at utoronto.ca
Tue Nov 21 12:28:13 GMT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
>> By the way, this seems like a rather developer-hostile patch.  I *want*
>> to see the traceback and this is making it more difficult to see.
> 
> Yes me too.  I saw you wanted to just revert it untill it was fixed,
> which would be ok.

Great.  I've submitted that.

> Here are some things we could do:
> 
>  * have a clear developer mode, where tracebacks are always shown
>    without trimmings -- might be bad if the behaviour diverges too much
>    though

Since apport won't be universally installed, there's going to be
divergence anyhow.  I'd just like my Ubuntu machine to behave the way my
Debian machines do.

>  * keep the message but make it small enough that it's not a burden, say
>    two lines -- would that be ok?

Reducing the size would help, but the main thing for me is showing the
traceback.  I think I would tolerate an environment variable or one of
these -D flags, if I could just do 'alias bzr="bzr -Dtracebacks"', or
something like that.

>  * always write a file even if we don't have apport, just with different 
>    content -- I think Robert agreed in principle

Which then raises the question: isn't it better to have the same content
and not use apport?

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFYvDd0F+nu1YWqI0RApO1AJwMUmIfoHg/cMkoKZNjcOVdRriKrACghgMB
6Bv6IP1jNiKbIW8kIlBEyZE=
=4Tbj
-----END PGP SIGNATURE-----




More information about the bazaar mailing list