Strange bzr handling of parent location from bzr branch when $HOME uses a symbolic link.

[David Ingamells]

John Arbash Meinel wrote:

 > David Ingamells wrote:
 > > Changing /etc/passwd to give the user's home as /volumes1/home/<user>
 > > and repeating the above commands (after a logout and login and of 
course
 > > removing the defective branch created above) solves the problem.

 > My guess is that the issue is that sometimes the branch under question
 > is accessed as "/home/user/foo" and other times as
 > "/volumes1/home/user/foo". And the parent pointer is being given as a
 > relative path.
 > So if we opened the branch as "/home/user/foo" and find the parent
 > location is "../../../data/id/repos" then when it is accessed as
 > "/volumes1/home/user/foo" the relative path breaks.

Your guess is correct as the behaviour depends on how the path to the 
branch is given.

 > Feel free to submit a bug on this. I think the basic fixes are:

https://bugs.launchpad.net/bzr/+bug/497654

 > 1) When computing a relative path, if it goes through '/' just use an 
absolute path.

I'd say the fix is: don't store relative paths in the config file. 
Always use the URL - which has to be done anyway if the parent was 
accessed by e.g. bzr+ssh .