On Mon, 2004-02-23 at 17:19, John F Meinel Jr wrote:
Well, I asked earlier, and I was able to break a lock. However, now
neither tla lock-revision -u or -b work. There is no revision lock that
I can tell, (there is nothing in the directory), and it just complains
that it can't rename the file.
Ahh! From Tom's post <address@hidden>:
So what exactly _is_ the lock directory supposed to look like now?
From your response I gather that something is obviously wrong ...
Just two directories and nothing else:
++revision-lock/
++revision-lock/+contents
You left files in +contents which is an "illegal lock state" -- I'm
not too happy that that state led to the confusing error message you
saw but, absent hand-munging of the archive, it's not a case that
should ever occur.
Does that (++revision-lock/+contents) accurately describe what you're
seeing?