Me again. :) ohloh reports now that all 3 DeVIDE enlistments have gone through. However, it's clear from the commit history and the code analysis that only the two very small C++ enlistments have ... [More] been analysed, and not the main Python enlistment. Should I give up on this? Thanks again. [Less]

Hi there! Have you had time to take another look at this? Thanks, Charl

Thanks again for diagnosing this! It doesn't ring any bells, please start the import over.

Thank you very much!!

Thanks for looking into this! Apparently I accidentally checked in that PYC file years ago, also with the svn:eol-style native property, hence the error you're seeing. Although I also removed that ... [More] file a long time ago (it's a generated binary and should not go into SVN), it's obviously still in the history. This is the discussion as it happen on googlecode: http://groups.google.com/group/google-code-hosting/browse_thread/thread/6ce6ba3bbc6d73fa So, the history can't be changed. Is there anything else that can be done, except for just accepting that the DeVIDE repo can't be analysed? Thanks again, Charl [Less]

Hi there, Since yesterday, the enlistment of the main #DeVIDE SVN repository ( http://devide.googlecode.com/svn/trunk ) is stuck at "Step 2 of 3: Importing source code into database (Failed)" It's ... [More] now 24 hours since I added this enlistment. Could you take a look at it? Thanks! cpbotha [Less]