branch in the root of treeless shared repository ignores --no-trees option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned |
Bug Description
bzr 1.10.
C:\Temp\1>bzr init-repo . --no-trees
Shared repository (format: pack-0.92)
Location:
shared repository: .
C:\Temp\1>bzr init a
Repository branch (format: pack-0.92)
Location:
shared repository: .
repository branch: a
C:\Temp\1>bzr init .
Repository tree (format: pack-0.92)
Location:
shared repository: .
repository branch: .
Expected behavior: branch in the root of shared repository is also treeless. But in fact it's not:
C:\Temp\1>bzr info -v
Repository tree (format: pack-0.92)
Location:
shared repository: .
repository branch: .
Format:
control: Meta directory format 1
working tree: Working tree format 4
branch: Branch format 6
repository: Packs containing knits without subtree support
In the working tree:
0 unchanged
0 modified
0 added
0 removed
0 renamed
1 unknown
0 ignored
0 versioned subdirectories
Branch history:
0 revisions
0 committers
Repository:
0 revisions
tags: | added: check-for-breezy |
I have found a workaround for this bug which some people may find useful.
I would like to state first that I DO NOT KNOW KNOW NOTHING about bazaar's I am not a bazaar developer and DO NOT KNOW how bazaar's repositories/ branches work. So, like me, if you do this it is at your own risk!
You can manually remove the working copy like this: pc:~/bzrtest$ bzr init-repo project --no-trees pc:~/bzrtest$ bzr init project pc:~/bzrtest$ rm -rf project/ .bzr/checkout pc:~/bzrtest$ bzr info -v project
edam@tims-
Shared repository (format: pack-0.92)
Location:
shared repository: project
edam@tims-
Repository tree (format: pack-0.92)
Location:
shared repository: project
repository branch: project
edam@tims-
edam@tims-
Perhaps a bzr developer could comment on this workaround - is it safe/correct?