branching over bzr+ssh does not propogate loom threads

Bug #193893 reported by Robert Collins
38
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Loom
Fix Released
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
Revision history for this message
Alexander Belchenko (bialix) wrote :

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

Revision history for this message
Andrew Bennetts (spiv) wrote : Re: [Bug 193893] Re: branching over bzr+ssh does not propogate loom threads

> 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.

Revision history for this message
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  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.