Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Ohloh fails to refresh code from upgraded sourceforge subversion...
Hello all. I have a problem.
Since I upgraded the repository of the K-Framework project in SourceForge, Ohloh reports failure to read the repository. I have checked the user and url with netbeans and rapidsvn, and I can browser the code with no problems. Since there is no more detailson Ohloh message Im not sure what can I do. Some advice will be appreicated...
-Alex
Sourceforge is an old tool that begins seriously to rust, I have seen may others enlistment to fail, I even attempted to message the sf team to fix the repo of the SpamBayes svn project that returns an error when attempting to download old logs, no response..., as ohloh user my advice would be to move your project on googlecode that offers more visibility and more tools, ie, anything goes wrong with your repo? no problems, click reset it and svnsync.
Hello Arnaud.
Actually, everything was ok with SF until the subversion was upgraded, a few months ago.
I had to relocate my copies and all that, and it all went very well.
I can develop using the new repo with netbeans, eclipse, rapidsvn etc...
It's only Ohloh which can seem to read the repo.
.. and, in the other hand, SF might be old and all that, but fact remains that a sizable percentage of all open source projects are hosted in SF, specially non java stuff....
So, I think, this should work for Ohloh to work...
Well that's what I think...
.. either way, thanks for the comment.
Thanks ssnow
Out of desperation y re-did all the repository and created a new trunk, called trunk1. I am now going to proceed and fix the corresponding Ohloh settings. Should I wait ?? Anyhow the current setting points to trunk
, which no longer exists ...
I guess I should have waited for your feedback... sorry :)
-Alex
Alex,
Go ahead and add the new enlistment and be sure to delete the old one. I'll monitor the progress and if I see problems I'll let you know here.
Thanks!
Hello ssnow
... this is not working. I mean SF. The new repo was a pain to load, with file and path errors everywhere.
Now it looks OK from rapidsvn, but while doing a test checkout I see that there are file checksum errors everywhere… Surely that’s why Ohloh could'nt read the repository.
I use to see these issues from time to time in SF, but the new
version is just plain unusable. Heck, my project is not that large…
I'm sorry to have bothered you. Until I can test a full checkout with out errors I would not expect Ohloh, or any one else, to be able to use it… maybe is time to leave SF, as the other poster commented.
Are you having these issues with other SF users ??
-Alex
Alex,
I'm not aware of any NEW problems with SourceForge but we do have continuing problems with OLD SourceForge subversions which are entirely our fault (and may be old history, I hope). Let me know here once you have your repository working to your satisfaction and I can monitor the process again.
Also let me know if you have any questions.
Thanks!
Great Thanks!
Alex,
Be aware that we have successfully analyzed the repository as it was before the changes. Any updates will fail, of course, but I did get a copy of it before the changes and I will print out the results as seen now to compare with the results you get once the repository is ready.
Thanks!