advice to break-lock includes the ".bzr/branch/lock" path, but should not
Bug #273393 reported by
Robert Collins
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
| Breezy |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
the advice for break-lock talks about the physical lock not the branch
object:
Will continue to try until 10:32:44, unless you press Ctrl-C
If you're sure that it's not being modified, use bzr break-lock
sftp://
affects bzr
--
GPG key available at: <http://
Revision history for this message
| Kent Tenney (ktenney) wrote | #1 |
| summary: |
- bad break-lock advice + break-lock message includes the ".bzr/branch/lock" path, but should not |
| summary: |
- break-lock message includes the ".bzr/branch/lock" path, but should not + advice to break-lock includes the ".bzr/branch/lock" path, but should + not |
| Changed in bzr: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| tags: | added: lock lockdir locking |
| tags: | added: ui |
| tags: | added: check-for-breezy |
| Changed in brz: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | removed: check-for-breezy |
To post a comment you must log in.
I just got this error message:
Unable to obtain lock lp-140342092:
held by <email address hidden> on host vostok [process #14126]
locked 8 hours, 7 minutes ago
Will continue to try until 11:43:31, unless you press Ctrl-C
If you're sure that it's not being modified, use
bzr break-lock lp-140342092:
I was able to break the lock after removing -140... from the URI