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]
Failed importing source for Vikingboard (4198)
Hi,
The enlistment stats on Vikingboard (id 4198) reports (and has been reporting for some time now) that it has halted on step 2: importing source code into database. It also says the source control is Subversion (Sync Beta)
. Is this some beta version of a new subversion importer?
Hi Jørgen,
It looks like this is a bug in our Subversion importer. There's a lot of source code re-arrangement in revisions 1677 and 1678, and our parser is getting lost. I'll investigate.
Did you find anything? The enlistment is still stuck on the same step.
Hi Jørgen,
Sorry for the long delay; I thought this had resolved itself and I didn't realize it was still stuck.
Our importer has been stung by the behavior described in this post. Some items in the Subversion log are being listed as action R
(replacements), when they in fact have no prior version. We'll need to make some workarounds in our importer code to get around this.
However, there's another looming issue for Vikingboard that will surely be bad news. It looks like you moved the source code from /Vikingboard/tags/release-0.2_beta to /trunk on 2007-12-02. Unfortunately, the Ohloh importer cannot follow this kind of Subversion branching, which means that the Ohloh report is only going to show activity since this move. I can reschedule a new Ohloh report, but the new report will not show any historical activity before 2007-12-02.
This is a known design limitation of our importer, and I would like to find the time to fix this. I'll schedule a new report, and get to work on the logging issue.
Thanks,
Robin