"Could not acquire lock" error doesn't tell you how to fix it

Bug #139202 reported by Matthew Paul Thomas on 2007-09-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Martin Albisetti

Bug Description

If you get a "Could not acquire lock" error, it's not obvious what to do next.

I suggest that instead of "bzr: ERROR: Could not acquire lock LockDir($URL)", the message say something like: "bzr: ERROR: This {branch|repository} is locked for modification. If you're sure that it's not being modified, use bzr break-lock $URL".

Martin Pool (mbp) wrote :

It should also invite you to press Ctrl-C to stop waiting...

Changed in bzr:
importance: Undecided → Medium
status: New → Triaged
Martin Albisetti (beuno) on 2008-05-21
Changed in bzr:
assignee: nobody → beuno
milestone: none → 1.6
status: Triaged → Fix Committed
Martin Albisetti (beuno) on 2008-05-21
Changed in bzr:
status: Fix Committed → Fix Released
Andrew Bennetts (spiv) wrote :

This bug was marked "Fix Released" a little prematurely, but Martin Albisetti's patch has now landed in bzr.dev r3467. It will should be part of the 1.6 release although it did miss 1.6beta1.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers