签入时出现 cvs 错误
添加新文件后尝试提交到 cvs 分支时出现此错误
Assertion failed: key != NULL, file hash.c, line 317
知道如何修复它以便我可以检查我的代码吗？
服务器和客户端都是Linux，并且涉及预提交。
When trying to commit to a cvs branch after adding a new file I get this error
Assertion failed: key != NULL, file hash.c, line 317
Any idea how to fix it so I can check my code in?
Both server and client are Linux and there are pre-commits involved.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
您是否在 Windows 上，是否将文件重命名为具有不同大小写的相同名称（例如 MAKEFILE、Makefile 与 makefile）？ CVS 曾经遇到过这个问题（也许现在仍然如此？）：
OSDir/mailarchive - 主题：回复：hash.c.312：findnode：
您可能还想阅读该线程中的其余消息。
Are you on Windows and did you rename a file to the same name with different case (e.g. MAKEFILE vs Makefile vs makefile)? CVS used to have a problem with this (and maybe still does?):
OSDir/mailarchive - Subject: Re: hash.c.312: findnode:
You might want to read the rest of the messages in the thread as well.
也许您的存储库上有某种预提交检查，请参阅 这里
Perhaps there is some kind of pre-commit check on your repository, see here
“阁楼”是 CVS 中删除的文件所在的位置。 在过去的某个时刻，有人签入了 newfile.v，但后来它被删除了，因此转移到了阁楼。
通过从存储库中删除 ,v 文件，您损坏了包含文件“newfile”的旧提交。 不要这样做。
正确的方法是恢复已删除的文件，然后用新文件替换其内容。
根据 http://www.cs.indiana.edu/~machrist/笔记/cvs.html
编辑回复评论以解释阁楼中的 ,v 文件的含义。
The "Attic" is the place where deleted files go in CVS. At some point in the past, someone checked in newfile.v, and at some later point it was deleted, hence moved to the Attic.
By deleting the ,v file from the repository you corrupted older commits that included the file "newfile". Do not do this.
The correct way is to restore the deleted file, then replace its content by the new file.
According to http://www.cs.indiana.edu/~machrist/notes/cvs.html
Edited in reply to comment to explain what the ,v file in the Attic means.
不确定问题是什么，但我通过进入服务器并删除存储库中的文件 Attic/newfile.v 并再次添加它来解决它。
Not sure what the issue was but I solved it by going onto the server and deleting the file Attic/newfile.v in the repository and adding it again.