[TEST IGNORE] testing apport vs sosreport

[Manoj Iyer]

Test collecting apport data vs sosreport for ppc64el.

== Using apport-cli (apport-collect) ==
The information collected for linux kernel on the ppc64el system. apport-collect and apport-cli should be installed on your system by default.

$ sudo apt install ppc64-diag

Note: ppc64-diag is needed for collecting information on kernel package.

$ sudo apport-cli -f --save /tmp/1717970.apport -p linux-image-4.10.0-35-generic

currently apport-cli does not support submitting .apport files to existing bug reports (Bug #1208508) using apport-cli. But you can attach the .apport file to the bug report instead as an attachment, developers can use apport-unpack ($ sudo apport-unpack /tmp/1717970.apport /tmp/report/) to unpack the attached file and get the information they are looking for. You may also want to consider compressing the .apport file after it is generated, as apport-cli does not support generating compressed files directly like sosreport does.

== using sosreport ==
$ sudo apt install sosreport
$ sudo sosreport

We prefer using apport-cli to collect information, this is leaner and collects all the relevant information that would help developers fix bugs in a given package.

[Manoj Iyer (manjo)]

This information was collected from ppc64el system using apport-cli.

[Manoj Iyer (manjo)]

sosreport generated on the same ppc64el system. As you can see the information contained is not package specific, and has a larger file size.