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]
The subversion repository for our project is not updating, although the URL has been active. The only issue might be that is uses a self-signed SSL certificate. Could this be the problem?
Here's the project:
https://www.ohloh.net/p/sc-codebase
And the SVN URL:
https://svn.strangecode.com/codebase/trunk/
Quinn,
Rescheduled the update which failed 711 days ago. Ohloh update completed about 10 hours ago.
It finished OK (23 added commits). Analysis is now at July 02, 2013 on code collected on July 02, 2013 and last commit is at July 01, 2013.
Please keep an eye on it for me and remind me here if the updates fail again.
Thanks!
P.S. The self-signed cert theoretically shouldn't be an issue but the error message from subversion is less than helpful: "svn: OPTIONS of 'Your_Repository/trunk': 200 OK (Grrr!) The re-try on my workstation didn't give a peep and I used the same command including --trust-server-cert so I think it's a non-issue. Just indigestion.
Thanks ssnow!