Please ignore my previous comment about it being fixed. I posted to the wrong bug tab.
Verification:
In a maverick chroot, I set
0.0.0.0 api.edge.launchpad.net xmlrpc.edge.launchpad.net
into /etc/hosts, and then tried 'bzr lp-propose' on a branch. With 2.2.0-1, I get invited to make an edge api token. With 2.2.4-0ubunt1 from maverick-proposed, my existing lpnet token is used, and it correctly reports
bzr: ERROR: There is already a branch merge proposal: https://code.launchpad.net/~mbp/bzr/progress/+merge/58627
So I conclude 2.2.4 is indeed correctly using lpnet not edge.
verified ok.
Please ignore my previous comment about it being fixed. I posted to the wrong bug tab.
Verification:
In a maverick chroot, I set
0.0.0.0 api.edge. launchpad. net xmlrpc. edge.launchpad. net
into /etc/hosts, and then tried 'bzr lp-propose' on a branch. With 2.2.0-1, I get invited to make an edge api token. With 2.2.4-0ubunt1 from maverick-proposed, my existing lpnet token is used, and it correctly reports
bzr: ERROR: There is already a branch merge proposal: https:/ /code.launchpad .net/~mbp/ bzr/progress/ +merge/ 58627
So I conclude 2.2.4 is indeed correctly using lpnet not edge.
verified ok.