No WorkingTree exists after branching

[Vincent Ladeuil]

Sorry for late reply :-/

>>>>> Eli Zaretskii <eliz at gnu.org> writes:

    >> Date: Tue, 22 Oct 2013 06:17:47 +0800
    >> From: Xue Fuqiao <xfq.free at gmail.com>
    >> Cc: bazaar at lists.canonical.com
    >> 
    >> Thanks, there are four lines:
    >> 
    >> parent_location = bzr+ssh://xfq@bzr.savannah.gnu.org/emacs/trunk/
    >> public_branch = bzr+ssh://xfq@bzr.savannah.gnu.org/emacs/trunk
    >> bound_location = bzr+ssh://xfq@bzr.savannah.gnu.org/emacs/trunk/
    >> bound = False
    >> 
    >> If I change the "False" to "True", "bzr up" will succeed.

    > Yes, it should be True.

    >> But I don't know why it is "False", since I have already used ‘bzr
    >> bind’.

    > Neither do I.  Your bzr does weird things.

I think this sums it up quite nicely: you seem to encounter issues
nobody else can reproduce :-/ I.e. *unless* you're using a shared
repository that you explicitly configured to *not* create working trees
you shouldn't end up with a branch without a working tree. 

If you're still encountering the issue, here are a few commands to check
your bzr install:

- 'bzr version' will gives you details about which bzr is used with
  which library,

- 'bzr plugins -v' will gives your details about which plugins are
  installed and where they are installed

- 'bzr --no-plugins <command> <args>' will run bzr without any plugins
  (be aware that this means that *core* bzr plugins like launchpad
  access are also disabled in that case). This helps diagnosing issues
  caused by any plugin,

- 'BZR_PLUGINS_PATH=-site bzr <command> <args>' will run bzr with the
  core plugins only. This is the preferred way to rule out user and
  system-wide installed plugins.

- 'bzr config' in any directory will tell you which config options are
  active for the current working tree, branch or repository,

- 'bzr config <option>=<value>', 'bzr config --remove <option>' will
  update the config files when used in the right directories (using the
  previous 'bzr config' is a good way to check before and after these
  commands that you're modifying the right config file). There is no
  need to edit the config files by hand and avoid corrupting them.

  Vincent