<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 --dirstate branch
% bzr info branch | head -1
Standalone tree (format: dirstate)
From #bzr:
<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 --dirstate branch
% bzr info branch | head -1
Standalone tree (format: dirstate)
% bzr checkout --lightweight branch checkout
% cd checkout && bzr upgrade
[...] finished
% cd ../branch && bzr info | head -1
Standalone tree (format: dirstate-tags)
affects /products/bzr