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]
Step 2 of 3: Importing source code into database (Failed 3 months ago.)
https://www.ohloh.net/p/solfege/enlistments
Are you able to have a look at this? Or at least send me the logs with the bzr commands that fails, so I can debug?
I know the repository has some problems with ghosts, so tags has to be run like this: bzr tags -r 1..
Hi, here is the log from the command that is failing -
bzr log --long --show-id --forward --include-merges -r 1.. -v
bzr: ERROR: bzrlib.errors.NoSuchRevision: KnitPackRepository('file:///home/ubuntu/ohloh_troubleshooting/otwo58/solfege.dev/.bzr/repository/') has no revision ('Arch-1:[email protected]%solfege--htmlwidget--0.2--version-0',)
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https://bugs.launchpad.net/bzr/+filebug
attaching the crash file
/home/ubuntu/.cache/crash/bzr-20101025182314-8365.crash
and including a description of the problem.
The crash file is plain text and you can inspect or edit it to remove
private information.
The error is caused by of ghost revisions in the repository. I don't claim to know anything about bzr or bzr repository internals, but I think it is related to this bug: https://bugs.launchpad.net/bzr/+bug/397556
I don't know if it is acceptable for you but running bzr log from revno 2 works fine:
bzr log -r 2.. --show-diffs http://solfege.org/bzr
@tca, I don't think we'll be able to make this change without impacting everyone else. Any chance you can fix this on your side?
Comments to this topic are now closed. Please create a new topic to get technical support.
The user who created the topic can reopen this topic at any time.