confusing message (or no message) if unable to open ~/.bzr.log
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
Bazaar should check if the user owns the ~/.bzr.log file and report an error if this is not the case, instead of just displaying the error: 'No handlers could be found for logger "bzr"'. For example:
$ bzr ci
No handlers could be found for logger "bzr"
[24096] 2009-04-03 23:49:35.225 INFO: Committing to: /home/jpds/
Committing to: /home/jpds/
[24096] 2009-04-03 23:49:35.253 INFO: modified TODO
modified TODO
[24096] 2009-04-03 23:50:10.122 INFO: Committed revision 373.
Committed revision 373.
It took me a while to realize that this was because I'd use etckeeper+bzr with sudo earlier and root had ownership of my user's ~/.bazaar directory and ~/.bzr.log file.
This is using the latest bzr package on Jaunty.
| Changed in bzr: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| summary: |
- Bzr should be smart about who owns ~/.bzr.log + better handle failure to open ~/.bzr.log - Bzr should be smart about who + owns ~/.bzr.log |
| tags: | added: easy |
| Martin Pool (mbp) wrote Re: better handle failure to open ~/.bzr.log - Bzr should be smart about who owns ~/.bzr.log | #1 |
| Martin Pool (mbp) wrote | #2 |
| tags: | added: trace |
| summary: |
- better handle failure to open ~/.bzr.log - Bzr should be smart about who - owns ~/.bzr.log + confusing message (or no message) if unable to open ~/.bzr.log |
| Changed in bzr: | |
| status: | Triaged → Confirmed |
| importance: | Medium → Low |
| tags: | added: check-for-breezy |
| tags: | removed: check-for-breezy |
With https:/