bzr init ignores format argument when creating branch inside of shared repository
Bug #274021 reported by
Jelmer Vernooij
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
bzr doesn't complain when specifying a format to "bzr branch" that is incompatible with the containing shared repository. E.g.:
bzr init-repo foo
bzr init --rich-root-pack foo/bar
will create a branch in foo/bar without rich root support.
bzr should either create a new repository in foo/bar or it should complain to the user.
Revision history for this message
| Alexander Belchenko (bialix) wrote | #1 |
| Changed in bzr: | |
| status: | New → Confirmed |
| tags: | added: check-for-breezy |
To post a comment you must log in.
Even worse that user has no ability to forcing creation of standalone branch in shred repo. Command `bzr branch` has flag --standalone that will prevent of using existing shared repository, but `bzr init` has not. I think this flag should be supported by `bzr init` too.