Bazaar

locations.conf is only consulted when there's a branch

Bug #276201 reported by Matthew Fuller
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Low
Unassigned

Bug Description

When there's no branch at a given location, locations.conf isn't consulted. This may be seen by setting something like:

[/home/fullermd/tmp]
email = <email address hidden>

then going into ~/tmp and running "bzr whoami". With no bzrdir there, the default is still shown. init-repo does the same. Only after init'ing a branch there does it get the new email.

(I have no verified whether this is actually just a quirk in whoami, but I'm guessing it's a general thing with locations.conf parsing)

Jelmer Vernooij (jelmer)
Changed in bzr:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
zsquareplusc (zsquareplusc) wrote :

seeing this too with bzr V1.17

Revision history for this message
zsquareplusc (zsquareplusc) wrote :

Even worse, there seems to be an issue when setting the name through whoami. It writes to bazaar.conf, but then when displaying it reads form locations.conf again. Either "bzr whoami <newname>" should be an error in this case, or it should write locations.conf.

Martin Pool (mbp)
Changed in bzr:
status: Triaged → Confirmed
Jelmer Vernooij (jelmer)
tags: added: config
Vincent Ladeuil (vila)
Changed in bzr:
assignee: nobody → Vincent Ladeuil (vila)
Vincent Ladeuil (vila)
Changed in bzr:
assignee: Vincent Ladeuil (vila) → nobody
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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