bzr upgrade should choose a reasonable default format
Bug #252908 reported by
Martin Pool
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
Jelmer Vernooij | ||
Bug Description
As of bzr 1.5, there are some old formats (rich-root, subtree) that contain more information than the bzr default format and so cannot be upgraded to the current default format. With such a directory running just 'bzr upgrade' will give an error that the formats are incompatible.
I think upgrade should determine the best/newest recommended format that's compatible with the source.
This bug could also be avoided by making sure the current default format *does* support upgrades from every previous format. (But not really, as it's possible the user has a component created by a plugin, etc.)
Related branches
lp:~jelmer/bzr/upgrade-rr
(Merged)
| Changed in bzr: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
Revision history for this message
| Martin Pool (mbp) wrote | #1 |
| Changed in bzr: | |
| assignee: | nobody → jelmer |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
tags master upgrade
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkl
u6EAn0Vva3N2cqv
=rUDD
-----END PGP SIGNATURE-----