Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 77883 - cvs is ingoring case of filenames
cvs is ingoring case of filenames
Product: Red Hat Linux
Classification: Retired
Component: cvs (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Eido Inoue
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-11-14 14:17 EST by Scott Otterson
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-29 14:14:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Scott Otterson 2002-11-14 14:17:11 EST
In my repository, I have checked in two files with names: linmap.m and linMap.m
  I also have a directory checked out that contains only linMap.m

In this directory, if I type:

  cvs update

I see that most files are updated correctly.  But I also get this error message:

  cvs update: move away ./linmap.m; it is in the way
  C linmap.m

and the file linmap.m is not copied into the directory.  CVS is incorrectly
flagging the conflict because it's ignoring the filename case.
Comment 1 Scott Otterson 2002-11-14 14:39:59 EST
I should add that I'm using remote CVS over ssh to update the directory without
the copy of linmap.m.  Maybe this has somthing to do with ssh?
Comment 2 Scott Otterson 2002-11-14 14:54:25 EST
Actually, this probably is a ssh problem -- if I do scp to directly copy
linmap.m to the remote directory, linmap is still missing.  The remote directory
is on a VFAT32 partition.  The filenames are displayed with the correct case but
I wonder if ssh is ignoring it because it's using some old DOS interface.
Comment 3 jonathan 2003-01-01 14:53:57 EST
I suspect the real issue is that VFAT32 is not case-sensitive!  Microsoft
filesystems are not case-sensitive, in my experience at least.

Try the same setup on an ext2 or ext3 filesystem; I expect all will be well.

Comment 4 Eido Inoue 2004-10-29 14:14:56 EDT
works on case-sensitive filesystems

Note You need to log in before you can comment on or make changes to this bug.