Configuring local colocated branches matches too broadly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Breezy |
Triaged
|
Medium
|
Unassigned |
Bug Description
Configuration of local branches ignores the branch name, so branches with the right colocated location but wrong name will match a config that should not match. This problem does not occur with remote branches, so it is likely the same root cause as Bug #1015570: file:/// locations being converted to filesystem paths too early.
Given the following config section:
[file:/
public_branch = !!
[bzr+ssh:
public_branch = !!
# Correct remote match
$ bzr config public_branch --scope=locations -d bzr+ssh:
!!
# Correct remote miss
$ bzr config public_branch --scope=locations -d bzr+ssh:
bzr: ERROR: The "public_branch" configuration option does not exist.
# Correct local match
$ bzr config public_branch --scope=locations -d file://
!!
# Incorrect local match
$ bzr config public_branch --scope=locations -d file://
!!
tags: | added: config |
Changed in bzr: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: check-for-breezy |
tags: |
added: colocated removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Medium |