Re: hash.c.312: findnode:

[Pierre Asselin]

In <mailman.878.1043352785.21513.bug-cvs@gnu.org> "Manu" <manubee@wanadoo.fr> 
writes:

>Larry Jones wrote:
>>Pierre Asselin writes:
>>> 
>>> Or he could rename the ,v file in the repository and check out a new
>>> working copy, couldn't he?
>> 
>> Yes, that works too, and is probably the better solution.

>Unfortunately, I don't have a shell access to my SF repository.
>I requested the SourceForge.net team to remove the files for me.
>The three "makefile" from lib, src, winui/src were manually removed.

>[ ... ]
>I can still "cvs add lib/Makefile src/Makefile",
>but "cvs commit" gives:

>cvs: hash.c:312: findnode: Assertion `key != ((void *)0)' failed.
>cvs [server aborted]: received abort signal

>"cvs update" gives:
>nothing known about lib/Makefile
>nothing know about src/Makefile

>Seems that cvs corrupted my repository,

Or your working copy.  Try editing the CVS/Entries file manually in
Notepad or Wordpad.  Do the entries have the correct case?

If you're worried about your repository state, check out a new sandbox
somewhere else, you'll see (indirectly) what files are in the repository
and what case they have.  Do a "cvs update -r1.1" if necessary to retrieve
any files in the Attic.


>[ ... ]
>IMO, this is a serious issue.

Yes, but what to do about it?  It's an OS issue as much as anything else.
Maybe the Windows clients could be bullet-proofed to detect the problem
and work around it, I don't know.  The clients certainly control the
case of the strings they send to the server, and I think they can ask
the server what it has in its repository.

I don't really understand the problem since I'm not a Windows programmer
and I don't know the API or semantics of the filesystem interface.