`bzr upgrade` in a lightweight checkout upgrades the parent branch
Bug #137976 reported by
Dato Simó
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
<dato> running `bzr upgrade` in a lightweight checkout makes a backup of
the light .bzr, not of the real .bzr. would that be considered a bug?
<lifeless> no, because its upgrading the lightweight checkout
<dato> but it changes the "remote" branch as well
<lifeless> ok thats a bug
<lifeless> it should only alter the lightweight checkout
<dato> okay, I'll double-check it does that, and file one
To reproduce:
% bzr init --<old format> branch
% bzr info branch | head -1
Standalone tree (format: <old format>)
% bzr checkout --lightweight branch checkout
% cd checkout && bzr upgrade
[...] finished
% cd ../branch && bzr info | head -1
Standalone tree (format: <current default>)
| Changed in bzr: | |
| status: | New → Confirmed |
| Changed in bzr: | |
| importance: | Undecided → Medium |
| description: | updated |
| tags: | added: upgrade |
| tags: | added: check-for-breezy |
Revision history for this message
| Jelmer Vernooij (jelmer) wrote | #1 |
| tags: | removed: check-for-breezy |
| Changed in bzr: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
This is already fixed:
This is a checkout. The branch (PATH) needs to be upgraded separately.
The bzrdir format Meta directory format 1 is already at the most recent format.