Comment 9 for bug 32669

Hello, I'm not sure this bug is solved.

Considering this files structure :
ls -l .
branch-one (hard-file branch)
branch-two (hard-file branch)
branch --> branch-one (symlink branch)

ls -l ./branch-one
(some dev files, but no symlinks inside the directory)

If I do 'cd branch && bzr status', this works fine. I think in this case that bzr has no symlink to resolve : 'bzr status' works with the '.' file, that's 'branch-one/.'.

But when I use a fresh bzr 2.0.3, latest bzr-eclipse and xmloutput plugins, I get this error in the bzr-eclipse console :
/home/path/branch is not in the same branch as /home/path/branch

As mentionned in a previous message of this bug report, the 'branch' symlink changes from one runtime to another : branch --> branch-one sometimes, but branch --> branch-two some other times.

In this case, bzr is not called from the inside of the branch directory (as it was in the previous example), but with an absolute path. In this path, symlink doesn't get resolved but is handled as a file itself. It should be handled as 'branch-one' hard-file.

It's only an hypothesis that doesn't explain much, I don't really understand where the error is.

This bug is old, and it really seems not to be solved. This is really important beeing ablse to use seemlinks on branch names, for scripting and sources organization purposes.

Thanks taking it in consideration and giving an opinion on this or a workaround in the trunk :)