Comment 1 for bug 144627

We're trying to unlock the remote repository, but the smart server medium is still in use by the interrupted operation.

I can see two options:
 * unlock should drain out the medium, discarding the current response, before sending its unlock request
 * delegate responsibility for releasing the lock to the server, when the medium is dropped -- but in general we have said we will allow clients to hold locks across connections.