We should definitely give a better error message in case "bzr commit" is used in a checkout where the user doesn't have write access to the master. The current one depends on the underlying transport and leaks internals.
I think it makes sense to mention "bzr unbind" but it's not necessarily the right command to use. It would be relevant if the user didn't really want a checkout but rather a clone of the remote branch.
Another possibility is that they want to commit to the writable version of the remote branch, e.g. by switching from a http:// URL to a bzr+ssh:// URL. Or perhaps they just want to do a local commit for the moment (--local).
We should definitely give a better error message in case "bzr commit" is used in a checkout where the user doesn't have write access to the master. The current one depends on the underlying transport and leaks internals.
I think it makes sense to mention "bzr unbind" but it's not necessarily the right command to use. It would be relevant if the user didn't really want a checkout but rather a clone of the remote branch.
Another possibility is that they want to commit to the writable version of the remote branch, e.g. by switching from a http:// URL to a bzr+ssh:// URL. Or perhaps they just want to do a local commit for the moment (--local).