Comment 9 for bug 657091

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apport - 1.15-0ubuntu1

apport (1.15-0ubuntu1) natty; urgency=low

  [ Martin Pitt ]
  * New upstream release. Changes since to our previous trunk snapshot:
    - Order symptom descriptions alphabetically. Thanks to Javier Collado.
    - Check $APPORT_SYMPTOMS_DIR environment variable for overriding the
      system default path. Thanks to Javier Collado.
    - testsuite: Check that crashdb.conf can have dynamic code to determine DB
      names and options.
    - test suite: Rewrite _gen_test_crash() to have the test process
      core dump itself, instead of using gdb to do it. The latter fails in
      ptrace restricted environments, such as Ubuntu 10.10.
    - Use launchpadlib to file a bug instead of screen scraping.
      The latter was completely broken with current Launchpad, so this makes
      the test suite actually work again. Thanks to Diogo Matsubara!
      that you can now specify "staging", "edge", or "dev" (for a local installation). Thanks to Diogo Matsubara!
    - backends/ Fix crash on empty lines in ProcMaps
    - doc/symptoms.txt: Fix typo, thanks Philip Muskovac. (LP: #590521)
    - apport/ rename ProcCmdLine to ProcKernelCmdLine to not wipe
      wipe out /proc/$pid/cmdline information. (LP: #657091)
    - apport/ attach_file() will not overwrite existing report
      keys, instead appending "_" until the key is unique.
    - Fix --save option to recognise ~, thanks Philip Mu┼íkovac. (LP: #657278)
    - Remove escalation_subscription from Ubuntu bug DB definition, turned out
      to not be useful; thanks Brian Murray.
    - Fix APPORT_LAUNCHPAD_INSTANCE values with a https://
    - apt backend: Opportunistically try to install a -dbg package in addition
      to -dbgsym, to increase the chance that at least one of it exists.
      Thanks Daniel J Blueman!
  * debian/control: Switch Vcs-Bzr: to natty branch.

  [ Brian Murray ]
  * data/package-hooks/ Drop regression-potential tag. We are
    moving away from using regression-potential as a tag in the management of
    regression bug reports. Instead we will tag bugs regression-release and
    then create series, release, tasks for the release affected if the bug is
    in fact a regression.
 -- Martin Pitt <email address hidden> Fri, 12 Nov 2010 14:59:01 +0100