Advice to "use bzr break-lock lp-NNNN:///..." is incorrect

Bug #255062 reported by seisen1
4
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
High
Unassigned
Launchpad itself
Triaged
Medium
Unassigned

Bug Description

 I continue to get this error:

Unable to obtain lock lp-147258124:///~seisen/5-a-day-data/main/.bzr/branch/lock
held by <email address hidden> on host vostok [process #16983]
locked 15 hours, 52 minutes ago
Will continue to try until 18:09:43, unless you press Ctrl-C
If you're sure that it's not being modified, use bzr break-lock lp-147258124:///~seisen/5-a-day-data/main/.bzr/branch/lock
bzr: ERROR: Could not acquire lock "(remote lock)"
bzr failed with error code 768

I have tried doing this: "bzr break-lock bzr+ssh:///~seisen/5-a-day-data/main/.bzr/branch/lock" and this "bzr break-lock sftp:///~seisen/5-a-day-data/main/.bzr/branch/lock" and both of these produce the same error which is this:

bzr: ERROR: Invalid url supplied to transport: "Host empty in: sftp:///~seisen/5-a-day-data/main/.bzr/branch/lock/"

Tags: lp-code
Revision history for this message
seisen1 (seisen-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Martin Albisetti (beuno) wrote :

We're giving out the wrong information in some cases for bzr+ssh.
jam pointed out this might happen, although I don't really know how to fix this.

Changed in bzr:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Andrew Bennetts (spiv) wrote :

The workaround is:

    bzr break-lock lp:~seisen/5-a-day-data/main

or:

    bzr break-lock bzr+ssh://<email address hidden>/~seisen/5-a-day-data/main

The cause is mainly that the bazaar.launchpad.net server sending an internal-only URL in the error it sends back to the client. Possibly bzr itself should be smarter about this, though. So for now let's mark the bug as open in both projects.

Revision history for this message
Jonathan Lange (jml) wrote :

The thing here is to always translate paths whenever we translate errors. I *think* this particular bug would face any and all smart servers, not just Launchpad.

Changed in launchpad-bazaar:
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.