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]
https://www.ohloh.net/p/ramaze/enlistments
git master branch enlistment
Thanks
Looks like someone restarted this, it failed again ...
Step 2 of 3: Importing source code into database (Failed 28 minutes ago.)
Hi Clive,
Thanks for the heads-up. I'm working to update Ramaze's report. It's a two-step process -- fetch the new commits and then do a full re-import. When the fetch succeeded, it automatically queued a new (partial) import that failed.
I've now scheduled a the full import and will watch its progress.
Thanks for keeping me honest!
-Andy
I'm guessing it's safe to assume that the mess inside ...
https://www.ohloh.net/p/ramaze/aliases
... will automagically get fixed when this succeeds?
Sorry Clive, I don't understand the question. The report is done now, perhaps it answers your question?
Don't worry Andy. Looking at the aliases page now, there is nothing to see. The update fixed the mess of unassigned aliases.
Thank you.