Q: Use rebase to get around corrupted knit file?

[Kevin Cole]

Marius Kruger <amanic <at> gmail.com> writes:

> 
> 
> 2008/12/5 Kevin Cole <dc.loco <at> gmail.com>
> 
> 
> ...
> Experiments with rebase so far have failed me.  How do I eliminate the first
> two revisions so that it starts with revision 3, where the log comment is that
> I got rid of the python library reference files?
> 
> 
> this looks similar to https://answers.edge.launchpad.net/bzr/+question/53349

It did, indeed. Thanks.  However, now I get:

| usr/lib/python2.5/site-packages/bzrlib/lockable_files.py:110: \
|  UserWarning: file group LockableFiles(<bzrlib.transport.local.LocalTransport 
\
|  url=file:///home/kjcole/rebuild/source/.bzr/repository/>) was not \
|  explicitly unlocked
|    warn("file group %r was not explicitly unlocked" % self)

What appeared to be the likely cure, "bzr break-lock" on the original didn't 
get me anywhere.

P.S. This is bzr 1.3.1 (I copied the entire broken repository from a 0.8.2 
system.)