whoopsie does not upload UnreportableReason field in crash reports

An easy test case for the sending of UnreportableReason on a 14.04 system is downgrade multiarch-support to the version in the release pocket, while having -updates enabled, and then kill sleep. After the apport collection process is run you'll see the following in the report:

UnreportableReason:
 You have some obsolete package versions installed. Please upgrade the following packages and check if the problem still occurs:

 multiarch-support

Even if we don't use UnreportableReason to filter it'd still be useful to know apport's opinion of the bug report. We regularly see crashes that failed to retrace and contain the following in the retracer log file.

2015-11-03 10:58:59,824:19470:140298671347456:INFO:root:d54a5d64-8219-11e5-be9c-fa163e339c81:swift:Processing.
2015-11-03 10:59:00,046:19470:140298671347456:INFO:root:d54a5d64-8219-11e5-be9c-fa163e339c81:swift:Decompressing to /tmp/tmpS8eT8N-swift.d54a5d64-8219-11e5-be9c-fa163e339c81.oopsid.core
2015-11-03 10:59:00,188:19470:140298671347456:INFO:root:d54a5d64-8219-11e5-be9c-fa163e339c81:swift:Not a core dump per gdb.

apport does some checking of the core dump itself and if gdb is installed would add information like the following to the report.

 699 reason = 'Invalid core dump: ' + warnings.strip()
 700 self['UnreportableReason'] = reason

Having UnreportableReason in the Error Tracker would help us determine, in this specific case, if the core dump was already corrupt on the client or became corrupt during upload / saving to swift.

It'd also likely be useful in other cases that we aren't yet aware of.

This bug was fixed in the package whoopsie - 0.2.50

---------------
whoopsie (0.2.50) xenial; urgency=medium

  * src/whoopsie.c: Move UnreportableReason from fields we don't send to
    errors to fields we do, that way we know apport's opinion of the crash.
    (LP: #1382233)

 -- Brian Murray <email address hidden> Tue, 03 Nov 2015 13:30:52 -0800

Hello Brian, or anyone else affected,

Accepted whoopsie into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/whoopsie/0.2.24.6ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Brian, or anyone else affected,

Accepted whoopsie into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/whoopsie/0.2.47.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Brian, or anyone else affected,

Accepted whoopsie into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/whoopsie/0.2.49.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Brian, or anyone else affected,

Accepted whoopsie-daisy into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/whoopsie-daisy/0.1.34.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Valiantly verified via Vivid.

https://errors.staging.ubuntu.com/oops/a3ee54aa-8994-11e5-b0b0-fa163e1893a8

Timely testing in Trusty.

https://errors.staging.ubuntu.com/oops/67e35180-8995-11e5-a417-fa163e1893a8

Perfectly passed in Precise.

https://errors.staging.ubuntu.com/oops/34dde498-8996-11e5-a417-fa163e1893a8

Worked with-in Wily.

https://errors.staging.ubuntu.com/oops/0aa73368-8997-11e5-b0b0-fa163e1893a8

This bug was fixed in the package whoopsie - 0.2.47.1

---------------
whoopsie (0.2.47.1) vivid-proposed; urgency=medium

  * src/whoopsie.c: Move UnreportableReason from fields we don't send to
    errors to fields we do, that way we know apport's opinion of the crash.
    (LP: #1382233)

 -- Brian Murray <email address hidden> Mon, 09 Nov 2015 13:17:18 -0800

The verification of the Stable Release Update for whoopsie has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package whoopsie - 0.2.49.1

---------------
whoopsie (0.2.49.1) wily-proposed; urgency=medium

  * src/whoopsie.c: Move UnreportableReason from fields we don't send to
    errors to fields we do, that way we know apport's opinion of the crash.
    (LP: #1382233)

 -- Brian Murray <email address hidden> Mon, 09 Nov 2015 13:09:34 -0800

This bug was fixed in the package whoopsie - 0.2.24.6ubuntu2

---------------
whoopsie (0.2.24.6ubuntu2) trusty-proposed; urgency=medium

  * src/whoopsie.c: Send UnreportableReason to the Error Tracker that way we
    know apport's opinion of the crash. (LP: #1382233)

 -- Brian Murray <email address hidden> Mon, 09 Nov 2015 13:24:00 -0800

This bug was fixed in the package whoopsie-daisy - 0.1.34.1

---------------
whoopsie-daisy (0.1.34.1) precise-proposed; urgency=medium

  * src/whoopsie.c: Move UnreportableReason from fields we don't send to
    errors to fields we do, that way we know apport's opinion of the crash.
    (LP: #1382233)

 -- Brian Murray <email address hidden> Mon, 09 Nov 2015 13:34:23 -0800