It would be interesting to see whether anybody has tested this bug on libboost1.40.0 from lucid, yet.
Is it still (going to be) an issue, or is it resolved on 1.40.0?
If so, then this bug would just "grow out". If not, then severe action is required in order to prevent another "broken" release on this issue.
It would be interesting to see whether anybody has tested this bug on libboost1.40.0 from lucid, yet.
Is it still (going to be) an issue, or is it resolved on 1.40.0?
If so, then this bug would just "grow out". If not, then severe action is required in order to prevent another "broken" release on this issue.