bzr nick breaks loom

Bug #203203 reported by John A Meinel on 2008-03-17
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Loom
High
Robert Collins

Bug Description

I started trying to do some development in looms.

First step was to do "bzr loomify" but it told me I needed to give a nickname. So I gave "bzr nick feature".

I then wanted to create a thread which was "upstream" to keep a pristine copy of bzr.dev. However, 'create-thread' only creates a thread above your current one.

So what I wanted was to have the original thread be named "upstream" and my current thread be named "feature".

So my first attempt was to do:
 bzr nick alt-feature

However, after that point all bzr commands fail during the unlock() phase with a traceback similar to:
...
  File "/home/jameinel/dev/bzr/bzr.dev/bzrlib/config.py", line 942, in set_option
    self.branch.unlock()
  File "/home/jameinel/.bazaar/plugins/loom/branch.py", line 658, in unlock
    if dict(state.get_threads_dict())[self.nick][0] != lastrev:
KeyError: u'assert_list'

Is there a way to rename a thread? Since it seemed that the current thread was labeled based on branch nickname I thought "bzr nick" would be the command to use to change it.

Anyway, the only way to get the branch working again seemed to be to use "bzr nick original_name".
(I actually just edited branch.conf manually, but I think it would do the same thing.)

Related branches

Changed in bzr-loom:
importance: Undecided → High
status: New → Triaged
Tim Penhey (thumper) wrote :

I'd really like to be able to rename threads. Is there a way?

On Tue, 2008-06-24 at 00:56 +0000, Tim Penhey wrote:
> I'd really like to be able to rename threads. Is there a way?

Right now,
bzr switch thread
bzr create-thread newname
bzr switch thread
bzr combine-thread
bzr switch newname

-Rob

--
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Changed in bzr-loom:
status: Triaged → Fix Released
assignee: nobody → Robert Collins (lifeless)
milestone: none → 2.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers