LocationConfig should look for options on parent locations when they're not found

Bug #45306 reported by Guilherme Salgado
4
Affects Status Importance Assigned to Milestone
Bazaar
New
Medium
Unassigned

Bug Description

Let's say I have the following branches.conf file:

[/home/salgado/repo/foo]
public_repository = sftp://example.com/foo
pqm_branch = sftp://example.com/pqm/foo
pqm_email = <email address hidden>
[/home/salgado/repo/foo/somebranch]
push_location = sftp://example.com/foo/somebranch

If I look for a pqm_branch option on the [/home/salgado/repo/foo/somebranch] location, I'll get the global pqm_branch option, when in fact I'd like it to give the pqm_branch defined on the parent location.

This problem happened when I wrote my .branches.conf file to use together with the pqm-submit plugin, and then after that I did a bzr push --remember on one of my repo's branches. The result was a .branches.conf file similar to the above one, which prevents me from using pqm-submit, as it'll always use the default pqm_branch.

Revision history for this message
Guilherme Salgado (salgado) wrote : Test case

Test case for the issue I'm reporting.

Revision history for this message
Guilherme Salgado (salgado) wrote :

David Allouche mentioned bug 33430 when I asked him to take a look at this one. He said it's a dupe but this one has the advantage of having a real user story. That's why I didn't mark it as a dupe yet. Please do so if apropriate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.