On 18 February 2010 03:30, Mark Grandi <email address hidden> wrote:
> Yeah, that makes sense as I just kinda reuploaded the branch to my FTP
> server and it ended up working fine after that.
>
> I guess the point of this bug is, is there a more graceful way of
> handling this error, instead of Bazaar explorer crashing and possibly a
> scary python traceback output in the terminal?
We could catch this error and point you to a faq. However if things
are breaking underneath us at the disk or OS level, as does sometimes
happen, it's pretty hard to predict precisely what will fail. If this
particular error turns out to be common perhaps we should handle it
that way.
On 18 February 2010 03:30, Mark Grandi <email address hidden> wrote:
> Yeah, that makes sense as I just kinda reuploaded the branch to my FTP
> server and it ended up working fine after that.
>
> I guess the point of this bug is, is there a more graceful way of
> handling this error, instead of Bazaar explorer crashing and possibly a
> scary python traceback output in the terminal?
We could catch this error and point you to a faq. However if things
are breaking underneath us at the disk or OS level, as does sometimes
happen, it's pretty hard to predict precisely what will fail. If this
particular error turns out to be common perhaps we should handle it
that way.
-- launchpad. net/~mbp/>
Martin <http://