Should suggest upgrading when remote smart branch is incompatible
Bug #124980 reported by
Jelmer Vernooij
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Low
|
Unassigned | ||
| Breezy |
Triaged
|
Low
|
Unassigned | ||
Bug Description
affects /products/bzr
importance low
Trying to check out a remote smart server branch that uses rich root
revisions into a local repository that doesn't gives an unhelpful error:
bzr: ERROR: Repository KnitRepository(
is not compatible with repository <bzrlib.
at 0xb6b2e10c>
Bazaar should mention that upgrading to dirstate-
| Changed in bzr: | |
| assignee: | nobody → jelmer |
| status: | New → Confirmed |
| assignee: | jelmer → nobody |
Revision history for this message
| Larry Gilbert (l2g) wrote | #1 |
| tags: | added: formats ui |
| tags: | added: check-for-breezy |
| tags: |
added: upgrade removed: check-for-breezy |
| Changed in brz: | |
| status: | New → Incomplete |
| status: | Incomplete → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
This is crucial in cases like this: the local user has a checkout of the remote, then the remote changes its repo format, leaving the user with a cryptic error the next time a pull is attempted. I was bitten by this when the repo for Bazaar itself changed its format. As I write this, I'm still in the middle of a trial-and-error process trying to figure out the right way to upgrade my local repo.