loggerhead

  1. Bug #1097567
  2. Comment #1

Comment 1 for bug 1097567

Revision history for this message
John A Meinel (jameinel) wrote : Re: [Bug 1097567] [NEW] LocalTransport have readonly+ in the file path

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

...

AssertionError: <bzrlib.transport.local.LocalTransport
url=file:///var/lib/loggerhead/trunk-rich/readonly%2B./>
>
> Is it normal that readonly+ is in the file path? Could it be a
> middleware that is not working?

Do you know where the '.' is coming from? It is, actually, expected to
have readonly+, but only at the beginning. So: "readonly+file:///...".
The issue is that somehow we are getting a simple relative path "."
rather than the expected URL file:///...

readonly+file:/// is our way to make sure to disallow write actions on
paths.

Offhand 'serve-branches' isn't a very maintained way of service
Loggerhead. (bzr serve --http IIRC is the recommended way.)

So there is probably a bug in here, but I'm not sure whether it is
that we aren't canonicalizing some input from the user, or whether it
is a configuration thing.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Cygwin)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDuXpMACgkQJdeBCYSNAAP5HwCfYCEChlNdxBD0Fzi/BC9gfaen
4v4AnR0jCrBPyJw3Q8svJRILGibegNn7
=QWyp
-----END PGP SIGNATURE-----