break-lock should have a --yes, --force or --unconditional option
Bug #397315 reported by
Martin Pool
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Martin Pool |
Bug Description
Sometimes, eg when debugging locking, you know you really want to break a lock without being asked. There should be an option that will do it without asking.
There is some risk people will harm themselves using this if there really is still a live process.
As a workaround on unix you can say "yes|bzr break-lock blah"
See also bug 397298 for checking if the locker is still alive
Related branches
lp://staging/~mbp/bzr/397315-break-lock
- Vincent Ladeuil: Approve
-
Diff: 172 lines (+49/-25)5 files modifiedNEWS (+4/-0)
bzrlib/builtins.py (+7/-1)
bzrlib/lockdir.py (+8/-1)
bzrlib/tests/blackbox/test_break_lock.py (+14/-4)
bzrlib/tests/test_ui.py (+16/-19)
tags: | added: confirmation lockdir locking ui |
Changed in bzr: | |
milestone: | none → 2.3b2 |
status: | In Progress → Fix Released |
To post a comment you must log in.
This would be part of a solution for bug 257217, stale locks generated by killing the process.