Skip Montanaro writes: > Try deleting /usr/lib/python2.0/newimp.py, then do a re-install. (Actually, > perhaps you should delete *.py in that directory and selectively delete > subdirectories as well.) I don't see newimp.py anywhere in the 2.0b1 tree. Something is really screwed up with CVS, or my understanding of it. Look at this transcript: buffalo:Lib$ pwd /usr/local/src/Python-CVS/python/dist/src/Lib buffalo:Lib$ rm newimp.py buffalo:Lib$ cvs status newimp.py =================================================================== File: no file newimp.py Status: Needs Checkout Working revision: 1.7 Repository revision: 1.7 /cvsroot/python/python/dist/src/Lib/Attic/newimp.py,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) buffalo:Lib$ cvs update -dAP cvs server: Updating . U newimp.py <rest of update output omitted> buffalo:Lib$ ls -l newimp.py -rwxr-xr-x 1 cgw g023 54767 Sep 6 12:50 newimp.py buffalo:Lib$ cvs status newimp.py =================================================================== File: newimp.py Status: Up-to-date Working revision: 1.7 Repository revision: 1.7 /cvsroot/python/python/dist/src/Lib/Attic/newimp.py,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) If I edit the CVS/Entries file and remove "newimp.py" from there, the problem goes away. But I work with many CVS repositories, and the Python repository at SourceForge is the only one that forces me to manually edit the Entries file. You're really not supposed to need to do that! I'm running CVS version 1.10.6. I think 1.10.6 is supposed to be a "good" version to use. What are other people using? Does everybody just go around editing CVS/Entries whenever files are removed from the repository? What am I doing wrong? I'm starting to get a little annoyed by the SourceForge CVS server. Is it just me?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4