bzr push from repository branch to location without shared repo creates weird sharedrepo+branch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
High
|
Unassigned |
Bug Description
I can reproduce this with both bzr 2.2 and bzr 2.3. The crucial point here is: using repository branch on local end and first push to the end where no shared repository exists. I can reproduce this with any transport: local, bzr:// bzr+ssh:// and sftp:// protocols.
Steps to reproduce:
C:\Temp\1>bzr --no-plugins init-repo repo
Shared repository with trees (format: 2a)
Location:
shared repository: repo
C:\Temp\1>bzr --no-plugins init repo/foo
Created a repository tree (format: 2a)
Using shared repository: C:/Temp/1/repo/
C:\Temp\1>bzr --no-plugins ci -m1 repo/foo --unchanged
Committing to: C:/Temp/1/repo/foo/
Committed revision 1.
C:\Temp\1>bzr --no-plugins push -d repo/foo foo
Created new branch.
C:\Temp\1>bzr --no-plugins info foo
Repository tree (format: 2a)
Location:
shared repository: foo
repository branch: foo
As you can see now I have repository tree with shared repository in the same directory. Why?
Changed in bzr: | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: check-for-breezy |