bzr incorrectly identifies file as modified (ntfs-3g)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
New
|
Undecided
|
Unassigned |
Bug Description
I'm running Ubuntu 11.10 64-bit. I have a personal repository which has two check-outs: one one my windows machine and one on this Ubuntu desktop. On Ubuntu, the bzr repository is located on a ntfs-3g mount.
Now I noticed the following behaviour:
1. I update a file on my windows machine and commit to the repository
2. I update my bzr check-out on the Ubuntu desktop
3. Now, I commit on the Ubuntu side (No changes made by me). bzr scans the hard disc for changes and comes up with all the files which were updated in step 2. However, I did not change the files, so those files are incorrectly identified as updated and are unnecessarily committed.
What could cause this behavior?
I'm running:
$ apt-cache policy bzr
bzr:
Installed: 2.5.0~beta2-
$ apt-cache policy ntfs-3g
ntfs-3g:
Installed: 1:2011.
On 12/15/2011 09:45 PM, Ernst wrote:
> Public bug reported:
>
> I'm running Ubuntu 11.10 64-bit. I have a personal repository which has
> two check-outs: one one my windows machine and one on this Ubuntu
> desktop. On Ubuntu, the bzr repository is located on a ntfs-3g mount.
>
> Now I noticed the following behaviour:
>
> 1. I update a file on my windows machine and commit to the repository
> 2. I update my bzr check-out on the Ubuntu desktop
> 3. Now, I commit on the Ubuntu side (No changes made by me). bzr scans
the hard disc for changes and comes up with all the files which were
updated in step 2. However, I did not change the files, so those files
are incorrectly identified as updated and are unnecessarily committed.
>
> What could cause this behavior?
>
Does "bzr status" report the files as changed?
Does "bzr diff" report any changes?
Cheers,
Jelmer