Ah right. So testing either Intrepid or Jaunty would verify that fix.
I'd still like to see this re-tested against Jaunty in any case, since upstream will want to know if this issue still exists in their 6.11.0 release before working on it.
Ah right. So testing either Intrepid or Jaunty would verify that fix.
I'd still like to see this re-tested against Jaunty in any case, since upstream will want to know if this issue still exists in their 6.11.0 release before working on it.