launchpad_user setting in locations.conf not working
Bug #598265 reported by
dobey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
I'm working with Stefan so we can get a working tarmac setup running on a server, to manage several branches for multiple projects. To do this, we need to be able to set the launchpad user for the separate branch locations. It appears that specifying launchpad_user in locations.conf for each local working tree should suffice to do this. However, in testing this, the setting does not appear to get picked up for me.
I created a new working directory config, specifying a different launchpad_user than the one set in authentication.conf as the global user, which I normally use. I then created a working tree in this location, and ran bzr lp-login, to see if it would work. But lp-login simply printed the global username.
| Changed in bzr: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| tags: | added: launchpad |
Revision history for this message
| Vincent Ladeuil (vila) wrote | #1 |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 598265] Re: launchpad_user setting in locations.conf not working | #2 |
Revision history for this message
| Vincent Ladeuil (vila) wrote | #3 |
Revision history for this message
| Robert Collins (lifeless) wrote | #4 |
| tags: | added: check-for-breezy |
To post a comment you must log in.
Given the bug title I suspect you missed the way locations.conf and authentication.conf are used:
- locations.conf targets your *local* directories,
- authentication.conf targets your *remote* branches
If you need different users when accessing different remote branches, you need to specify them in authentication.
Can you attach your locations.conf and authentication.conf files ?