bzr commit FILE breaks when given symlink as argument
Bug #128562 reported by
James Troup
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Martin Pool | ||
2.0 |
Fix Released
|
Medium
|
Unassigned | ||
2.1 |
Fix Released
|
Undecided
|
Unassigned | ||
2.2 |
Fix Released
|
Undecided
|
Unassigned | ||
bzr (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
/etc# bzr commit -m "lala" alternatives/
bzr: ERROR: Not a branch: /usr/share/
/etc# ls -l alternatives/
lrwxrwxrwx 1 root root 51 Jul 24 10:50 alternatives/
/etc#
If I run bzr commit without specifying the filename, it works just fine.
Related branches
lp:~mbp/bzr/192859-2.0-symlinks
- John A Meinel: Needs Fixing
-
Diff: 67 lines (+25/-12)1 file modifiedbzrlib/tests/per_workingtree/test_symlinks.py (+25/-12)
Changed in bzr: | |
status: | In Progress → Fix Released |
Changed in bzr (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
Specifically, this is related to bug #32669. And relates to our overall decisions as to when to dereference a symlink, and when not to.
In this case, we are dereferencing right away, and so we look at the target of the symlink and start searching for a branch there.
Most likely this is because we are opening a transport using a 'base' of the symlink, which causes us to dereference it. And then when we start walking up from there, we are walking the wrong location.