bzr log fails on ghost revisions

On Mon, 2011-02-28 at 11:29 +0000, Tom Cato Amundsen wrote:
> bzr log -r ..1 http://solfege.org/bzr/solfege.dev fails because of
> ghosts in the revision history.
The log until the ghost revision appears to be displayed correctly.

We could improve the error message a bit to more clearly say to the user
that there is a revision missing so we can't display beyond that point
in the logs. Is that how you'd like to see this resolved?

Cheers,

Jelmer

What I really would like is to make my bzr repo work with ohloh.net: https://www.ohloh.net/topics/3485?page=1#post_16138
But they are not very interested in making special exceptions for my repo, and asks me to fix things. I have not found a way to get rid of the problem without dropping history and starting from scratch again in the repo.

I re-read the forum on ohloh.net, I see that I (think I) only need "bzr log -r 1.. -v" to work, not "-r ..1". Sorry for not being precise in the initial message.

The problem is the "-v" option, it works without it, but not with it.

And here is the .bzr.log showing "bzr log -r 1.. -v http://solfege.org/bzr/solfege.dev

On Mon, 2011-02-28 at 22:13 +0000, Tom Cato Amundsen wrote:
> And here is the .bzr.log showing "bzr log -r 1.. -v
> http://solfege.org/bzr/solfege.dev
>
> ** Attachment added: "bzr log"
> https://bugs.launchpad.net/bzr/+bug/726466/+attachment/1877441/+files/.bzr.log
>
Ah, it should definitely not trigger a traceback. We'll probably still
need to have it print an error of some sort though, as it's important to
let the user know that we don't know the history (rather than that there
is no more).

Cheers,

Jelmer

Exactly. An error message is ok and avoiding a traceback will keep both ohloh.net and loggerhead happy. I'm looking forward to this :-)

On Tue, 2011-03-01 at 17:17 +0000, Tom Cato Amundsen wrote:
> Exactly. An error message is ok and avoiding a traceback will keep both
> ohloh.net and loggerhead happy. I'm looking forward to this :-)
This won't have any effect on loggerhead, it doesn't use "bzr log" in any way.

If loggerhead also fails on this particular branch, please file a
separate bug in loggerhead.

Cheers,

Jelmer