sftp oddities

[Jan Hudec]

On Tue, Dec 20, 2005 at 14:29:08 +0100, Jeff Rose wrote:
> On Tue, 2005-12-20 at 12:27 +0100, Jan Hudec wrote:
> [...]
> > Because it does not work for URL. Colon after hostname is followed by port
> > there (It's not mandatory anywhere, so it /could/ be done -- but it would not
> > be more expectable).
> 
> I don't know about official URL syntax, but I just wanted to let you
> know what someone "from the outside" thinks when they first use the
> tool.  If you are going to be using url's (er, addresses) that are

Um, that means it's badly documented.

> different from tools people are familiar with then it is especially
> important to have really informative error messages and examples in
> help.  Since bzr supports pluggable transports maybe they could
> implement a method that spits out an example using their transport or
> something like that...?

Well, I am familiar with other tools that use sftp://user@host:port/path
Basically anything except scp, sftp and rsync themselves. Eg. konqueror.

> [...] 
> Well, sftp should be running on the correct port.  Otherwise in the very
> rare case where its on a non-standard port something like this could
> work:
> 
> bzr branch -p 443 sftp://foo.com:/home/myfriend/code/project

The point of URL is to contain *all* the information necessary to connect.
This breaks it.

> [...]
> > >   Pushing a fresh tree (at least with sftp) prints a warning that makes
> > > you think it has failed:
> > > 
> > > --------------------------------------------
> > > rosejn at jive:~/code/icalendar$ bzr push
> > > sftp://research.inf.unisi.ch/code/icalendar
> > > bzr: WARNING: Unable to update the working tree of:
> > > sftp://research.inf.unisi.ch/code/icalendar
> > > 7 revision(s) pushed.
> > > --------------------------------------------
> > > 
> > > Then checking the remote branch to see if it did indeed work, we find an
> > > empty project directory.  Branching seems to work fine though, so I
> > > guess it rebuilds the working tree when you pull it down?
> > 
> > It does not build the working directory on the server - just as it says.
> > Never. But it builds it locally when you branch from it.
> 
> Hmmm.  It says "WARNING", which doesn't sound like behavior that is
> supposed to occur.  If that is incorrect then maybe it can be my first
> patch :-)

The behaviour is expected. So it should say something like "NOTE: Remote
working tree is NOT upated.".

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051221/abff6f9d/attachment.pgp