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]

musicbrainz-server enlistments haven't been updated in 3 months.

Hi,
http://www.ohloh.net/p/musicbrainz-server/enlistments

I noticed that the git enlistments for musicbrainz-server haven't been updated in 3 months - quite a long time given how active the project is ;)

In particular: git://git.musicbrainz.org/musicbrainz-server.git master
which serves as the project's primary official repository. No errors are shown.

While I'm around, another question: This project migrated from svn to git a while back, and I'm pretty sure that git contains migrated history. The svn repo is now inaccessible, can the svn enlistment be deleted without losing data?

Calvin Walton about 12 years ago
 

Calvin,

The inaccessible subversion is probably the reason the git server(s) haven't been updating properly. It's an all-or-nothing arrangement that all enlistments must update successfully for any enlistments to update completely. If the git enlistments contain all the historical data, then you can do history / undo for the subversion enlistment(s) and an update will start almost immediately. This will confirm what the state of the git(s) is.

I'll check in tomorrow and see what may have run overnight.

Thanks!

ssnow-blackduck about 12 years ago
 

Calvin,

I misunderstood you to say that the subversion was no longer in-service. I see today that the subversion is alive-and-well and was only being interrupted by a trivial issue on ohloh's end which is now fixed.

Update for the subversion finished OK. An update of the remaining enlistments started immediately and also finished OK. (The three remaining git enlistments all had 700 plus new commits.) Analysis page is now at Jan 27 2012 and last commit is at 2012-01-26 (about 18 hours ago).

You can try the project without the subversion as I outlined above (history / undo). It probably is contributing to an inaccurate view of the project's lines-of-code counts. You can then determine if the code transfer contained all the historical commits as well.

Please remind me here if the project goes astray again.

Thanks!

ssnow-blackduck about 12 years ago