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]
History is lost after converting from CVS to SVN
There are no commits seen on Ohloh for commits before the conversion from CVS to SVN. But svn log
does show them. Why is that so?
ohloh doesn't completely understand svn completely.
Does svn log --stop-on-copy
show the commits you are concerned about? If not this is your problem.
Sometimes errors (particularly character encoding errors) cause bugs like this. Can you view the svn logs around the time of the last reversion that made it into ohloh? An error in those logs can be the reason.
If the cut-off point is a point of conversion, a simple solution is to point ohloh at a copy of the old repository as a new enlistment.
Hi Mitar,
The problem for Ohloh occurs at revision 5608, when /branches/Qt4 was copied on top of /trunk.
Ohloh's Subversion importer is not capable of following directory renames or branches. This means that in Ohloh's eyes, the /trunk directory did not exist before revision 5608.
This is a limitation of our importer, and I do not believe there is any workaround on your end.
Oh why oh why I have then deleted the old repositories (which had those old commits)? Is it possible to get them back? (As that CVS repository does not exist anymore.)
Sorry, Mitar, this is not currently possible.
We probably do still have the CVS data, and could bring it back (you can do it as well yourself by going to the Edit History
page of the project and clicking Undo/Redo to bring them back).
However, if you do this, our system will poll the CVS server for the latest updates, and this will of course fail. Those errors will prevent our project report from ever updating. It's not currently possible to shut off updates for repositories that no longer exist.
These are all limitations of our current code, and in the fullness of time we'd like to get it all fixed, but for now that's how things work. :-(
Anything new about this?
Hi Mitar,
Yes, we do have an improved Subversion adapter that can follow some kinds of directory moves. I've just checked the Orange repository, and it looks like our new adapter will correctly follow the entire history for this project.
Switching to the new Subversion adapter requires a clean import of the entire project history.
Once our current update of the Orange project completes, I will start a new report. It will probably take a day or two to complete. I'll keep an eye on it.
Thanks,
Robin
It works!