If you scroll down long enough, the procedure says that the bug has to be fixed in the "current development release" before it gets considered. Since I think it's going to be a while (at least until after the UDS to plan for Hardy+1) before development starts up again, I'd expect it to be at least a few weeks before this gets some love, especially since I think this particular package simply gets auto-updated from Debian unstable.
In the meantime, since I've been able to build a package with the fix, I'll see if I can figure out how to set up a PPA to get this out there.
(MOTU people: if my understanding of the process is wrong, please let me know!)
I can also confirm that Anton Blanchard's patch worked for me, and nahoo's did not, FWIW.
As to getting it fixed officially, they have a process for that: /wiki.ubuntu. com/StableRelea seUpdates
https:/
If you scroll down long enough, the procedure says that the bug has to be fixed in the "current development release" before it gets considered. Since I think it's going to be a while (at least until after the UDS to plan for Hardy+1) before development starts up again, I'd expect it to be at least a few weeks before this gets some love, especially since I think this particular package simply gets auto-updated from Debian unstable.
In the meantime, since I've been able to build a package with the fix, I'll see if I can figure out how to set up a PPA to get this out there.
(MOTU people: if my understanding of the process is wrong, please let me know!)