Please backport sosreport 3.1-1ubuntu2 (main) from trusty

[Dimitri John Ledkov]

Please backport sosreport 3.1-1ubuntu2 (main) from trusty to precise.

Reason for the backport:
========================
* New upstream release
* New plugins
* Improved OpenStack plugins
* Python3 support
* Security fixes

Testing:
========
Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing.

You can test-build the backport in your PPA with backportpackage:
$ backportpackage -u ppa:<lp username>/<ppa name> -s trusty -d precise sosreport

* precise:
[ ] Package builds without modification
[ ] sosreport installs cleanly and runs

No reverse dependencies

[Iain Lane (laney)]

They want to backport the trusty SRU, which is in unapproved currently.

This build-depends on dh-python which Precise doesn't have.

[Dimitri John Ledkov (xnox)]

There is no ongoing trusty SRU for sosreport, and no sosreport in trusty unapproved.
https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=sosreport

This bugreport is for tracking purposes, and is being worked on. Hence the two ticks are not marked as done yet, for "builds without modification" and "installs cleanly and runs".

[Dimitri John Ledkov (xnox)]

Can the bug status be reverted back to New please?

[Dimitri John Ledkov (xnox)]

(this is not a "Confirmed" backport, and thus is not ready for review by Backports team yet.)

[Iain Lane (laney)]

On Wed, Jul 09, 2014 at 09:10:30AM -0000, Iain Lane wrote:
> They want to backport the trusty SRU, which is in unapproved currently.

I meant Saucy.

I have actually been talking to cairbou about this, and sponsored the
SRU that's going to be backported, so I'm a bit surprised to see this
one pop up.

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

[Louis Bouchard (louis)]

Indeed this is a follow up from the Saucy's SRU & backport request.

Saucy will be EOL in a few days. This request is to take care of the future so sosreport in Precise does not goes incredibly out of sync

[Iain Lane (laney)]

It sat around in the SRU queue for long enough that saucy went EOL and now we can't go down this route.

So we have to figure out the source change backport route.

[Louis Bouchard (louis)]

This is ridiculous; this package has been uploaded twice and yet nothing happened. We will find a better way to get fixes to sosreport without waiting ages

[Louis Bouchard (louis)]

No longer a valid request, sosreport 3.2 is now available. Marking it Invalid.