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]
An issue here:
https://www.ohloh.net/p/idthemes/enlistments
Thanks!
Marc,
Repo update for the git failed 1298 days ago. It appears that they began enforcing the need for a full, accurate repository path at that time or changed the addressing scheme. Added a new enlistment as seen on the Git page at SourceForge. Fetch finished OK (10 total commits). Now just waiting for four additional (svn, CVS) enlistments to update.
Thanks!
Marc,
A full update started one to two hours later and also finished OK (one or no added commits for all). Analysis is at March 04, 2013 on code collected on March 04, 2013 and last commit is at September 12, 2009 (confirmed with the web interface).
I notice that two of the svn: enlistments are redundant. I leave that exercise for you... (I'm trying to be circumspect.) Both are contained in the main subversion enlistment which is the one that contains the latest commit. Hmmm. I'll jog the manager and see what happens.
Thanks!