All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] Change bzr fetcher to use branch instead of co. Fixes: bzr: ERROR: No pull location known or specified.
@ 2012-07-19 11:26 Martin Ertsaas
  2012-07-24  9:37 ` Richard Purdie
  0 siblings, 1 reply; 2+ messages in thread
From: Martin Ertsaas @ 2012-07-19 11:26 UTC (permalink / raw)
  To: bitbake-devel

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:
-- 
1.7.8.6




^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] Change bzr fetcher to use branch instead of co. Fixes: bzr: ERROR: No pull location known or specified.
  2012-07-19 11:26 [PATCH] Change bzr fetcher to use branch instead of co. Fixes: bzr: ERROR: No pull location known or specified Martin Ertsaas
@ 2012-07-24  9:37 ` Richard Purdie
  0 siblings, 0 replies; 2+ messages in thread
From: Richard Purdie @ 2012-07-24  9:37 UTC (permalink / raw)
  To: Martin Ertsaas; +Cc: bitbake-devel

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




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-07-24  9:48 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-19 11:26 [PATCH] Change bzr fetcher to use branch instead of co. Fixes: bzr: ERROR: No pull location known or specified Martin Ertsaas
2012-07-24  9:37 ` Richard Purdie

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.