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]
We have 2 different Bazaar branches (an old and new codebase) that are registered with ohloh, but the old one refuses to update; it just says (Failed 1 day ago)
on the Enlistments page. The URL for the failed enlistment is http://dev.skewedaspect.com/bzr/precursors/trunk-2010; using Bazaar, I can branch and pull from this URL perfectly fine, so the problem seems to be on ohloh's end; could the dash in the branch name be causing a problem?
David,
You are correct. This is due to a known bug in our bazaar handling here at ohloh. I'm running a re-fetch for that problem
enlistment now. Will report back once it is finished.
Thanks!
David,
Re-fetch has finished OK. Analysis is now up-to-date. Last commit is 2011-03-15.
Please don't hesitate to ask for a re-fetch again here should it continue to fail over time.
Thanks!
Thanks! The Enlistments page does say (Failed 1 day ago)
again, but the commits are there; since this is an old, unused branch, we won't be updating it any more, so this shouldn't be an issue.
David,
The problem is, no updates to either enlistment will be complete unless both enlistments succeed on each update. The nature of this bug is that a fetch of the entire Bazaar repository for that enlistment will work OK but an incremental pull from the same repo will fail. The commits data may appear to update regularly (dependent on the order in which the enlistments were entered originally, I think) but the Code Analysis page will not be properly updated. Please keep bugging me to re-fetch the broken enlistment until the bug is finally squashed.
Thanks!