Apport 2.14.7
Milestone information
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- No users assigned to blueprints and bugs.
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- No bugs are targeted to this milestone.
Download files for this release
Release notes
* Adjust backend_
versions do not provide /etc/blkid.tab any more.
* Fix interpretation of core dump ulimits: they are in bytes, not kB.
(LP: #1346497)
* apport-retrace: Don't require specifying an operation; default to updating
the given .crash file. (LP: #1361242)
* Write report even on UnreportableRea
them. (LP: #1360417)
* apt/dpkg install_packages(): Write a "packages.txt" into sandbox root
directory to keep track of installed packages and their versions.
Prerequisite for LP #1352591.
* apt/dpkg install_packages(): Avoid re-downloading/
are already installed into a permanent sandbox. Prerequisite for LP #1352591.
* sandboxutils.py, make_sandbox(): Drop check for already existing files when
dynamically resolving libraries and ExecutablePaths; with that, these
packages would never get updated in a permanent sandbox. The new version
tracking from above now takes care of that. (LP: #1352591)
* Fix report.
"init", as one can specify a different one on the kernel command line.
* report.py, add_gdb_info(): Check for truncated core dumps, and set
Unreportable
apport-retrace and whoopsie-upload-all to fail properly instead of silently
producing broken Stacktraces. (LP: #1354571)
Changelog
This release does not have a changelog.
0 blueprints and 0 bugs targeted
There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.