[ubuntu/jaunty] apport 0.125 (Accepted)

[Martin Pitt]

apport (0.125) jaunty; urgency=low

  * bin/apport-chroot: Exit with apport-retraces' exit status, to
    propagate errors upwards to crash-digger.
  * bin/apport-retrace: Do not put outdated -dbgsym comments into the
    bug comments.
  * Rewrite bin/crash-digger to become much more robust and easier for
    retracer maintainers:
    - Now designed around cron-based maintenance: start, process all
      pending bugs, exit. This makes memory leaks irrelevant, and gets
      rid of all the logging, daemonizing, and looping code.
    - Adapt stdout/stderr reporting to be suitable for cron and
      redirecting stdout to a log file.
    - Use lock files to avoid overlapping instances and avoid damaging
      bugs with broken retracers after crash-digger failed.
    - Handle chroot upgrading, so that this does not need separate
      cronjobs any more.
    - Drop old -i option, replace with -D/--dupcheck which is a mode
      which *only* checks duplicates of Python crashes (no fakechroot
      handling).
    - Mark bug as retraced after apport-chroot retrace finished
      successfully; the process is robust enough now to avoid enless
      loops even if retracing fails.
    - Adapt test-crash-digger accordingly.
    - UbuntuSpec:apport-retracer-maintenance

Date: Fri, 09 Jan 2009 12:14:44 +0100
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
https://launchpad.net/ubuntu/jaunty/+source/apport/0.125
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 09 Jan 2009 12:14:44 +0100
Source: apport
Binary: apport python-problem-report python-apport apport-retrace apport-gtk apport-qt
Architecture: source
Version: 0.125
Distribution: jaunty
Urgency: low
Maintainer: Martin Pitt <martin.pitt at ubuntu.com>
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Description: 
 apport     - automatically generate crash reports for debugging
 apport-gtk - GTK+ frontend for the apport crash report system
 apport-qt  - Qt4 frontend for the apport crash report system
 apport-retrace - tools for reprocessing Apport crash reports
 python-apport - apport crash report handling library
 python-problem-report - Python library to handle problem reports
Changes: 
 apport (0.125) jaunty; urgency=low
 .
   * bin/apport-chroot: Exit with apport-retraces' exit status, to
     propagate errors upwards to crash-digger.
   * bin/apport-retrace: Do not put outdated -dbgsym comments into the
     bug comments.
   * Rewrite bin/crash-digger to become much more robust and easier for
     retracer maintainers:
     - Now designed around cron-based maintenance: start, process all
       pending bugs, exit. This makes memory leaks irrelevant, and gets
       rid of all the logging, daemonizing, and looping code.
     - Adapt stdout/stderr reporting to be suitable for cron and
       redirecting stdout to a log file.
     - Use lock files to avoid overlapping instances and avoid damaging
       bugs with broken retracers after crash-digger failed.
     - Handle chroot upgrading, so that this does not need separate
       cronjobs any more.
     - Drop old -i option, replace with -D/--dupcheck which is a mode
       which *only* checks duplicates of Python crashes (no fakechroot
       handling).
     - Mark bug as retraced after apport-chroot retrace finished
       successfully; the process is robust enough now to avoid enless
       loops even if retracing fails.
     - Adapt test-crash-digger accordingly.
     - UbuntuSpec:apport-retracer-maintenance
Checksums-Sha1: 
 4aeb7542a8b049e6cb2417f81a7efbe45d03e0a6 971 apport_0.125.dsc
 2560f1bf9a37b38807399f90bba90288a210fb46 208836 apport_0.125.tar.gz
Checksums-Sha256: 
 2f4cd44d9ce78a1f764314683796d0bb5a48c3ee17cacb0dec15013ef2406a1a 971 apport_0.125.dsc
 005f6f6a586a21f0008bf5335a8ecb0f1e0b6740c57e2cc4bb6a2d46d8f571ac 208836 apport_0.125.tar.gz
Files: 
 e7294455a588e01984d5ac38855bf917 971 utils optional apport_0.125.dsc
 824a8b4d645782234958f5a88402bdfd 208836 utils optional apport_0.125.tar.gz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAklnMbwACgkQDecnbV4Fd/LTpACgm15cwQUF23V1fpiKVefyLkYU
TakAoO0xRpsq1oRPzn/JATJrrImO9aTD
=YSAz
-----END PGP SIGNATURE-----