I released 0.8-0ubuntu2.2 to quantal by mistake before noticing that this bug was still verification-needed. However, I think that was artificial; 0.8-0ubuntu2.1 had already been copied to quantal-updates and was the version containing the fix for this bug; it's just that the .changes file for 0.8-0ubuntu2.2 was generated with respect to 0.8-0ubuntu2.
If this release was a problem, please let me know on IRC and we'll see what we can do about it.
I released 0.8-0ubuntu2.2 to quantal by mistake before noticing that this bug was still verification- needed. However, I think that was artificial; 0.8-0ubuntu2.1 had already been copied to quantal-updates and was the version containing the fix for this bug; it's just that the .changes file for 0.8-0ubuntu2.2 was generated with respect to 0.8-0ubuntu2.
If this release was a problem, please let me know on IRC and we'll see what we can do about it.