sftp bugs

[Andrew Bennetts]

John A Meinel wrote:
> Robert Collins wrote:
[...]
> > 
> > For HTTP, FTP, and File:// urls the latter syntax is used: the
> > presumption is that all resources on the filesystem have the same
> > location *regardless* of user credentials.
> > 
> > I think that this is easier to debug and easier to understand than URL's
> > where the resource location randomly changes if the credentials change.
> 
> Well, how does the supermirror handle it? I could have sworn that it
> gave you a different path depending on you username. So if you connected
> as sftp://arch%ive-foo/cat--b--v@sourcecontrol.net/ it would put you at
> the root of your project.
> Which means that even with absolute paths, you still have a floating
> root directory depending on username.

The supermirror sftp server always logs you into a root directory,
so that there's no difference between /foo/bar and foo/bar.  Or if you prefer,
the user's home directory is the root directory of a virtual filesystem.

For Bazaar 1.x, the root directory contains foo at example.com-bar archives.

For bzr, the root directory will contain a ~username directory, and ~teamname
directory for each Launchpad team the user is a member of.  This means that all
members of a team have access to a branch at the same sftp url, and also that
all branches can be published over http at their sftp url, except that 'sftp://'
is replaced with 'http://'.  This has nothing to do with how the branches are
stored on disk, but users don't have to care about that :)

See https://wiki.launchpad.canonical.com/SupermirrorFilesystemHierarchy for
details if you're interested.

(The sftp server is able to distinguish between 1.x and 2 logins because for 1.x
we use an email address as a username, for 2 we use the launchpad nickname.)

-Andrew.