error about failure to take lock printed to smart server protocol socket

[Alexandre Garnier]

When there is a lock, I get this message :

bzr: ERROR: Received bad protocol version marker: "Unable to obtain lock chroot-46912585500240:///dev/.bzr/branch/lock\nheld by <email address hidden> on host server.lan [process #29153]\nlocked 57 seconds ago\nWill continue to try until 18:03:10, unless you press Ctrl-C\nIf you're sure that it's not being modified, use bzr break-lock chroot-46912585500240:///dev/.bzr/branch/lock\n"

Not really readable with \n ...

I have this on concurrent commit on a shared repository accessed with bzr:// by a lightweight checkout.

[Andrew Bennetts (spiv)]

Huh, that's weird. At a guess, the bzr:// server is launched via inetd (and thus run with the --inet option)? If so, then I suspect that the server is erroneously emitting that text to stderr, which is then being relayed over the TCP socket, and screwing up the proper communication of errors between client and server.

This may be a dupe of an existing bug report, this does sound familiar.

[Alexandre Garnier (zigarn)]

Yes, the server is launched via inetd.