Forum Posts

these are all awesome ideas. Grrr - why must a day only contain 24 hours? ;-). dartar: Our code parser is decent, but a little primitive. I would love to upgrade to something more modern - and ... [More] definitely make it open source. Do you know anyone with reasonable parsing/compiling skills who would be interested in spearheading this effort? daniel: we have this data -- almost. For every file in every checkin, we know how many lines were added and deleted,by languange and by code/comment/blanks. The part that we don't know about is whether the lines deleted were previously your lines or someone else's. This means that we aren't able to determine, in a project, what percentage of the code is due to which developer. We know how many lines they added and deleted, but not how many they're responsible for. We'd need to run something like a 'blame' command and keep track, on a line-by-line basis, who editing who's code. I'd like to get there - its just something that keeps slipping under higher-priority issues. If someone could help us with the code parser - we might just get there sooner tho! [Less]

Ah, OK, so the checkout error is expected. It will take some time to convince our automated scripts to do all of this and get the code into our system, but after 1000 hours of server time I'm not ... [More] going to let a little thing like this get in the way of our report :-). [Less]

yes but after removing it (step 4) the update works fine :) [pterjan@plop tmp]$ rm -f test/syncupdatesnew__genhdlist2 [pterjan@plop tmp]$ svn update -r224133 test [...] Actualisé à la révision ... [More] 224133. (BTW, thanks for the time you spend on this) [Less]

Hi Pascal, This doesn't seem to work for me. During checkout, I get this error: svn: Failed to add file 'test/sync_updates_new__genhdlist2': object of the same name already exists ...which isn't surprising, since I just created that file.

Hi Shawn, I looked into Tailor about 18 months ago, and at that time it didn't seem like we could use it. Specifically, we needed two features: Lightning-fast updates of existing projects. At the ... [More] time, Tailor conversion seemed like a one-time process, and you couldn't pull in deltas of ongoing development. This looks like it has changed. Arbitrarily large projects. It takes us a while, but we can import projects of just about any size. For instance, any conversion tools built on cvsps (not sure if Tailor falls in this camp) are unusuable because cvsps just can't handle extremely long histories without oceans of memory and time. I might be wrong about Tailor, and it might be considerably improved since last time we checked. It really would make our life much happier if Tailor could be used for Ohloh. [Less]

Yes, this is a known limitation with our Subversion importer -- we don't follow any file copies or renames. I'd desperately love to get this fixed.

Yes, we are running about 3 weeks behind, and are slowly catching up. I'll schedule all of these projects for update today.

Thanks. I've seen the task rescheduled. But result seems to be the same (step 2 failed).

Here is the answer I got : [root@svn tmp]$ ls -la test/sync_updates lrwxrwxrwx 1 root root 28 Aug 27 16:24 test/syncupdates -> syncupdates_new__genhdlist2 Someone managed to import a symlink... ... [More] You can still checkout by: 1. mkdir test/ 2. touch test/syncupdatesnewgenhdlist2 3. svn co ... test 4. rm test/syncupdatesnewgenhdlis2 5. svn update test/ [Less]

Same here: http://www.ohloh.net/projects/6065/ - 21 days Thanks, Hagen.