Thanks for packaging the patch as a debdiff, that helps.
I see this is already fixed in Jaunty, so I'll close the development task for that.
Because Hardy is already released, the process for getting changes into it involves a bit more paperwork, and requires structuring the debdiffs slightly differently. They are targeted to 'hardy-proposed' instead of 'hardy', and the version numbering increments by .1's. I fixed up your debdiff accordingly and include it for your review.
I've also gone ahead and uploaded the fix to hardy-proposed so it'll be available for testing.
The 'paperwork' is described at https://wiki.ubuntu.com/StableReleaseUpdates - basically the process is to help ensure changes that go out to everyone are 100% regression free and fix issues that really do need fixed. I'll fill out the bits I know, could you please fill in the remaining blanks? That part is necessary (along with testing) in order to get the fix approved to move from hardy-proposed to hardy.
Heya Bruce,
Thanks for packaging the patch as a debdiff, that helps.
I see this is already fixed in Jaunty, so I'll close the development task for that.
Because Hardy is already released, the process for getting changes into it involves a bit more paperwork, and requires structuring the debdiffs slightly differently. They are targeted to 'hardy-proposed' instead of 'hardy', and the version numbering increments by .1's. I fixed up your debdiff accordingly and include it for your review.
I've also gone ahead and uploaded the fix to hardy-proposed so it'll be available for testing.
The 'paperwork' is described at https:/ /wiki.ubuntu. com/StableRelea seUpdates - basically the process is to help ensure changes that go out to everyone are 100% regression free and fix issues that really do need fixed. I'll fill out the bits I know, could you please fill in the remaining blanks? That part is necessary (along with testing) in order to get the fix approved to move from hardy-proposed to hardy.