Forum Posts

Showing page 1,813 of 2,074
Post Title Author Date Views
RackTables repo resync

Hello. May I request, that RackTables project commit history be discarded and re-imported from scratch? The repository was migrated (which also involved some filtering of unrelated history) to ... [More] SourceForge around a year ago, and Ohloh could not handle that. There should be 6 contributors on the timeline after the resync, and the most recent commit was made today. Thank you. [Less]

infrastation  over 2 years ago 246
RackTables repo resync

Infrastation, I can re-import the repo as requested, but cannot be sure all history will be discarded. It is my guess that what you want will be achieved but I'll only know once the re-fetch is ... [More] done. I'll start on this in one hour, but check in with me here if you want to add anything. Thanks! [Less]

ssnow-blackduck  over 2 years ago 246
pysoy stopped updating 7 days ago

http://hg.pysoy.org/pysoy is marked as failed 7 days ago and for some reason ohloh doesn't seem to be trying again. Can you give it a kick? Thanks

ArcRiley  about 2 years ago 364
Language detection / custom languages

Is there a policy or plan yet on how to deal with custom file extensions / content? Our project, Vexi, has 30k lines of Perl and 30k lines of XSL according to Ohloh: ... [More] https://www.ohloh.net/p/vexi/analyses/latest Actually it has neither. It has a custom XML+JS format kept in files with a .t extension. They should really be reported as XML or JS or a hybrid of the two or even as VexiCode since it is very specific to Vexi and there's several Vexi-based applications appearing now. We also have a Java-like *.jpp type of file that is a pre-processed format of Java (support for macros and other stuff). From what I can tell, ohcount correctly identifies this. Is it worth me making a patch for ohcount that detects VexiCode? (VexiCode being Vexi's XML+JS.) It's simple enough - file extension of .t and a root node of <vexi> - and applies to multiple projects (there's several on ohloh now with VexiCode). [Less]

charlie  over 2 years ago 528
VTK enlistment failing for 22 days now

VTK updated when you rescheduled, but does not seem to have updated since. 17 days now, whereas many other projects I work on seem to update daily. Is there an issue with the VTK enlistment? ParaView ... [More] says that it failed 7 days ago, but I am not sure why that might be. Are there any specific issues Ohloh is having with our git repositories? Thanks for looking into this before, and anything you can do to remedy the current issue. [Less]

cryos  over 2 years ago 494
EGroupware enlistment (svn) stoped working 7 month ago

Thanks for the quick fix :) Ralf

RalfBecker  over 2 years ago 560
montone -> git

I´m trying to set up a git clone of a monotone repository, so that we can get good data into ohloh, but I´m having a bit of a problem.. The incremenal updating of git from monotone fails, so I´m ... [More] wondering if it will be OK to point ohloh at a git repo that is re-created from scratch every time we update it from monotone ? i.e. rm -rf repo.git; git init; mtn --db db.mtn git_export | git fast-import; [Less]

janfrode  over 2 years ago 206
Charm++ enlistment failed 11 days ago

Abhinav, A local error here at ohloh caused the update to fail. Have started a re-fetch which completed OK. Following that, a complete update ran which brought the analysis up-to-date. Thanks!

ssnow-blackduck  over 2 years ago 278
Charm++ enlistment failed 11 days ago

Thanks!

bhatele  over 2 years ago 278
Embed stacks on GoogleCode

I'd like to embed my "jMonkeyEngine Stack" on our GoogleCode page. Is this possible?

erlend_sh  over 2 years ago 453
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.