Comment 16 for bug 113823

I seem to have encountered this bug, except this time with plain text files.

I've attached a folder containing several files which consistently trigger the bug if I initialize the repository in default (2a), 1.14 or 1.14-rich root. Note that it does *NOT* occur if I create a pack-092 repository.

I'm running under Windows 7, using TortoiseBZR 0.58 and Bazaar 2.2.1.

To reproduce:
Delete .bzr tree, initialize Libs folder in 2a repository format, add everything, commit, explore

Expected behaviour:
The working tree should be up to date in Revision 1

Observed behaviour:
Working tree differs from Revision 1

An example unidiff:

=== modified file AceAddon-3.0/AceAddon-3.0.lua
--- AceAddon-3.0/AceAddon-3.0.lua 2010-10-25 14:28:46 +0000
+++ AceAddon-3.0/AceAddon-3.0.lua 2010-08-16 07:52:50 +0000

Looking at the file in question, the creation date is 25/10/2010 10:22 PM, and the modified date is 16/8/2010 3:52 PM. However, another file in the same subfolder has the exact same timestamps, and is *not* being shown as modified.

On closing the explore/unidiff, I get a "bzr: ERROR: [Errno 9] Bad file descriptor" pop up.

Does any of this ring bells?