BZFlag enlistment is stuck (on download)

BZFlag migrated from CVS to SVN on sourceforge, so we removed the existing CVS enlistment and added our SVN enlistment a few months ago. To date, the enlistment has still not completed and I'm just now getting around to making this request to give it a kick.

I remember there being a thread many months about having to manually accept sf https svn certificates manually, but of course dont' know if that's still an issue or if it's simply because the original enlistment failed and it's just been stuck ever since. We would, however, really like to see the stats back in sync.

BZFlag's enlistment is at http://www.ohloh.net/projects/189/enlistments. As always, thank you very much for your help and for providing such a great resource to the community!

Cheers!
Sean

Hi Andy and.. hrmph. Well, good to know -- thanks. I'm not sure what that error exactly means just yet, but I'll look into it and see if we can't fix whatever is causing that result.

Cheers!
Sean

Robin,

Thanks for the link to that post with the trick to fix our svnroot. Our repository is hosted on Sourceforge so there's a bit of an indirection that I have to work around to get at the svnroot in order to fix the files, but I think that is the way we should go so that it works down the road. It'll just be a while, but I'll post a note here when it's ready for reenlistment.

As for how the .svn dirs got in there -- someone working on code in an local svn repo committed a checkout of their files (including the .svn dirs accidentally, of course) to our CVS repository when it came time to bring it in. CVS of course doesn't care, and when our repository was converted over to SVN, cvs2svn didn't care. The history was actually preserved even though the other svn commands don't like it.

Nice forethought on getting him to report the trick he used so you'd know for others. Given the breadth of details you're seeing across a landscape of thousands of projects, you guys could probably write an interesting book.

Cheers!
Sean

Andy/Robin,

Our SVN root should now be fixed. We applied pretty much the same technique as the Adium guys, except as it applies to a Sourceforge repo. Please give our enlistment another kick and hopefully it should complete this time. I tested with version 1789 and had no problems. Thanks again for pointing out the problem in our repository as well as to the fix! It'll be nice to have our stats online again.

Cheers!
Sean

Robin/Andy,

Thank you again so much for your efforts in getting our stats back on-line. Looks like the report took about 12-18 hours total but it did complete and we seem to be good to go now. It's also comforting to know that our root is now "repaired" for future operations. We'll probably want to sort out a few incorrect license detections later, but for now I'm quite satisfied and glad to see it tracking project stats again. Let me know where to send the beer.

Cheers!
Sean