sftp oddities

[Jan Hudec]

On Tue, Dec 20, 2005 at 11:54:22 +0100, Jeff Rose wrote:
> Hello again,
>   I was thinking it could be helpful to bring up issues as we jump into
> bazaar, but if this isn't the right forum let me know.  Both of my
> roommates and I are grad students in CS with years of cvs/svn under our
> belts, and we probably represent the type of people you hope to bring to
> bazaar as time goes on.  Hopefully our perspectives can be
> constructive...
> 
> 1. Why does pushing and branching with sftp use an odd url that doesn't
> correspond with what people already know about sftp?  Why not use a
> colon after the hostname, and then if you have a slash it goes to the

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).

> root of the fs, like the normal utils?
> 
> sftp://foo.com:/home/myfriend/code/project

Because things like:
sftp://foo.com:443/home/myfriend/code/project
need to be possible too.

> otherwise you have to do this, which seems pretty weird:
> 
> sftp://foo.com/../myfriend/code/project

That's invalid URL! It's forbidden to have . and .. components in URL.

Well, there is the issue with latest sftp url draft that says:
sftp://host/path/relative/to/users/home
sftp://host/%2Fabsolute/path
The draft is expired now. AFAIK it's only followed by mercurial and bzr now.
There was talk about switching to:
sftp://host/absolute/path
sftp://host/~/path/relative/to/users/home
but I don't know whether it's already implemented.

>   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.

-- 
						 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/20051220/e032a64a/attachment.pgp