I have encountered similar error when updating to 2.6.24.16 to 2.6.24-17 using the automatic updates. Can someone tells me why this had happened.
I have encountered similar error when updating to 2.6.24.16 to 2.6.24-17 using the automatic updates. Can someone tells me why this had happened.