Problems with absolute paths stored in 'location' file.

[Gerard Murphy]

Hi,

I'm working with a mixed OS setup - Mac OS X Snow Leopard on the one hand and Windows 7 in a Parallels virtual machine on the same computer. I would like to be able to switch back and forth between my Windows bzr installation and MacOS one; this seems to work fine for the usual scenarios, so I can run 'bzr log', 'bzr mv', 'bzr commit' etc with (apparently so far) so problem.

However I'm getting problems with the pipeline plugin: these hinge around the mapping in the file:
.../.bzr/branch/location
- this is storing an absolute path which obviously doesn't translate between the two OS viewpoints. As the pipe branches referred to in this file are created by the pipeline plugin, would it be possible to use a relative path wrt the pipeline's checkout directory within this file to fudge a workaround?

I tried a quick and dirty test by hand-editing 'location' to use a relative path and it seemed to work - although as soon as I do 'bzr switch-pipe' I'm back in trouble. I also checked that 'bzr explorer' works correctly with the hand-edited file: seems OK as long as the hand-edit is preserved.

Regards,

Gerard

[Gerard Murphy (g-j-murphy)]

The error encountered (say when running 'bzr log' in Windows after doing 'bzr switch-pipe' on the MacOS side) is:-

bzr: ERROR: Invalid url supplied to transport: "file:///Users/gerardMurphy/Documents/SageSerpent/bzrRepository/singletonWork/": Win32 file urls start with file:///x:/, where x is a valid drive letter

[Martin Pool (mbp)]

This seems basically the same as bug 135234, or similar?

[Gerard Murphy (g-j-murphy)]

Yes indeed, although the use-case driving this I believe different from that in bug #135234: what I was trying to do was to refer to the same checkout location via two different UNCs, so that one was conflicting with the stored absolute path. OTOH, bug #135234 seems to be concerned with relocating a checkout around the same filesystem.

(Although Alexander Belchenko's comment in the other bug's comment trail does look like the same use case as here.)

I stress the difference in use-cases to add a plus vote for fixing #135234, or possibly doing a different fix that would sort this one out.