I copy my devel tree from one machine to another. On one machine my tree resides on drive D:, but on another it's on drive C:. But relative paths between branches stay the same.
I have lightweight checkout. After copying branches master branch o lightweight checkout resides by another full path, but on the same relative path. Any operations with checkout ends with NotBranchError. The worst part is command 'info' also fails with the same error.
C:\work\Bazaar\plugins.work\bzr-gtk.bialix>bzr info
bzr: ERROR: Not a branch: D:/Bazaar/bzr-gtk/bzr-gtk.win32.bialix/
I think 'bzr info' should be more robust against disappearing of master branch and say something reasonable to user in this situation.
I copy my devel tree from one machine to another. On one machine my tree resides on drive D:, but on another it's on drive C:. But relative paths between branches stay the same.
I have lightweight checkout. After copying branches master branch o lightweight checkout resides by another full path, but on the same relative path. Any operations with checkout ends with NotBranchError. The worst part is command 'info' also fails with the same error.
C:\work\ Bazaar\ plugins. work\bzr- gtk.bialix> bzr info bzr-gtk/ bzr-gtk. win32.bialix/
bzr: ERROR: Not a branch: D:/Bazaar/
I think 'bzr info' should be more robust against disappearing of master branch and say something reasonable to user in this situation.