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.synopsys.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]

Plomino project not updating

Plomino development moved from sourceforge to github. I added the github repos some days ago, but the project has not been updated yet. The old sourceforge repo is showing an error (Failed about 1 month ago.). Is that blocking update, or can it be ignored?

Jean Jordaan over 10 years ago
 

Jean,

Yes, that's the source of the problem. By now, all the SourceForge subversions have been forcibly moved to new addresses due to the Allura upgrade. I have entered the new address as a new enlistment and removed the old enlistment. I'll report back on the results once it is ready.

In the meantime you will need to think about whether it is advisable to keep the SourceForge repository in-place now. Projects with dual, duplicated repositories always are challenged with this issue. If all the history has been imported into the GitHub repository, then it's a no-brainer and SF will need to go. If not, then you have a conundrum: preserve history at the cost of accurate lines-of-code counts (and all the statistics they drive) or sacrifice history to get better metrics. Your best friend now will be the full commits page. If all commits before the addition of GitHub show twice then the history is in both repositories. If not then a decision is called for.

You can delete the SF repository without fear --- ohloh remembers. Just wait for a new analysis to run. You can return the enlistment from the edits menu; just press redo and wait for the analysis to run again. Compare the stats on the languages summary page and you should see about a doubling of the lines-of-code statistics with both repositories included versus the GitHub repository (or the SF repository) alone.

Thanks!

ssnow-blackduck over 10 years ago
 

Jean,

Initial fetch of the new SourceForge enlistment finished OK (773 total commits.) Analysis is now at October 17, 2013 on code collected on October 15, 2013 and last commit is at October 14, 2013. The GitHub enlistment is somewhat behind by two days and should update soon.

Please let me know here how you decide. I may have additional suggestions if you need them.

Thanks!

ssnow-blackduck over 10 years ago
 

Awesome, thanks for the help and advice! The old commits indeed show up twice, e.g.
https://www.ohloh.net/p/plomino/commits/299061619 (github, Files Modified: 12)
https://www.ohloh.net/p/plomino/commits/299317138 (sourceforge, Files Modified: 14)
are both Access control level declaration on 19-May-2006 at 11:47.

I don't know why the files show up differently, but it looks like it's just a glitch. Everything else (lines of code modified, etc.) is the same.

I've removed the sourceforge repo.

Thanks!

Jean Jordaan over 10 years ago