Pushing to a branch with empty working tree gives error

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Widhopf-Fenk wrote:
> When pushing to a local branch where I removed the working
> tree by (rm *) I get an error message that the working tree
> files do not exist.
> 
> But still push did what it should do.
> 
> What is the right way to generate a branch without working
> tree and not cause this error?

Unfortunately, push currently has a bug that it always generates a
working tree for a local push. Doing:
bzr push sftp://localhost/path/to/branch

Would create a branch without a working tree, but I realize that isn't
very nice.

https://launchpad.net/products/bzr/+bug/50582


> 
> I removed .bzr/checkout by hand, but that seems like there
> should be a command to nuke the working tree of a branch, a
> command I must have missed so far.

No. We've discussed adding an explicit command for it. But:

a) Not 100% sure what it should be called (uncheckout, remove-checkout, ???)

b) Just haven't gotten around to implementing it.

> 
> Is there a command or should I do
> 
>   bzr inventory | xargs rm -rf
> 
> Also I wonder why the working tree is created by push while
> its docs say:
> 
> ,----
> | The target branch will not have its working tree populated because this
> | is both expensive, and is not supported on remote file systems.
> `----

^- This is true if you create it by ftp or sftp. And should be true if
you push into a repository with 'no-working-trees' set.

But in general, push is a way to update another tree. So if you have
access to a local working tree, push should update it.

> 
> Odd.
> 
> Robert
> 
> 

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE7jpQJdeBCYSNAAMRAkysAKDNgS5Q4yq9Oz50hDt8P2QMWvCDdgCfS5n8
4bMjxSFnUaMSzjnCH3qXF7E=
=OyVR
-----END PGP SIGNATURE-----