Mercurial, can't clone on Windows 7, “abort: No usable temporary filename found”

冷暖自知 提交于 2019-12-11 04:35:30

问题


I'm trying to clone a repo and it's failing on Windows 7. Looks like this:

C:\nodropwork>hg clone repoalias examplerepo
requesting all changes
adding changesets
adding manifests
adding file changes
added 1244 changesets with 9087 changes to 4816 files (+2 heads)
updating to branch default
abort: No usable temporary filename found
C:\nodropwork>cd examplerepo
C:\nodropwork\examplerepo>hg up
abort: No usable temporary filename found

The filesystem then contains the first few directories of source (the first 3, out of about 10 total).

When I try this on WinXP, the clone works, although I get an error message on a particular file:

updating to branch default
[partial xml console output removed]
abort: The system cannot find the file specified:
C:\nodropwork\examplerepo\collateral/con.xml

When the guy who owns the repo does a test clone on his Ubuntu system, it works fine with no errors or warnings at all.

Googling on "No usable temporary filename found" I see Mercurial source with functions like rename() and unlink(), notably in windows.py. Not sure what to do with this info though.

I'm guessing that there is something in the repo that WinXP tolerate but Win 7 chokes on. We tried removing con.xml from the repo and this didn't fix. About to give up and use WinXP.

Has anyone seen this before? Know a fix? Clever idea for troubleshooting?


回答1:


This is resolved, the problem was the "con.xml" file in the repo (apparently it was still hiding somewhere even though we thought we removed).

You can't name a file "con"-anything on Windows, "con" is a forbidden name.

We renamed the con.xml file and the repo clones and updates correctly on Win 7 now.



来源:https://stackoverflow.com/questions/5543294/mercurial-cant-clone-on-windows-7-abort-no-usable-temporary-filename-found

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!