Comment 2 for bug 763195

Revision history for this message
Mike Coleman (tutufan) wrote :

Looking further, the directory in question was actually corrupted, apparently due to either an I/O error or perhaps a kernel bug. In any case, I'm confident it has nothing to do with this package.