2 Sep 03, 2007 21:45
Same thing happened on my end, and I haven't made any major change in my installation—apart from updating to 1.10.
But then again, I've downloaded updates to the blacklist without any problems at all (at least three times) since I upped to b2evo 1.10 (which was like 1 or 2 weeks ago).
Maybe there's an error in the new blacklist file that causes b2evo to choke on it... who knows.
Anyone has a better idea of what may be wrong?