We have had a similar problem in Windows where MAIN.C becomes main.c, but is the same file to Windows because Windows is currently setup case-insensitive. Looking at the ideas above, it seems most ideas are platform specific. I would suggest that Bazaar more generically checks to see if the underlying file system is currently case sensitive and behaves accordingly. (If the repo had two files that would become the same, I guess you'd have to broadcast an error.)
We have had a similar problem in Windows where MAIN.C becomes main.c, but is the same file to Windows because Windows is currently setup case-insensitive. Looking at the ideas above, it seems most ideas are platform specific. I would suggest that Bazaar more generically checks to see if the underlying file system is currently case sensitive and behaves accordingly. (If the repo had two files that would become the same, I guess you'd have to broadcast an error.)