MaxReports not honoured

Bug #1254499 reported by Luke Faraone
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Fix Released
High
Michael Vogt

Bug Description

Setting «APT::Apport::MaxReports "100000";» or similar (without "") still results in log messages like this being printed on package installation errors:

No apport report written because MaxReports has already been reached

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 0.9.13~exp1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-52.78-generic 3.2.48
Uname: Linux 3.2.0-52-generic x86_64
ApportVersion: 2.12.7-0ubuntu1
Architecture: amd64
Date: Sun Nov 24 14:02:00 2013
InstallationDate: Installed on 2013-03-18 (251 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214)
SourcePackage: apt
UpgradeStatus: Upgraded to trusty on 2013-11-23 (0 days ago)

Related branches

Revision history for this message
Luke Faraone (lfaraone) wrote :
Michael Vogt (mvo)
Changed in apt (Ubuntu):
status: New → Confirmed
assignee: nobody → Michael Vogt (mvo)
importance: Undecided → High
status: Confirmed → In Progress
Michael Vogt (mvo)
Changed in apt (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apt - 0.9.14.1ubuntu1

---------------
apt (0.9.14.1ubuntu1) trusty; urgency=low

  * Merge from debian/sid
  * disable autopkgtest for now until it can test the installed
    packages and not only the build-tree (thanks to Martin Pitt)

apt (0.9.14.1) unstable; urgency=medium

  * fix apt-get source -t dist regression (closes: #731853)
    and add testcase
  * clarify error message when apt-get source=ver fails
    (thans to David Kalnischkies)
  * Fix conffile prompt regression (LP: #1260297)
    and add testcase
  * improve error message for apt-get source pkg:arch{=ver,/release}
 -- Michael Vogt <email address hidden> Thu, 12 Dec 2013 21:19:49 +0100

Changed in apt (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.