This one is going to be tenacious - need to figure out what the error message means... Probably going to push this one upstairs.
Some early indication that either the commit ID or the file ID (or some combination of the two) conflicts with another in the repo. Hmmm.
Any updates regarding this? It's still broken...
So I've isolated Ohloh's problem to this commit.
This commit contains, within its comment message, a complete quotation of a log fragment of another commit.
Worse, this quoted log fragment is indented by exactly two spaces, which is precisely the number of spaces required to make this quoted log fragment appear indistinguishable from an actual commit on a branch line.
Our parser becomes rather confused at this point.
Bzr isn't so kind as to provide an easily machine-readable log format preset, and this isn't the first time we've been stumped by what we found in a log.
I'm looking into this problem now, and hopefully I can find some distinguishing factor that will allow us to determine that this quoted log fragment is not an actual commit.
If anyone can help this Bzr hacker (and I mean that in the n00b sense) see the light, I'd appreciate it :-)
We're currently working on a a new importer for Bazaar built around the XML logging plugin, which should resolve our problem here (as well as fix a few other problems we've had with Bazaar). It will take us a few weeks to get this implemented and pushed into production.
Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.