branching over bzr+ssh does not propogate loom threads

Bug #193893 reported by Robert Collins on 2008-02-21
38
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Loom
Critical
Robert Collins

Bug Description

Loom threads are not correctly copied from bzr+ssh urls. Probably the class-conditional check for a LoomBranch is failing.

Changed in bzr-loom:
importance: Undecided → High
status: New → Triaged
Alexander Belchenko (bialix) wrote :

I'm not sure it's the same bug, but `bzr branch bzr://host/loom` also does not work correctly.

> I'm not sure it's the same bug, but `bzr branch bzr://host/loom` also
> does not work correctly.

Yes, that's the same bug. The remote object logic is the same regardless of the
medium the smart protocol is using.

Edwin Grubbs (edwin-grubbs) wrote :

This is probably the same error as when you branch after creating a loom but never run "bzr record" on the original loomified branch. Here is a simple script which tests the problem.

---------------------
#!/bin/bash

mkdir foo
cd foo
bzr init
touch bar
bzr add bar
bzr commit -m 'added bar'

bzr nick trunk
bzr loomify
echo "%%% The loom exists, sorta %%%"
bzr show-loom
# don't bzr record

cd ..
bzr branch foo foo2
cd foo2
echo "%%% The branched loom doesn't exist %%%"
bzr show-loom
bzr nick trunk2
echo "%%% The branch is in loom format but without a loom %%%"
bzr loomify

Changed in bzr-loom:
status: Triaged → Fix Released
importance: High → Critical
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.

Duplicates of this bug

Other bug subscribers