Comment 39 for bug 140051

Actually, putting these into gutsy-proposed before Hardy is doing things in the wrong order; gutsy-proposed should only be used for patches known to fix issues, and where you are working towards getting them posted as an SRU. From the descriptions, these patches change the failure behavior but don't solve the issue, so I would expect the SRU reviewers to reject it.

Generally, the order I prefer is to produce a one-off deb and/or ppa package, get a few people to validate it, then upload to Hardy for moderately wider testing. If after a few days in Hardy, it hasn't caused any mayhem, *then* it would be appropriate to put into gutsy-proposed, and work towards an SRU.

I can take care of doing all of that packaging work.

If you do wish to get this into gutsy as an SRU, please file two bug reports (one for each patch), with the following information:
  - Add to description a statement explaining impact of the bug to
    justify the backport
  - Explain how the bug has been addressed in the development branch
  - Point at the (small, unobtrusive) patch being proposed
  - Add to description detailed steps for reproducing the issue
  - Discuss regression potential and how users could be affected

(The above is from the SRU process at wiki.ubuntu.com).