Recent Posts

Topic: Unable to import enlistment named hamcrest-c++

I was wondering if that might be the culprit. Problem fixed -- thanks!

Topic: How often does ohloh update a repository?

Hi,

http://www.ohloh.net/projects/10406 has not been updated since April 24. Anything wrong there?

Cheers, Erwin

Topic: Apache Synapse recently became a Top ...

Hi Jason

Thanks for your guidelines, I think I can again believe this is somehow possible now..

I tried your steps, but run into some issues.. btw this is my first time with git.. hope you can help me

asankha@asankha:~/GIT$ git-svn clone http://svn.apache.org/repos/asf/synapse/trunk/java synapse Initialized empty Git repository in .git/ W: Ignoring error from SVN, path probably does not exist: (175007): HTTP Path Not Found: REPORT request failed on '/repos/asf/!svn/bc/100/synapse/trunk/java': '/repos/asf/!svn/bc/100/synapse/trunk/java' path not found

After that it almost seems like its done.. or stuck.. and inside the synapse directory created, I see no files :(..

Can you try to replicate the Synapse repo to see if there is some problems with it?

thanks asankha

Topic: Issues with repositories using a different than standard repo layout (plain text patches and binary source tar ball)

It would be nice if you would be able to support the apparently non-standard layout used in some repositories that are provided to build Linux RPMs from, one of those examples is SME Server.

The repository layout is more or less like this:

• F/
• S/
• P/

Where:

• F/ contains a spec file used to build the RPM package
• S/ contains a zipped tar ball of the source (as a starting point)
• P/ contains patches against the zipped tar ball

I understand that this might be a bit harder than the more standard layouts containing plain text only. But due to build bots historically preferring/depending this layout the layout of the SME Server repositories are set up like this.

Due to the nature of this layout code count seems to go wrong as well as a lot off code is marked as Erlang, which is not used at all in this project.

Judging from the code count libs this is most likely because of the patch files starting with a - or a + sign, just like some Erlang lines might.

I know it might be a lot of work but would it be able to fix this so our code count and code determination is more accurate?

Kind regards,

Jonathan

Topic: Password Field in New Entlistment Page

The best option here is to find a public repository that doesn't require a username and password. Most open source repositories have anon public repositories that anyone can access, does yours not?

Topic: Password Field in New Entlistment Page

Hi Guys, great website here! I just expirenced some problems adding my svn server as entlistment because the page does not accept my password. I use some other characters than a-z/A-Z/0-9 and _

Could you please allow some more special characters?

Topic: WebKit line count failure

Judging by http://www.ohloh.net/projects/WebKit/, it hasn't managed to update successfully in quite a while. Looking at the enlistments page it appears to be failing while counting lines of code. Any ideas on what might be causing this?

Topic: Ohcount 2.0 beta

For those of you unaware, there is a new version of Ohcount in the making that uses the Ragel state machine engine for language parsing. It's faster and more robust. http://labs.ohloh.net/ohcount. It's getting some good testing on production servers, but I also encourage you to run it against your own code and report any bugs or miscounts.

Topic: Another enlistment failure

Well, it seems my request at the google-code-hosting list did not spark much interest over at Google.

However, I noticed that the Spiff repositories are now successfully downloaded frequently, so your force-download method probably worked. Thanks a lot for the effort!

-Samuel

Topic: Bad projects

Commercial open source projects should be allowed as there is nothing wrong with commercial free software.

But I really wouldn't like to see non-free projects in Ohloh.