Results 0 - 10 of 2,473.

39 VIEWS

Hi rlg, It looks like there were some nasty data corruption errors reported by the Subversion server during our last attempt. I've rescheduled the update, and so far it looks OK. I'll keep an eye on it today. Thanks, Robin

129 VIEWS

Never mind, I think I figured it out :-) An update is on its way.

129 VIEWS

Hi Daan, Yes, Ohloh works incrementally, and doesn't examine commits with old timestamps. I'm happy to schedule a clean download, which will get all of the project history from scratch. Ohloh is ... [More] currently tracking four repository directories. Which of the four require new analyses? Or should we just re-download all of them? [Less]

76 VIEWS

Hi Petr, It looks like we had trouble connecting to the Subversion server, and our system eventually gave up. It seems OK now, though, so I've rescheduled the updates. I'll keep an eye on it today. Thanks, Robin

54 VIEWS

OK, it's running now.

54 VIEWS

Hi John, Which repository? I can do a clean import.

54 VIEWS

Hi Jonathan, Yes, there was some trouble on our end. I've cleaned up the error and rescheduled the update. I'll keep an eye on it today. Thanks, Robin

163 VIEWS

Hi Aidan, Sorry for the very delayed response, and also for the problematic Ohloh UI :-(. I've cleaned up the name mappings, so you are now properly associated with your commits. The trouble here ... [More] is that aliases only work to map between currently active names -- aliases can't be used to map old, unused names from the old CVS. On your account profile page, there is a small "EDIT" link next to each project. This link takes you to a form where you can edit the committer name you use in the project source control. I used this form to change your name from the old CVS name to the new Git name, and now everything seems OK. Let me know if there's any more trouble. Thanks, Robin [Less]

558 VIEWS

Hi Ozan, I've rescheduled the update. I'll let you know if we encounter any errors. Thanks, Robin

226 VIEWS

Hi chorny, The kwiki enlistment was delayed. Our local mirror of this repository was corrupted, and I had to schedule a clean mirror. It might take a while. net-bittorrent appears to have been ... [More] rebased, so I've started a clean mirror of that repository as well. The others appear to have been blocked by some repeated connection issues. Things seem to be OK, now, so I've rescheduled the updates. I'll keep an eye on them. Thanks, Robin [Less]