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?
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. :-(