Your message dated Sat, 6 Apr 2019 06:43:20 +0200 with message-id <[email protected]> and subject line apport was removed from Debian has caused the Debian Bug report #782203, regarding "dont create .upload file if report is incomplete" to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 782203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782203 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: apport Version: 2.16.2-2 Severity: important The way apport works to determine if a crash has already been reported or not, is by creating a .upload file for every successful report. But, in its current form in Debian, even if the crash is incomplete, and apport complains about its failure to send the report, it ends up creating the .upload file, thus ignoring further crashes from it. We need to intercept in between whether apport was able to determine the completeness of the crash report, and then, accordingly, create a .upload file, only when the report is submitted to the Debian BTS. In case of Debian crashdb, that'd mean after the email is formatted and submitted to the SMTP module. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.3-bfq+ (SMP w/4 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apport depends on: ii gir1.2-glib-2.0 1.42.0-2.2 ii lsb-base 4.1+Debian13+nmu1 ii python3 3.4.2-2 ii python3-apport 2.16.2-2 ii python3-gi 3.14.0-1 pn python:any <none> Versions of packages apport recommends: ii policykit-1 0.105-8 Versions of packages apport suggests: ii apport-gtk 2.16.2-2 -- Configuration Files: /etc/apport/crashdb.conf changed: default = 'debian-debug' databases = { 'ubuntu': { 'impl': 'launchpad', 'bug_pattern_url': 'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml', 'dupdb_url': 'http://people.canonical.com/~ubuntu-archive/apport-duplicates', 'distro': 'ubuntu', 'escalation_tag': 'bugpattern-needed', 'escalated_tag': 'bugpattern-written', }, 'fedora': { # NOTE this will change Fall '07 when RHT switches to bugzilla 3.x! 'impl': 'rhbugzilla', 'bug_pattern_url': 'http://qa.fedoraproject.org/apport/bugpatterns.xml', 'distro': 'fedora' }, 'debian': { 'impl': 'debian', 'distro': 'debian', 'smtphost': 'reportbug.debian.org', 'recipient': '[email protected]', 'sender': '' }, 'debian-debug': { 'impl': 'debian', 'distro': 'debian', 'smtphost': 'localhost', 'recipient': '[email protected]', 'sender': '[email protected]' }, 'debug': { # for debugging 'impl': 'memory', 'bug_pattern_url': '/tmp/bugpatterns.xml', 'distro': 'debug' }, } -- no debconf information
--- End Message ---
--- Begin Message ---Version: 2.20.4-5+rm apport has been removed from Debian/experimental, it was never part of unstable. See https://bugs.debian.org/924960 for details on the removal. I'm therefore closing the remaining bugs. Andreas
--- End Message ---
