This is the expected behaviour (because of difficulties with handling conflicts): when pushing locally, the working tree will be updated.
when pushing remotely, the working tree will not be updated.
The push-and-update plugin will try to ssh in and do a `bzr update` for you when you do a push, but I don't think it works when committing to a checkout. And it requires ssh access to the server.
bug #325355 suggest that this should be possible when using the smart server, although I'm not sure how it would handle conflicts differently.
This is the expected behaviour (because of difficulties with handling conflicts): when pushing locally, the working tree will be updated.
when pushing remotely, the working tree will not be updated.
The push-and-update plugin will try to ssh in and do a `bzr update` for you when you do a push, but I don't think it works when committing to a checkout. And it requires ssh access to the server.
bug #325355 suggest that this should be possible when using the smart server, although I'm not sure how it would handle conflicts differently.