I was having a similar issue. I've fixed this a little bit further up in the chain in BranchConfig. Teaching it that it needs to unchroot the chroot URI.
then I need file:///bzr/srv/project1/trunk to be passed into LocationConfig to reproduce that URL in bzr-email.
The patch I'm proposing does this.
It might make sense for this work to happen in bzrlib.transport.chroot maybe in external_url however I don't think there is acess to the branch in there so you can't access the /project1/trunk bit
I was having a similar issue. I've fixed this a little bit further up in the chain in BranchConfig. Teaching it that it needs to unchroot the chroot URI.
Branch with fixes can be found at http:// bzr.inodes. org/bzr/ chroot_ location_ support/
Not quite sure if this is correct though. My use case is as follows.
* Running "bzr server"
* directory points at /bzr/srv which has multiple directorys which contain branches
* locations.conf has
[/bzr/srv] repo.com/ branch: policy = appendpath
public_branch = http://
public_
Say I'm pushing to bzr://repo. com/project1/ trunk
then I need file:// /bzr/srv/ project1/ trunk to be passed into LocationConfig to reproduce that URL in bzr-email.
The patch I'm proposing does this.
It might make sense for this work to happen in bzrlib. transport. chroot maybe in external_url however I don't think there is acess to the branch in there so you can't access the /project1/trunk bit