Branching a Git repository

[Martin Pool]

2009/9/10 Russel Winder <russel.winder at concertant.com>:
> Until I install Dulwich then:
>
>        |> bzr co git://github.com/gradle/gradle.git Master
>        bzr: ERROR: exceptions.ImportError: bzr-git: Please install dulwich, https://launchpad.net/dulwich
>
>        *** 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/users/russel/.cache/crash/bzr-20090910070024-23760.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.
>
> Is almost sensible.  I get the information that bzr-git is missing a
> component which is fine.  However getting the whole "Bazaar internal
> error" message seems to me to be just plain wrong.  This isn't a Bazaar
> internal error, it is a "the user hasn't properly configured the system"
> error, and should be treated as such.

Yes, I thought we normally showed ImportError with a message saying
this.  It's a bug if it's not happening there.

>  Should I raise a bug for this somewhere?

Come on.  The error message tells you to file a bug and gives you a
url to do it.

>
> Of course there are actually two forms of URL for Git clones, so I tried
> the other one:
>
>          |> bzr co git at github.com:gradle/gradle.git Master
>        bzr: ERROR: Not a branch: "/home/users/russel/Repositories/Bazaar/SharedRepositories/Gradle/git at github.com:gradle/gradle.git/".
>
> I consider this to be a Bazaar internal error, well bzr-git anyway, so
> the question is what is the right way of dealing with bug reports for
> bzr-git.

https://bzr.launchpad.net/bzr-git/

-- 
Martin <http://launchpad.net/~mbp/>