backtrace when locking failed unexpectedly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
See shell text below:
......
Committed revision 11.
maorozco@
bzr: ERROR: No push location known or specified.
maorozco@
bzr: ERROR: Cannot lock LockDir(
maorozco@
bzr: ERROR: bzrlib.
*** Bazaar has encountered an internal error. This probably indicates a
bug in Bazaar. You can help us fix it by filing a bug report at
https:/
attaching the crash file
and including a description of the problem.
The crash file is plain text and you can inspect or edit it to remove
private information.
maorozco@
Changed in bzr: | |
status: | Invalid → Won't Fix |
status: | Won't Fix → Confirmed |
importance: | Undecided → Medium |
summary: |
- Second bzr push to remote repo crashes after first bzr push failed due - to permission denied on remote repo + backtrace when locking failed unexpectedly |
tags: | added: hpss locking |
tags: | added: check-for-breezy |
I think you should be find if you just delete the lock dir and create it again with appropriate permissions. You'll need to make sure that your groups are set up appropriately on the server; I think our admin docs have something about this.
There isn't actually anything wrong in the bzr code related to this as far as I can tell.