[win32] problem with parent location on another local drive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Alexander Belchenko | ||
Ubuntu |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Win32-specific:
When branch has parent on another local disk, bzr anyway store parent location in .bzr/branch/parent as relative path, and this is wrong and cause errors when such branch moved around the filesystem.
G:\work\
Location:
shared repository: file://
repository checkout: selftest.win32
Related branches:
parent branch: file://
publish to branch: file://
Format:
control: Meta directory format 1
working tree: Working tree format 3
branch: Branch format 5
repository: Knit repository format 1
Working tree is out of date: missing 2 revisions.
In the working tree:
548 unchanged
0 modified
0 added
0 removed
0 renamed
0 unknown
0 ignored
45 versioned subdirectories
Branch history:
2326 revisions
620 days old
first revision: Sun 2005-06-26 16:55:27 -0500
latest revision: Wed 2007-03-07 13:40:14 +0200
Revision store:
9409 revisions
42491 KiB
Note that content of parent file is:
G:\work\
../../.
When I move this branch level up/down in filesystem I got error:
G:\sandbox\
Location:
shared repository: file:///G:/sandbox/
repository checkout: selftest.win32
bzr: ERROR: Parent not accessible given base file://
ox/selftest.win32/
This bug also affects pull operation, not only info.
Required fix: if parent location is on another local drive or UNC path it should be stored without relative prefix like '../'*n
Changed in bzr: | |
assignee: | nobody → bialix |
importance: | Undecided → Low |
status: | Unconfirmed → Confirmed |
Changed in bzr: | |
assignee: | bialix → nobody |
Changed in bzr: | |
assignee: | nobody → bialix |
milestone: | none → 1.1 |
status: | Confirmed → Fix Committed |
second