2 months ago
It seems that supertux analysis got negative line count before 2006: http://www.ohloh.net/projects/supertux/analyses/latest
Why does Ohloh think this and when will the issue be fixed? The point in time that the line count turns positive is about the same time (I think) as the repo was converted from CVS to SVN if it matters.
2 months ago
Hi AnMaster,
The negative line count problem was fixed a while ago -- the problem is that we need to reanalyze the entire project history for the fix to be reflected in the report. We've been steadily recounting all the code on Ohloh, but it takes a while.
I've bumped supertux to the front of the recount queue, so it should get an update today.
2 months ago
Ah thanks nice to know.
2 months ago
However now it says:
http://supertux.lethargik.org/svn/supertux/trunk Subversion Step 1 of 3: Downloading source code history (Failed)
We had some issues with anon svn yesterday but they were quickly fixed, I guess you have to restart your re-download or something.
2 months ago
I restarted the download. I'll keep an eye on it today.
2 months ago
Hmm, after a recount it looks like we still show the negative lines of code problem. The problem may not just in our analysis; it might be that our original download of the code history is corrupted.
I've scheduled a clean re-download of the history. This will probably take a few days to go through.
2 months ago
Odd. If the history is corrupted, svnadmin verfiy doesn't find it at least...
2 months ago
Sorry AnMaster, I should have been a little more specific.
There's very likely no problem in your repository; something just went wrong on our end.
A project goes through a lot of steps before the report appears on Ohloh. First we create a local mirror of the repository on our servers. Then we parse the log and store that in the our database. Finally, we count the lines of code to compute the reports.
When something goes wrong, the cheapest thing for us to try is the last step only: the count. If that doesn't clear it up, we can back up one more step and try reimporting the log from our local mirror. Finally, if none of that cleans up the problem, it means that our local mirror is corrupted.
Recreating our local mirror is painful because it can take a long time to re-download the entire project history to our servers. That's where we are now with SuperTux,
It's taking a while, but the download is proceeding. It should take a couple more days.
Robin