checkout silently upgrades repo data
Bug #195971 reported by
Robert Collins
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
We have a interoperability issue between plain and subtree/rich-root
with checkout.
bzr init-repo --pack-0.92-subtree local
bzr init mainline
bzr checkout mainline local/tree
cd local/tree
bzr commit -m 'Error'
bzr checkout should not use the shared repository when the remote format
is not bidirectionally compatible.
affects bzr
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in bzr: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in bzr: | |
| status: | Triaged → Confirmed |
| tags: | added: format-infrastructure formats |
| tags: | added: check-for-breezy |
To post a comment you must log in.
Interestingly enough, going the other way (having source be rich-root and target be normal) fails at "checkout" time with incompatible rich-root information.
I can agree that 'bzr co' should probably recognize that it would be upgrading the data during the fetch, and try to do something different. I'm not 100% sure what the appropriate fix is. Probably just have it create a new standalone repository.