I've just run into the same bug. The workaround was to add the following line to the bzr service description in /etc/xinet.d/bzr:
env = HOME=/srv/bzr
I've just run into the same bug. The workaround was to add the following line to the bzr service description in /etc/xinet.d/bzr:
env = HOME=/srv/bzr