bzr reconfigure --standalone has no effect on lightweight checkouts

Bug #1005532 reported by Florian Rathgeber on 2012-05-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I have a co-located workspace (using bzr-colo, but I believe the bug is unrelated to the plugin) in /path/to/colo and a shared repository in /path/to

$ bzr --version
Bazaar (bzr) 2.5.0 (2.5.0-2ubuntu2 on Ubuntu 12.04 Precise)
  Python interpreter: /usr/bin/python 2.7.3
  Python standard library: /usr/lib/python2.7
  Platform: Linux-3.2.0-24-generic-x86_64-with-Ubuntu-12.04-precise
  bzrlib: /usr/lib/python2.7/dist-packages/bzrlib


$ bzr colo-checkout ../mybranch && cd ../mybranch

$ bzr info
Lightweight checkout (format: 2a)
  light checkout root: .
   checkout of branch: /path/to/colo/.bzr/branches/mybranch
    shared repository: /path/to

Related branches:
    push branch: bzr+ssh://
  parent branch: /path/to/colo

$ bzr reconfigure --standalone # no output == success

$ bzr info # as before

$ bzr reconfigure --standalone
bzr: ERROR: '/data/fr710/projects/fluidity/op2-state-interface/' is already standalone.

$ bzr reconfigure --use-shared # no output == success

$ bzr info # as before

Apparently bzr reconfigure successfully changes the flag from 'use shared' to 'standalone' and vice versa, but apart from the that bzr reconfigure seems to have no effect on lightweight checkouts. It also returns instantly, so it clearly doesn't copy any revisions into the local repository of the branch.

If it's intentionally not working (i.e. requires to first reconfigure to be a branch instead of a lightweight checkout), it should raise an error and not change the shared repository flag.

Jelmer Vernooij (jelmer) on 2012-05-28
affects: bzr → bzr-colo

Need to add to that: It did actually have a very nasty side-effect. It completely broke my co-located workspace: before those shenanigans the colocated branches would use the shared repository in .bzr/branches. After the failed reconfigure attempt, that shared repository has vanished. I'm not sure exactly which command caused that to happen. I'll attach the relevant bit from my ~/.bzr.log

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments