[Fredrik Lundh] > > cvs add Objects\unicodetype_db.h > cvs server: scheduling file `Objects/unicodetype_db.h' for addition > cvs server: use 'cvs commit' to add this file permanently > > > cvs commit Objects\unicodetype_db.h > cvs server: [11:05:10] waiting for anoncvs_python's lock in > /cvsroot/python/python/dist/src/Objects > > yet another stale lock? if so, what happened? and more > importantly, how do I get rid of it? I expect this one goes away by itself -- anoncvs can't be doing a commit, and I don't believe we've ever seen a stale lock from anoncvs. Probably just some fan doing their first read-only checkout over a slow line. BTW, I just did a full update & didn't get any lock msgs. Try again!
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