On 30 March 2010 17:48, Martin Pitt <email address hidden> wrote:
> The branch looks okay to me. I just don't understand why bzrlib/crash.py
> would need to set CrashDb, SourcePackage, and Package fields? The latter
> two are done during post-processing in the Apport UI, and the apport
> hook sets CrashDb already.
If the SourcePackage and Package are not recorded, it seems to also
fail as in 528114: apport counts on them being there.
On 30 March 2010 17:48, Martin Pitt <email address hidden> wrote:
> The branch looks okay to me. I just don't understand why bzrlib/crash.py
> would need to set CrashDb, SourcePackage, and Package fields? The latter
> two are done during post-processing in the Apport UI, and the apport
> hook sets CrashDb already.
If the SourcePackage and Package are not recorded, it seems to also
fail as in 528114: apport counts on them being there.
-- launchpad. net/~mbp/>
Martin <http://