Robert Collins пишет:
> On Wed, 2009-09-30 at 08:49 +0000, Alexander Belchenko wrote:
>> Robert Collins пишет:
>>> (working is a branch of 2.0)
>> Does it mean 2.0.1?
>
> I'd be surprised if its not fixed in 2.0.0, I thought I fixed it around
> 1.18 time frame. What do you see when you try - can you post a
> transcript like I just did?
OK, It works for local branches BUT does not work for bzr:// protocol
when server is down.
Local case:
C:\Temp\1>bzr init master
Created a standalone tree (format: pack-0.92)
C:\Temp\1>bzr ci -m1 master --unchanged
Committing to: C:/Temp/1/master/
Committed revision 1.
C:\Temp\1>bzr get master copy
Branched 1 revision(s).
C:\Temp\1>bzr co --light master checkout
C:\Temp\1>ren master master-renamed
C:\Temp\1\checkout>bzr switch ../copy
bzr: ERROR: Not a branch: "C:/Temp/1/master/".
C:\Temp\1\checkout>bzr switch ../copy --force
Tree is up to date at revision 1.
Switched to branch: C:/Temp/1/copy/
With bzr:// server:
C:\Temp\1>bzr init master
Created a standalone tree (format: pack-0.92)
C:\Temp\1>bzr ci -m1 master --unchanged
Committing to: C:/Temp/1/master/
Committed revision 1.
C:\Temp\1>bzr get master copy
Branched 1 revision(s).
Robert Collins пишет:
> On Wed, 2009-09-30 at 08:49 +0000, Alexander Belchenko wrote:
>> Robert Collins пишет:
>>> (working is a branch of 2.0)
>> Does it mean 2.0.1?
>
> I'd be surprised if its not fixed in 2.0.0, I thought I fixed it around
> 1.18 time frame. What do you see when you try - can you post a
> transcript like I just did?
OK, It works for local branches BUT does not work for bzr:// protocol
when server is down.
Local case:
C:\Temp\1>bzr init master
Created a standalone tree (format: pack-0.92)
C:\Temp\1>bzr ci -m1 master --unchanged
Committing to: C:/Temp/1/master/
Committed revision 1.
C:\Temp\1>bzr get master copy
Branched 1 revision(s).
C:\Temp\1>bzr co --light master checkout
C:\Temp\1>ren master master-renamed
C:\Temp\ 1\checkout> bzr switch ../copy 1/master/ ".
bzr: ERROR: Not a branch: "C:/Temp/
C:\Temp\ 1\checkout> bzr switch ../copy --force
Tree is up to date at revision 1.
Switched to branch: C:/Temp/1/copy/
With bzr:// server:
C:\Temp\1>bzr init master
Created a standalone tree (format: pack-0.92)
C:\Temp\1>bzr ci -m1 master --unchanged
Committing to: C:/Temp/1/master/
Committed revision 1.
C:\Temp\1>bzr get master copy
Branched 1 revision(s).
C:\Temp\1>start bzr server --allow-writes --dir=.
# server started, check the available branches
C:\Temp\1>bzr branches bzr://localhost/
copy
master
C:\Temp\1>bzr co --light bzr://localhost /master checkout
# halt bzr server
C:\Temp\1>bzr branches bzr://localhost/
bzr: ERROR: Connection error: failed to connect to localhost:4155:
Connection refused
C:\Temp\ 1\checkout> bzr switch ../copy --force
bzr: ERROR: Connection error: failed to connect to localhost:4155:
Connection refused
C:\Temp\ 1\checkout> bzr switch C:\Temp\1\copy\ --force
bzr: ERROR: Connection error: failed to connect to localhost:4155:
Connection refused