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]
svn failed for OpenOffice.org
The svn enlistement for OpenOffice.org failed.
http://svn.services.openoffice.org/ooo/trunk
Subversion
Step 1 of 3: Downloading source code history (Failed)
Any idea what we can do?
Thanks
Hi stx12,
We had a server connection problem. I've restarted the download.
I'll warn you that with 187,000 revisions, this is going to take a while for Ohloh to download -- probably a couple of weeks.
I'll keep an eye on it until it goes through.
Thanks,
Robin
In this case, we use the following:
svn info # to determine whether our code is up-to-date or not
svn log --verbose --stop-on-copy # to get the list of commits
svn checkout # called once for every revision to get the code
It's brute-force, and it's slow, but it works. :-)
We do also have an alternate importer that uses svnsync to clone the entire repository locally. This is usually much, much faster, if the repository itself is mostly the code we care about (/trunk in this case) and does not contain vast amounts of other projects or branches. We could give that a try if you think it's appropriate.
Thanks,
Robin
Hi,
I just read the posting about development in branches. The OpenOffice.org repository moved in October 2008 from CVS to SVN and the most interesting area is /cws
http://svn.services.openoffice.org/ooo/cws/
So I removed /trunk and added /cws
You might want to consider a full copy to come to results in a reasonable timeframe.
Thanks, Stefan