Problems with push and branch

[Wouter van Heyst]

On Thu, Mar 02, 2006 at 05:56:16PM +0000, Joseph Wakeling wrote:
> Hello all,
> 
> First off: is there really no built-in search option for the mailing
> list archives?  There doesn't appear to be.  I did look through the
> gzipped text and do text searches with my web browser, but didn't come
> up with anything useful regarding the problems described herein...

I use google or the gmane interface:
http://news.gmane.org/gmane.comp.version-control.bazaar-ng.general

<snip>

> I have a few remote computer systems/clusters that I use to run
> simulations (access via ssh), and it would be best of all to have
> separate bzr branches on each, so that occasionally when I might work on
> a remote system I can pull back any changes that might be worthwhile. 
> However, since I'm not in control of whether bazaar-ng is installed on
> those systems, as a second-best option I'd like to be able to develop on
> my own machine and then just upload all the latest code, automatically,
> to the remote systems.
> 
> Anyway, I've tried commands as follows:
> 
>     bzr branch . ssh://myname@remote.computer.com/home/myname/location/
> 
> and also,
> 
>     bzr push ssh://myname@remote.computer.com/home/myname/location/
> 
> and in both cases got the same error: "bzr: ERROR: Parent directory of
> ssh://myname@remote.computer.com/location/ does not exist."

This is because bzr does not know the ssh:// protocol, so it tries to
push to a local directory structure of the name
ssh:/myname at host/location, which does not exist.

Do you have sftp access to those machines? If so, use sftp:// instead of
ssh://.

<snip>

> Is it simply that bazaar-ng is not installed on the remote system and
> needs to be, or is there something wrong about what I'm trying to do?

You do not need bzr on remote systems if you push with a 'dumb' protocol
like sftp, rsync or ftp.

> ... and ... assuming that I can't get bazaar-ng installed on those
> systems any time soon, how do I solve my problem of automatically
> copying across the latest committed version of code in my repository to
> remote machines, short of doing it by hand?

Ah, this is a tougher question. If you have several systems where you
can not install bzr, perhaps a post-commit plugin that pushes to several
hosts (not forgetting the workingtree!) is a good option. Since you do
not have bzr with you on those systems, you can't make full use of the
branches there. Are you planning to just deploy, or also develop on
them?

Wouter van Heyst