bzr complains if 'bzr whoami' is not run on servers:
Bug #304985 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
10:42 using bzr+ssh it says "Unable to determine your name. Use "bzr
whoami" to set it.", but the whoami is already set to "Forename Lastname
<email address hidden>".
11:09 it was caused by not setting whoami on the SERVER side
bzr server should probably disable this check...
affects bzr
--
GPG key available at: <http://
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in bzr: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| tags: | added: easy |
| tags: | added: whoami |
| tags: | added: check-for-breezy |
To post a comment you must log in.
Part of the problem is that we use the email address inside the lock file. So if we can't figure out what to put in the file, I'm not entirely sure what we should substitute. I'm sure we could do something. But certainly it is nice if we could send the username across so people inspecting the lock later would know what happened.
Perhaps RemoteRepositor