Re: Major rename bug occurring in bk-3.2.3

Rick Smith wrote:

> Can you give me an example of what used to work that is not working now?
> 
> For example, have you seen a rename handled automatically in a version
> prior to 3.2.3?

I _knew_ you were going to ask me for that.

Off the top of my head, I cannot say with absolute certainty that I have 
seen a "rename" handled properly before. I'm 95% sure I have, but I 
can't come up with a suitable example quickly.

However, in this specific case, the patch did not contain a rename, it 
contained a complete file removal (which apparently is handled using a 
similar code path during "bk import"). I _know_ I have imported patches 
containing file removals before, and have never had this issue, and the 
repos have always ended up containing the correct contents. If I still 
had a machine running bk-3.0.2 (which was what I was using prior to 
moving to bk-3.2.3) I'd try to reproduce it.

I do know that I have never had bk bring up this error trying to run 
renametool before, and I know that it has never left incomplete imports 
into a repo due to this problem. After this failed import, I tried to 
"bk rm" the file that the patch wanted to remove, and bk complained that 
the .del file was "locked but not writable". That repo is still in that 
condition, as best I can tell, and I can most likely provide you the 
before-import repo and the patch, if you want to try it yourself. Email 
me off-list if you would like them (actually I can just give you the 
instructions to regenerate them from their original sources on the net).
_______________________________________________
Bitkeeper-users mailing list
[email protected]
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.