Additionally this bug suggests the fix was committed against the 2.6.20 package - was this really the case?
Additionally this bug suggests the fix was committed against the 2.6.20 package - was this really the case?