Re: [PATCH] Change bzr fetcher to use branch instead of co. Fixes: bzr: ERROR: No pull location known or specified.

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Thu, 2012-07-19 at 13:26 +0200, Martin Ertsaas wrote:
> This problem occurs when fetching a different revision of the same source. Which mean every time you update a bzr package.
> Using branch sets the pull location, and are the preferred way of cloning/branching a repository in bzr.
> 
> Signed-off-by: Martin Ertsaas <mertsas@cisco.com>
> ---
>  lib/bb/fetch2/bzr.py |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/lib/bb/fetch2/bzr.py b/lib/bb/fetch2/bzr.py
> index 97daa62..58e80c8 100644
> --- a/lib/bb/fetch2/bzr.py
> +++ b/lib/bb/fetch2/bzr.py
> @@ -73,7 +73,7 @@ class Bzr(FetchMethod):
>                  options.append("-r %s" % ud.revision)
>  
>              if command == "fetch":
> -                bzrcmd = "%s co %s %s://%s" % (basecmd, " ".join(options), proto, bzrroot)
> +                bzrcmd = "%s branch %s %s://%s" % (basecmd, " ".join(options), proto, bzrroot)
>              elif command == "update":
>                  bzrcmd = "%s pull %s --overwrite" % (basecmd, " ".join(options))
>              else:

Merged to master, thanks.

Richard