[BUG] full local path to bundle don't accepted in merge/pull commands

[Alexander Belchenko]

I discover this strange behaviour when I write my gzipped_bundle plugin. 
Problem appears only when I give full path to bundle file. See 
reproduction log below:

----------------------------------------------------
E:\Bazaar-NG\__test>bzr init a

E:\Bazaar-NG\__test>cd a

E:\Bazaar-NG\__test\a>echo spam  1>spam

E:\Bazaar-NG\__test\a>bzr add
added spam

E:\Bazaar-NG\__test\a>bzr commit -m initial
added spam
Committed revision 1.

E:\Bazaar-NG\__test\a>cd ..

E:\Bazaar-NG\__test>bzr branch a b
1 revision(s).

E:\Bazaar-NG\__test>cd b

E:\Bazaar-NG\__test\b>echo foo  1>spam

E:\Bazaar-NG\__test\b>bzr status
modified:
   spam

E:\Bazaar-NG\__test\b>bzr commit -m second
modified spam
Committed revision 2.

E:\Bazaar-NG\__test\b>bzr bundle --output=b.patch
Using saved location: E:/Bazaar-NG/__test/a/

E:\Bazaar-NG\__test\b>cd ..

E:\Bazaar-NG\__test>cd a

E:\Bazaar-NG\__test\a>bzr merge ../b
All changes applied successfully.

E:\Bazaar-NG\__test\a>bzr status
modified:
   spam
pending merges:
   Alexander Belchenko 2006-07-29 second

E:\Bazaar-NG\__test\a>bzr revert

E:\Bazaar-NG\__test\a>bzr merge ../b/b.patch
All changes applied successfully.

E:\Bazaar-NG\__test\a>bzr status
modified:
   spam
pending merges:
   Alexander Belchenko 2006-07-29 second

E:\Bazaar-NG\__test\a>bzr revert

E:\Bazaar-NG\__test\a>bzr merge E:\Bazaar-NG\__test\b\b.patch
bzr: ERROR: b.patch is not a source file in any tree.

E:\Bazaar-NG\__test\a>bzr status

E:\Bazaar-NG\__test\a>bzr revert

E:\Bazaar-NG\__test\a>bzr pull ../b/b.patch
All changes applied successfully.
1 revision(s) pulled.

E:\Bazaar-NG\__test\a>bzr status

E:\Bazaar-NG\__test\a>bzr revno
2

E:\Bazaar-NG\__test\a>bzr uncommit --force
     2 Alexander Belchenko	2006-07-29
       second

The above revision(s) will be removed.

E:\Bazaar-NG\__test\a>bzr pull E:\Bazaar-NG\__test\b\b.patch
bzr: ERROR: Not a branch: E:/Bazaar-NG/__test/b/b.patch/
-----------------------------------------------------------------

I hope it's not win32-specific.

--
Alexander