feature or bug?

[Guo Tang]

Hi,

I am trying to convert a clearcase branch to hg.  The first
problem I had is the default hg storage method change upper case file
name to underscore lower case. I have some file names really long, then
after conversion, the file name length is over what allowed by OS. After 
digging a little bit, I finally found out the option

[format]
usestore=False

It seems solved my problem.  The clearcase to hg conversion went smoothly. 
But after conversion, "hg verify" found the repository is corrupted. I 
finally found out it is due to one file name in clearcase has changed 
case.

A simple example is:

md rename
cd rename
ls > text.txt
hg init
hg ci -A -m "nc"
del text.txt
ls > TEXT.TXT
hg ci -A -m "nc"
hg verify

Now I got

checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
 TEXT.TXT@?: rev 0 points to unexpected changeset 0
 (expected 1)
 TEXT.TXT@?: 37c8e05722d7 not in manifests
 TEXT.TXT@?: rev 2 points to unexpected changeset 1
** unknown exception encountered, details follow
** report bug details to http://www.selenic.com/mercurial/bts
** or mercurial at selenic.com
** Mercurial Distributed SCM (version 0.9.5)
Traceback (most recent call last):
  File "hg", line 14, in ?
  File "mercurial\dispatch.pyc", line 20, in run
  File "mercurial\dispatch.pyc", line 29, in dispatch
  File "mercurial\dispatch.pyc", line 45, in _runcatch
  File "mercurial\dispatch.pyc", line 348, in _dispatch
  File "mercurial\dispatch.pyc", line 401, in _runcommand
  File "mercurial\dispatch.pyc", line 357, in checkargs
  File "mercurial\dispatch.pyc", line 340, in <lambda>
  File "mercurial\commands.pyc", line 2737, in verify
  File "mercurial\hg.pyc", line 298, in verify
  File "mercurial\verify.pyc", line 15, in verify
  File "mercurial\verify.pyc", line 182, in _verify
IndexError: list index out of range

With usestore=True in mercurial.ini, I don't have the repository 
corruption problem. But it cannot really work for me due to OS file length 
limitaion.

Gentlemen, do we have plan to solve it? Or treat it as feature?

Thanks,