Comment 2 for bug 435316

This should be fixed in devel r9708 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/revision/9708>.

I can't find the above oops to verify whether this bug was caused by the corrupt data in our database producing invalid index files (in which case the work-around is already CP'd in production) or whether it's the result of the initial parsing error (in which case the fix is in r9708 which will be rolled out with LP 3.1.10).

I've chatted with Sebastien and he'll let us know if it re-occurs :)